#define USE_ADVANCED_IPFS
at the top of the contract file while following the steps below. If you have already deployed a contract that does not use advanced features, do not add this line, as it is not backwards compatible. With this addition, the primary key may be uint32
, uint64
, uint128
, and checksum256
.warmuprow
and cleanuprow
actions. The warmuprow
action allows for faster warmups for IPFS actions. The warmup process is where data is fetched and loaded into RAM to be used. Previously each RAM entry touched would require 3 separate warmup actions, now this can be done within 1 action. The cleanuprow
action removes all the data entries created by the warmuprow
in the case that a rollback is required.warmupcode
action. This is done the same way as a regular multi_index table by specifying a code
other than _self
. For example, by replacing:warmupchain
and cleanchain
actions. Similar to reading from other contracts, this may be done using some additional parameters:chain
is the name of the side chain as specified in the LiquidX chain model file. In the case of reading from the EOSIO mainnet, specify chain
as ‘mainnet’.