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:
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
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
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
Example
Optional properties
Depending on the endpoint some of the following optional properties may be included in the Deploy
entity:
account_info
Deploy caller AccountInfo
entity.
contract_package
contract
contract_entrypoint
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:
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
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