Re: DID Method requirements (revocability)

With BTCR, the resolver always can construct a DID document. But it must
check to see if the “tip” bitcoin address has been spent — if it has, the
DID document has been revoked (or rotated) as of the date of the address
being spent. The tip transaction can contain no information (default
revoke), revocation information (revoke with details why), or link to
updated DID document (rotation).

It never gets ‘nil’ and I’m not sure that is the best way for other methods
to work. What about DoS?

— Christopher Allen