Record Keeping
and Code

Overview

If a Dapp can be trusted also means if the code being executed can be trusted. To be trusted, Dapps should be as transparent as possible about all the aspects of their code.

Takeaways

1

Clarify Blockchain

Allow the user to inspect all interactions ever made with the Smart Contract.

2

Smart Contract

Clarify the address of the Smart Contract(s) that are being used for reading and writing operations

3

Code Transparency

Clarify which code is open source and where to find it.

4

Local vs Remote

Clarify where code is being run (local vs Remote Server).

5

Control

If possible or relevant allow users to switch to their own node.

6

Smart Contract Inputs

Clarify the inputs required by the Smart Contract.

7

Web3 Provider & Blockchain Node

Clarify the web3 provider / Blockchain node (local node, Dapp controlled node, Infura, MetaMask, or another node).

8

MainNet vs Test Net

Make sure that the user understands that actions are being run on the MainNet or TestNet.

9

Data Oracles

Clarify which data read from the chain comes from Oracles or has been influenced by oracles.

10

DIY Code

Allow more advanced users to see the transaction function call before it is sent so that they could verify it and reproduce the action by themselves via the command line.

Example

1

Many NFT market platforms have the contract address of each product. Allowing each user to inspect all interactions ever made with the smart contract.

Record Keeping and Code