3

Yes jungle testnet upgraded to 2.0 and before updating they have started account migration programme but it's ended now, and they have given manual migration form on this site https://jungletestnet.io/ to migrate your accounts.


3

When an EOS blockchain is created, it will implicitly create an account (called eosio). This is a privileged account that can be used to setup and configure the blockchain, as well as create new accounts. In the case of the main net, part of the launch process was to use this account to create the accounts for everyone who has purchased EOS tokens in the ...


2

In the first line you're entering an EOS public key in what should be a private key const addPrivateKey = "EOS8i1CXTY4Sz39XaQWX2RpccsCZ1nWM3w9zRhjCFChdci2Y65ck4"; Change this to the private key but as the comments say, be sure you keep this private, don't upload it or anything.


2

You can't send money to a public key, because the same public key can be used for many accounts, and the code wouldn't know which account should receive the money. This is the same on any eos.io based blockchain. You can keep a record in one of your tables about which public key has what money associated with it, and then only send money to an account when ...


2

# wait for nodeos until curl http://127.0.0.1:8888/v1/chain/get_info do sleep 1s done


1

The very first batch of EOS accounts was created by the system account from the ERC20 EOS Token snapshot during the mainnet launch. The mainnet launch process is like this: https://medium.com/eos-new-york/eos-mainnet-launch-the-order-of-events-ed89a816beb8


1

Genensis-accounts were created during the initial launch only and no new genesis-accounts will be created. The only way to get a genesis-account these days is to buy someone else's genesis-account.


1

Have you tried adding the flag -p eosio@active to ensure that it's trying to utilize the correct auth? (I'm assuming that the wallet is unlocked and accessible and contains the correct keys)


1

There was an opened issue in the repository. It was fixed today. You can get the updated eoslime code from the development branch. The fix is going to be uploaded on master branch and npm through the next week


1

There's no feature like that in Cleos. You have write your own function for generating random accountnames and afterwards you need to verify that the generated accountname is available.


1

1.From your information, you ran nodeos like: nodeos --genesis-json eos_data/config/genesis.json --config-dir eos_data/config/ --data-dir eos_data/data/ 1.1 this node is not a producer as no -p specified; 1.2 this node have no chain-plugin, so it will not accept you cleos request, and say "Error 3110001: Missing Chain API Plugin"; 1.3 the default ...


1

You forgot to indicate the permission after the transaction. You have to add at the end: -p eosio So that the full command looks like: cleos -u http://127.0.0.1:5801 create account eosio NEW_ACCOUNT owner_public_key active_public_key -p eosio


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