Account
The Account
entity represents the account observed in the network activity. For example, when the corresponding public key was passed as a deploy argument. Because of that, an Account
may not necessarily have a purse and on-chain balance.
Properties
The Account
entity has the following properties:
Property | Type | Description |
---|---|---|
|
| Account public key represented as a hexadecimal string. Primary account identifier |
|
| 32-byte hash of the |
|
| Account main purse URef in the |
|
| Account main purse balance in motes |
Example
Optional properties
Depending on the endpoint some of the following optional properties may be included in the Account
entity:
Property | Type | Description |
---|---|---|
|
| Account auction status: |
|
| Total funds delegated across all validators |
|
| Total funds staked as validator |
|
| Total undelegated funds that will be returned to the account main purse after the 7 era lockdown period |
Relations
The Account
entity has the following relations with other entities:
Entity | Mapping property | Description |
---|---|---|
| Account can have account info data if provided by the owner to the Account Info contract | |
| Account can be a bidder in the auction | |
| Account can deploy contracts to the network | |
| Account can call deploys on the network | |
| Account can have delegations to validators | |
| Account can receive delegator rewards | |
| Account can own fungible tokens | |
| Account can be on the sending or receiving end of a fungible token action | |
| Account can own NFTs | |
| Account can be on the sending or receiving end of a fungible token action | |
| Account can own multiple NFTs in one NFT contract | |
| Account can initiate transfers and be a transfer recipient | |
| Account can be a validator |
Endpoints
The Account
entity has the following endpoints:
Relation endpoints
The Account
entity has the following relation endpoints:
Last updated