Skip to content

Deploy a smart contract from your application

Deploying a new smart contract, is done by sending a transaction calling a deployment action on one of the following special governance contracts.

The deployment action needs the smart contract code, the ABI and initialization parameters. You can read more about how to get the contract code and ABI and how to deploy smart contracts manually here

To deploy a smart contract from your application, the application must perform the following steps:

  • Create or load the WASM/ZKWA containing the the executable smart contract byte code.
  • Create or load the ABI (Application Binary Interface) containing the metadata for the smart contract.
  • Create the RPC containing the parameters for initializing the smart contract you want to deploy.
  • Create, sign and send a transaction, that calls the deployment action on the appropriate governance contract.

The following guide assumes you have followed the local integration environment, and currently have a running instance of your deployment.

The address of the deployed contract

The newly smart contract will be assigned an address on the blockchain during deployment. When you want to interact with the new contract you need this address.

The address of a smart contract is based on the identifier of the signed transaction that deployed the contract. The first byte of the address defines the type of contract. The last 20 bytes of the identifier for the signed transaction is used as the address identifier.

How to deploy a non-MPC smart contract

You want to deploy a smart contract from your application. In your application you have to send a signed transaction, that calls the deployment action on the Deploy contract. The Deploy contract has the address 0197a0e238e924025bad144aa0c4913e46308f9a4d, and you view it in the browser here. You can view the actions available for the contract, by downloading the ABI from the browser, and run the following command in the folder the downloaded ABI is in.

cargo pbc abi show 0197a0e238e924025bad144aa0c4913e46308f9a4d.abi

To deploy a new smart contract you call the action named deployContractWithBinderId, that has the following definition.

#[action(shortname = 0x04)]
pub fn deployContractWithBinderId (
    contract: Vec<u8>,
    abi: Vec<u8>,
    initialization: Vec<u8>,
    binderId: i32,
)

The binder id

The binderId specifies which version of the binder to use for deployment. The binder is responsible for connecting the smart contract with the blockchain.

When new features are added to the smart contract language new binders are released. Compiled smart contracts contain information about which binder versions they work with in the ABI-file.

To use the correct binder, first look up the version, that your contract needs. Run the following command and see the binder version your contract needs.

cargo pbc abi show <path-to-abi>

In the browser you can see the versions of the available binders in the state of the Deploy contract here.

To learn how to create the RPC for the above action - click here.

How to deploy a MPC smart contract

You want to deploy a MPC smart contract from your application, so you need to send a transaction from your application, that calls the deployment action on the MPC Deploy contract. The MPC Deploy contract has the address 018bc1ccbb672b87710327713c97d43204905082cb, and you view it in the browser here.

To view the ABI, download the ABI from the browser and run the following command in the folder, the downloaded ABI is in.

cargo pbc abi show 018bc1ccbb672b87710327713c97d43204905082cb.abi

To deploy an MPC smart contract you have to call the action deploycontractv3().

#[action(shortname = 0x02)]
pub fn deploycontractv3 (
    contractjar: vec<u8>,
    initialization: vec<u8>,
    abi: vec<u8>,
    requiredstakes: i64,
    allowedjurisdictions: vec<vec<i32>>,
    uniqueid: i32,
)

Since MPC smart contracts need MPC nodes assigned to perform the secret computation for the contract some configuration parameters are needed for the deployment.

  • The requiredstakes must be 2000.
  • The allowedjurisdictions is the list of jurisdictions, that the MPC nodes are must be located in. All MPC nodes are registered with information about which jurisdiction they are located in. allowedjurisdictions can be used to ensure that MPC nodes allocated for the MPC contract are located in specific countries, regions etc. Passing an empty list of jurisdictions, means that any MPC node can be used for the MPC contract.
  • The uniqueid specifies the binder to use. See the binder id for information.

In the browser you can see the versions of the available binders in the state of the MPC Deploy contract here.

To learn how to create the RPC for the above action - click here.