Deploy

The Deploy entity provides a normalized representation of the Casper Network deploy. It is enriched with normalized contract data to make it possible to filter deploys by the contract regardless of the execution type.

Properties

The Deploy entity has the following properties:

PropertyTypeDescription

deploy_hash

string(64)

Deploy hash represented as a hexadecimal string. Primary deploy identifier.

block_hash

string(64)

Hash of the block containing the deploy represented as a hexadecimal string.

block_height

uint64

Height of the block containing the deploy.

caller_public_key

string(68)

Public key of the deploy caller account represented as a hexademical string.

execution_type_id

uint8

DeployExecutionType unique identifier.

contract_package_hash

string(64)

Hash of the contract package called by the deploy represented as a hexadecimal string. null if the deploy had no contract call.

contract_hash

string(64)

Hash of the contract called by the deploy represented as a hexadecimal string. null if the deploy had no contract call.

entry_point_id

uint32

Identifier of the ContractEntrypoint called by deploy. null if the deploy had no contract call.

args

JSON

Deploy sessions arguments provided for contract execution.

payment_amount

string

Payment amount provided by the caller in motes. The type is string to avoid overflow in languages that don't support uint64, which is the correct type. null if a custom payment contract was provided to the deploy instead of the value in motes.

cost

string

Deploy execution cost. The type is string to avoid overflow in languages that don't support uint64, which is the correct type.

error_message

string(128)

Error message in case of a failed deploy. null for successful. deploys.

status

string

Deploy status (pending, expired, or processed).

timestamp

string

Deploy creation timestamp in the ISO 8601 format.

Example

{
  "deploy_hash": "88461218a5e972fcda1d764d7cc4edb2e0c3a538123b97890d484f43c55935f5",
  "block_hash": "d76b4ce5281f2306911a0e5e9ac0b29f1f4daf36f4636e78599ce64a7f7528a1",
  "block_height": 2404577,
  "caller_public_key": "020304811a7b142c32860cb1c114f23b0754215918d819f485b0a201af6cde70fa6c",
  "execution_type_id": 6,
  "contract_package_hash": null,
  "contract_hash": null,
  "entry_point_id": null,
  "args": {
    "amount": {
      "cl_type": "U512",
      "parsed": "2500000000"
    },
    "id": {
      "cl_type": {
        "Option": "U64"
      },
      "parsed": null
    },
    "target": {
      "cl_type": {
        "ByteArray": 32
      },
      "parsed": "536345751b7c6c6299d5ef10862d76736ed062bc32c1dabcd1179c06469d93ca"
    }
  },
  "payment_amount": "100000000",
  "cost": "100000000",
  "error_message": null,
  "status": "processed",
  "timestamp": "2024-01-08T15:24:47Z"
}

Optional properties

Depending on the endpoint some of the following optional properties may be included in the Deploy entity:

PropertyTypeDescription

account_info

Account info provided by the deploy caller account

centralized_account_info

Account information available for known accounts provided by CSPR.cloud team

caller_cspr_name

string

Primary CSPR.name of the deploy caller account

contract_package

ContractPackage called by deploy.

contract

Contract called by deploy.

contract_entrypoint

ContractEntrypoint called by deploy.

rate

float32

CSPR rate for specified currency that was relevant at the moment of deploy creation.

Relations

The Deploy entity has the following relations with other entities:

EntityMapping propertyDescription

caller_public_key

Deploys are called by accounts.

block_hash

Deploys are executed in blocks.

contract_hash

Deploys can call contracts, and contracts are deployed with deploys.

entry_point

Deploys can call entry points.

contract_package_hash

Deploys can call contracts in contract packages.

execution_type_id

Deploys call contracts via different execution types.

deploy_hash

Fungible token actions are result of deploy execution.

NFTs are created as result of deploy execution. There is no direct mapping, but rather a semantic relationship between deploys and nft tokens.

deploy_hash

NFT actions are result of deploy execution.

deploy_hash

Transfers are result of deploy execution.

Endpoints

The Deploy entity has the following endpoints:

Relation endpoints

Last updated