Hot answers tagged

6

That's the eosjs object that you have in the browser as Scatter requires it to be present to be able to sign EOS transactions. See here: https://github.com/EOSIO/eosjs Eos = require('eosjs') The Scatter documentations are pretty new and are really terse. This should be expanded in the documentation of scatter.


4

const sortedBPs = producers.sort(); await eos.voteproducer(userAccountName, proxy, sortedBPs ); ...Adding a sort and moving it outside the await fixed the issue.


4

dApp's generating their own private keys for each user is not a viable strategy. Users won't want to hold many of the keys as it's stressful and are objectively harder to memorize than a typical username/password combination. A more likely future to the above - but by no means a good solution - would be for users to generate a new public/private key for all ...


3

After searching the official doc and trying different approches I finally got it to work. I've used eos.transaction instead of eos.transfer and the following example is working for those interested: var res = await eos.transaction({ actions: [ { account: "eosjackscoin", //has to be the smart contract name of the token you want to transfer - ...


2

If you use the Scatter Desktop wallet, you can view a list of all of your Blockchain Accounts, and then view the your staked cpu/net, and remaining RAM, by clicking on the "Account" you want to view the details of. Your Identities are stored separately from your blockchain accounts. Here's an example of having multiple Accounts, with one account selected to ...


2

Block.one released the Universal Authenticator Library - UAL a week ago. Here are some helpful links: Medium Article about the UAL UAL Authenticator Walkthrough UAL Github-Repository There are are several different UAL-Repositories + Usage-Examples for use with the different available Wallets. Scattter UAL Lynx UAL Ledger UAL Token-Pocket UAL Meet.One ...


2

As @Ami Heines suggested this can be achieve using async nature of js. So define your getScatter action like this and try to define network in a config.json file like I used async getScatter(PropsValue) { const scatter = PropsValue.scatterObj; const { accounts } = await scatter.getIdentity({ accounts: [config.EOS_CONFIG.network] }); ...


2

The chrome extension is deprecated and unsafe. You should move to the desktop application as soon as possible. In the desktop application, you can simply click on "View Tokens", and it will list all of your tokens.


2

Before you create the account in Scatter, you'll want to add your local testnet's chain ID and API endpoint (probably 127.0.0.1). From there, you can import your keys and create an account while setting the local testnet you just added as the chain of choice. Select New Network top right


1

Probably the best tutorial is to take a look at the Universal Authenticator Library - UAL and how it works. Here are some helpful links: Medium Article about the UAL UAL Authenticator Walkthrough UAL Github-Repository There are are several different UAL-Repositories + Usage-Examples for use with the different available Wallets. Scattter UAL Lynx UAL ...


1

Both scatter extension and scatter desktop are client side applications. End user is the only authority to decide whether scatter automatically sign the transaction without asking every time. If the user trust your contract then he/she can set the contract in whitelist so that, all signing request from the same contract will be done automatically without ...


1

For the user, Scatter has "Enable Whitelist". You agree to the prompt, then check the boxes for the fields that are allowed to change. And then you are never asked again, unless you manually remove the whitelist entry. Here is an article from Scatter author about whitelist permissions.


1

After searching the official doc and trying different approches I finally got it to work. I've used eos.transaction instead of eos.transfer and the following example is working for those interested: var res = await eos.transaction({ actions: [ { account: "eosjackscoin", //has to be the smart contract name of the token you want to transfer - ...


1

I suspect you have a timing issue in your code. The javascript code is non blocking and runs in a strange order for programmers coming from a different background. You are calling getIdentity above but the code keeps on running and trying to use the scatter.identity.accounts without waiting for the result of the call to getIdentity. Move the line of code ...


1

Scatter founder, Nathan James, made a post explaining why he created Scatter Desktop and Scatter Mobile instead of continuing his focus on the web extension. The post is quite detailed; here's an excerpt that summarises some of his thoughts: After almost a year of deep shower-thought contemplation I came to the conclusion that an extension wasn’t working ...


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

You can use the key pairs section in your scatter extension:


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