We use SHA hashes of the public key of the HD root node for the wallet:
Utils.sha256hash160(getPubKey())
And then pass that through the same trapdoor functions we use for the regular wallets (and which use the seed).
The only difference between a 'wallet id' and a 'BRIT wallet id' is that we use a different salt in the scrypt (one of the trapdoor functions). We don't need a link the local files stored on your machine (which use a wallet id) with what we have on our server (indexed by BRIT wallet id) so we don't make one.
Thus we don't use the Trezor seed phrase (which we don't know for a Trezor hard wallet)
Topic: How is a unique BRIT wallet identifier derived from a Trezor wallet? (Read 619 times)
May 03, 2015, 03:49:40 PM
Hi, just curious- how is a unique BRIT wallet identifier derived from a Trezor wallet?
I am sure You won't expect the user to type in the Trezor seed phrase for deriving it, as that would fundamentally bypass the Trezor security.
I guess the Trezor needs to compute that identifier on it's own via API command?
I am sure You won't expect the user to type in the Trezor seed phrase for deriving it, as that would fundamentally bypass the Trezor security.
I guess the Trezor needs to compute that identifier on it's own via API command?
Quote
5. Payer derives a unique BRIT wallet identifier
The Payer runs a number of one way trapdoor functions over their wallet seed phrase to deterministically generate a wallet identifier (payer.britWalletId).
(source: https://github.com/bitcoin-solutions/brit-service/blob/develop/src/main/doc/Overview-of-BRIT.md) The Payer runs a number of one way trapdoor functions over their wallet seed phrase to deterministically generate a wallet identifier (payer.britWalletId).
Jump to: