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:
Property | Type | Description |
---|---|---|
|
| Deploy hash represented as a hexadecimal string. Primary deploy identifier. |
|
| Hash of the block containing the deploy represented as a hexadecimal string. |
|
| Height of the block containing the deploy. |
|
| Public key of the deploy caller account represented as a hexademical string. |
|
|
|
|
| Hash of the contract package called by the deploy represented as a hexadecimal string. |
|
| Hash of the contract called by the deploy represented as a hexadecimal string. |
|
| Identifier of the |
|
| Deploy sessions arguments provided for contract execution. |
|
| Payment amount provided by the caller in motes. The type is string to avoid overflow in languages that don't support |
|
| Deploy execution cost. The type is |
|
| Error message in case of a failed deploy. |
|
| Deploy status ( |
|
| Deploy creation timestamp in the ISO 8601 format. |
Example
Optional properties
Depending on the endpoint some of the following optional properties may be included in the Deploy
entity:
Property | Type | Description |
---|---|---|
| Account info provided by the deploy caller account | |
| Account information available for known accounts provided by CSPR.cloud team | |
|
| Primary CSPR.name of the deploy caller account |
|
| |
|
| |
|
| |
|
| 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:
Entity | Mapping property | Description |
---|---|---|
| Deploys are called by accounts. | |
| Deploys are executed in blocks. | |
| Deploys can call contracts, and contracts are deployed with deploys. | |
| Deploys can call entry points. | |
| Deploys can call contracts in contract packages. | |
| Deploys call contracts via different execution types. | |
| 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. | ||
| NFT actions are result of deploy execution. | |
| Transfers are result of deploy execution. |
Endpoints
The Deploy
entity has the following endpoints:
Relation endpoints
Last updated