Hot answers tagged

10

A public key, by it's very nature (and definition) is safely exposable online. This is what you would send someone if they were going to pay you in EOS. The same concept is true of any crypto currency. To verify if your EOS are registered you only need your ETH public key. You can safely input your ETH public key on this site (left side: TOKEN REGISTRATION) ...


9

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


7

Yes. EOS keys use a Base 58 encoding where uppercase and lowercase letters have different values.


6

To change the owner key, you can use this command: cleos set account permission account_name owner EOS_public_key_of_new_owner -p account_name@owner Multiple owners on an account is essentially a multi-sig account, it's possible and it's described here Accounts and Permissions As a concrete example, to configure two keys to the owner group of an account ...


4

This depends strongly on your application. The web approach maybe more comfortable for the user but will put you and your application in certain responsibilities and risks. From my understanding you have at least this three possibilities. Possibilities: Web Only If you are running a pure Web-Portal like an Exchange this maybe the way to go. You would kind ...


4

Private keys are very confidential information and they need to be stored somewhere very safe where only the owner can access them. But, if you are storing them at your side even after encryption you can always access them because you have the access to your local DB and you know what algorithm you used to encrypt that so you can easily decrypt the keys and ...


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


3

I would reconsider this approach because it is possible to expose your/the users private key if you rely on a thrid party to create the key. Even if the third party behaves correct, due to transmissions you were also likely to be exposed to middleman attacks. Also currently there is no RPC call for safely creating key-pairs via 3rd party available.


2

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


2

The following command removes a keypair from an opened, unlocked wallet: cleos wallet remove_key -n wallet_name --password passwd public_key where wallet_name is the name of your wallet, passwd is your wallet password given to you by the "wallet create" command, and public_key is the public key of the key pair you'd like to remove from the wallet. If you ...


2

When you run nodeos, the RPC is start on the port number 8888. You can generate new keypair by following method: Note:- Creates a key within the specified wallet, wallet must be opened and unlocked. Parameters are: 1.name of the wallet to create key in; 2. type of key to create, currently that support two values: K1 and R1 Run following command in ...


2

Whoop, turns out it was "SIG_K1_" + base58check(65 bits of the signature) Getting the proper 65 bits is another headache for now, but yeah


2

no you will not have lost your tokens. It takes 3 days to unstake your tokens, after that they should go from "refunding" to "available". Things to note are: If you unstake again before the current unstake is finished, then the refund timer will be reset to a 3 day wait. Sometimes, the money is unstaked but the "refund" action to convert them to liquid EOS ...


2

You can go to eostoolkit to do that. Enter the public key you'd like to keep, set owner as parent, your account name, then keep the threshold at 1 and sign the transaction. Remove a permission Specify the Permission and Parent, and leave a single Authority row empty with the default Weight of 1. Link: https://eostoolkit.io/account/advanced


2

Testing with v1.5.1, adding a new permission to an account (set account): Corresponding contract action: updateauth RAM: 32 bytes NET: 185 bytes CPU: 320 time for set action permission: Corresponding contract action: linkauth RAM: 144 bytes NET: 127 bytes CPU: 664 time Important to know: Ram usage is about using the storage, that means if update a ...


2

No. Owner can change active but active can't change owner.


2

When storing in keosd, you can take preventive action to keep the keys out of your console's logs. Also, you can sign transactions in a cold-storage way so that you're only broadcasting the signed transaction. Not sure what you mean by bad user experience on Scatter, I think it's the bee's knees. Why would you want to generate the keys yourself? I wouldn'...


1

Use eosjs-ecc or eosjs-keygen to generate key pairs.


1

On first glance, you can transfer a token only to a recipient account. A key can control multiple accounts, and an account can have multiple keys. However, the "transfer" can actually be tied to account creation. There are smart contracts which, given some EOS, a public key and a new account name, create an account with that name, buy RAM for it, and stake ...


1

Steemit currently has a similar functionality, I would look at their coding, as it will be very similar to EOS. Specifically in steemit see: https://steemit.com/steemit/@adept/tutorial-how-to-sent-and-recieve-private-encrypted-messages-on-steemit


1

You can add as many key pairs as you want. This is the unique conept in EOS by using which you can maintain the permissions for your different actions defined in contract. You can assign different key pairs to different actions by setting special permissons. Use set permission command to assign a particular key pair to execute a specific action in your ...


1

The problem is due to the Docker Quickstart tutorial. In short, the files are inside the Docker Container running the eosio instance. To find the files inside the docker do the following: Find the path to the wallet: There might be better ways to do that, but the way I did was reading eosio logs running in one terminal docker logs --tail 10 eosio -f ...


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

Mnemonic is a standard of bip39 for you to manage all chain private keys with a single master seed, so it's just a method to generate the private key, you can specify any private key you'd like if you don't want to use that standard.


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