Anchor is the evolution of the wallet we've been working on since EOS launched: eos-voter (aka "Greymass Wallet"). Fuel is the first iteration of our idea on how to best deal with the current resource situation on EOS while waiting for changes to the network itself. These two products now work together to help EOS accounts use the network while they may not have enough CPU/NET themselves.
In order to use Fuel in Anchor, one condition must be met: you must use our API endpoint at
https://eos.greymass.com. By default, Anchor uses this API endpoint, so if you haven't changed it in the past Anchor is probably already using it. If you run into problems with Fuel not working and would like to check the API node, instructions are provided in the next section.
Using Fuel itself is incredibly simple, it just needs to be enabled using the Fuel logo in the upper right. It can also be disabled from the same context menu. Once enabled (and after you start using Fuel), this menu will also display the quota you have available and how much you've used of your daily quota.
You can tell if Fuel is enabled if the logo is colored, and it will be black and white when disabled.
That's it, Anchor now uses Fuel. While Fuel is enabled, any transaction you perform in the wallet (or using the EEP-7 signing protocol) will have its resource costs covered.
Fuel is designed to give every account 5ms worth of free transactions, per day. This is typically enough to perform a couple transactions. To give you a sense of how much different transactions use, here are some ballpark estimates of some typical transactions:
We are designing Fuel to be a solution to replace the need for users to stake their own EOS, similar to the design goals of how REX operates. Soon users will be able to spend EOS to purchase resource usage quotas within Fuel, which can then be used on-demand whenever the user wishes to perform transactions. Keep an eye on our social media and/or blog for updates when this becomes available.
To double check if you are using this API, you'll use the "Manage Blockchain" feature, and click the gear icon on the EOS blockchain. Then check the "Default node" field to ensure it is using the appropriate API. The animated gif below shows how exactly to check and where to find this information.
For those who already use eos-voter, we set out to make the migration process to Anchor as simple as possible.
Both applications are installed separately, meaning you can have both eos-voter and Anchor installed to the same computer without the risk of one overwriting the other. You can even run them at the same time since they both use their own configurations. If one works better for you, you can continue on using it while we continue to improve Anchor. At some point we will stop updating eos-voter completely, and encourage everyone to make the transition to this new wallet.
To move your accounts and settings from eos-voter to Anchor only requires creating a backup and then restoring it into the new application. To do this, you would:
You may be prompted to "Upgrade" your wallets, which simply requires entering your existing wallet password (from the backed up wallet). Once this is complete, your new Anchor wallet will be completely setup with the same accounts and settings you were using in eos-voter.
If you have questions or want to keep up to date with what's happening with Anchor, Fuel, or Greymass in general, feel free to use one of the methods below.