did:cow, a proposal for an ID resolution method with most of the convenience of did:plc/did:web and the robustness of a public blockchain
3
fork

Configure Feed

Select the types of activity you want to include in your feed.

words

+10 -6
+10 -6
README.md
··· 128 128 129 129 ### 7.2 Wrapped DID Dependence 130 130 131 - The did:cow address inherits all security properties of wrapped DID. 132 - - did:web → DNS hijacking risk 133 - - did:key → no rotation ability 134 - - did:plc → key compromise, risk of abuse by the trusted central server 131 + The did:cow address inherits the security risks of the wrapped DID: 132 + - did:web: DNS hijacking risk 133 + - did:key: no rotation ability 134 + - did:plc: key compromise, risk of abuse by the trusted central server 135 135 136 136 However, since users can switch to another wrapped DID they can recover from a compromise of the wrapped DID, and also exit in circumstances where the wrapped DID appears likely to become unreliable in future. 137 137 ··· 139 139 140 140 **Why Ethereum:** 141 141 142 - Ethereum offers high security, an established ecosystem and well-supported tooling for multisig and organizational control. 142 + Ethereum offers high security, an established ecosystem and well-supported tooling for multisig and organizational control. It also operates without needing proof-of-work, which many users dislike for its environmental impact. 143 143 144 - Strong social consensus on anti-censorship means we can be confident that the main Ethereum chain, or failing that a viable fork of the Ethereum chain, will continue accepting updates without censorship for the foreseeable future. 144 + Strong social consensus on anti-censorship means we can reasonably confident that the main Ethereum chain will continue accepting updates without censorship for the foreseeable future. We can also be highly confident that in the event that the dominant Ethereum chain lost this property, there would be a well-supported fork preserving its history that continued to have it. 145 145 146 146 **Trade-offs:** 147 147 148 148 *Time until finality:* Updates typically take up to 12 seconds to confirm, and longer to finalize. 149 149 150 150 *Cost*: A system requiring consensus will typically have capacity limits. Systems aiming for censorship resistance cannot exercise discretion about which transactions are worthwhile, so they typically regulate usage by charging fees. Usage is unpredictable, so costs are also unpredictable: Although Ethereum gas prices are currently low, they may increase if usage grows faster than capacity, and may also be subject to sudden spikes. DID:Cow updates cost 40,000 to 100,000 gas per update depending on DID length and whether the account has already been registered on-chain. This is roughly equivalent to the cost of a transferring a token. 151 + 152 + **Why only one chain:** 153 + 154 + Some identity standards support multiple chains, for example by putting a Chain ID in the identifier. DID:Cow supports only a single chain, to avoid the additional complexity, the longer identifiers, and the requirement for resolvers to handle multiple RPC endpoints. 151 155 152 156 ## 8. Privacy Considerations 153 157