Jungle 4 (Testnet)

Proposals

Network proposals for Vaulta, published for public review.

VP-0001
Proposed
Updated Oct 19, 2026
Network-Funded Account Onboarding

Approved creators draw on a RAM endowment held by the network-owned account gift.vaulta to gift RAM to accounts they create, onboarding users without carrying the RAM cost. The system launches with no registered creators, and each creator is admitted by its own 15/21 BP MSIG.

VP-0002
Proposed
Updated Sep 3, 2026
Self-Serve Account Creation

A proposal to create the new.vaulta account and deploy an account creation contract to it: one canonical, network-secured home where a user pays in the network token and receives their account and its RAM in one step.

VP-0003
Draft
Updated Oct 19, 2026
Network Steering Committee, RFP Framework Approval, and On-Chain Program Funding

This proposal asks block producers to approve the Vaulta Network RFP Framework, continue the Oversight Committee as a five-seat Network Steering Committee, and authorize a bounded RFP funding mandate and on-chain program fund. Published decisions, conflict rules, payment delays, and recurring funding approval keep the Committee accountable to the Network.

VP-0004
Review
Updated Oct 21, 2026
Register gm as a VP-0001 Creator

This proposal registers gm as a creator under VP-0001 with a daily quota of 256 KiB. Greymass operates gm through Sextant, the account creation service behind Anchor for iOS and Android and Web Authenticator, and uses it to give new users a free account after a Google or Apple sign-in. gm already gifts RAM to every free account it creates; with the endowment, that RAM comes from the network, and Greymass's own RAM covers any account above the quota.

VP-0005
Proposed
Updated Oct 21, 2026
Raise the Inline Action Size Limit

An msig can upgrade a contract only while its code stays under about 512 KB, half the size an account's own keys can deploy. This proposal raises that limit to 1 MB, so contracts that only governance can upgrade, such as the EOS EVM runtime, which sits 16,620 bytes below the current limit, can be upgraded at any size a key holder could deploy.