...

...

• block

• transaction

• trace

• specific account and name inside trace → action_traces → act. It will be presented as Trigger: action_account:action:name, e.g. Trigger: eosio:newaccount

• table deltas

and are organized by defining the table where record needs to be added as well as data source, typically from the trace.

...

Table: handles

Status
colour Green title NEW RECORD

or

Status
colour Yellow title update

(if exists based on handle)

...

Trigger

...

: Table Deltas: added:false and kvo->table:domains

Table: domains

Status
colour Yellow title update

Table: domain_activity

Status
colour Green title NEW RECORD

API

/get_blocks

Returns block information.

Request

...

Parameter

...

Description

...

time_start

Trigger: Table Deltas: added:false and kvo->table:fionames

Additional check needs to be performed:

• If this handle burn was already processed as a result of Trigger: fio.address:burnaddress and action_ordinal = 1 do not process this trigger.

Table: handles

Status
colour

...

Yellow title

...

time_end

update

Table: handle_activity

Status
colour Green title NEW RECORD

API

/get_blocks

Returns block information.

Request

...

...

Return records from transactions which match all request parameters andexcept:

• impacted_account is supplied:

  • Constrains transactions to those that are present in account_activity → account and:

    impacted_account_direction is supplied and is “sender”

    • Records from transactions where impacted_account = account_activity->account and type is “sender”

  • impacted_account_direction is supplied and is “receiver”

    • Records from transactions where impacted_account = account_activity->account and type is “receiver”

  • impacted_account_direction is

    not

    supplied

    or

    and is “both”

    type is “receiver” OR type is “sender”

    or not supplied

    • Records from transactions where impacted_account = account_activity->account

  • Please note: a single transaction can be affecting the same account as sender and receiver! In this case the same transaction should be returned twice.

Also include related data from:

• blocks

  • timestamp

• traces

  • All traces for transactiontransaction should be returned twice.

Also include related data from:

• blocks

  • timestamp

• traces

  • All traces for transaction

• token_transfers

  • id matches transaction_id

  • Include

    • payer_account

    • payee_account

    • amount

    • type

    • memo

• domain_activity

  • id matches transaction_id

  • Include

    • domain

    • type

• handle_activity

  • id matches transaction_id

  • Include

    • handle

    • type

• token_staking

  • id matches transaction_id

  • Include

    • staker_account

    • amount

• fio_requests

  • id matches transaction_id

  • Include

    • id

    • payee_handle

    • payer_handle

    • content

    • payee_pub_key

    • payer_pub_key

    • status

• fio_data

  • id matches transaction_id

  • Include

    • request_id

    • payee_handle

    • payer_handle

    • content

    • payee_pub_key

    • payer_pub_key

    • status

Sort by:

• timestamp_asc: blocks → timestamp ASC

• timestamp_desc: blocks → timestamp DESC

...

Example

[
	{
		
	}
]

TODO

...

• reverse handle look-up