Hot answers tagged

5

There is an article in the documentation detailing how you can setup and run a network with multiple producers, voting, and resource consumption. Excerpt: In this tutorial, we will start a number of nodeos nodes, point them to each other, and eventually vote on a set of producers. All of the nodeos nodes will run on the same server. In the following ...


5

I solved it. The problem was that I was using .wast and you can no longer use .wast you have to use .wasm


4

I'm still seeing the option under keosd -h for help. keosd --version v1.5.0 --unlock-timeout arg (=900) Timeout for unlocked wallet in seconds (default 900 (15 minutes)). Wallets will automatically lock after specified number of ...


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

What you are missing here is the chain ID of the network. Mainnet: aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906 Jungle Testnet: e70aaab8997e1dfce58fbfac80cbbb8fecec7b99cf982a9444273cbc64c41473 It has to be added in the " " field just after the key. Your request for Jungle Testnet should be: [{ "expiration": "2018-10-26T15:30:...


3

The api '/v1/wallet' is from the server keosd, not the nodeosd. You may change the port that keosd served.


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


2

Yes, you can. To create an account in Mainnet, you need to use cleos -u MAINNET_API_URL system newaccount instead of cleos create account, since the back one is for boot or development purpose, you can't create an account in Mainnet in this way.


2

If i don't run keosd and run that command cleos --print-request --print-response wallet list That is the result i get from console that clearly tell me it's not using ip/port but unix socket as a host Wallets: REQUEST: --------------------- POST /v1/wallet/list_wallets HTTP/1.0 Host: /home/user/eosio-wallet/keosd.sock: content-length: 0 Accept: */* ...


2

EOS is very new, things are changing rapidly. Currently the easiest and best way to keep the private keys private is to use a different tool to handle signing of transactions. The easiest and most popular is Scatter. Here are the documentations for it. The user stores his keys in Scatter and there is a suite of functions to interact with it from within ...


2

eosio.recovery contract provide user to recover their account if their owner keys are stolen. For this purpose you need to set a permission ‘recover’ and provide a trusted account for recovery. Now let any one stolen your account keys. If you are an active member of EOS then you must use your account at least one time in a month. So if your keys ...


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


2

You can refer to RPC API document of v1.1.0 which had wallet APIs before. https://developers.eos.io/eosio-nodeos/v1.1.0/reference


2

Try this command cleos -u http://127.0.0.1:8892 --wallet-url http://127.0.0.1:8891 create account eosio eosio.token your_key your_key


1

This method would work, but it would only be as secure as your server, as you would need to keep the private key in plain text format, so anyone who could access the machine could sign transactions. I asked a friend of mine who is a front end dev, he said: Have an oracle listen for on chain tx on irreversible block signal, then it’s just a matter of ...


1

The RPC Api params for all EOS API endpoints are defined in the docs: https://developers.eos.io/eosio-nodeos/reference For example the get account POST request would look like this: var request = require("request"); var options = { method: 'POST', url: 'http://127.0.0.1:8888/v1/chain/get_account', body: { account_name: 'eosio' }, // JSON json: true ...


1

Ans 1: Yes, you have to add this information as it helps in validating and adding the blocks in the blockchain. Ans 2: Yes, EOS has this concept of deferred transaction which lets you execute your transaction after a certain delay. To create a deferred transaction, check out this question. How can I create a deferred transaction?


1

tx signing: Yes. You must use keosd. Yes. So I can better understand your approach, what are you trying to do? I cannot envision a scenario in which you wouldn't want to use keosd unless you're using eosjs in which case you could store and sign with keys in a .env file. keosd is what is used natively to sign the transactions in the request and response ...


1

Wallets: No. There are services that can create an account and pass you the keys. As for signing, yes you need some sort of wallet to sign for you to be secure. If you don't care about security then you could hard code a private key to a .env file and sign with eosjs: https://github.com/eosio/eosjs Idk what you mean by "super wallet". The whole idea of ...


1

According to the release notes of v1.2.0, the wallet_api_plugin has been removed: it is no longer possible to run the wallet_plugin or wallet_api_plugin as part of nodeos. This configuration has not been recommended for many versions as it places private information in the same process space as unrelated RPCs and the execution environment for ...


1

before deleting the wallet stop the wallet using cleos wallet stop -n wallet_name and then delete the wallet i guess this will help


1

Steps to install keosd globally Clone the eos git repository Run eosio_build.sh for building it Run /root/opt/mongodb/bin/mongod -f /root/opt/mongodb/mongod.conf & then export PATH=${HOME}/opt/mongodb/bin:$PATH cd eos/build Run sudo make install Run eosio_install.sh shell script or add keosd into the system path Try running cleos or keosd ...


1

After cloning eos you will find two shell script files first you run eosio_build.sh to install eos and then run eosio_install.sh. eosio_install will add all programs of eosio in the system path so you can access eosio programs anywhere regardless of their locations. eosio.cdt is provided only for contract related stuff. So running keosd has nothing to do ...


1

I have solved it. What I found is, keosd is running somehow in the system. Find it and kill it. Try the commands below Find PID of the running keosd process ps -ef | grep keosd Kill it kill -9 pid //replace 'pid' with value returned by the first command Run keosd in a specified port(8900) keosd --http-server-address=127.0.0.1:8900 Also, make sure that ...


1

A packed transaction is one where the transaction structure is converted from the JSON format into a packed binary format. In the C++ code in EOS, this is done using Boost. The abi_json_to_bin method is used to pack smart contract method arguments into a packed format. Packing a transaction uses a similar process.


1

I believe you have followed EOSBlock/EOS-Tutorials documentation. If so then you have to add the chain ID into the payload of sign_transaction. [ { "ref_block_num": 246190, "ref_block_prefix": 1753012779, "expiration": "2018-05-24T15:30:32.000", "actions": [ { "account": "eosio.token", "name": "transfer", "...


1

Maybe you will copy keosd from docker, and put it in the same directory of cleos. When call cleos to interact with wallet, keosd will be launched by cleos.


1

OP found their answer, but to give a slightly different answer, keosd was never recommended for accepting external connections. Using it locally is fine, but once you start making API calls from a machine external to your local network, things can get ugly, as keosd wasn't designed with this type of security in mind. In other words, your keys may be ...


1

I found the answer by trying various things posting this answer as a help. So everyone can view this. Ok that is true that wallet_plugin has been removed from the nodeos but kleosd is still using that and we can still perform any rpc of wallet operations suppose your keosd is running on the port 9999 and you want to create a wallet using rpc call you can do ...


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