Hot answers tagged

5

The sender_id is just a value set by the contract that sends the deferred transaction so that later operations can refer to the same transaction. The semantics are: sending a new transaction with the same sender_id as one in-flight will replace the in-flight transaction canceling a transaction can be achieved by passing that sender_id into cancel_deferred ...


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


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.


3

This is a dynamic and constantly changing list and you need to find some sources for it and keep your system updated with it. Here is one place I found that lists some of the BP endpoints. Also, note that you don't have to rely on BPs for this service. You can set up a witness node and filter it to sync and listen on the info relevant to your application. ...


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

You can create a nodejs app (for example) that watches incoming blocks from EOSIO. Probably would be a good idea to create a 'cache' database for more streamlined "reading" not to query the eosio node every time. Your nodejs app can have socket connections available for your end users.


2

That's a really good question. Blockchain development is awesome but we have to find ways to build great experiences around it. We're asking the same type of questions as we're building our Carmel product (carmel.io) and the way we're implementing this is by building a hybrid architecture, using EOS, Ethereum, AWS Lambda and Firebase on the backend and React ...


2

As long as the EOS nodes are open source, we can always create plugins for it in C++. So I think it's a good idea to create a plugin that enables the running node to serve websockets connections in a pub/sub fashion. (Not sure EOS Core team already have plans or are building that)


2

If you want a websockets API that streams current blocks, but also past blocks, and allows you to filter actions, but also table changes.. check out https://dfuse.io .. just released!


2

According to the responses in this GitHub issue, the mechanisms that are meant to mitigate this issue are as follows: There's a maximum cpu time(30ms) for every transaction. If a transaction failed, it will not be broadcast to other nodes, which means that hackers can only exhausts one see node rather than the whole network. greylist feature ...


2

You can check balance using account name. Check out get_currency_balance endpoint Balances are specific to a smart contract. Use eosio.token as code parameter for a system smart contract polling. You can left symbol parameter empty to poll all the tokens. Also you can get account names from public key using get_key_accounts endpoint


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 should be able to use get_account


1

Most of the listed API end-points in EOSDocs.io is not enabled with history plug-in. So actions like get_transactions and get_actions are not possible. I found https://public.eosinfra.io is working to date for history actions


1

I think you are confused with account_name. Here, I can see two different names gy3dgnbsgige and eosblackteam. So, make sure you are using the correct account name which you created by using cleos create account eosio <your-account-name> command. By looking at this error Exception Details: unknown key, I think gy3dgnbsgige is not your account name. ...


1

First of all I would recommend upgrading your client to match the version of the servers, since there could be a mismatch in the format or structure of the data passed around or something like that. Secondly, how are you specifying the host? This might also depend on your version of cleos, but if you're using a recent version, you would need to use ...


1

Update: EOS NY Will Pull a Snapshot for you on request and they've also open sourced their code: https://medium.com/eos-new-york/snapshots-as-a-service-airdrops-for-all-2bd51548b1ac https://www.eossnapshots.io/ account names/publikeys: You can use a snapshot generator. https://github.com/EveripediaNetwork/airdrop Or you can use one of their snapshots ...


1

Yes you can query that api end points as i have performed query on this api from https://www.eosdocs.io/resources/apiendpoints/ with post parameter {"public_key":"EOS6M1m2KBk8BF6uwEnRyjXvpBTUxqLfMUZALzsUGtrHvcEHTYFi1"} and api url is https://eos.greymass.com:443/v1/history/get_key_accounts I am not sure but i think this can be done by eosjs also. Here ...


1

@gustavomick , I think the issue is with the way you pack key256 in checksum256_to_sha256 I tested your code with static key256 checksum256_to_sha256(const checksum256 &hash) { const uint128_t *p128 = reinterpret_cast<const uint128_t *>(&hash); key256 k; k.data()[0] = p128[0]; k.data()[1] = p128[1]; return k; } And it worked ...


1

cleos get table testtesttest testtesttest hasher --index 2 --key-type sha256 -L 45d944598dccadd8c5a56e29c9786f05fa4b23402b735de61ce2912c86bac4de This command giving you 3 rows because of usage of scope. Here i am assuming deployment account is testtesttest so scope declaration may be like this table_name taba(_self,_self.value). that's why it gives you ...


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

You can use the get_actions filter on a Websocket connection and keep that running, and trigger things on your side with the https://dfuse.io API.


1

EOSTracker is a block explorer that stores actions for users and also provides an API.


1

Technically yes. Examle: a wallet can you only EOS and no backend. But in reality most probably you will need some backend.


1

Short answer: there is no free, open-source honey. You can start with small EC2 instance on Amazon AWS (even with "free" one) and scale up when you need it. So you will not pay a ton until you actually have some load.


1

It seems like retrieving transactions from an account works through get_actions but apparently, it doesn't show any data on the testnet, for people having this problem. Try check it on the mainnet.


1

You can also use demux to watch for blocks that contain the actions you are interested in, then using websocket to push the data to your application


1

Here is example: i want to check token with this account name "bitfinexeos1" I should check it with each contract name : eosio.token, eosadddddddd, eosdactokens, eoxeoxeoxeox ... from the link https://raw.githubusercontent.com/eoscafe/eos-airdrops/master/tokens.json ─$ cleos -u https://mainnet.genereos.io get table eosio.token bitfinexeos1 accounts { "...


1

Attually, they have a list token name with token'account. You can refer here: https://raw.githubusercontent.com/eoscafe/eos-airdrops/master/tokens.json


1

The action's ABI describes how to encode it. e.g. here's the newaccount ABI: { "name": "newaccount", "base": "", "fields": [ {"name":"creator", "type":"account_name"}, {"name":"name", "type":"account_name"}, {"name":"owner", "type":"authority"}, {"name":"active", "type":"authority"} ] } account_name is an alias for the built-...


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