9

This is a very subjective thing. Personally I would recommend to learn React with Redux. Here is a little Tutorial The main advantage is that you can use React for the visual representation und decapsule it from the application logic which is build with Redux. Other stuff to look at would be Angular 4 (visual Framework) Vue (visual Framework) and maybe ...


7

You have several ways to retrieve data from eos chain as i know. They differs a lot, so you should find a better one for you case. #1. Get from table As you noted there is getTableRows method in eosjs lib, and by default it returns packed response. You can pass option json: true to instruct library to unpack response for you. eos.getTableRows({ code:'...


7

Just add the below param to your config file: access-control-allow-origin = "*" Or you can even run the nodeos command with this parameter, check mine: nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin --access-control-allow-origin "*" --access-control-allow-headers "*" --access-control-allow-credentials true


6

I think the best examples lives in Scatter-Demo repository: https://github.com/EOSEssentials/Scatter-Demos I have also built MonsterEOS where you can check another interaction with EOSJS and Scatter: https://github.com/leordev/monstereos


5

I heavily use eosjs with Vue.js+Vuex, it is much more developer friendly and easier to learn than React when you want to scale. The first EOS browser extension, Scatter, also uses Vue for the frontend very effectively, so does Bloks.io(best EOS block explorer with wallet), BetDice(biggest probably fair EOS gambling site) and many more.


4

There is a system contract for voting. It can be found here: https://github.com/EOSIO/eos/blob/master/contracts/eosio.system/voting.cpp ABI can be found here: https://github.com/EOSIO/eos/blob/master/contracts/eosio.system/eosio.system.abi You can run a cleos action command for the system contract: cleos push action eosio voteproducer '["voter", "proxy",...


3

Of course, eosjs provides method getActions. Here's an example: const Eos = require('eosjs'); const api = new Eos({ httpEndpoint: 'https://eos.greymass.com', chainId: 'aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906', }); api.getActions('wangruixiwww').then(console.log); You can send direct request to some API like this https://...


3

You can simply request a node to give you the action history of an account. Using cleos: cleos --url https://api1.eosdublin.io get actions <EOS account name> Using eosjs: const eosjs = require("eosjs") const eos = eosjs({ httpEndpoint: 'https://api1.eosdublin.io', chainId: 'aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906' }) ...


3

Basically nodeos is providing a REST interface which you can query and use for blockchain communication. You just need an address for your local or a public nodeos endpoint. However this is getting even easier with eosjs. This can be found here. You can install it via npm and import/require the library in your code. Then you can access the blockchain data.


3

Yes, it is possible with eosjs. You can create an instance of Eos with a given config and then do getTableRows with the given parameters. You might find the api footprint here. Also check the github repository for more info about the config parameters. Here is an example how I do it at EOSIO BP alarm: eos = new Eos(config) eos.populateBlockProducers()....


3

Call voteproducer.. > eos.voteproducer() CONTRACT eosio FUNCTION voteproducer PARAMETERS { "voter": "account_name", "proxy": "account_name", "producers": "account_name[]" } EXAMPLE { "voter": "", "proxy": "", "producers": [ "" ] } Lookup your account name using your EOS Claim Key. This is one tool for the job: ...


2

Like Patrick said you need to build a front end to communicate with smart contracts on the eosio blockchain. Here a couple of library's to get you started. I have seen a few others as well. Just search eosio on github and look around, there is always new libraries and boilerplates popping up. https://github.com/EOSIO/demux-js https://github.com/EOSIO/eosjs


2

I guess the problem lies in the this.test allocation, because the result of your eos call is this.test, which is likely to be a promise. If you have Babel installed or ES6 support you can use an arrow function: eos[camelCase](action) .then(response => { console.log(response) }) .catch(error => console.log(error)) Otherwise you can try ...


2

xxd make a hexdump or do the reverse -r revert, convert hexdump into binary -p output 'plain hexdump style' sha256sum compute and check SHA256 message digest -b read in binary mode Here the combination of -r -p options for the xxd command will read plain hexadecimal dumps without line number information and without a particular column layout ...


1

You need to authorize the transaction with signatures for both accounts. 1. The ressource-paying-account and 2. the acting account. Assuming that lionstester1010 should pay for the transaction but lionstester1011 is the acting account/the sender of the token: actions: [{ account: 'eosio.token', name: 'transfer', authorization: [{ actor: '...


1

There was an opened issue in the repository. It was fixed today. You can get the updated eoslime code from the development branch. The fix is going to be uploaded on master branch and npm through the next week


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

Create front end and make it interecting with contract using eosiojs


1

eosjs team confirmed, question could be closed now. https://github.com/EOSIO/eosjs/issues/152


1

I think the idea is that you create a web front end using react. The user probably doesn't ever see there is a contract or even blockchain behind the webpage


1

Create a non producer node and then to connect it to net, You can follow this link to understand: https://steemit.com/eos/@fundurian/learning-diary-connecting-to-eos-mainnet This tutorial helps in connecting to mainnet, if you wish to connect to testnet you can follow the same steps as mentioned in the tutorial. But, modify config.ini for nodeos and genesis....


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

BlockIndexState, is a mongoose defined schema, where dapp know about the processed blocks, Demux watch the node block from particular defined block[ eg:153343 https://github.com/EOSIO/demux-js#example, check NodeosActionReader ] block and store the state of block that being watched and continue from that point. async updateIndexState (state, block, ...


1

The EOS code uses fcbuffer to pack the transactions. Once packed, the packed data is combined with the chain ID and the Context Free Data to generate the signature. Specifically, the chain ID, packed data, and hash of the context free data are concatenated then run through the hash function. Once the hash is generated, it can be signed by the private key. ...


1

node_modules/eosjs/lib/schema/eosio_system.json helped me. In case it's not one of the most used ones, I just return the whole object


1

In EOSIO, The block_num_hint argument is optional, and it represents the block number where the transaction should be. This can help find the transaction by fetching just one block when not all history is known. How can I get the block_num_hint In most cases you won't know the block in which the transaction is, but if you happen to know or have an idea ...


1

The basic EOSJS documentation is found on the GitHub-Page Unfortunately I haven't found any tutorials yet, but here is another good overview for general Information as awesome list. I guess some knowledge about NodeJS, ES6 and Docker would be good as well.


1

The answer to this question is being documented here. TL/DR: Getting the most basic functionality to work is very easy. You only need to export an apply(uint64, uint64, uint64) function in webassembly, which can be easily done in AssemblyScript.


1

I think the answer is: it all depends on your architecture. My preferred architecture is to not have the user private key never. So I'm using eosjs in the UI with Scatter to sign transactions. And my application server receive requests and utilizes EOSRPC endpoints to sign transactions to my contracts with keys being handled by a keosd instance. Now, you ...


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