Hot answers tagged

8

the producers all agree "offline" and then sign a multi-sig message setting the current max block size and total available RAM.


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

There's also a Swift library: https://github.com/ProChain/SwiftyEOS And Go: https://github.com/eoscanada/eos-go


5

We built the Elixir one: https://hex.pm/packages/eosrpc As our project depends on it, we will always keep it updated! Feel free to create issues to report bug, new ideas and any discussion! :)


4

There is an endpoint at /v1/chain/push_transactions which takes a payload that is a JSON array of the same JSON transactions you would send to /v1/chain/push_transaction and returns a JSON array of the results you would get back from the individual calls.


4

eosjs does require chainId, but if it isn't provided directly it will be retrieved from the host endpoint. Api accepts chainId as an argument but if chainId isn't passed as an argument when the api is constructed, Api will fetch it from the host endpoint via JsonRpc. transact() checks to see if chainId is set. If not, it calls rpc.get_info() which returns ...


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.


3

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.


3

Query your account name by publick key cleos -u https://mainnet.meet.one get accounts *publick_key* Query your balance by account name cleos -u https://mainnet.meet.one get currency balance eosio.token *account_name* Query your account info(CPU/NET/RAM) by account name cleos -u https://mainnet.meet.one get account *account_name* Query your refunding ...


3

To get transaction history, you need to hit a node that has that filter installed (otherwise you'll get back an empty array). Here's a working curl request (replace accountnamehere with a real account name): curl --request POST \ --url http://api.eosnewyork.io/v1/history/get_actions \ --data '{"account_name":"accountnamehere","pos":0,"offset":200}' Not ...


2

A java sdk with eos-rpc: https://github.com/adyliu/jeos local signature support like this: Transfer EOS with java Create account with java Create EOS Key with java without RPC Sign transaction offline


2

This is happening because localhost is not relaying the browser's request to the docker container. Run docker-machine ip default to get the ip for your docker container. $ docker-machine ip default 192.XXX.XX.XXX Now try accessing the RPC interface from your browser using the returned ip address: http://192.XXX.XX.XXX:8888/v1/chain/get_info You should ...


2

Yes there is. You can get this data from nodes that are running with the history_plugin plugin. You could use the HTTP API directly as in /v1/history/get_transaction, or you could use cleos: cleos --url https://api1.eosdublin.io get transaction <Transaction ID> You could also use eosjs: const eosjs = require("eosjs") const eos = eosjs({ ...


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

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

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


2

Here is my final code that is working ... Thank you leettamna const { Api, JsonRpc, RpcError, JsSignatureProvider } = require('eosjs'); const fetch = require('node-fetch'); // node only; not needed in browsers const { TextDecoder, TextEncoder } = require('text-encoding'); // node, IE11 and IE Edge Browsers const ...


2

It was an error in the documentation. lower_bound and upper_bound do exist in the source code: struct get_table_rows_params { bool json = false; name code; string scope; name table; string table_key; string lower_bound; string upper_bound; uint32_t limit = 10; string key_type; // type of ...


2

There is no RPC api for create account. But you can implement it using push_transaction api. In eos, only an existing account can create a new account. You can create a new account by pushing some transactions defined in eosio.system contract from an existing account. eosio.system contract is deployed in eosio account. So for creating a new account, you ...


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

Try 'eosjs'. It is official javascript eos rpc library. repository has simple example. https://github.com/EOSIO/eosjs modify defaultPrivateKey = "shlee_private_key", and parameter1 ~ parameter3 to correct parameter name and http://127.0.0.1:8000 to your node api endpoint const { Api, JsonRpc, RpcError, JsSignatureProvider } = require('eosjs'); const ...


1

I ended up using https://github.com/OracleChain/chainkit/blob/master/chain/packedtransaction.cpp. This is my packtx.cpp: #include <iostream> #include <string> #include "chain/packedtransaction.h" #include <QDebug> using namespace std; int main(int argc, char *argv[]) { std::string jsonString; jsonString = argv[1]; ...


1

Answering my own question, The bin data should be generated for each individual json in payload and appended in the actions field as a list. The transaction will then be signed, packed and pushed.


1

I can see your transaction on both block explorers, but eosflare labels it as a hard_fail transaction. Therefore, I assume your transaction exceeded the resources it was entitled to without running into an assert. For reference, according to /libraries/chain/include/eosio/chain/block.hpp there are several states of transactions: enum status_enum { ...


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

it's related to not compiling source code using EOS as core symbol.


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

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 that by following operation using curl. curl -X POST http://127.0.0.1:9999/v1/wallet/create -H '...


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

Most simple way is using Js library for rpc. Alternatively, you can see JavaWrapper (this is old realisation, but I see this)


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