anoma / namada

Rust implementation of Namada, a Proof-of-Stake L1 for interchain asset-agnostic privacy
https://namada.net
GNU General Public License v3.0
2.39k stars 945 forks source link

Mainnet phases of operation #2563

Closed cwgoes closed 3 weeks ago

cwgoes commented 7 months ago

This list is still tentative and subject to change.

The following must happen before mainnet:

  1. [ ] Attain protocol stability.
    • Protocol stability requires that the community (including Heliax) is confident in the correctness of and familiar with the usage of a stable version of the software.
    • At minimum, this requires a release version which we intend to use for mainnet. This release version must:
      • [ ] Complete everything in https://github.com/anoma/namada/issues/2528, software-wise.
      • [ ] Be run on the SE for 1-2 weeks stably
      • [ ] Be subjected to 2 weeks of full-time internal red teaming with no further finds
      • [ ] Be subjected to final external audits (details still TBD)
  2. [ ] Finalize a genesis block proposal and publish it alongside instructions to:
    • Reconstruct the generation process using input data.
    • Check for the presence of an account in the genesis file, and the associated balance.
    • Check that the keys associated with this account are accessible and can produce a valid signature.
  3. [ ] Genesis block proposal is published for at least 1 week of community review
    • People should have a chance to test their keys. This is the last time we can change addresses.

Mainnet is expected to follow the following phases (names are tentative):

Phase 1: Block Party

Phase 2: Staking Party

Phase 3: Shielding Party

Phase 4: Shielding Party Overdrive

Phase 5: NAM NAM NAM

brentstone commented 7 months ago

What does it look like to disable NAM transfers in the code? It sounds like before we want to enable them, accounts will still be able to bond and unbond tokens and make governance proposals. These actions require transferring tokens to and from an account and an internal address like PoS or Governance. Perhaps we have some logic that forbids transfers between (implicit | established) <---> (implicit | established) addresses?

cwgoes commented 7 months ago

What does it look like to disable NAM transfers in the code? It sounds like before we want to enable them, accounts will still be able to bond and unbond tokens and make governance proposals. These actions require transferring tokens to and from an account and an internal address like PoS or Governance. Perhaps we have some logic that forbids transfers between (implicit | established) <---> (implicit | established) addresses?

Yes; I think we would only allow transfers to and from PoS and governance, and the transfers back can only be to the account which controlled the bond or made the deposit, respectively.

ahaunz commented 6 months ago

As I understand it, the concept is that when Phase 5 is reached, the entire 100% of the 1b (NAM) supply will become available for transfer/transfers. And no vesting for all of them.

How useful is this in terms of tokenomics and long term development of Namada, how does launching the first fractal instance of Anoma follow such a method?

Because of this approach, the support of the long-term and retail investor is lost, including there may be a problem with listing on the CEX exchanges and with this approach developers will have no incentive to continue to support and develop the project, because with this approach its value/value of NAM including will tend to zero.

Still, I suggest to consider creating a more fair and accurate tokenomics, for example, to pay attention to Celestia (With a small amount of unlocked assets for the community/developers/treasury, about 12-18% at the time of listing followed by gradual unlocking of the rest)

ragnarok5562 commented 5 months ago

Let me ask a simple question. The testnet has been running for so long and the above problems were solved before the mainnet was launched. Why can’t the mainnet transfer tokens yet but continue to do testing? Are you sure this is the mainnet and not testnet 2?

cryptomolot commented 5 months ago

The proposed plan appears promising, with the flexibility to make adjustments through governance. The Namada community and pilots, in particular, will play a crucial role in ensuring its success :)

Viva La Namada!

brlck974 commented 5 months ago

great team , i like this plan

ValarDragon commented 5 months ago

X-posting my comment from the forums:

Exciting that this is happening!

Phase 1 makes sense to me to start getting some user-determined validator set choices determined. I personally would hope that this phase is like 3 days, but at most 2 weeks.

I don’t get why phase 2 and phase 3 can’t be combined. I don’t really see any point in turning on staking inflation prior to allowing IBC. I think it will lead to phase 2 user frustration to have to stake early for yield, but come back later to do their first thing here. (The NAM they get won’t even be distributable) Hence I think just combine phase 2 + 3 and jump to utility being provided. Seems like an unnecessary delay in time to market, with unclear utility to me.

gavinly commented 5 months ago

fyi this is also being discussed on the Namada forum: https://forum.namada.net/t/proposal-for-mainnet-launch-phases/560

cwgoes commented 3 weeks ago

Out-of-date, superseded by more recent discussions on the forums.