Table 2.
Role responsibilities and trust assumptions.
| Role | Duty | Trust Assumptions |
|---|---|---|
| Creator | Generate digital artwork metadata to initiate the initial signature process. | Assume a trusted entity, but use authentication (such as a digital certificate) to prevent identity forgery. |
| Validators | Participate in distributed key generation (DKG); validate and sign transactions or usage records. | The nodes may be partially Byzantine (malicious), but the total number does not exceed the threshold t − 1 |
| Platform Auditor | Review the legitimacy of metadata (e.g., copyright ownership, content compliance) and participate in multi-party signatures. | It needs to be elected through an on-chain governance mechanism, assuming that its behavior is subject to economic staking (such as staking). |
| Buyers or consumers | Buy or use digital artwork, verify historical signatures, and initiate transaction signatures. | It is possible that a rational attacker (attempting to tamper with ownership) relies on cryptography to constrain its behavior. |
| Auditors | Independently verify PROV chain integrity and detect anomalous behavior. | There is no need to hold a key, only need to read the on-chain data, assuming that it has compliance review capabilities. |