Cubewire supports deploying new smart contracts and interacting with existing contracts on supported blockchains. All contract operations follow the same security model as transactions, including policy evaluation and approval workflows.
This section covers dedicated contract endpoints:
Note: For state-changing contract calls, use the Transactions API with type: CONTRACT_WRITE.
Deploy compiled smart contracts with constructor parameters to any supported blockchain network.
How to Use:
The deployment process is asynchronous - you receive an immediate response with a workflow ID and transaction ID for tracking. See the Deploy a smart contract endpoint for complete request and response details.
Query smart contract state without modifying the blockchain or consuming gas.
How to Use:
Read operations are perfect for checking token balances, querying configuration values, or verifying contract state. The function must be a view or pure function that doesn't modify state. See the Read contract state endpoint for complete request and response details.
Deploy ERC-20 or ERC-721 tokens:
Deploy Gnosis Safe or similar multisig contracts:
Deploy custom contracts for:
Read contract state for:
| Practice | Description |
|---|---|
| Test on testnets first | Deploy to Sepolia/Mumbai before mainnet |
| Verify bytecode | Ensure bytecode matches audited source |
| Document deployments | Track contract addresses and purposes |
| Practice | Description |
|---|---|
| Audit contracts | Professional audit before deployment |
| Use established patterns | OpenZeppelin, etc. |
| Verify on block explorer | Verify source code after deployment |
| Practice | Description |
|---|---|
| Provide ABI | Include ABI for proper result decoding |
| Validate addresses | Verify contract exists before calling |
| Handle errors | Contract calls may revert |
For complete API documentation including endpoints, request/response examples, and code samples:
POST /api/v1/contracts/deployPOST /api/v1/contracts/readCubewire supports deploying new smart contracts and interacting with existing contracts on supported blockchains. All contract operations follow the same security model as transactions, including policy evaluation and approval workflows.
This section covers dedicated contract endpoints:
Note: For state-changing contract calls, use the Transactions API with type: CONTRACT_WRITE.
Deploy compiled smart contracts with constructor parameters to any supported blockchain network.
How to Use:
The deployment process is asynchronous - you receive an immediate response with a workflow ID and transaction ID for tracking. See the Deploy a smart contract endpoint for complete request and response details.
Query smart contract state without modifying the blockchain or consuming gas.
How to Use:
Read operations are perfect for checking token balances, querying configuration values, or verifying contract state. The function must be a view or pure function that doesn't modify state. See the Read contract state endpoint for complete request and response details.
Deploy ERC-20 or ERC-721 tokens:
Deploy Gnosis Safe or similar multisig contracts:
Deploy custom contracts for:
Read contract state for:
| Practice | Description |
|---|---|
| Test on testnets first | Deploy to Sepolia/Mumbai before mainnet |
| Verify bytecode | Ensure bytecode matches audited source |
| Document deployments | Track contract addresses and purposes |
| Practice | Description |
|---|---|
| Audit contracts | Professional audit before deployment |
| Use established patterns | OpenZeppelin, etc. |
| Verify on block explorer | Verify source code after deployment |
| Practice | Description |
|---|---|
| Provide ABI | Include ABI for proper result decoding |
| Validate addresses | Verify contract exists before calling |
| Handle errors | Contract calls may revert |
For complete API documentation including endpoints, request/response examples, and code samples:
POST /api/v1/contracts/deployPOST /api/v1/contracts/read