Hot answers tagged

7

EOSIO can run with very little memory, less than 100MB + shared memory file size. The requirements for the shared memory file depends upon the state of your local application (number of users, etc).


4

I was able to run Single Node Testnet on Ubuntu using Docker on my machine with around 2GB RAM without problem (as bytemaster said it requires little memory actually). The CPU and Disk Space are not mentioned explicitly. I guess you will need decent disk space once the blockchain increases in size. Also, probably it's good idea to compare the hardware ...


3

Ask for a download link from a BP for a higher block number. Link for 7m+: https://s3-us-west-2.amazonaws.com/blocks-nodeos/blocks.tar.gz Up vote confused00 for providing better link: https://eosnode.tools/blocks


2

You are not providing signature signing your transaction. It says you are trying to push it as david@active, but to not have authorization attached. Try adding the following options to your transaction construction. const options = { authorization: 'david@active', broadcast: false, sign: false, };


2

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


2

After some more research, I realized that even if I don't want to keep historical state, I have to start at the genesis block for consensus. An option is to download a snapshot and use that (but that carries some risk): https://eosnode.tools/snapshots


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 ...


2

When you start a nodeos process for the first time, a config file is generated automatically at .local/share/eosio/nodeos/config/config.ini by default. In the config.ini file, peers can be specified by including one or many p2p-peer-address entries, e.g. p2p-peer-address = ctestnet.eosdetroit.com:1339 These peers can be any nodeos, including block ...


1

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


1

You need to authorize the transaction with signatures for both accounts. 1. The ressource-paying-account and 2. the acting account. Assuming that lionstester1010 should pay for the transaction but lionstester1011 is the acting account/the sender of the token: actions: [{ account: 'eosio.token', name: 'transfer', authorization: [{ actor: '...


1

You can check out dfuse On Demand Networks. We can operate the network on your behalf. Here's a link to get some more info: https://www.dfuse.io/en/blog/let-dfuse-launch-your-on-demand-network


1

Find your nodeos process ID and kill it! You can kill the nodeos process using: pkill nodeos or using the PID which can be listed by ps -aux | grep nodeos and then killing the process using kill PIDofNodeos


1

On the EOS Mainnet, new peers need to be manually added. See https://validate.eosnation.io/mainnet/reports/config.txt for an up-to-date and validated list.


1

Heifner (Contributor) replied on Github here: abi-serializer-max-time-ms = 5000 needs to be larger or you will have problems with action data not being serialized and remaining in hex. What you store depends on what kind of queries you want to support. - # Enables storing blocks in mongodb. (eosio::mongo_db_plugin) mongodb-store-blocks = 1 # Enables ...


1

There are different ways to generate a random uint64/ulong in Javascript like concatenating/multiplying the results of Math.Random() or Math.Floor() or using third-party-libs. But here's not really the right place to ask for these things as it's not directly eos-related. You need to serialize and sign the whole transaction before you push it through chain ...


1

One hack is that use --dbpath armament,its the path provided externally.


1

MongoDB is typically stored at /data/db. If it's not there, check out this question, this question, etc. for advice on finding the location. edit: The database was found at /var/lib/mongodb as explained in the comments below.


1

It sounds like you are not trying to connect to the main net which is a production EOSIO network with 21 block producers with BP's like EOS New York, Canada, etc. If you're trying to run a single node test net I highly recommend using the Docker image that's provided by Block One, it's fantastic for development purposes and if you screw anything up you can ...


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