🔖 Title: bitcoind multiplexing proxy - request/response routing problem
🏷️ Categories: Bitcoin-development
👥 Authors:
• Mike Hearn ( Mike Hearn [ARCHIVE] (npub17ty…qgyd) )
• Steve diy-eco-life ( Steve diy-eco-life [ARCHIVE] (npub1z8n…v4ea) )
• Steve ( Steve [ARCHIVE] (npub1lmy…8rda) )
🗒️ Conversation Summary: Steve discusses three approaches to building a multiplexing proxy between a local bitcoind and a remote node. He favors the first approach, which generates a unique key from the request and response. Steve also suggests serializing request/response exchanges by locking channels until a response is received or timeout. Mike Hearn suggests keeping the discussion on one mailing list to avoid confusion.
📅 Messages Date Range: 2011-09-07 to 2011-09-08
✉️ Message Count: 4
📚 Total Characters in Messages: 8031
Bitcoin Mailing List
npub15g…x08lk
2023-06-07 02:22:59
Author Public Key
npub15g7m7mrveqlpfnpa7njke3ccghmpryyqsn87vg8g8eqvqmxd60gqmx08lkPublished at
2023-06-07 02:22:59Event JSON
{
"id": "84f886c581f79ae0e62167f62ed88aefa7cda08705a70faadd465e3524d4e5cf",
"pubkey": "a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0",
"created_at": 1686104579,
"kind": 1,
"tags": [
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
],
[
"p",
"11e740cae0df287c038c624c32dd1299216c2fe5d2fcd03d9c8d910a25a1a8ed"
],
[
"p",
"fec9b86ad53f610a8cab1b299acd9dc48a0c018163c9a3ac28bfef2117de2ae6"
]
],
"content": "🔖 Title: bitcoind multiplexing proxy - request/response routing problem\n🏷️ Categories: Bitcoin-development\n👥 Authors: \n• Mike Hearn ( nostr:npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd )\n• Steve diy-eco-life ( nostr:npub1z8n5pjhqmu58cquvvfxr9hgjnyskctl96t7dq0vu3kgs5fdp4rkskkv4ea )\n• Steve ( nostr:npub1lmyms6k48ass4r9trv5e4nvacj9qcqvpv0y68tpghlhjz9779tnqgh8rda )\n🗒️ Conversation Summary: Steve discusses three approaches to building a multiplexing proxy between a local bitcoind and a remote node. He favors the first approach, which generates a unique key from the request and response. Steve also suggests serializing request/response exchanges by locking channels until a response is received or timeout. Mike Hearn suggests keeping the discussion on one mailing list to avoid confusion.\n📅 Messages Date Range: 2011-09-07 to 2011-09-08\n✉️ Message Count: 4\n📚 Total Characters in Messages: 8031\n",
"sig": "e5ea75b3f21485fd03650470a9488898d47098314a565439f1c273c1990f6fde9e49d4465c311b275e7ff64ce06dc692505d4bd369ea9e6d1d2bd3a580d83885"
}