ERC-884 DGCL-compliant stock token (DGCL Token)
Stagnant · Tokens · created 2018-02-14
A standard for creating ERC-20-based stock tokens that can only be traded between identity-verified addresses, in compliance with Delaware corporate law.
Why it is needed
Existing ERC-20 tokens are designed so that anyone can freely send and receive them, and they do not support the identity verification (KYC/AML) or shareholder registry management required by Delaware corporate law. To distribute company-issued stock as tokens, the law requires verifying shareholders' names and addresses, being able to pull a shareholder list at any time, and having a way to reissue the shares of a shareholder who lost their wallet key to a new address. Standard ERC-20 has none of these mechanisms, so even after the law opened the door to issuing stock on the blockchain, there was no standard for creating a token that actually complies with the law. ERC-884 fills this gap by adding a list of identity-verified addresses, a shareholder registry, and lost-share reissuance functionality on top of ERC-20.
What to implement
event VerifiedAddressRemoved(address indexed addr, address indexed sender);: Fired when an identity-verified address is removed from the contract.function addVerified(address addr, bytes32 hash) public;: Registers an address that has completed identity verification, along with its identity hash, in the contract.function removeVerified(address addr) public;: Removes an identity-verified address from the registry list. Addresses that hold tokens cannot be removed.function updateVerified(address addr, bytes32 hash) public;: Updates the identity hash of an already registered address to a new value.function cancelAndReissue(address original, address replacement) public;: Cancels a lost original address and reissues the token to a new verified address.function transfer(address to, uint256 value) public returns (bool);: Transfers tokens only to identity-verified addresses and automatically updates the holder list.function transferFrom(address from, address to, uint256 value) public returns (bool);: Transfers tokens, via delegated approval, only to identity-verified addresses and automatically updates the holder list.function isVerified(address addr) public view returns (bool);: Checks whether the given address is identity-verified and registered in the contract.function isHolder(address addr) public view returns (bool);: Checks whether the given address is currently a shareholder holding tokens (shares).function hasHash(address addr, bytes32 hash) public view returns (bool);: Checks whether the given hash matches the identity hash recorded for that address.function holderCount() public view returns (uint);: Returns the number of unique shareholder addresses that hold tokens.function holderAt(uint256 index) public view returns (address);: Looks up shareholder addresses one by one in index order, allowing the full roster to be extracted.function isSuperseded(address addr) public view returns (bool);: Checks whether the given address has been superseded by another address and is no longer in use.function getCurrentFor(address addr) public view returns (address);: Follows the chain of superseded addresses to return the current valid address that holds the shares.
In depth
ERC-20 extension and indivisible shares
ERC884 includes ERC-20's totalSupply, balanceOf, transfer, approve, and so on as is, while requiring decimals to always return 0. Each token corresponds to one fully paid share, so there is no need to record fractional shares or partial payment information. Providing name and symbol is recommended for wallet and exchange compatibility.
Registering, updating, and deleting verified addresses
addVerified(addr, hash) registers an address together with a hash of that person's identity information and emits VerifiedAddressAdded; it must fail if the address or hash is zero or the address is already registered. removeVerified(addr) deletes the registration and emits VerifiedAddressRemoved, but an address holding tokens cannot be removed. updateVerified(addr, hash) updates the hash and emits VerifiedAddressUpdated, but does not emit the event if the hash is unchanged. Who holds access rights to these functions is outside the scope of the standard and is left to implementers.
Restricting transfers to verified addresses
transfer and transferFrom must block transfers to addresses that are not identity-verified. If the receiving address is receiving tokens for the first time, it is added to the shareholder list, and if the sending address's balance reaches zero, it is removed from the shareholder list. This way the contract always maintains the current shareholder roster on its own.
Reissuance for lost addresses
cancelAndReissue(original, replacement) is a function for shareholders who have lost their private key. The original address must already be an existing shareholder, and the replacement address must already be identity-verified and must not yet hold any tokens. Once executed, the original address is removed from the verified address list and cannot be reused, and a VerifiedAddressSuperseded event is emitted. Access to this function must be strictly controlled.
Querying the shareholder roster
holderCount returns the number of unique addresses currently holding tokens, and holderAt(index) returns an individual shareholder address by index, so used together with holderCount it can extract the full shareholder list. isHolder(addr) checks whether a given address is a current shareholder, and isVerified(addr) checks whether an address is identity-verified. This supports the preparation of shareholder lists required under Delaware General Corporation Law sections 219 and 220.
Identity hash and off-chain data
No personal information such as names or addresses is stored directly on chain; only a hash combining name and address is recorded via addVerified/updateVerified. hasHash(addr, hash) checks whether a given hash matches the value recorded for that address. Implementers should separately operate a private off-chain database containing names, addresses, and Ethereum addresses, and it is desirable to provide a REST API in the form GET https://<host>/<pathPrefix>/:ethereumAddress so that third-party auditors can verify whether a specific address is verified.
Connection to SEC requirements
This standard itself does not prescribe how a crowdsale should be operated or what information must be disclosed, but it is designed to support such requirements. For example, the SEC requires funds raised to be disclosed in dollars, which is something the crowdsale contract must handle separately, for instance via an exchange rate oracle. Also, depending on the type of investment, there may be limits on the number of shareholders, which can be checked using holderCount and isHolder.
Proposal status
This proposal is in Stagnant status, meaning it is a draft where discussion has stopped and is no longer progressing.