9

If chain wasn't started yet, and I have some EOS ERC20, then I need to register my tokens. I need to make sure, to save my private key, which will become an owner key to my account Yes, you need to register your EOS public key against your Ethereum Public key on the EOS smart contract deployed to the Ethereum network. I need to wait for announcement of ...


8

Use the name struct. 'name' is defined in types.hpp. For example, if you have the variable user of type account_name, you can print the user as follows: auto n = name{user}; print("Hello, ", n); std::string str = n.to_string();


6

The eosjs library has a format module that will transform account name strings into the appropriate table keys... const Eos = require("eosjs") const BigNumber = require("bignumber.js") const accountName = 'myaccount' const encodedName = new BigNumber(Eos.modules.format.encodeName(accountName, false)) ** Notes: Be sure to pass false to format.encodeName, ...


6

There are 26 letters and 5 numbers available for making standard EOS names, meaning there are = 787662783788549761 possible names available. And that excludes all the non-standard names that are currently being bid on. Each EOS account currently costs about 0.7 EOS in RAM to create. We will not run out of names.


4

Yes, it is possible. Using cleos you can just run this command: cleos --url https://api1.eosdublin.io get accounts <EOS public key> This will give you a list of account names associated to that public key. Otherwise, you can simply search the public key in https://eosflare.io/ or any other EOS block explorer.


4

The account name is converted into an integer uint64 using the function string_to_name defined in types.hpp file static constexpr uint64_t string_to_name( const char* str ) { uint32_t len = 0; while( str[len] ) ++len; uint64_t value = 0; for( uint32_t i = 0; i <= 12; ++i ) { uint64_t c = 0; if( i < len && i <= 12 ) c ...


4

They are not strings, but rather base32 string representations of the uint64s. That’s why they are limited to 12 chars length and only the characters a-z, 1-5 and . When ever you see the preprocessor function N(something) being called is actually doing the conversion https://github.com/EOSIO/eos/blob/9be89106da1d6a1543eb19dd0f3b96a53e286088/libraries/chain/...


4

You cannot rename (nor delete) an account. Once created an account exists on the blockchain forever (immutability of blockchains and all that, transactions and accounts stay on forever). You could transfer or give away an account that you don't want with this command: cleos set account permission youraccountname owner ...


2

It takes an existing account on the EOS main net in order to create a new one. You can create one using cleos by Block One or if you prefer a GUI interface you can use this toolkit by Genereos.io. Short video guide


2

Will it be public information that ABC created SupportPoliticalCandidate? yes, every transaction has an id named tranaction id, by query the id, everyone can know what happened. If you create another account, YourName, will it be public information that YourName and SupportPoliticalCandidate are related? yes and no. You can use cleos get ...


2

Use eosjs get_key_accounts. See https://github.com/EOSIO/eosjs-api/commit/21675aec294d6f65f3cbace049839751a087676f


2

No, it is currently not working. I asked why in telegram and received no response. I also did a brief search of the issues and did not find anything. You can post an issue on the repo if you like: https://github.com/EOSIO/eos/issues


2

Why was the 12 character limit chosen for account names? Why can't I make a 4 letter account name? As explained by Dan here: Currently EOSIO prohibits the creation of new account names that are less than 12 characters long and/or contain a ".". The purpose of this restriction is to discourage name squatting. Note, however, that name bidding ...


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

You should be able to use get_account


1

There isn't a concept of "alias account names" in EOSIO--account names are unique identifiers, and they all cost the same and have the same functionalities. Accounts cost network resources to store the necessary identifying data and metadata, so there is a RAM cost associated with creating a new account, making squatting names a costly process. Thus, each ...


1

The correct format is: cleos push action myaccount hello '{"person":"0"}' Note: The name of the action is hello, not hi


1

If you know your account name go this site and there is a option called Account Info on the top left corner. Click on that and put your account name. After enter you will find all info , ram and cpu allocation to your account. Now there is a option at top Get accounts transactions history. History. click on history and you will get who created your account....


1

You can use this service which does this periodically for you: https://www.eossnapshots.io/


1

Best solution I can think of is running a mainnet node with --plugin eosio::mongo_db_plugin to get all accounts in a mongo collection. However, by default, the public keys are not stored in the collection, so you'd have to use $ cleos get account <account_name> to find all the keys associated with the account. This is quite time/resources consuming, ...


1

Update: EOS NY Will Pull a Snapshot for you on request and they've also open sourced their code: https://medium.com/eos-new-york/snapshots-as-a-service-airdrops-for-all-2bd51548b1ac https://www.eossnapshots.io/ account names/publikeys: You can use a snapshot generator. https://github.com/EveripediaNetwork/airdrop Or you can use one of their snapshots ...


1

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'


1

did you provided the same owner keys for the new account, then just select the new account in scatter or if you are using cleos just load(import) the keys and use new accountname while doing transaction. scatter -> identities -> edit(account)-> select the new account.


1

Have you connected an account in eostoolkit? You'll see 'Attach an Account' in the 'Creator' field on the create account form if you haven't. If not, click 'Connect Account' at the top of the dashboard. This should be the scatter account you wish to use to create the new account. You also need enough EOS in the creator account to be able to cover the ...


1

Not sure about the exact date/time in UTC or any timezone. All we know it is suppose to start after 14 days of mainnet start. If you win the bid for com, you can register any name using: [a-z1-5]{1,8}.com Once you will a premium name suffix (same as traditional top-level-domain), you can register any name for the suffix and sell them or give them away. If ...


1

Normal acccount names Are exactly 12 characters long and do not contain a dot. These can be created right now by sending a newaccount action to the eosio.system contract. Premium Account Names These are less than 12 characters or contain a dot. To obtain the right to create one of those with the newaccount action you must first win an auction for that ...


1

If you want to hack it, GenerEOS has a site that tracks bidding: https://toolkit.genereos.io/names They've also posted their source code: https://github.com/genereos/eostoolkit


1

Here is an example using eosjs@20 const BigNumber = require('bignumber.js') const { Serialize, Numeric } = require('eosjs') const { TextEncoder, TextDecoder } = require('util') const numericFromName = (accountName) => { const sb = new Serialize.SerialBuffer({ textEncoder: new TextEncoder(), textDecoder: new TextDecoder() }) sb....


1

Accounts represent entities or identities and for a normal user or business the number of accounts and their names is likely to be small. If you compare account names to URIs or URLs people will be more interested in short names that are easy to remember or even form a word. Things start to get complicated if you want your account name to be representative ...


1

The EOS account names can easily be used like the Steem ones as well as every other dApp deployed on the main net. Think of it as a global twitter handle across all dApps. Rather than quote a public key when your friend want's to reimburse you for pizza night you can just give him your account name. He can then look up your high score on Space Invaders and ...


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