-
Notifications
You must be signed in to change notification settings - Fork 647
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
Ledger Nano S Hardware Wallet Support #1340
Comments
@marcialvieira and I would like to take a crack at this one. @ryanRfox |
fuck yeah! It shouldn't be TOO hard if you use the EOS one as a starting point...I would've tried it myself but i'm not a C/C++ coder. |
Nice! I actually didn't realize there was progress already being made on the EOS front. Yes, that should definitely help ensure smooth sailing! |
Adding a task for myself:
|
@christophersanborn I think that is reasonable. |
Declaring the first task, "Do ten hours of immersive research" to be complete. Specific products of this research are:
Tagging: @ryanRfox |
Overall Roadmap:Goal is to have both a Nano S app that runs on the device, allowing any wallet developer to add support, and, at minimum, a simple GUI App to submit to the Ledger App Store to facilitate safe storage and transfer of assets. (I.e. basic "wallet" functionality). Beyond that, we may also work on adding support to the cli_wallet and/or providing the bitshares-ui team with the resources that they would need to add support to the reference GUI wallet.
For the time being, work is being done in christophersanborn/ledger-app-bitshares, and detailed task management in christophersanborn/ledger-app-bitshares/issues. |
as far as GUI app is concerned, I plan to be adding support for it to Beet once you have the device side working using https://github.com/LedgerHQ/ledgerjs |
Yes, you are cordially invited to use Beet as your standalone GUI app Christopher |
Nice! @clockworkgr and @sschiessl-bcp; I love the idea of Beet support, and this looks very easy to achieve and opens up so many possibilities. I've added it to the roadmap above. |
Nice. To be honest, if you finish the on-device work I should be able to handle the JS side myself. ofcourse, any help would be greatly appreciated :) |
Estimating between 10 and 20 hours for this component, but may be less because of the similarities. |
Thanks @christophersanborn and @marcialvieira for your estimates and roadmap. I'v updated the Core Team Task List to reflect them. Please continue with your design and development efforts. |
Estimating between 40 and 80 hours for this component. This is based on the complexity and general inscrutability of code written for BOLOS devices. It also accounts for things like constructing test data packets to use during the dev process and other supporting tasks. |
As user of Nano Ledger, would love to see BTS supported on it. Keep up the great work and ideas! |
Logging 10 hours complete towards target "Device Side: Nano app" within the Week 48–49 period. |
Would love to see this come to Trezor also, given it is open hardware aswell as open software. |
Logging 15 hours toward target "Device Side: Nano app" within the Week 50–51 time period. (Bringing total thus far toward the target to 25 hours.) Tagging: @ryanRfox |
Thanks @christophersanborn for the update. |
Logging 30 hours toward target "Device Side: Nano app" in the time period from 1/1/2019 to 1/27/2019. This covers 21 commits by me from b41063b up through e9f572c. This brings total thus far toward the target to 55 hours. Tagging: @ryanRfox |
Logging 24 hours toward target "Host Side: Nano app" in the time period from 1/18/2019 to 2/4/2019. This covers 8 commits by me from d4e2ece up through 5cfbf3b. Estimating between 40 and 60 hours for this component, including the 24 hours already done, depending on the need of operations, I'm expecting that the complexity decreases a lot by similarities between operations, already implemented operations: transfer, limit_order_create, limit_order_cancel and account_update. Tagging: @ryanRfox |
I'm adding this to our Feature Release project board for visual reference. This does not have any impact on the release nor is it held the schedule. It's just may way to show the Community "we are working on it". |
User Story
As a
Ledger Nano S user
I want an implementation tosupport BitShares accounts
so that I maysafely store my private keys, sign transactions and submit them to the network
.Additional Context
CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: