10

for a normal user to run a full node on his PC? If we define a "normal user" as Average Joe, who would like to just transfer some tokens or even deploy a smart contract, then there are not many reason why such a user would want to run a witness node. But there are some: If you are a developer/service provider (like exchange, block explorer) and you need ...


6

Aside from monetary incentives, the primary incentives for running your own node would be speed of access to the information in the block, and the ability to run custom plugins that are needed to power your application. Since any node that runs will replicate all of the blocks as they are produced, accessing a local node will allow your application to query ...


3

EOS Nation Snapshots: https://snapshots.eosnation.io/ Also Sw/Eden: https://snapshots.eossweden.org/ We also keep this updated to get peers, genesis, etc: https://docs.liquidapps.io/en/stable/dsps/eosio-node.html


2

solved by adding chain-state-db-size-mb = 65536 to config.ini. thanx to Cryptolions in Telegram :)


2

The Docker image you're pointing to probably is built with the SYS CORE_SYMBOL. It's a way for Block.one to say: we're not running the mainnet. You can use images we provide (at your own risk) here: https://hub.docker.com/r/eoscanada/eos/tags/ If you want get_actions, you'll want to enable the history_api_plugin (which serves the /v1/history/get_actions ...


2

The philosophy behind DPoS is that, even though only a small set of nodes (in case of EOS, 21 Active BPs) are elected to produce blocks, every full node keeps an entire copy of block data & state data. So basically: Every full node will validate the incoming blocks, checking signatures for transactions, checking contract execution results, checking if ...


1

Snapshot doesn't have any history. (History here means blocks and transactions) It only contains the latest state, and you can sync blocks from the block where snapshot was generated. If you need past blocks (eg. for making a query about transactions before snapshot generation), you need complete blocks.log. However, you can use snapshot to build the latest ...


1

Currently there is no such data in the mongodb directly. You could use the RPC API, which is POST v1/chain/get_account with account_name field. Like this: curl --request POST --url https://api.eosbean.com/v1/chain/get_account --data '{"account_name":"eosbeaneosbp"}' If you really want to retrieve that data from mongodb, you could query the action_traces ...


1

For instance, if you set a small queue size, and your mongodb writing is slow, the queue will populate too fast that it reaches the capacity easily. This will cause the mongodb plugin to crash. If you set a large queue size, your nodeos will consume more RAM.


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