william3johnson/eos-transit-demo-multipass

Example for handling multi-wallet/chain/account/device sessions using eos-transit

eos-transit-demo-multipass

This demo is a developer focused example to help show how eos-transit can be used to create EOSIO applications supporting multiple chains, wallets, accounts, and devices. It was created using the create-react-app generic boilerplate and also includes eos-transit and the providers eos-transit-anchorlink-provider and eos-transit-scatter-provider.

To run the demo, you'll just need to clone down this repository and run:

yarn install --frozen-lockfile
yarn start

The demo will launch in your browser in a local server.

You can also view this demo live at the following URL:

https://greymass.github.io/eos-transit-demo-multipass/

Documentation

The code itself is documented and the bulk of the implementation can be found inside ./src/App.js. If you read through this code, you should be able to understand exactly how to instantiate anchor-link with the browser transport, and create ESR protocol requests.

Signature Provider Support

This demo has been confirmed to work with:

• Anchor Desktop (1.0.0): https://github.com/greymass/anchor
• Anchor Mobile (0.1.0): Unreleased, beta testing in progress.
• Scatter: https://github.com/GetScatter/ScatterDesktop

It should work with any signature provider/wallet that integrates with eos-transit.

Testnet Support

The current test networks are defined in ./src/assets/blockchain.json. Additional networks can be enabled by adding new definitions to this file.

The logos for each network are also located in ./src/assets, and are defined in ./src/Blockchains.js.

Further reading

For more information about the technologies involved, please refer to:

• eosnewyork/eos-transit
• greymass/anchor-link
• greymass/anchor-link-browser-transport
• ESR (EOSIO Signing Request, EEP-7) Specification

Communications

Feel free to join us in telegram to discuss this or ask questions:

• https://t.me/anchor_link