System Wallet Integration
Wallet Types​
MOUNTAIN manages system wallets using two secure methods:
- Fireblocks Custody Service: Enterprise-grade custody solution
- Google Secret Manager: Securely stored BIP39 mnemonic phrases
Wallet Ownership Types​
- Shared Wallets: Used across multiple projects for cost efficiency
- Dedicated Wallets: Exclusively assigned to a single project for enhanced isolation
Wallet Selection​
Each project is configured with specific system wallets for transaction signing:
- Network Type: Separate wallets for mainnet and testnet environments
- Project Configuration: Wallet assignment is configured during project setup
- Ownership Type: Projects may use shared or dedicated wallets based on requirements
Contact support for wallet configuration or to discuss dedicated wallet options.
Nonce Management​
MOUNTAIN handles nonce management automatically:
- Sequential Processing: Ensures transactions are processed in order
- Conflict Resolution: Handles nonce conflicts between concurrent transactions
- Retry Logic: Automatically retries failed transactions with adjusted nonces
Security Features​
Authentication​
All transaction endpoints require:
- Valid Public API access token
- Project API key for project identification
- Appropriate role permissions (admin or editor)
Function Activation​
- Only activated contract functions can be executed
- Function activation requires admin or editor permissions
- Deactivated functions are immediately unavailable for execution
System Wallet Security​
- Fireblocks Integration: Enterprise-grade custody with multi-party computation
- Google Secret Manager: Encrypted mnemonic storage with access controls
- Private Key Protection: Private keys never leave the secure environment
- Transaction Logging: All transactions are logged and auditable for compliance
Gas Fees and Billing​
Cost Structure​
Transaction execution requires gas fees to be paid on the blockchain network:
- Gas Responsibility: Projects are billed for all gas consumed by their transactions
- Automatic Estimation: MOUNTAIN estimates optimal gas limits and prices
- Failed Transactions: Gas fees are still consumed even if transactions revert
- Cost Planning: Factor gas costs into your application's economic model
Billing Process​
- Gas fees are consumed for all transaction executions on the blockchain
- Billing structure and payment terms are defined in your MOUNTAIN contract
- Contact support for questions about gas costs and billing arrangements
Next Steps​
- Review best practices for secure transaction management
- Understand transaction lifecycle and error handling
- Get started with transactions