Skip to content

Data Structures Overview ​

delband - delegated POWER bandwidth per account ​

The table contains the information about POWER bandwidth delegation between different accounts.

Table namedelband
Codeeosio.system
Scopeaccount
Primary keyto
FieldsTypeDescription
fromeosio::nameThe account that delegates POWER
toeosio::nameThe account it is delegated to
power_weighteosio::assetThe amount of staked UOS to POWER

kyc - account KYC information ​

Table namekyc
Codeeosio.system
Scopeaccount
Primary keyprovider
FieldsTypeDescription
providereosio::nameThe KYC provider account
cert_ideosio::checksum256The KYC provider certificate ID
req_signatureeosio::signatureThe account signature
pro_signatureeosio::signatureThe KYC provider signature

paycntactid - contract action ID catalog ​

Table namepaycntactid
Codeeosio.system
Scopepaid contract
Primary keypaid_action
FieldsTypeDescription
paid_actioneosio::nameThe catalog contract action ID
paid_contract_action_iduint64_tAuto incremented ID for the contract action

payerpred - predicates for paying for 3rd parties ​

Table namepayerpred
Codeeosio.system
Scopepayer account
Primary keypaid_contract_action_id
FieldsTypeDescription
paid_contract_action_iduint64_tThe catalog contract action ID, references paycntactid::paid_contract_action_id
maximum_power_usageuint64_tThe max POWER to be paid for
predicate_contractstd::optional<eosio::name>The contract to use for inline action creation
predicate_actionstd::optional<eosio::name>The inline action to create when the predicate is executed

rammarket - RAM trades settings and limitations ​

The table contains the information about the RAM market (buys / sells) settings such as KYC/non KYC account limits, global RAM reserve and fee calculation coefficients

Table namerammarket
Codeeosio.system
Scopeeosio.system
Primary keyram_supply.symbol
FieldsTypeDescription
ram_supplyeosio::assetRAM available on the market
ram_reservedeosio::assetRAM reserved for ultra and its partners
ram_total_non_kyceosio::assetMaximum amount of RAM for non-KYC users
ram_threshold_kyceosio::assetUnused RAM limits for KYC users
ram_purchase_limiteosio::assetRAM purchase limit in a single buy action
core_reserveeosio::assetUOS reserve that represents market state at full ram supply
connector_weightdoubleIn Bancor algorithm describes how tightly the RAM is connected to UOS
ram_fee_ratedoubleRAM fee fraction applied to each purchase
is_trade_enabledboolenables buy and sell actions for RAM

refunds - information on refunding of the delegated POWER ​

The table contains information about the refunds that delegating accounts can request after delegation period. For example, if Alice delegates some POWER to Bob, Alice can refund the POWER after the delegation period (3 days).

Table namerefunds
Codeeosio.system
Scopeaccount
Primary keyowner
FieldsTypeDescription
ownereosio::nameThe account that delegated POWER and now being refunded
request_timeeosio::time_point_secThe time when the POWER was delegated
power_amounteosio::assetThe amount of staked UOS to POWER

userres - resource allocation per account ​

The table contains the information about the resources that are allocated some account.

Table nameuserres
Codeeosio.system
Scopeaccount
Primary keyowner
FieldsTypeDescription
ownereosio::nameThe account that currently owns the resources
power_weighteosio::assetThe amount of staked UOS to POWER
ram_bytesint64_tThe amount of available RAM
flagsuint32_tIndicates if RAM or POWER is managed by the accountram_managed = 1, power_managed = 2