8

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


4

Can you call the below to activate ACTION_RETURN_VALUE cleos push action eosio activate '["c3a6138c5061cf291310887c0b5c71fcaffeab90d5deb50d3b9e687cead45071"]' It looks like you called activate with the description_digest and not the feature_digest. curl -X POST http://localhost:8888/v1/producer/get_supported_protocol_features | jq -r ... { ...


4

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


2

Found the answer. It is genesis block initialization (mostly by eosio.bios.wast).


2

System tables are not (yet) well documented. You have to browse the source code. E.g. for voters you will find table eosio voters here: https://github.com/EOSIO/eos/blob/905e7c85714aee4286fa180ce946f15ceb4ce73c/contracts/eosio.system/eosio.system.hpp#L115 cleos -u https://eu.eosdac.io get table eosio eosio voters will return the first rows.


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.


2

Any event (action) that occurs on an eosio chain is at least a part of a transaction. The transactions are sent to a node that either belongs directly to a block producer, or will be forwarded to one. When sending transactions, resources are used up and can not be reused for 24 hours. These are CPU and NET bandwidth, and possibly RAM. In order to access ...


2

Key generation is generating an R1 or K1 curve key, can be done with cleos cleos create key --to-console ...


1

For any reason it's missing in the master-branch, if you are using a v2.1.0 version of EOS like the tutorial says, you probably have to switch to tag v2.1.0-rc3 or something similar. Helpful link to git tags The tutorial for Boot Sequence v2.0 should work as expected from what I can see.


1

What is the key generation process? As Nat says in his answer, the keys are secp256k1 or secp256r1 curve keys. You can read more about that here: http://www.secg.org/sec2-v2.pdf Can the same keypairs generated for the mainnet be used on any private network? Yes. A private/public keypair created for one EOSIO chain is usable on another chain. What is the ...


1

If you want to build a single contract with eosio.cdt you would need to modify the code. Just use the build-script build.sh (located in the eosio.contracts-directory) to compile all system-contracts at once, without the need to modify any of them.


1

EosSharp and EosWsSharp and EosDotNet are what you looking for. EosSharp and EosDotNet are based on the normal RPC-API, EosWsSharp uses dfuse.io for real-time websocket-connections.


1

The nodes cannot communicate with each other directly but both the nodes can communicate with the chain or genesis node. you have to just add IP and port of the genesis node into the -p2p-peer-address field of .conf file of the node.


1

EOSIO Private network tutorial by EOS Costa Rica: https://guide.eoscostarica.io/docs/tutorials/private-network-installation


1

this tutorial written by EOS developer. https://medium.com/@kaloliya/step-by-step-guide-to-set-up-your-private-eos-network-eosio-6d80c30dd520


1

You have two options two read any table (whether system table or table of another contract) by connecting to a public node: cleos get table call: https://developers.eos.io/eosio-cleos/reference#cleos-get-table rcp api get_table_rows call https://developers.eos.io/eosio-nodeos/reference#get_table_rows


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