Operational and upgrade procedures for blockchain infrastructure management, focusing on Polygon ecosystem protocols and smart contract operations.
├── operations/ # Contract interactions and operational procedures
└── upgrades/ # Smart contract upgrade procedures
- Appropriate system permissions and network access
- Web3 wallet (MetaMask, etc.)
- Gnosis Safe multisig access (where applicable)
- Required tools as specified in individual procedures
- Navigate to the relevant directory (
operations/
orupgrades/
) - Read the specific runbook's prerequisites
- Follow the step-by-step instructions
- Verify results as documented
Many procedures require multisig operations:
- Proposers: Can propose transactions (e.g., Polygon IPs)
- Signers: Can review, approve, and execute transactions
- Execution: Requires meeting the signature threshold
- Always verify contract addresses and parameters before execution
- Test procedures in testnet environments when possible
- Ensure proper authorization before executing operations
- Keep detailed records for audit purposes
- Blockchain operations are irreversible - proceed with caution
When adding new runbooks:
- Use the established documentation format
- Include prerequisites, step-by-step instructions, and verification steps
- Add security considerations and troubleshooting guidance
- Test procedures before committing
Licensed under the terms in the LICENSE file.
Use at your own risk. Always verify procedures in testing environments first and ensure proper authorization. This documentation is provided as-is without warranty.