[Proposal] Mainnet 🚀 plan

Mainnet Ops
1

wen mainnet? Let’s figure that out :rocket:
This is how we (Knowable) are seeing things take shape:

Next steps

We (Namada) will need social consensus on balances.toml before we can move to Pre-genesis Stage 2, so that will be our (Gavin; Knowable) top priority. I’m synthesizing community concerns/feedback and discussing with advocates who have been vocal about the matter. I think we’ll need Anoma Foundation to make some revisions.

We can’t forget about parameters.toml. Feels like we’re really close, but will be important to finish this. This is my next priority, so if there are concerns about the parameters, let’s make a hot topic in Discord and/or a dedicated forum topic NOW and get each parameter sorted out ASAP.

Once we have Social Consensus, things get rolling! Pre-genesis Stages 2 & 3 can progress and we’ll know what the mainnet Namada validator set will be. Then we do our dry run: relaunch Housefire with mainnet balances, parameters, and transactions, then progress through the Mainnet Phases.

wen mainnet

Initial timeline estimate (subject to change!!)
NOW - Pre-Genesis Stage 1 begins! - create validators for transactions.toml

After Social Consensus (? days), I estimate that we’ll need 9 days to progress through Pre-Genesis Stages 2 and 3 to begin Genesis Dry Run. I estimate that we could do the entire dry run in 8 days, and then it may be good to have at least 7 more days of prep before Genesis Mainnet.

So if all goes smoothly (and it never does), we could have a mainnet launch as early as 24 days after we finish Social Consensus.

Once these are done, we (Namada) can begin targeting a launch date/time. Unless someone has a better idea for mainnet launch plans, the answer to “wen mainnet” is “we haven’t decided yet, but here’s our plan: https://forum.namada.net/t/proposal-mainnet-plan/903”

Please reply with any concerns, questions, preferences, suggestions, alternatives!

12 Likes
2

The other topic about parameters seems to focus on economic parameters. I am interested in discussing the other parameters in terms of efficiency and resource consumption. Should we have a separate topic for those?

1 Like
3

If for example a new validator is created with different keys than those from the Shielded Expedition, could it be included in the transactions.toml a staking tx to this validator from the SE account? Because in the balances.toml only the accounts from the SE will be included, so to have staked NAM at launch is the only option that validators need to be created with the SE keys to include staking tx in the transactions.toml?
Also, in the parameters list it seems the epoch time proposed is 6h, so this would mean that validators without staked NAM at genesis launch will need to wait 2 epochs or 12h before being able to do a staking tx?

4

yes, please do!
(this is here to meet the 20 char minimum)

5

Yes, the idea is to put something like 0.05 NAM in the balances.toml for each validator with maybe >= 100 NAM delegated.

You create your validator in Stage 1 with whatever operator address you want, even if it has no NAM. then you delegate to your validator in Stage 2.

Then when Pre-genesis is done, we revise balances.toml so that your operator address has enough NAM to do basic operations (change meta data; vote on governance proposals, etc) prior to Mainnet Phase 5, when NAM transfers are enabled.

6

Yes, I think validators created right after genesis will have to wait two epochs (12 hours) before being elected into the active set (assuming we proceed with 6h epochs)

7
1 Like
9

Pre-Genesis Stage 1 update: Pre-Genesis Stage 1 begins!

1 Like
10

Two concerns I’d like to flag and better understand how they fit into the mainnet timeline:

  1. Ledger Support - is broken. I see that github issue has been assigned the tags pre-mainnet and last-minute . I’d consider this a mainnet blocker (and it seems others do too given the tags) - but it would be great to have this confirmed.
  2. Offline Signing (Issue, PR) - is broken. This should similarly be fixed before mainnet genesis.

Thanks + appreciate feedback on the above

2 Likes
11

thanks! @brentstone can you pls speak to these?

12

Hi @mike-u410, thanks for bringing these up!

Both things are actively being worked on, and they are both intended to be done before mainnet genesis. There’s also still some work needed from other collaborators to fix support for signing some shielded actions. Mainnet genesis Phase 1 could in principle begin with other ledger support aside from this. We would just need it by phase 3.

Hope this answers your questions!

3 Likes
13

Thanks for the confirmation, @brentstone! That should work. IMO what’s most important is that anyone who wants to keep their keys cold and still participate at every phase can do so from genesis. Your timelines sound like they’d support that :slight_smile:

In the meantime, we’ll follow along with those PRs!

2 Likes
14

quick suggestion not to use google docs anymore but crypto e2ee alt instead-

https://docs.fileverse.io/0x314090B56E4Df3e3bd6B481EAb2e1fb2C37a23Ce/4#key=xkxZJQItTuNOtJc3TQq7XOJedMHbs6taHniolIUQdjYHdAqalMRGOKZpmcwid3SN

2 Likes
15

hey Mike, i think we have our solution! will post soon

1 Like
16

good time for this,we will day day up

17

@mike-u410, @spork.Knowable has updated the docs to show how to use a Ledger Nano device in pre-genesis: Namada Documentation - Pre-genesis participants

2 Likes
18

Pre-Genesis Stage 1 update: deadline announced - Sep 16 at 21:00 utc

Pre-Genesis Stage 2 update: beginning Sep 17 at 8:00 utc (no deadline yet; will give 5 days’ notice)

image
image1656Ă—1026 175 KB

3 Likes