ERC-3475 Abstract Storage Bonds
Interface for creating tokenized obligations with abstract on-chain metadata storage
Functions this standard introduces (13)
0xb15edbe5 | activeSupply(uint256,uint256) | view |
0x443b63b9 | allowance(address,address,uint256,uint256) | |
0x2d760d57 | balanceOf(address,uint256,uint256) | view |
0xbc3c19f7 | burnedSupply(uint256,uint256) | view |
0x3cf3a604 | classMetadata(uint256) | view |
0xc7da92e1 | classValues(uint256,uint256) | view |
0x572e5ef2 | getProgress(uint256,uint256) | view |
0x1fa03a2b | isApprovedFor(address,address) | view |
0x029ba4eb | nonceMetadata(uint256,uint256) | view |
0x693f5548 | nonceValues(uint256,uint256,uint256) | view |
0xccea7b86 | redeemedSupply(uint256,uint256) | view |
0x4bb95aa2 | setApprovalFor(address,bool) | |
0xc2458d6b | totalSupply(uint256,uint256) | view |
Events (1)
Topic0 is the keccak256 hash of the signature, which is what a log filter matches on.
0x3a950f10bb6df353a4ab85913de7c26461edd1b6250912c3ddcbe92b91643584 | ApprovalFor(address,address,bool) |
Depends on (3)
Proposals this one names in its requires field.
Built on by (1)
Later proposals that name this one in their requires field.
What the specification covers
Compare with
Parsed from the canonical specification · discussion