iota-ledger / blue-app-iota Goto Github PK

See: LedgerHQ/ledger-live-desktop#1621

I understand that a 24 word BIP39 recovery phrase represent less information than the 27 tryte iota seed. Personally I'm very interested in how this problem has been handled but didn't find any mention of it anywhere. Perhaps it should be added to the file Ledger Nano S Documentation.md

If i recall correctly there was some talk of squeezing the passphrase for the remaining entropy. If this was the chosen solution, should it be added as a security concern that no passphrase will be less secure than a strong passphrase even if no one obtains access to your recovery key?

First of all, thanks for this awesome implementation, on my i7 takes only 0.002 secs to generate the address.
Is there any plan for the Proof of Work written in C?
The C implementation can help to speed up the Java and Swift IOTA lib as well.

Thanks, Pascal

See: Address-test for tests.

@peterwilli :

I now narrowed it down to trits_to_words which seems to be returning different results too
it's called by Kerl so it might be the problem
I edited the word_to_trits function, but both my version and the original give different results than IOTA.lib.js
so there's room for improvement there
@diskings let me know when back, you can read up on this 😛
tl;dr: seems like trints_to_words is giving flawed results, in turn polluting kerl
IOTA word conversion: word conversion Uint32Array [
1067197689,
3486346416,
3826045239,
11191935,
2408969240,
4013166582,
2021906185,
2062403453,
980365332,
1369509650,
2280778051,
2689248909 ]
Ledger [original conversion.c] Response: 244606070 587111619 3262320401 took: 0 seconds (first 3 numbers)
Ledger [edited conversion.c] Response: 2377009824 587111619 3262320401 took: 0 seconds

• Use wollac/ledger-bolos in Dockerfile

IO exceptions lead to a reset of UI and state in the IOTA Ledger application. When a different library is polling the Ledger device in the background, this leads to "wrong CLA" exceptions, rendering the IOTA application unusable.

Steps To Reproduce

1. Start IOTA on the Ledger device
2. Start Ledger Live and go to the Manager tab

Actual behaviour

On every request of Ledger Live (a few times per second) the UI is reset.

Expected behaviour

The UI (and internal state) should not reset or there should some warning, that the application is being accessed by two different libraries.