...
Table of Contents | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
--cleanup--
FIO Relic is an application which connects to to the FIO Chain node to receive all transaction data, transforms this data into FIO Protocol specific data, inserts int into a relational database and makes the content available via HTTP API. The following document is intended to be functional specification for the FIO Relic System.
...
Trigger: Table Deltas: added:false
and kvo->table:domains
Secondary conditions (all must be true):
There must be a transaction in the
block_num
which hasaction_name: burnexpired
is_public
forkvo
→value
→name
in domains table has not changedexpiration
forkvo
→value
→name
in domains table has not changed
Table: domains
Status | ||||
---|---|---|---|---|
|
...
Field | Source Data |
---|---|
domain |
|
transaction_id | transaction id of transaction with |
type | “auto_burn” |
Trigger: Table Deltas: added:false
and kvo->table:fionames
Additional check needs to be performed:
...
Secondary conditions (all must be true):
There must be a transaction in the
block_num
which hasaction_name: burnexpired
and its traces do not have a trace withaction_name: burnaddress and action_ordinal = 1
do not process this trigger.
Table: handles
Status | ||||
---|---|---|---|---|
|
...
Field | Source Data |
---|---|
handle |
|
transaction_id | transaction id of transaction with |
type | “auto_burn” |
API
/get_blocks
...