Binance has confirmed support of the token registration for it's users, so for that reason you can leave them on the exchange safely and still be credited with the official EOS coin when it launches.
However just because they will auto-register you doesn't mean you will also receive all the possible airdrops that will be happening in early June. The safest ...
Chintai is building a dApp (decentralized app) on the EOS blockchain
that will allow you to lease your tokens. You can view it here: https://chintai-eos.io/
They will likely be on the Chintai marketplace, or other similar marketplaces.
You will be compensated in EOS tokens.
It will likely be an automated process on leasing marketplaces.
You will likely be ...
You can find the api endpoint for any BP by querying their bp.json file.
The bp.json file has information about the BP publishing it, and among other things it has a key called api_endpoint which is what you need.
Every BP should publish their bp.json on their url - copy the web link for the BP you want from http://eosnetworkmonitor.io/ and append /bp....
Here is one counter-argument.
A side chain needs resources, namely block producers, voters, and incentives for all of them to act.
A block producer that's voted in for the main chain might not be interested to support a side chain.
The majority of voters might not care for a side chain.
If, on the other hand, the side chain is supposed to run with only ...
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
EOSDAC pitch themselves as "The Community Block Producer". Their tokens represent your stake in the block producer.
It is not yet entirely clear how your EOSDAC ERC20 tokens will transfer to the EOS platform, the EOSDAC website still says that the process will be "defined by the launch team, that will be described on the eosDAC website and social media ...
What is initial_key in genesis.json and role of this property?
initial_key is public key of genesis nodeos, this property used on genesis nodeos to start producing. All other nodes those who want to participate in the network should have the same key in their genesis.json file.
How is the initial key generated?
$cleos create key
Just writing this so that there is a formal answer.
The problem can be fixed by running your normal nodeos command with the additional --delete-all-blocks option, example shown below:
nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin --delete-all-blocks
Please note that doing this will delete all the information stored ...
Yes, you can.
To create an account in Mainnet, you need to use cleos -u MAINNET_API_URL system newaccount instead of cleos create account, since the back one is for boot
or development purpose, you can't create an account in Mainnet in this way.
You can retrieve the EOSIO version by making API call to /v1/chain/get_info endpoint and see the server_version property there, which is the first letters of the git commit id from the official repository https://github.com/EOSIO/eos/commits/master
For example, you can use http://dev.cryptolions.io/mainnet/ (or actually any BP API server from "Address" ...
First you need the genesis.json file that matches everyone else's. Then you will need to launch with it (only the first time you run nodeos, after that don't use it)
nodeos --genesis-json genesis.json
The genesis file for the mainnet looks like this:
your cleos command looks absolutely right.
if your transaction did not appear on the blockchain - may be it's because it was accepted by your node (the one that gave you transaction hash), but was not accepted by any of block producers. why? may be you was on the edge of your CPU time and it was enough to run your transaction on your node, but not enough to ...
Probably not very much yet. There are very few transactions and actual RAM usage. Seems like actual RAM usage is ~7-8GB, and very few transactions. Will probably be able to run on entry level hardware. The blockchain should support up to 64GB RAM usage and around 500 TPS, so it's possible that your node will be subjected to that, worst case.
So you should ...
After some digging and some help from EOS New York, I think I understand the process of making changes better, and I can answer my question:
The setramrate update was proposed on 23rd July 2018 by Argentinaeos under the name of 1dot1dotzero, and it determined that EOS RAM should increase at 1kb per block.
The transaction that incorporated this change has ...
You must wait for a block height to be lower than the current Last Irreversible Block (also known as LIB) to be considered irreversible. With the quick speed of the network, it is common to see microforks that occur - often when ProducerB starts producing its schedule off of Block 11 of ProducerA's round. This can happen due to latency conditions because of ...
It was mentioned on the Telegram channel for developers that a bug has been found, so the BPs blacklisted the command until it's fixed. No other details were provided for now, but some BPs mentioned that a more detailed report should be coming soon. There's also an issue raised on GitHub about this.
Post-mortem explanation thanks to Kevin Rose from EOS New ...
The code used for the MainNet and other networks, such as TestNets or alternate networks, is normally the same. Some alternate networks may make alterations to the code for their specific purposes, but generally, the code is the same.
The EOS code that runs MainNet can be found on GitHub here, while the BlockOne developed source code that forms the ...
I know you want a web API for this but the simple thing to do would be to get cleos installed and call it from an AJAX endpoint to run:
cleos -u http://api.eosnewyork.io system listproducers
This returns the list of BPs with URLs and then you can just call any of these BP websites with /bp.json to retrieve the API endpoints for that BP.
PS: The cleos ...
What you have written looks right to me.
The reference for this is:
Something I noticed is that transferring EOS doesn't always work if you don't specify the correct precision. So you could also try delegating at the precision that the EOS supply was created with.
EOS NY Will Pull a Snapshot for you on request and they've also open sourced their code:
You can use a snapshot generator. https://github.com/EveripediaNetwork/airdrop Or you can use one of their snapshots ...
Description of adding/changing private keys is available here.
To transfer EOS tokens using cleos, use:
cleos -u <RPC API URL> transfer <sender account name> <recipient account name> '<EOS amount> EOS' <[optional] memo>
cleos -u https://api.tokenika.io transfer aaaaaaaaaaaa bbbbbbbbbbbb '1 EOS'
TL;DR: Using docker cap_add option to add IPC_LOCK privilege resolves this issue.
This is actually a docker-related question.
Process in docker container needs IPC_LOCK privilege to pin memory, which means prohibiting its memory page being swapped into swap.
More info: #4632
It is official.
See the link below.
This article was written by EOS New York. EOS New York is the top 21 Block Producer on the EOS Mainnet Blockchain.
I asked EOS New York about this content via Twitter.
EOS New York responded as follows.
Block on isn't ...