eosio::multi_indextable with the same name as the
dapp::multi_indexvRam table defined by the smart contract. Each row in the regular
eosio::multi_indextable represents the merkle root of a partition of the sharded data with the root hash being
vector<char> shard_uriand the partition id being
uint64_t shard. Note that this is equivalent to having a single merkle root with the second layer of the tree being written to RAM for faster access. The default amount of shards (which is proportional to the maximum amount of permanent RAM required) is 1024 meaning that, the total amount of RAM that a
dapp::multi_indextable will need to permanently use is
1024 * (sizeof(vector<char> shard_uri) + sizeof(uint64_t id)).
ipfsentrytable. The DAPP Services Provider is responsible for removing this data after the transaction’s lifecycle. If the DSP does not perform this action, the
ipfsentrytable will continue to grow until the account’s RAM supply has been exhausted or the DSP resumes its services.
xwarmupevents and 1
xcommitevent, this can be further leaned out to 1
xwarmuprowaction, see the advanced features section. Each action is charged in QUOTA, the default for a package is
0.0001QUOTA per action unless the DSP increases that default amount which they may do at any time.
delay_seclogic operates on deferred transactions which are deprecated; however, the LiquidScheduler's schedule service would be a great use to schedule the committing of the user's data for the future.
loadis called at the user's login. The DSP can load all of the associated data for that user until that user becomes inactive.