10

There are a few ways to setup EOS ACCOUNT if you don't have one already: Ask a friend that has an existing EOS account owner to create one for you. Use an account generator tool or service https://eos-account-creator.com/ https://www.zeos.co/ Directly off an exchange by using the signupeoseos smart contract. You can do this by sending a recommended 2-3 ...


9

I found it in Dawn 4.0 release, it's simply is_account(account_name) Check out the eosio.token new contract in transfer action, release: https://github.com/EOSIO/eos/blob/dawn-v4.0.0/contracts/eosio.token/eosio.token.cpp#L76 eosio_assert( is_account( to ), "to account does not exist");


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


9

There's not a command to create an account on EOS chain out of a "thin-air". To create an account we always need a "parent" account which will create the new one. So, if you want an account, what will happen is that some applications will have create an account for you upon signup. From whitepaper: In a decentralized context, application developers ...


8

Looks like I found the answer I was looking for. cleos set account permission accountname active '{"threshold": 1, "keys": [{"key": "NEW_ACTIVE_PUBLIC_KEY", "weight": 1}]}' owner When having weight 1 you can simply use this alias instead: cleos set account permission accountname active NEW_ACTIVE_PUBLIC_KEY owner -p accountname@owner After, you can check ...


5

NET bandwidth is the amount of space in the blockchain log consumed. RAM is the amount of space in multi-index containers CPU is the wall-clock time consumed as measured by the producers when the execute your transaction.


5

This issue is discussed Here on GitHub by Dan and also in his development update a few months ago The general concept is that every account will have three special permissions: owner, active, and recovery. You will be able to choose recovery partners you trust (friends/family) who will be able to update the active authority and grant you access back into ...


5

It won't. I spoke with Dan about this recently and there is no intention to prevent name squatting. However, you cannot use a name to defraud someone so your squatting might be speculative but it cannot be fraudulent, or you'll be taken to Arbitration for violating the Constitution. Details of the naming rules are here: https://github.com/EOSIO/eos/issues/...


5

There's a new intrinsic in the slim branch, but isn't declared yet in a header. extern "C" int64_t get_account_creation_date(account_name account); It looks like this function will fail if the account doesn't exist.


5

There are basically two steps you need to do. First you create a new account permission and then you give it the authority to use voteproducer action on eosio contract. As a prerequisite for this instruction I expect that your account's active key is stored in a cleos wallet and the wallet is unlocked. 1. Create new account permission For the new ...


4

Before you start You need to generate 2 sets of private and public keys, 1 for the active permission and 1 for the owner permission. If you have access to cleos, you can do this with the following command: cleos create key --to-console Various wallets also offer the option to generate private and public keys. The private key you should keep safe and ...


4

The full text of Name Squatting section in the Dawn 4 release notes is as follows: Due to the limited development time between now and the release of version 1.0 of the EOSIO software, we are going to recommend that all account names be forced to 12 characters and not contain any ‘.’ characters. The community can then upgrade the system contract (...


4

If the system contract isn't running, then accounts don't need to buy ram or stake resources. cleos create account works in this mode. If the system contract is running, then accounts need enough ram to hold the account information. They also need staked resources to cover any transactions they sign. cleos system newaccount takes care of these issues.


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

After some research, account cannot be deleted.


4

Bios sequence tutorial (Deprecated Wiki) explain these well - eosio.token, eosio.msig. The remaining accounts are described below. all RAM trading fees sent from user to eosio.ramfee all proceeds from selling RAM sent from eosio.ram all staked tokens sent to eosio.stake all unstaked tokens sent from eosio.stake all auction proceeds sent to eosio.names ...


4

I ran into the same problem. So I developed my own solution. You can try it out by visiting https://namevault.co. The dApp lets you create an EOS account without having any EOS, existing keypairs, or bribing a friend with an account. The entire process is easy to use and takes about 60 seconds. Additionally the fee markup is minimal (offsetting for ...


3

Yes, you can. Original fff account's owner key and active key are EOS4zQiTie***tBQ4. bob@bob-VirtualBox:~/eosio-wallet$ cleos get account fff permissions: owner 1: 1 EOS4zQiTiebtvcQqUe1t2Bkn4aLZcdRWR5NcqAZ4bsXxHyBP1tBQ4 active 1: 1 EOS4zQiTiebtvcQqUe1t2Bkn4aLZcdRWR5NcqAZ4bsXxHyBP1tBQ4 memory: quota: unlimited used: ...


3

when someone create an account it will be propagated to all BPs and then be stored on blockchain comprising with 2 public keys. In EOS eco-system user has only one way to transfer EOS to each other via Account Name so logically and technically it can't be deleted.


3

cleos create account is for boot purpose, several accounts MUST created first before deploy eosio.system contract. See more. eosio.bpay eosio.msig eosio.names eosio.ram eosio.ramfee eosio.saving eosio.stake eosio.token eosio.vpay And cleos system newaccount is a normal way to create account, it is call 'action' (same like function) of ...


3

You can do that by simply running cleos get account youraccount, also you can check it out in https://eosflare.io Finally, if you want to have a better understanding about EOS RAM and Bandwith check my study here: https://steemit.com/eos/@leordev/eos-ram-and-bandwith-analysis-airdropping-steps-on-junglenet I hope it helps you!


3

You can simply request a node to give you the action history of an account. Using cleos: cleos --url https://api1.eosdublin.io get actions <EOS account name> Using eosjs: const eosjs = require("eosjs") const eos = eosjs({ httpEndpoint: 'https://api1.eosdublin.io', chainId: 'aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906' }) ...


3

Of course, eosjs provides method getActions. Here's an example: const Eos = require('eosjs'); const api = new Eos({ httpEndpoint: 'https://eos.greymass.com', chainId: 'aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906', }); api.getActions('wangruixiwww').then(console.log); You can send direct request to some API like this https://...


3

My doubt is, what are the consequences if someone leaves his/her wallet unlocked for a while? The wallet is just a software that doesn't communicate with nodeos directly. If you have your wallet unlocked, then someone who has access to your machine can list your keys (by default, listing private keys in an unlocked wallet still requires the password) and ...


3

You can buy more RAM for your account xxxxx: cleos system buyram xxxxx xxxxx "10 EOS"


3

I believe this project by NSJames might be able to help you. https://github.com/nsjames/Account-Has-Code I believe the idea is an existing contract you can ask if another account has code on it or not. See the example to see how you might be able to implement it.


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


3

The permission that you would set your account to would not be a key, but would instead be the account eosio.null@active. This is a special permission that can not be used by anybody ever (it has no associated keys and therefore can not be hacked). Note: This permission is implementation specific, so whilst it exists on the EOS mainnet, it could be that it ...


2

As I can not comment yet due to the low reputation as I made the account recently, I have some queries related to your problem. You are running cleos command at port 8899 whereas you did not mention the port 8899 while starting the blockchain. It might have set the default port 8888 which might be the reason of failing this command. ./keosd --data-dir data ...


2

So you always have to stake something to have the account: First check that the creator account (e.g. accname1) has funds... ./cleos.sh get currency balance eosio.token accname1 ... and the output might be something like... 832.5970 EOS ...and then check what NET and CPU accname1 has remaining: ./cleos.sh get account accname1 e.g. privileged: false ...


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