Vaulta Development - Multisig Proposals

Infrastructure and governance proposals for the Vaulta network

This repository contains multisig proposals for the Vaulta network. Each proposal is self-contained with its own documentation.

Stage 1: Foundation Transition

Written Proposal

Document: Stage 1 Proposal
Purpose: Describes the transition from Vaulta Foundation to new entities (VDT & VNT)
Status: 📝 Draft v6

This document provides the full context and rationale for the Stage 1 transition, including:

• Creation of Vaulta Development Team (VDT) and Vaulta Network Trust (VNT)
• New funding distribution mechanism
• Resolution of Foundation account access issues

Technical Proposals

1. ⏳ Account Creation (dev.accounts)

Purpose: Creates accounts for Vaulta development infrastructure
Dependencies: None
Signers: 15/21 BPs
Proposal: https://unicove.com/msig/aaron/fwmpntxlmfhz
Links: Documentation | Code

---

2. ⏳ Contracts & Configuration (coredevdist)

Purpose: Deploys distribution contracts and configures funding
Dependencies: Requires dev.accounts to be executed first
Signers: 15/21 BPs
Links: Documentation | Code

---

Foundation Cleanup

3. ✅ Unwind VF1 - Permission Reset (unwindvf1)

Purpose: Resets permissions for admin.grants and eosio.grants accounts
Status: Completed
Dependencies: None
Signers: 2/3 Foundation
Links: Documentation | Code

Transactions:

• Created: 4daa332d...
• Executed: efb12b90...

---

Platform Infrastructure

4. ⏳ Miscellaneous Accounts (miscaccounts)

Purpose: Creates accounts for new Vaulta platform contracts
Dependencies: Requires dev.accounts to be executed first
Signers: 15/21 BPs
Links: Documentation | Code

---

Installation

# Install dependencies
bun install

Environment Setup

Copy the example environment file:

cp .env.example .env

Edit .env to set local configuration values.

Running Proposals

Each proposal can be executed by targetting the directory:

bun run proposals/<proposal-name>

This will create and submit a multisig proposal to Vaulta, which can then be reviewed and approved by the appropriate signers.

Document Hashing

Calculate SHA-256 hashes of documentation files for on-chain proposal references:

./scripts/hash-docs.sh                   # Hash all markdown files in subfolders
./scripts/hash-docs.sh documents/*.md    # Hash specific files

Output format:

documents/stage-1.md
fe708b714a4fb976b2f291269f18bed17427f0121da62c6ad1c71583d47de157

Document hashes can be included in multisig proposals (via token transfer memo) to create a permanent on-chain reference to the approved document version.

Contributing

When creating new proposals:

1. Create a new directory in proposals/
2. Add an index.ts file with the proposal logic
3. Create a README.md describing the proposal
4. Document all actions, permissions, and security considerations
5. Include contract verification steps if deploying contracts