Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add provider for trezor #22

Open
cryptosig opened this issue Jun 10, 2019 · 3 comments
Open

Add provider for trezor #22

cryptosig opened this issue Jun 10, 2019 · 3 comments

Comments

@cryptosig
Copy link

Hello, the latest version of the Trezor firmware has support for EOS, and is compatible with CLEOS. What is the best way to integrate a provider with transit?

@WarrickFitz
Copy link
Member

Thanks for creating the issue. I wasn't aware that EOS was now available on Trezor. I'll get a device and see what needs to be done to add support.

@WarrickFitz
Copy link
Member

Order placed. Should have a device before the end of the week.

@cryptosig
Copy link
Author

You can optionally just git clone the firmware and run the emu.sh in the core which should get you started very quickly.

There are two ways in which eos-transit could easily interface with the trezor, through the python libraries, and there is some JS libraries with message payloads, but they are located in the trezor-suite repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants