Hot answers tagged

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


3

RocksDB intended use is to perform better than Chainbase with data sets that have larger (64KiB+) data associated with the average row in the database and data access patterns that favor fewer highly trafficked rows. It also has an operational advantage when there is a preference for SSD or disk storage rather than physical RAM. However, remember that ...


2

No, you don't need to create a wallet for each node. It does not communicate with wallet at all. You should set producer-name and signature-provider options for each block producing node. You need to create an account with the producer-name and set a pair of private and public key for sigining produced block. These keys don't need to same to those of owner ...


2

I ran this command then i can create new account. cleos push action eosio.token issue '["eosio", "400000000.0000 SYS", "memo"]' -p eosio


1

1MB max block size on EOS mainnet. You can query with cleos get table eosio eosio global Transactions that don't make it into the current block will be queued for subsequent blocks.


1

First of all, please double-check your startup command as yours is modified comparing to the example: nodeos -e -p eosio \ --plugin eosio::producer_plugin \ --plugin eosio::producer_api_plugin \ --plugin eosio::chain_api_plugin \ --plugin eosio::http_plugin \ --plugin eosio::history_plugin \ --plugin eosio::history_api_plugin \ --filter-on="" \ --...


1

You are correct in that you need to create a wallet on inita node as well as on the genesis node. Actions can only be pushed to the blockchain from a location where the private key is accessible. The most common way to do this is to store the private key in a wallet and then unlock that wallet before pushing the action to the chain. You set up a wallet and ...


1

Now(2020.08.08) you can get blocks.log from here https://archive.eoseoul.io/


1

We can do this programmatically by utilizing cleos, jq, sed, and wget. First of all, we get a list of all the block producers, and specifically we get the URL for their websites: cleos get table eosio eosio producers -l -1 | jq -r '.rows[].url' > bp_url.dat Next, we need to add wget to each of these URLs sed -e 's/^/wget -t 1 --timeout=1 /' -i bp_url....


1

Its not about the storing of data, but about the authentification and authorization of that data. A blockchain allows you to know that a specific person performed a specific transaction. Transaction IDs are useful for looking back into the history to understand what happened in the past. You can copy and paste a transaction ID into a block explorer such as ...


1

Imagine the blockchain as a tamper resistant database. You interact with it per transactions that are signed and the log is signed as well. The method of hashing hashes (blocks) and chaining them is used for making it resistant to manipulation. In a traditional system an attacker would be able manipulate the database and the transaction log more or less ...


1

Check whether nodeos was run with the option --plugin eosio::chain_api_plugin. This option can be put in config.ini like plugin = eosio::chain_api_plugin.


1

The key to the problem is this part of the error message: std::exception::what: Unknown option 'bnet-follow-irreversible' inside the config file /Users/wilfra/Library/Application Support/eosio/nodeos/config/config.ini It tells you that you have an option in your config.ini file that is no longer valid, and removing it would fix the problem (or at least ...


1

I was given a solution by conr2d on Telegram. The problem was I had an old config.ini file. I deleted it and ran the nodeos commands again and it solved these errors. Running nodeos generates a new config.ini if one does not exist. File is in: ~/Library/Application\ Support/eosio/nodeos/data


1

the problem is coming from beforeEach function => you are deploying each time a new contract and it throws, because you are creating your user only in the first test suite Solutions: Replace beforeEach with before Create a user in each of your tests


1

You'll find the scripts for building eosio in the scripts-folder. Do $ cd scripts $ ./eosio_build.sh or $ ./scripts/eosio_build.sh to build eosio. EDIT: follow this guide to Build from Shell Scripts or this guide to install prebuild binaries


1

blocks.log contains all transactions which are the requests for changes on the state, and the state is built by sequential execution of all transactions from genesis block. 1) Snapshot only stores the latest state (sum of all changes occurred by execution of transactions) including created accounts, their permissions and keys, multi-index table, smart ...


1

All of them are backup data generated during replay. If you don't have any issues in execution of nodeos, you can delete them. The current process of nodeos you run refers to "blocks" directory only.


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


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