Hot answers tagged

4

I asked my friend Andrew Coutts this question on your behalf, and he said: So the state history plugin is just a piece of the equation. The history plugin exposes the RPC API that we're all familiar with. The state history plugin saves state data to a new flat file format that’s designed to be read from external components and is faster to ...


3

This is a dynamic and constantly changing list and you need to find some sources for it and keep your system updated with it. Here is one place I found that lists some of the BP endpoints. Also, note that you don't have to rely on BPs for this service. You can set up a witness node and filter it to sync and listen on the info relevant to your application. ...


2

From eosjs module You can use eosjs node module to get tx status var txDetail = await eos.getTransaction(req.params.txid); console.log(txDetail.trx.receipt.status) From command line using cleos You can use cleos to get transaction details, and then use trx.receipt.status to check the status of your transaction cleos get transaction txHash


1

It's due to the design of eosio. You can find the related information from here. https://github.com/EOSIO/eos/pull/7690


1

This is not a direct way, but you can check whether ***_api_plugin is activated by calling /v1/node/get_supported_apis. Run the next command in command line (in the case of local testnet). You should stop nodeos first to toggle plugin activation. curl http://127.0.0.1:8888/v1/node/get_supported_apis


1

Other than the error of the duplicate key I would get a deadlock detected error, if I ever ran the demux after previously running it, or I would get current transaction is aborted, commands ignored until end of transaction block. I solved this issue, by commenting out the check functions in throwIfNotSetup() function in MigrationRunner.js (line 150 as of ...


1

Overall: Both state_history_plugin and demux can be used to cache the contract action data into database/memory for fast access in a structured manner. State_History_Plugin: State_history_plugin is block.one recommended plugin that comes with eosio setup which can be used to cache the full block information (i.e. inline action data) in file. nodeos -e -p ...


1

I found answer: Just set PG* environment variables. If so, fill-pg will use them.


1

You need to use an abi deserializer, such as abieos or eosjs. eosjs: const deserializedActionData = deserializeActionData( contract: "eosio.token", account: "eosio.token", name: "transfer", data: "\x3042a6875e7a90c310b2b9062173b239e80300000000000004454f530000000000", ...


1

The solution is simple but obscure if you are not used to nodejs applications. Just run the application with the flag --max-old-space-size=8192 For example, node --max-old-space-size=8192 fill.js The issue is caused by blocks bigger than the application can handle by default. Since State Plugin downloads the whole block at once, the only way around is ...


1

https://eos.greymass.com:443 This one works at the time of my posting


1

Most of the listed API end-points in EOSDocs.io is not enabled with history plug-in. So actions like get_transactions and get_actions are not possible. I found https://public.eosinfra.io is working to date for history actions


1

I tried to find get receipt too but can't find anything related. but int the path libraries/testing we can see a simple test. void base_tester::open() { control.reset( new controller(cfg) ); control->startup(); chain_transactions.clear(); control->accepted_block.connect([this]( const block_state_ptr& block_state ){ FC_ASSERT( ...


1

No, the blockchain is immutable and distributed. Due to immutability, any change in past blocks would alter the block hash, making the rest of the chain invalid. Due to being distributed, anyone can download the blockchain, and it would be difficult to erase it from everyone's memory storage.


1

It is sufficient. As long as you have server powerful enough. Especially storage.


1

It would help if you elaborated on what your "requirement" is as well as what "functions" are not being provided by the MongoDB plugin. If you want to store actions to MongoDB, you could use demux to listen to the chain and then append your database of choice with the information.


Only top voted, non community-wiki answers of a minimum length are eligible