7

Whenever you set up a local testnet node or run nodeos on your home computer, you are creating a new EOS chain. What matters is how you choose to connect it to other nodes to decentralise the system. If you want a private blockchain for, say, your office building, then you would set up several instances of nodeos in the office and connect them to each ...


3

Yes you can create a private blockchain take a look to this tutorial : https://developers.eos.io/eosio-nodeos/docs/bios-boot-sequence


2

The chain id is the is the SHA256 serialization of the genesis_state. genesis_state.hpp : /** * Get the chain_id corresponding to this genesis state. * * This is the SHA256 serialization of the genesis_state. */ chain_id_type compute_chain_id() const; genesis_state.cpp : /** * @file * @copyright defined in eos/LICENSE.txt */ #...


2

If you need them all to be in one block, increase block time and max block cpu usage, and check you're using wabt and not wasm. All these can be configured in config.ini I believe. Also ensure the action your calling uses minimum cpu, as you won't get anywhere near 8000tps for more expensive actions.


2

You can change number of BPs in system contract, Change "21" to your desired number as below: refer:eos/contracts/eosio.system/voting.cpp top_producers.reserve(**21**); for ( auto it = idx.cbegin(); it != idx.cend() && top_producers.size() < **21** && 0 < it->total_votes && it->active(); ++it ) { top_producers....


2

In [producer_pay.cpp][1], you'll find: const int64_t min_activated_stake = 150'000'000'0000; You'll want to either alter that when loading the contracts, or just issue tokens to some accounts and ensure that enough votes (150 million) have been cast to pass this threshold.


1

This got me as well, it's related to the new WTMSIG_BLOCK_SIGNATURES in eosio 2.0 and the requirement to pre-activate the new eosio chain. There is a pull request which includes a simplified version of the eosio.bios contract called eosio.boot which once deployed gives you the ability to pre-activate and then activate the necessary features. Details can be ...


1

If you just want to run a dapp in sandbox environment you can run local EOS node (nodeos). It will contain only your data and will not sync all blocks from testchain. You can start by downloading binaries of EOSIO and EOSIO.CDT. and then simply starting local node through nodeos. By default local node will run on http://127.0.0.1:8888/


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

You can find a guide on biosboot sequence in EOSIO developer portal and I think you will find it useful understanding such configurations. The p2p-listen-address field indicates which IP address and port will be opened for other peers to communicate with this certain node. Think of it as a server address. On the other hand, the p2p-peer-address field ...


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