How to Deploy a Contract with DeployContract API

Blockdaemon’s deployment flow is smart-contract agnostic. That means you can deploy custom EVM bytecode instead of being limited to a predefined contract library. The same custody and policy framework can then be used to manage the deployed contract after launch.

This is useful for tokenization teams that need custom compliance logic, product-specific features, proxy patterns, or deterministic deployments.

How it works

The deployment flow supports:

• arbitrary EVM contract bytecode
• custom smart contract patterns
• proxy upgrade patterns
• CREATE2 deployment patterns
• policy enforcement at deployment time

At deployment, policy can govern:

• the initiating user or system
• the signing wallet
• the destination blockchain

After deployment, the same governance model can be applied to contract execution through Contract Calls or raw transaction flows.

Example request

{
  "chain": "ethereum-mainnet",
  "fromVaultId": "vault_123",
  "bytecode": "0x608060405234801561001057600080fd5b50...",
  "constructorArgs": [
    "BlockToken",
    "BLK",
    "0x1234567890abcdef1234567890abcdef12345678"
  ],
  "deploymentMode": "create2",
  "salt": "0x4d7953616c74466f7244657465726d696e69736d",
  "policyProfile": "token-deployment-prod"
}

Example Solidity constructor

contract ComplianceToken {
    string public name;
    string public symbol;
    address public admin;

    constructor(
        string memory _name,
        string memory _symbol,
        address _admin
    ) {
        name = _name;
        symbol = _symbol;
        admin = _admin;
    }
}

Why it matters

Custom contracts do not need to sit outside your control plane. You can deploy bespoke token logic and still keep:

• institutional signing controls
• approval workflows
• execution policies
• auditability
• operational consistency across chains

That is especially important for tokenization projects where standard token interfaces do not cover the full compliance or operational model.

When to use it

Use the Deploy Contract API when you need to:

• deploy a custom token or registry contract
• launch a proxy-based architecture
• use CREATE2 for deterministic addresses
• keep custom deployments within the same governance framework as production operations

Notes

Policy enforcement continues after deployment through execution-time controls such as wallet, destination contract, function name, and token-related values for actions like transfer, mint, burn, or forced transfer.

Deploy custom EVM smart contracts while keeping custody, policy, and governance controls in place.Blockdaemon’s deployment flow is smart-contract agnostic. That means you can deploy custom EVM bytecode instead of being limited to a predefined contract library. The same custody and policy framework can then be used to manage the deployed contract after launch.

This is useful for tokenization teams that need custom compliance logic, product-specific features, proxy patterns, or deterministic deployments.

How it works

The deployment flow supports:

• arbitrary EVM contract bytecode
• custom smart contract patterns
• proxy upgrade patterns
• CREATE2 deployment patterns
• policy enforcement at deployment time

At deployment, policy can govern:

• the initiating user or system
• the signing wallet
• the destination blockchain

After deployment, the same governance model can be applied to contract execution through Contract Calls or raw transaction flows.

Example request

{
  "chain": "ethereum-mainnet",
  "fromVaultId": "vault_123",
  "bytecode": "0x608060405234801561001057600080fd5b50...",
  "constructorArgs": [
    "BlockToken",
    "BLK",
    "0x1234567890abcdef1234567890abcdef12345678"
  ],
  "deploymentMode": "create2",
  "salt": "0x4d7953616c74466f7244657465726d696e69736d",
  "policyProfile": "token-deployment-prod"
}