Ethereum registry for ERC-1056 ethr did methods
Ethereum registry for ERC-1056 ethr did methods
This library contains the Ethereum contract code that allows the owner of an ethr-did identity to update the attributes that appear in its did-document. It exposes an API that allows developers to call the contract functions using Javascript.
Use this if you want to interact directly with a deployed registry contract directly, or deploy a copy of the contract to another Ethereum network.
A DID is an Identifier that allows you to lookup a DID document that can be used to authenticate you and messages created by you.
It's designed for resolving public keys for off-chain authentication—where the public key resolution is handled by using decentralized technology.
This contract allows Ethereum addresses to present signing information about themselves with no prior registration. It allows them to perform key rotation and specify different keys and services that are used on its behalf for both on and off-chain usage.
WARNING Most of these are deployments of version 0.0.3 of the contract and they do not include recent updates. Join the discussion as to how to adopt these new changes on our discord
| Network Name | name | chainId | hexChainId | Registry Address | Registry version |
|---|---|---|---|---|---|
| Mainnet | mainnet | 1 | 0x1 | 0xdca7...f21b | 4278342e |
| 3 | 0x3 | 0xdca7...f21b | 4278342e | ||
| 4 | 0x4 | 0xdca7...f21b | 4278342e | ||
| 5 | 0x5 | 0xdca7...f21b | 4278342e | ||
| 42 | 0x2a | 0xdca7...f21b | 4278342e | ||
| RSK | rsk | 30 | 0x1e | 0xdca7...f21b | 4278342e |
| RSK Testnet | rsk:test | 31 | 0x1f | 0xdca7...f21b | 4278342e |
| EnergyWeb | ewc | 246 | 0xf6 | 0xe296...bce4 | c9063836 |
| EWC Volta | volta | 73799 | 0x12047 | 0xc15d...c4af | f4e17ee1 |
| 246785 | 0x3c401 | 0xdca7...f21b | 4278342e | ||
| 246529 | 0x3c301 | 0xdca7...f21b | 4278342e | ||
| Polygon | polygon | 137 | 0x89 | 0xdca7...f21b | 4278342e |
| 80001 | 0x13881 | 0xdca7...f21b | 4278342e | ||
| Aurora | aurora | 1313161554 | 0x4e454152 | 0x63ed...98e0 | 0ab4f151 |
| 421613 | 0x66eed | 0x8FFf...517E | af1c2db | ||
| 59140 | 0xe704 | 0x03d5...3818 | af1c2db | ||
| Sepolia | sepolia | 11155111 | 0xaa36a7 | 0x03d5...3818 | af1c2db |
| Cardona | cardona | 2442 | 0x98a | 0x03d5...3818 | 0ab4f151 |
| Holešky | holesky | 17000 | 0x4268 | 0x03d5...3818 | 0ab4f151 |
| Gnosis Chain | gno | 100 | 0x64 | 0x03d5...3818 | 0ab4f151 |
The DID Registry can be used from JavaScript as well as directly from other contracts.
To use the contract, we provide hardhat artifacts. Once you require the ethr-did-registry module, you will get an
object containing the JSON.
const {EthereumDIDRegistry} = require('ethr-did-registry')You can use ethers.js to utilize these artifacts.
const {ethers} = require('ethers')
const DidReg = new ethers.Contract(registryAddress, EthereumDIDRegistry.abi)
DidReg.connect(yourSignerOrProvider)For on-chain interactions Ethereum has a built-in account abstraction that can be used regardless of whether the account
is a smart contract or a key pair. Any transaction has a msg.sender as the verified sender of the transaction.
Since each Ethereum transaction must be funded, there is a growing trend of on-chain transactions that are authenticated via an externally created signature and not by the actual transaction originator. This allows for 3rd party funding services, or for receivers to pay without any fundamental changes to the underlying Ethereum architecture.
These kinds of transactions have to be signed by an actual key pair and thus cannot be used to represent smart contract based Ethereum accounts.
We propose a way of a smart contract or regular key pair delegating signing for various purposes to externally managed key pairs. This allows a smart contract to be represented, both on-chain as well as off-chain or in payment channels through temporary or permanent delegates.
Any Ethereum account regardless of whether it's a key pair or smart contract based is considered to be an account identifier.
An identity needs no registration.
Each identity has a single address which maintains ultimate control over it. By default, each identity is controlled by itself. As ongoing technological and security improvements occur, an owner can replace themselves with any other Ethereum address, such as an advanced multi-signature contract.
There is only ever a single identity owner. More advanced ownership models are managed through a multi-signature contract.
Ownership of identity is verified by calling the identityOwner(address identity) public view returns(address)
function. This returns the address of the current Identity Owner.
The account owner can replace themselves at any time, by calling the changeOwner(address identity, address newOwner)
function.
There is also a version of this function which is called with an externally created signature, that is passed to a transaction funding service.
The externally signed version has the following
signature changeOwnerSigned(address identity, uint8 sigV, bytes32 sigR, bytes32 sigS, address newOwner).
The signature should be signed of the keccak256 hash of the following tightly packed parameters:
byte(0x19), byte(0), address of registry, nonce[currentOwner], identity, "changeOwner", newOwner
Delegates are addresses that are delegated for a specific time to perform a function on behalf of an identity.
They can be accessed both on and off-chain.
The type of function is simply a string, that is determined by a protocol or application higher up.
Examples:
Delegates expire. The expiration time is application specific and dependent on the security requirements of the identity owner.
Validity is set using the number of seconds from the time that adding the delegate is set.
You can check to see if an address is a delegate for an identity using
thevalidDelegate(address identity, bytes32 delegateType, address delegate) returns(bool) function. This returns true
if the address is a valid delegate of the given delegate
No open issues yet, or sync has not completed.