You should explore the ledger nano related githubs . This is an adventure in software development finally we cn all join in, steem has made things accessible to all, we ARE the new github.
IM SO HAPPY @techcoderx decided to do this becaus eI was thinking I WAS going to have to be the one who did iut, but THANK YOU so MUCH techcoderx for this!!!1
WOOOWWWW Youre ALREADY almost there! MAKE SURE the title is changed to SHOW everyone YOU ALREADY HAVE A WORKING PROTOTYPE thats IMPORTANT!
Its ok let this image be inspiration for you. Make this silver diamond steem pendent with pedger on the chain have meaning finally!
I believe in you!
(Tell ppl i have an extra for sale, $500 and its silver 999 and lab diamonds . i can then make another one for eos :)
Soone nuf we will be using your sps for hardware wallet, mine for scatter, and we will be getting steem MAIN NET on newdex and trading main net steem with hardware wallets on a Real dex no pegged assets needed! we could even get steem engine tokens trading on newdex for steem directly
In the case of hardware wallets, the 24-word recovery seed will be the master password. The public and private keys are derived from this recovery seed using m/44'/135'/0'/0/address_index derivation path, the same way of how EOS public keys get generated but with a different coin type in the derivation path, which is outlined here. I have tried generating a Steem public key from the private key generated from an EOS keypair generation tool, and the only difference in the generated public keys are the first 3 letters, where Steem public keys start with STM, whereas EOS public keys start with EOS.
The address_index that completes the path to derive the public key (that is bound to Steem accounts) will be stored in desktop wallets. The WIF private key will be generated using the same derivation path every time there is a signing request, hence there is nothing to write to the flash memory which has limited cycles (500,000 writes according to Ledger's documentation)
Thanks for explaining. I take it that means the master password and keys will have to change to make the account compatible without compromising or resetting the device. It should also mean it is possible to store additional accounts by changing the address path similar to how separate xlm accounts are stored (change last 0).
There will be options in the desktop wallet apps to only change certain public keys, so that an account is not tied completely to the hardware wallet.
For example a curation bot may need to store plain text private posting key on a server. They have the option to only change their active and owner public keys, so that funds may only be accessed through the hardware wallet, but able to comment/vote with the posting key like how we're doing it now.
An account may also have more than one public key associated with a particular authority. For example there may be 2 public keys that is associated with posting authority, in which transactions that only require posting authority can be signed with the hardware wallet or another private key.
Would there be any listing fees by Ledger to get a working application listed on Ledger's "app store"?
No Ledger does not have any fees
You should explore the ledger nano related githubs . This is an adventure in software development finally we cn all join in, steem has made things accessible to all, we ARE the new github.
IM SO HAPPY @techcoderx decided to do this becaus eI was thinking I WAS going to have to be the one who did iut, but THANK YOU so MUCH techcoderx for this!!!1
WOOOWWWW Youre ALREADY almost there! MAKE SURE the title is changed to SHOW everyone YOU ALREADY HAVE A WORKING PROTOTYPE thats IMPORTANT!
@inertia @surfyogi @meesterboom @luciper @thejohalfiles should all know about this project so we can get this funded, however, id be willing to help get private funding for @techcoderx to ENSURE this happens.
When we combine THIS SPS proposal for ledger nano support with my Steem on Scatter proposal, things will get very serious!
I will have an update video on DTube coming soon 😃
Spoiler alert: it still can't generate a valid signature yet 😔
Its ok let this image be inspiration for you. Make this silver diamond steem pendent with pedger on the chain have meaning finally!
I believe in you!
(Tell ppl i have an extra for sale, $500 and its silver 999 and lab diamonds . i can then make another one for eos :)
Soone nuf we will be using your sps for hardware wallet, mine for scatter, and we will be getting steem MAIN NET on newdex and trading main net steem with hardware wallets on a Real dex no pegged assets needed! we could even get steem engine tokens trading on newdex for steem directly
This is a great idea. I have a Nano S. I'm just curious, will only the master key be stored on the device or will all of them be stored?
In the case of hardware wallets, the 24-word recovery seed will be the master password. The public and private keys are derived from this recovery seed using
m/44'/135'/0'/0/address_indexderivation path, the same way of how EOS public keys get generated but with a different coin type in the derivation path, which is outlined here. I have tried generating a Steem public key from the private key generated from an EOS keypair generation tool, and the only difference in the generated public keys are the first 3 letters, where Steem public keys start withSTM, whereas EOS public keys start withEOS.The
address_indexthat completes the path to derive the public key (that is bound to Steem accounts) will be stored in desktop wallets. The WIF private key will be generated using the same derivation path every time there is a signing request, hence there is nothing to write to the flash memory which has limited cycles (500,000 writes according to Ledger's documentation)You may find the source code here
Thanks for explaining. I take it that means the master password and keys will have to change to make the account compatible without compromising or resetting the device. It should also mean it is possible to store additional accounts by changing the address path similar to how separate xlm accounts are stored (change last 0).
There will be options in the desktop wallet apps to only change certain public keys, so that an account is not tied completely to the hardware wallet.
For example a curation bot may need to store plain text private posting key on a server. They have the option to only change their active and owner public keys, so that funds may only be accessed through the hardware wallet, but able to comment/vote with the posting key like how we're doing it now.
An account may also have more than one public key associated with a particular authority. For example there may be 2 public keys that is associated with posting authority, in which transactions that only require posting authority can be signed with the hardware wallet or another private key.
👍
~Smartsteem Curation Team