Peter Todd [ARCHIVE] on Nostr: 📅 Original date posted:2015-05-26 📝 Original message:On Tue, May 26, 2015 at ...
📅 Original date posted:2015-05-26
📝 Original message:On Tue, May 26, 2015 at 12:52:07AM -0400, Matt Whitlock wrote:
> On Monday, 25 May 2015, at 11:48 pm, Jim Phillips wrote:
> > Do any wallets actually do this yet?
>
> Not that I know of, but they do seed their address database via DNS, which you can poison if you control the LAN's DNS resolver. I did this for a Bitcoin-only Wi-Fi network I operated at a remote festival. We had well over a hundred lightweight wallets, all trying to connect to the Bitcoin P2P network over a very bandwidth-constrained Internet link, so I poisoned the DNS and rejected all outbound connection attempts on port 8333, to force all the wallets to connect to a single local full node, which had connectivity to a single remote node over the Internet. Thus, all the lightweight wallets at the festival had Bitcoin network connectivity, but we only needed to backhaul the Bitcoin network's transaction traffic once.
Interesting!
What festival was this?
--
'peter'[:-1]@petertodd.org
000000000000000003ce9f2f90736ab7bd24d29f40346057f9e217b3753896bb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 650 bytes
Desc: Digital signature
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150526/bf034861/attachment.sig>
Published at
2023-06-07 15:35:37Event JSON
{
"id": "c341b493f609ecfece9b060363728477c655c1e7f31b73358b47e3743f0f1ed7",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686152137,
"kind": 1,
"tags": [
[
"e",
"2754f6df425d0f26fe27c6426d73b5ed47aee2228af52009176ded69f7bbcf5e",
"",
"root"
],
[
"e",
"dee1ba2a9d04a0feedc231582a17df5a3161c7e77a0e3bc376fab39b8cdd4f83",
"",
"reply"
],
[
"p",
"f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91"
]
],
"content": "📅 Original date posted:2015-05-26\n📝 Original message:On Tue, May 26, 2015 at 12:52:07AM -0400, Matt Whitlock wrote:\n\u003e On Monday, 25 May 2015, at 11:48 pm, Jim Phillips wrote:\n\u003e \u003e Do any wallets actually do this yet?\n\u003e \n\u003e Not that I know of, but they do seed their address database via DNS, which you can poison if you control the LAN's DNS resolver. I did this for a Bitcoin-only Wi-Fi network I operated at a remote festival. We had well over a hundred lightweight wallets, all trying to connect to the Bitcoin P2P network over a very bandwidth-constrained Internet link, so I poisoned the DNS and rejected all outbound connection attempts on port 8333, to force all the wallets to connect to a single local full node, which had connectivity to a single remote node over the Internet. Thus, all the lightweight wallets at the festival had Bitcoin network connectivity, but we only needed to backhaul the Bitcoin network's transaction traffic once.\n\nInteresting!\n\nWhat festival was this?\n\n-- \n'peter'[:-1]@petertodd.org\n000000000000000003ce9f2f90736ab7bd24d29f40346057f9e217b3753896bb\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 650 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150526/bf034861/attachment.sig\u003e",
"sig": "934e444b28cd468ca7519fb4068081b83e01f92231bec087fae7ce1446d8af8033174b144c72d5117cf152d6e6d6017e5ebad8a6662f0f7e1f28dae9934b2762"
}