|
| 1 | +# Vaulta Development - Multisig Proposals |
| 2 | + |
| 3 | +> Infrastructure and governance proposals for the Vaulta network |
| 4 | +
|
| 5 | +This repository contains multisig proposals for the Vaulta network. Each proposal is self-contained with its own documentation. |
| 6 | + |
| 7 | +## Proposals |
| 8 | + |
| 9 | +This repository contains the following proposals for the Vaulta network: |
| 10 | + |
| 11 | +### 1. Development Accounts Creation (`dev.accounts`) |
| 12 | + |
| 13 | +**Purpose**: Creates accounts for Vaulta development team |
| 14 | + |
| 15 | +**Dependencies**: None |
| 16 | + |
| 17 | +**Signers**: 15/21 BPs |
| 18 | + |
| 19 | +**Documentation**: [proposals/dev.accounts/README.md](proposals/dev.accounts/README.md) |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +### 2. Development Team Account Setup (`coredevdist`) |
| 24 | + |
| 25 | +**Purpose**: Unlocks funding mechanism for core development team and removes Foundation account access |
| 26 | + |
| 27 | +**Dependencies**: Requires `dev.accounts` proposal to be executed first |
| 28 | + |
| 29 | +**Signers**: 15/21 BPs |
| 30 | + |
| 31 | +**Documentation**: [proposals/coredevdist/README.md](proposals/coredevdist/README.md) |
| 32 | + |
| 33 | +--- |
| 34 | + |
| 35 | +### 3. Miscellaneous Vaulta Accounts Setup (`miscaccounts`) |
| 36 | + |
| 37 | +**Purpose**: Creates accounts for new Vaulta Contracts |
| 38 | + |
| 39 | +**Dependencies**: Requires `dev.accounts` proposal to be executed first |
| 40 | + |
| 41 | +**Signers**: 15/21 BPs |
| 42 | + |
| 43 | +**Documentation**: [proposals/miscaccounts/README.md](proposals/miscaccounts/README.md) |
| 44 | + |
| 45 | +--- |
| 46 | + |
| 47 | +### 4. Unwind VF1 Account Permission Reset (`unwindvf1`) |
| 48 | + |
| 49 | +**Purpose**: Resets permissions for admin.grants and eosio.grants accounts |
| 50 | + |
| 51 | +**Dependencies**: None |
| 52 | + |
| 53 | +**Signers**: 2/3 Foundation |
| 54 | + |
| 55 | +**Documentation**: [proposals/unwindvf1/README.md](proposals/unwindvf1/README.md) |
| 56 | + |
| 57 | +## Installation |
| 58 | + |
| 59 | +```bash |
| 60 | +# Install dependencies |
| 61 | +bun install |
| 62 | +``` |
| 63 | + |
| 64 | +## Environment Setup |
| 65 | + |
| 66 | +Copy the example environment file: |
| 67 | + |
| 68 | +```bash |
| 69 | +cp .env.example .env |
| 70 | +``` |
| 71 | + |
| 72 | +Edit `.env` to set local configuration values. |
| 73 | + |
| 74 | +## Running Proposals |
| 75 | + |
| 76 | +Each proposal can be executed from its directory: |
| 77 | + |
| 78 | +```bash |
| 79 | +# Navigate to a proposal directory |
| 80 | +cd proposals/<proposal-name> |
| 81 | + |
| 82 | +# Execute the proposal |
| 83 | +bun run index.ts |
| 84 | +``` |
| 85 | + |
| 86 | +This will generate a multisig proposal that can be reviewed and approved by the appropriate signers. |
| 87 | + |
| 88 | +## Contributing |
| 89 | + |
| 90 | +When creating new proposals: |
| 91 | + |
| 92 | +1. Create a new directory in `proposals/` |
| 93 | +2. Add an `index.ts` file with the proposal logic |
| 94 | +3. Create a `README.md` describing the proposal |
| 95 | +4. Document all actions, permissions, and security considerations |
| 96 | +5. Include contract verification steps if deploying contracts |
0 commit comments