Anoma v1 spec cleanup tasks

[cwgoes]

• Avoid using "Namada", the specs should only refer to protocol versions, and staking tokens in the abstract
• Basic format for spec pages (assigned to @arafey)
• Component versioning (e.g. Tendermint is consensus v1)
• Clarify inflation system
• Clarify slashing system
• Clarify fee system
• Clarify web explorer requirements
• Reorganise main "Anoma v1" page with diagrams

[cwgoes]

Should incorporate and close:

• Specs: Ethereum bridge recovery multisig #170
• https://github.com/anoma/specs/issues/58
• https://github.com/anoma/specs/issues/24

Additional v1 inclusion candidates:

• Decentralised genesis transaction submission and data availability (probably use Ethereum/Filecoin)
• Public-goods funding

[cwgoes]

PGF design constraints:

• No anti-Sybil mechanism for now (needs to correlate to delegated stake)
• Assume high cost-of-attention
• Entities apply for continuous funding (a such entity could be a grants program), the bar is high but so are rewards
  • On-chain mechanism should handle coarse funding choices
  • Coarse funding choices entail long-term commitment (e.g. years in advance, long notice periods)
  • First recipient(s) can be grants programs, potential other development organisations
  • Earmarked portion for internal PGF (split tactical/strategic), earmarked portion for external PGF
• Retro-PGF rounds at fixed cadence

[cwgoes]

Additional blockers

• Spec writeup of https://github.com/anoma/specs/issues/100

[cwgoes]

final point will be closed by #245