Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Table of Contents
minLevel1
maxLevel6
include
outlinefalse
indent
stylenone
exclude
typelist
class
printabletrue

Overview

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.

...

  • “Notify supplied webhook on every new FIO Domain registration”

  • “Notify when a FIO Request for specific FIO Handle is observed”

Specification

Data Model

Tables

...

blocks

Field

Description

Data stream field name

Relationship

block_numnumber

Block number as generated by FIO Node

block_numReferences transactions in this

blocktransactions->block_num

id

Block ID as generated by FIO Node

id

timestamp

Timestamp as generated by FIO Node

timestamp

producer

Account name of producer which produced the block

producer

schedule_version

Version of BP schedule

schedule_version

...

transactions

Field

Description

Data stream field name

Relationship

block_numnumber

Block which contained this transaction

block_numReferences block which contains this transaction

blocks->number

id

Transaction id

idReferences

traces in this transactiontraces->transaction_id

account

Account name for action

account

action

Action name

name

actor

Actor which executed the transaction

actor

tpid

TPID which was recorded in tranaction

tpid

fee

FIO Chain fee paid for this transaction

fee_collected

request_data

Raw request data for primary trace

data

response_data

Raw response data for primary trace

response

...

traces

Field

Description

Data stream field name

Relationship

id

Trace id

accounts->trace_id

References transaction which contained this tracetransaction_id

Transaction ID

transactions->id

action_ordinal

Sequential order of trace in transaction

action_ordinal

account

Account name for trace

account

action

Action name fro trace

name

request_data

Raw request data for trace

data

accounts

Field

Description

Data stream field name

Relationship

account

Account name

account_transactions->account

trace_id

Trace ID which created account

traces->id

account_transactions

Field

Description

Data stream field name

Relationship

account

Account name

accounts->account

transaction_id

Transaction ID

transactions->id

type

Type of impact the transaction had on on account

domains

Field

Description

Data stream field name

Relationship

domain

Domain name

domain_activity->domain

owner

Account Name of current owner

accounts->account

expiration

Timestamp of domain expiration

status

Current status of domain

domain_activity

Field

Description

Data stream field name

Relationship

domain

Domain name

domains->domain

owner

Account Name of current owner

accounts->account

trace_id

Trace ID of domain activity

traces->id

type

Type of activity

handles

Field

Description

Data stream field name

Relationship

handle

Handle name

owner

Account Name of current owner

accounts->account

bundled_tx

Bundled tx count

handle_activity

Field

Description

Data stream field name

Relationship

handle

Handle name

handles->handle

owner

Account Name of current owner

accounts->account

trace_id

Trace ID of handle activity

traces->id

type

Type of activity