Overview of dapp development process. Introduce the tools and SDKs and link to the detailed articles that already exist.

Can maybe reuse slides from SF Blockchain Week.

Edit here: https://github.com/aergoio/guide/blob/master/source/dapp-development/index.rst

Need to copy over the relevant sections from the release announcement and add some details.

Missing information:

• public hostname for RPC
• public IP for peering

Short explanation of currently implemented consensus algorithm (dpos).

Some keywords I would like to have explained:

• BP selection
• Staking
• Voting
• Fees

Edit here: https://github.com/aergoio/guide/blob/master/source/specs/consensus.rst

source/running-node/quickstart.rst links to https://docs.aergo.io/en/latest/using-testnet/syncing.html which does not exist.

We need a nice introduction and high-level overview. It should answer the question, "as a developer, why should I care about aergo?"

• Vision
• Main features (available now)
• Roadmap

Edit here: https://github.com/aergoio/guide/blob/master/source/introduction/index.rst

https://docs.aergo.io/en/latest/running-node/configuration.html says:

There are three common modes of operation for aergo server:

• BP Node - Block provider node, which mines and propagates blocks
• Full Node - Node to get and validate all blocks
• Single Node - BP Node without peer, which uses to something like test.

We describe only single node configuration in this. More will updated for the BP Node and full node.

So currently it is not clear how to join e.g. the testnet. I see that #4 was closed but not sure what the resolution was.

It's not clear from the guide whether it's possible to iterate over a state.map(). Based on my reading of contract/state_module.c, I see that state_array_iter is implemented, but there is no corresponding state_map_iter. So it seems that this is not possible. If I'm right then this limitation should be documented, and it should be made clear that it doesn't behave like a normal table.

I have found a workaround, which is to use a state.value() and then set it to a table, but this makes reading/writing quite awkward.