See bytemaster's answer:
EOSIO supports the R1 elliptic curve which means every iMac Pro, MacBook Pro, iPhone and iPad can use the secure enclave as biometric secured hardware wallet. The same R1 curve is used on many smart-cards and Android devices.
UPDATE: Ledger Nano S now supports EOS
I will update this post as more information becomes available.
This answer probably will change over time, but you should be able to find a list of wallets on:
Currently listed are:
// disclaimer: I am creator of eosprojects
EOSIO supports the R1 elliptic curve which means every iMac Pro, MacBook Pro, iPhone and iPad can use the secure enclave as biometric secured hardware wallet.
The same R1 curve is used on many smart-cards and Android devices.
To reset your chain data on a local testnet you should:
Stop your node
Delete the blocks and shared_mem folders which you can find under:
Mac OS: ~/Library/Application Support/eosio/nodeos/data
Deleting the wallets and imported keys information is a separate and independent step (you don't need to reset your chain, ...
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.
If you are running a pure Web-Portal like an Exchange this maybe the way to go. You would kind of ...
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 ...
How do I find out the keys for the eosio account?
The keys for the eosio account are in config.ini; this is what you find in the docker container by default, for example:
signature-provider = EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV=KEY:5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Do we need to import eosio into a wallet for normal ...
An account can have a smart contract associated with it, as well as having tokens stored in it, and staked tokens.
A wallet is just a way to access an account. It contains the public and private keys for accounts.
When you create a wallet, it automatically creates a password for accessing the wallet.
When you create an account, a public-private key pair ...
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 ...
Q1/2. Don't connect to an API when dealing with private keys. It is completely unnecessary, and I don't think it will do anything anyway. Wallets are made to be locally stored, not on chain, so I would recommend --wallet-url localhost:8080 (8080 as nodeos comes pre configured to 8888). You can configure this in your wallet's config file or set the flag ...
The keosd wallet daemon has an option to set the wallet directory.
--wallet-dir arg (=".") The path of the wallet files (absolute path or relative to application data dir)
If you have the wallet plugin enabled in nodeos, the same parameter can be used for it to set its wallet location as well.
Among other things EOS.CYBEX claims they will launch the world's first hardware cold wallet for EOS.
They state on their home page, linked, that "transactions happening on EOS are rather big in data volume, which will translate into a problem in embedded devices like hardware wallet, for the length of signature accounts hugely for hardware storage capacity."...
I have bought some eos on Binance. Now i m looking a way to create a wallet on eos mainnet in order to get my eos from Binance. But There is no simple way and decentralized information about HOW to create a wallet and account.
Please confirm Binance are allowing withdrawals and that they aren't offering an account creation service.
Accounts can only be ...
Here's the list of Wallets that support EOS:
Personally, I use Exodus and Scatter
The community believes that there will be an official EOS Wallet when the main net launches, but you can currently use Exodus and Scatter for the main net as well.
Here you can see the work of the official EOS Wallet:
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 ...
As far as I know, it is not. But your question is reasonable. The wallet has only a master key, so you should be able to enter the master key first and enter a new one.
This key is not used for signing transactions, but for opening wallets only.
Even if it is not now, it seems to be a possible function in the future. It would be nice to have eos github as ...
What I did to get eos working on an AWS free tier instance was I temporarily opened up a large ubuntu instance with enough RAM to install it, and I ran the install. Once it was done you can scp the eos/build directory to a free tier AWS instance and that's all you need to run nodeos/keosd/cleos.
First of all you should create a account on jungle testnet, you should also have a wallet already created in your system, in my case wallet path is:
after that you have to link you wallet to your account , if your keosd running port 8900 you can do like :
make sure you store your keys in secure location
private_key = "...
Either indicate a file using "--file" or pass "--to-console"
You need to specify the location to write password output to:
$ cleos wallet create --to-console
$ cleos wallet create -n <wallet-name> --to-console
See the dev documentation:
-n, --name TEXT - The name of the new wallet -f, --file TEXT - Name
of file to write wallet ...
I personally like EOS Lynx (unsecure link) because of the user friendly UI, and a UX that I'm used to. Supports Android and IOS. They also support an array of options, such as creating an account, or importing existing keys into an account.
I used the eosjs library to generate eos keys by providing a text string.
I have this integrated into my brain/paper wallet generator:
Just type in a user / pass combination and it will always generate the same keys. The generation is time and memory intensive to prevent brute force guessing.
Yes, multisig is natively supported in the permission model of EOSIO. There used to be an article in the official documentation in previous versions, but there doesn't seem to be a page on this yet in the v1.3.0 docs.
However, it is quite straightforward to enable a multisig mechanism on an account. For instance, for a multisig account that requires 2-of-2 ...
It's not because of the "wallet eosio", but you didn't specify the creator in
cleos create account demoaccounteos EOS58wkLHPuYfX8jpvEYZi6PviCkk7v4bBQSU2sa8WJvJtXWa7XBX
The create account usage is :
cleos create account [OPTIONS] creator name OwnerKey [ActiveKey]
It's just lucky eosio is a system predefined account,and you can run this without a "...
No, you don't need to create a wallet for each node. It does not communicate with wallet at all.
You should set producer-name and signature-provider options for each block producing node. You need to create an account with the producer-name and set a pair of private and public key for sigining produced block. These keys don't need to same to those of owner ...
You are correct in that you need to create a wallet on inita node as well as on the genesis node.
Actions can only be pushed to the blockchain from a location where the private key is accessible. The most common way to do this is to store the private key in a wallet and then unlock that wallet before pushing the action to the chain.
You set up a wallet and ...