...
Table of Contents | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
TODO
burned addresses and domains pre JAN-2024 - maybe table deltas?
FIO Relic is a fork of Antelope Memento and is intended to receive FIO Chain data stream from the FIO Chain Node via EOS Chronicle. FIO specific data is extracted from the stream and stored in a Relational Database (RDB) for future query via API. The following document is intended to be functional specification for the FIO Relic System.
...
Field | Source Data |
---|---|
domain |
|
transaction_id |
|
type | “auto_burn” |
API
/get_blocks
Returns block information from blocks table.
Request
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
time_start |
timestamp | ||||||
time_end |
timestamp | ||||||
producer |
producer | ||||||
sort |
timestamp_asc timestamp_desc |
Response
Field | Source Data |
---|---|
number |
|
id |
|
timestamp |
|
producer |
|
schedule_version |
|
Example
Code Block | ||
---|---|---|
| ||
[
{
"number": "2",
"id": "00000002953a8ab87a1855c0c40786e6a910a86cb2dd160f181418d05d233ea7",
"timestamp": "2020-03-25T00:05:21.000",
"producer": "eosio",
"schedule_version": "1"
}
] |
/get_transactions
Returns transaction information from transactions table.
Request
Parameter | Description | ||||||
---|---|---|---|---|---|---|---|
time_start |
timestamp | ||||||
time_end |
timestamp | ||||||
block_number |
block_number | ||||||
action_account |
action_account | ||||||
action_name |
action_name | ||||||
sort |
timestamp_asc timestamp_desc |
Response
Field | Source Data |
---|---|
id |
|
block_number |
|
action_account |
|
action_name |
|
account |
|
tpid |
|
fee |
|
request_data |
|
request_data |
|
status |
|
type_specific_data |
Example
Code Block |
---|
[
{
}
] |
TODO
burned addresses and domains pre JAN-2024 - maybe table deltas?