cicnet/cic-contracts
5
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Add back ERC interfaces

Browse Source
This commit is contained in:
lash
2023-03-25 12:32:56 +00:00
parent a28cfdbb36
commit 46cc35b54c
27 changed files with 198 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/texinfo/multihash.sol.texi
View File

@@ -1,6 +1,6 @@
@subsection Multihash
A complement to @code{Locator}, enabling validation and generation for multihashes that have been registered to the contract.
A complement to @code{Locator}, enabling validation and generation of multihashes for multicodecs that have been registered to the contract.
@table @dfn

8
doc/texinfo/overview.texi
View File

@@ -14,6 +14,7 @@ CIC smart contracts are implemented using the @emph{solidity} programming langua
The following well-known solidity interfaces are used directly.
@itemize @bullet
@item
@uref{https://eips.ethereum.org/EIPS/eip-20, ERC20 - Token Standard}
@@ -26,7 +27,7 @@ The following well-known solidity interfaces are used directly.
@end itemize
@subsection Extended ERC definitions
@subsection Partial use
@itemize @dfn
@item
@@ -34,7 +35,7 @@ The following well-known solidity interfaces are used directly.
@end itemize
@section Native implementations
@section Native interfaces
@include accountsindex.sol.texi
@@ -56,5 +57,6 @@ The following well-known solidity interfaces are used directly.
@include registry.sol.texi
@include writer.sol.texi
@include seal.sol.texi
@include writer.sol.texi

2
doc/texinfo/registry.sol.texi
View File

@@ -16,7 +16,7 @@ Unique (ERC20) token symbol resolver.
@include ../../build/RegistryClient.interface
@item Solidity interface definition
@include ../../build/contract_RegistryClient.texi
@item Reference implementation
@item Contract registry implementation
@uref{git://holbrook.no/eth-contract-registry.git,}
@item Token index implementation
@uref{git://holbrook.no/eth-contract-registry.git,}

4
doc/texinfo/writer.sol.texi
View File

@@ -2,7 +2,9 @@
A complement to ERC173, which allows definition of a class of super-users for a contract.
Typically, a super-user address may perform @emph{more} actions than a "normal" address, aswell as @emph{some} actions normally limited to the @emph{contract owner}.
A super-user address may perform @emph{more} actions than a "normal" address, aswell as @emph{some} actions normally limited to the @emph{contract owner}.
No super-user should be able to perform actions that @emph{contract owner} cannot perform.
Typically, only the @emph{contract owner} can add or remove a super-user.