📅 Original date posted:2014-04-26
📝 Original message:Actually gap in parallel branches already fails with BIP64 as it starts with m/64'/…. without having m/63'
Regards,
Tamas Blummer
http://bitsofproof.com
On 26.04.2014, at 12:59, Tamas Blummer <tamas at bitsofproof.com> wrote:
> Yes, it is expensive but possible to discover any funds associated with a seed, provided there are set limits to:
>
> 1. gap of address use (e.g. 20)
> 2. depth of hierarchy (e.g. 6)
> 3. gap in use of parallel branches (e.g. 0)
>
> I would pick the limits in brackets above.
>
> Regards,
>
> Tamas Blummer
> http://bitsofproof.com
>
> On 26.04.2014, at 12:48, Tier Nolan <tier.nolan at gmail.com> wrote:
>
>> Maybe the solution is to have a defined way to import an unknown wallet?
>>
>> This means that the gap space and a search ordering needs to be defined.
>>
>> Given a blockchain and a root seed, it should be possible to find all the addresses for that root seed.
>>
>> The hierarchy that the wallet actually uses could be anything.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.html>;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.sig>;
Tamas Blummer [ARCHIVE] /
npub1cc…ex8m8
2023-06-07 15:20:07
in reply to nevent1q…l438
Author Public Key
npub1ccegg9n9lnx6huppxg43m95488yur7pfemkn3pz0agjws5ffvtts0ex8m8Published at
2023-06-07 15:20:07Event JSON
{
"id": "7ebf8b359cb7ee7c2d6c911df447f12ba5dba1f49b93daeeb14f32b0af0715c3",
"pubkey": "c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7",
"created_at": 1686151207,
"kind": 1,
"tags": [
[
"e",
"692eac5a75f05a182335e76c9b1e0f6eb679dd54e3d43b36d140b5454edcc477",
"",
"root"
],
[
"e",
"39e7a5f8494e09acfbee475f09497d0bce16b43ee2e4a2a4e60f30d2d78c54f6",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2014-04-26\n📝 Original message:Actually gap in parallel branches already fails with BIP64 as it starts with m/64'/…. without having m/63'\n\nRegards,\n\nTamas Blummer\nhttp://bitsofproof.com\n\nOn 26.04.2014, at 12:59, Tamas Blummer \u003ctamas at bitsofproof.com\u003e wrote:\n\n\u003e Yes, it is expensive but possible to discover any funds associated with a seed, provided there are set limits to:\n\u003e \n\u003e 1. gap of address use (e.g. 20)\n\u003e 2. depth of hierarchy (e.g. 6)\n\u003e 3. gap in use of parallel branches (e.g. 0) \n\u003e \n\u003e I would pick the limits in brackets above. \n\u003e \n\u003e Regards,\n\u003e \n\u003e Tamas Blummer\n\u003e http://bitsofproof.com\n\u003e \n\u003e On 26.04.2014, at 12:48, Tier Nolan \u003ctier.nolan at gmail.com\u003e wrote:\n\u003e \n\u003e\u003e Maybe the solution is to have a defined way to import an unknown wallet?\n\u003e\u003e \n\u003e\u003e This means that the gap space and a search ordering needs to be defined.\n\u003e\u003e \n\u003e\u003e Given a blockchain and a root seed, it should be possible to find all the addresses for that root seed.\n\u003e\u003e \n\u003e\u003e The hierarchy that the wallet actually uses could be anything.\n\u003e \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.html\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 495 bytes\nDesc: Message signed with OpenPGP using GPGMail\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/16c43082/attachment.sig\u003e",
"sig": "f11acc32d37a0495608e83d2604df374c6a523819c5b3eecf2eec816cad722fc0e71f09bde1545bf97e91f90720a483981e931bda71600f0fc5d4aefc58e5c78"
}