[META] 🏗4️⃣ test4.gno.land

[moul]

Meta issue for https://github.com/gnolang/gno/milestone/4, to keep a place for discussions.
Blocked by #361

• initial discord faucet Community faucet bot #364
• initial namespace support feat: r/system/names public functions and checks with AddPackage #384
• fix banker module fix: minting additional GNOTs  #393
• fix bugs, reorganize content, and prepare the project for the Game Of Realms event.
• Bonus, this list: https://github.com/gnolang/gno/milestone/4

[zivkovicmilos]

@moul
How updated is this issue?

[moul]

It's not, let's speak about this during an upcoming team sync.

[moul]

Next Steps:

1. Test full node connection and synchronization on test3.
2. Create a separate repository for multi-node experimentations to maintain a clean main repository. (will do soon)
3. Create a docker-compose file or equivalent to experiment locally with several nodes, and write some integration tests.
4. Bootstrap a simple r/system/validators realm integrated with the chain.

[r3v4s]

Meta issue for https://github.com/gnolang/gno/milestone/4, to keep a place for discussions. Blocked by #361

• initial discord faucet Community faucet bot #364
• initial namespace support feat: r/system/names public functions and checks with AddPackage #384
• fix banker module fix: minting additional GNOTs  #393
• fix bugs, reorganize content, and prepare the project for the Game Of Realms event.
• Bonus, this list: https://github.com/gnolang/gno/milestone/4

fix banker module(new pr): #875

[moul]

🔗 Proposal: See my new testnet idea here. I'm thinking of launching test4 with this approach.

Why? The deprecated AVL on the current testnet was a setback. With the new testnet setup, I hope to streamline deployments from GitHub and improve our feedback loop.

[zivkovicmilos]

@moul

Can I own this issue / effort?
I want to define with the team the exact scope of test4 and launch it, given as it's going to be a release candidate for other future, bigger, launches