Tamas Blummer [ARCHIVE] on Nostr: 📅 Original date posted:2014-04-26 📝 Original message:Yes, it is expensive but ...
📅 Original date posted:2014-04-26
📝 Original message: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.comOn 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/e6b66a73/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/e6b66a73/attachment.sig>
Published at
2023-06-07 15:20:07Event JSON
{
"id": "39e7a5f8494e09acfbee475f09497d0bce16b43ee2e4a2a4e60f30d2d78c54f6",
"pubkey": "c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7",
"created_at": 1686151207,
"kind": 1,
"tags": [
[
"e",
"692eac5a75f05a182335e76c9b1e0f6eb679dd54e3d43b36d140b5454edcc477",
"",
"root"
],
[
"e",
"55a7b9253e25b74e810f994a4a7adcbc237d3c7f2fe2b285b86a818666c53c3a",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2014-04-26\n📝 Original message:Yes, it is expensive but possible to discover any funds associated with a seed, provided there are set limits to:\n\n1. gap of address use (e.g. 20)\n2. depth of hierarchy (e.g. 6)\n3. gap in use of parallel branches (e.g. 0) \n\nI would pick the limits in brackets above. \n\nRegards,\n\nTamas Blummer\nhttp://bitsofproof.com\n\nOn 26.04.2014, at 12:48, Tier Nolan \u003ctier.nolan at gmail.com\u003e wrote:\n\n\u003e Maybe the solution is to have a defined way to import an unknown wallet?\n\u003e \n\u003e This means that the gap space and a search ordering needs to be defined.\n\u003e \n\u003e Given a blockchain and a root seed, it should be possible to find all the addresses for that root seed.\n\u003e \n\u003e The hierarchy that the wallet actually uses could be anything.\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140426/e6b66a73/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/e6b66a73/attachment.sig\u003e",
"sig": "996c134b162faca7702a285ea84b1a4ac4e458b1d409ed1020be22554d38085ff06399a35eacdd5023948d3ee0e082529cfe573700a98e2d700e4050db87de7f"
}