history-tools
history-tools copied to clipboard
EOSIO
EOSIO History Tools
history-api v1/history/get_transaction have not the inline actions info as https://developers.eos.io/eosio-nodeos/reference#get_transaction-1 I want to know if there are plans to support the feature
Please help, I want to build history api node using legacy server WASM. These tests work fine. ```txt cd build curl localhost:8880/v1/chain/get_table_rows -d '{"code":"eosio", "scope":"eosio", "table":"namebids", "show_payer":true, "json":true, "key_type": "name",...
when I execute the example request: `curl localhost:8880/v1/chain/get_table_rows -d '{"code":"eosio", "scope":"eosio", "table":"namebids", "show_payer":true, "json":true, "key_type": "name", "index_position": "2", "limit":100}'` I get the following error using postgres: ` LINE 1: select...
in file "legacy-server.cpp",just use params.account_name and params.offset ,but there is no "pos". void get_actions(std::string_view request, const eosio::database_status& /*status*/) { auto params = eosio::parse_json(request); auto s = query_database(eosio::query_action_trace_receipt_receiver{ .snapshot_block = std::numeric_limits::max(),...
I read doc, demo code and src code, but I did't find a way to write a descend query. When people query his transfer records, he wants to see a...
Looks like legacy-server (https://github.com/EOSIO/history-tools/blob/d8312a722c78f7c7742a728274df18603680534a/wasms/legacy/legacy-server.cpp) don't compatible with API from History API. It's quite confusing. And it's more about functionality than data formats. For example: /v1/history/get_actions just always returns actions from...
Per https://eosio.github.io/history-tools/wasm-ql.html almost all of the legacy API functions are available via wasm-ql based functions. It looks like only 2 are missing: ``` get_key_accounts get_controlled_accounts ``` The critical one `get_key_accounts`...
if use postgresql database，I hope that get_table_rows API could support complexly query by multi fields in column value using where clause。 Could you support it in the near future。
chain: jungle 1) payload in db: ```sql select encode(abi, 'base64') as abi, name as account_name, null as wasm from account where name='eosio.token' order by block_num DESC; abi | account_name |...
