You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How can a VC and an NFT express resource rights together?
Separate a verifiable claim, ownership state and service authorization.
In ArcBlock’s resource-rights design, a DID identifies a participant or resource, a VC carries an issuer’s claim about rights, and an NFT connects that claim with trackable ownership state. The service decides what the evidence permits.
A software entitlement might describe allowed use and a validity period. Verification needs the claim’s source, current state and requested operation, not just the object’s displayed name.
This is not a definition of every NFT. Historical ArcBlock Chain documentation distinguishes issuer, owner and transferrable fields; transfer is not universal. Presentation, transfer, consumption and service authorization are separate operations.
Likewise, a credential’s subject, its holder and an NFT’s owner can have different roles, even when each is identified with a DID.
Sources and further reading
Check your understanding
Is every NFT automatically a VC that grants resource access?
No. This is an ArcBlock design; credential representation and authorization need specific implementations.