Table 2.
Features | Traditional database | Ethereum (public) | Oasis Devnet |
Data read access control | Yes | No, data is public | Yes, dependent on smart contract logic |
Anonymity | Yes, if host is honest | Pseudo-anonymous | Pseudo-anonymous |
Cost | Fixed | Variable | Free on developer network, will be variable in production mainnet |
Data privacy | Yes, if host is honest | No, data is public | Yes, dependent on smart contract logic |
Data mutability | Mutable, but can be immutable via role permissions | Immutable | Devnet gets reset, but the production mainnet will be immutable |
Code can be updated | Yes | Yes | Not yet. Intercontract calls are planned |
Publicly verifiable | No, the public cannot verify stored procedures | Yes, the public can verify smart contract codea | Yes, the public can verify smart contract codea |
Widely accessible | Yes | Yes | Yes |
aFor both Ethereum and Oasis Devnet, the smart contract source code must be made public to verify that the contract is doing what is claimed.