Ledger Hardware Wallet - Monero integration : some news #4
Been tracking progress on the ledger integration. Think it will bring in allot of investors who are waiting for a hardware wallet to dip their toe into Monero
https://www.reddit.com/r/Monero/comments/7de2pj/ledger_hardware_wallet_monero_integration_some/
"Hi all
Just performed a new push, here are the news:
Status
The wallet private key is now inited with the device seed. It do not use the 24 words mnemonic of Monero but the seed device from path:
/0x8000002C/0x80000080/0x80000000/0x00000000/0x00000000
aka
/44'/128'/account'/0/0
To make short the scheme is the following, assuming S is the seed from given path:
a = keccak(S)
a[0] &= 0xF8;
a[31] = (a[31] & 0x7F) | 0x40;
b = keccak(a)
b[0] &= 0xF8;
b[31] = (b[31] & 0x7F) | 0x40;
The --generate-from-device seems to be fully functional. It retrieves the public keys (A,B) from the device and restore the wallet from them. If it exists any funds on the block chain associated with, they are retrieved. Note that scanning the whole blockchain is long, very long as all block as to be decode by the device.
Transfer are now required to be validated on-screen: destinations amounts and fees have to be validated by user. Ok, I need to finish the check on the client side to abort tx is user reject it. Don't blame me for not doing it in this push :)
Next
So what next?
Reference doc has to be updated!
On device side, I have to add the hash-state machine to ensure the integrity of the whole process and avoid data modification between destination/amount validation and final signature.
On client side all error code returned by device has to be checked and TX has to be aborted if needed.
And then? Prepare a Push Request on 0.11.0 branch :). This will start the code review by the core team and I expect by others. During that, I will start a merge on master branch and work on the sub-address feature from kenshi84. I will also provide linux cli binary for those who want to test various scenario on testnet."
https://www.reddit.com/r/Monero/comments/7de2pj/ledger_hardware_wallet_monero_integration_some/
"Hi all
Just performed a new push, here are the news:
Status
The wallet private key is now inited with the device seed. It do not use the 24 words mnemonic of Monero but the seed device from path:
/0x8000002C/0x80000080/0x80000000/0x00000000/0x00000000
aka
/44'/128'/account'/0/0
To make short the scheme is the following, assuming S is the seed from given path:
a = keccak(S)
a[0] &= 0xF8;
a[31] = (a[31] & 0x7F) | 0x40;
b = keccak(a)
b[0] &= 0xF8;
b[31] = (b[31] & 0x7F) | 0x40;
The --generate-from-device seems to be fully functional. It retrieves the public keys (A,B) from the device and restore the wallet from them. If it exists any funds on the block chain associated with, they are retrieved. Note that scanning the whole blockchain is long, very long as all block as to be decode by the device.
Transfer are now required to be validated on-screen: destinations amounts and fees have to be validated by user. Ok, I need to finish the check on the client side to abort tx is user reject it. Don't blame me for not doing it in this push :)
Next
So what next?
Reference doc has to be updated!
On device side, I have to add the hash-state machine to ensure the integrity of the whole process and avoid data modification between destination/amount validation and final signature.
On client side all error code returned by device has to be checked and TX has to be aborted if needed.
And then? Prepare a Push Request on 0.11.0 branch :). This will start the code review by the core team and I expect by others. During that, I will start a merge on master branch and work on the sub-address feature from kenshi84. I will also provide linux cli binary for those who want to test various scenario on testnet."
相關出版品
免責聲明
這些資訊和出版物並不意味著也不構成TradingView提供或認可的金融、投資、交易或其他類型的意見或建議。請在使用條款閱讀更多資訊。