📅 Original date posted:2011-08-04
🗒️ Summary of this message: A patch for bitcoind will allow mining pools to offer a real-time feed of accepted transactions and blocks to fight double-spending.
📝 Original message:On Thu, 2011-08-04 at 16:07 -0400, Andrew Schaaf wrote:
> One double-spend fighting option is for each mining pool to offer a realtime feed of accepted TXs.
>
> I am hoping to complete the following later this month:
>
> (1) A minimal bitcoind patch that writes raw accepted TXs and BLOCKs to stdout with a prefix of ("2naXaRQj--TX\n%d\n" % (data_length))
> (Proof-of-concept done — I'll submit a pull request with "--print-accepted-txs-and-blocks" when I get a chance to clean it up)
>
> (2) A minimal NodeJS app which invokes bitcoind as a subprocess, parses the TXs and BLOCKs, and offers a realtime feed
They already do if they provide the IP of their node (or a proxy node on
top of theirs which would be recommended for security). This has been
my whole point the entire time.
Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110804/6bbe2769/attachment.sig>;
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 02:12:18
in reply to nevent1q…qxxe
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 02:12:18Event JSON
{
"id": "69c81a57602b33e25f87d2acf27cc829c46bc6f2f095894b49c3ebdd028a44bb",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686103938,
"kind": 1,
"tags": [
[
"e",
"f7bac66510d148bc7cd5c36f79897fafe3410a2bc9df45238a65f8429b9407f0",
"",
"root"
],
[
"e",
"7d7def923248030f952b8de54492e1b5add1f5f3d443a8bdba7bdf7f46b84788",
"",
"reply"
],
[
"p",
"a39e787f74c9e461ef1636771f7b7d38d1ba5cd34548f3208871ffe9edfc67cf"
]
],
"content": "📅 Original date posted:2011-08-04\n🗒️ Summary of this message: A patch for bitcoind will allow mining pools to offer a real-time feed of accepted transactions and blocks to fight double-spending.\n📝 Original message:On Thu, 2011-08-04 at 16:07 -0400, Andrew Schaaf wrote:\n\u003e One double-spend fighting option is for each mining pool to offer a realtime feed of accepted TXs.\n\u003e \n\u003e I am hoping to complete the following later this month:\n\u003e \t\n\u003e \t(1) A minimal bitcoind patch that writes raw accepted TXs and BLOCKs to stdout with a prefix of (\"2naXaRQj--TX\\n%d\\n\" % (data_length))\n\u003e \t\t(Proof-of-concept done — I'll submit a pull request with \"--print-accepted-txs-and-blocks\" when I get a chance to clean it up)\n\u003e \t\n\u003e \t(2) A minimal NodeJS app which invokes bitcoind as a subprocess, parses the TXs and BLOCKs, and offers a realtime feed\n\nThey already do if they provide the IP of their node (or a proxy node on\ntop of theirs which would be recommended for security). This has been\nmy whole point the entire time.\n\nMatt\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 836 bytes\nDesc: This is a digitally signed message part\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110804/6bbe2769/attachment.sig\u003e",
"sig": "c4caa4a103e7951114c508507bf79c8a66620fe0ffef31d8c5bc0f9014b345ad7513a17c7025c7c9ea26730522f319913d2830cc6699165e801938f04825ec24"
}