summaryrefslogtreecommitdiff
path: root/7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c
diff options
context:
space:
mode:
authorPrayank <prayank@tutanota.de>2021-11-27 14:42:38 +0100
committerbitcoindev <bitcoindev@gnusha.org>2021-11-27 13:42:43 +0000
commit67964c60c1cffe51def873c5c10798695ca0e410 (patch)
tree54cd1885c2122e2fd12ff40a17410f9e58c2b848 /7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c
parent471f5ac8c48d8f016984e4830c408cc9f3f75884 (diff)
downloadpi-bitcoindev-67964c60c1cffe51def873c5c10798695ca0e410.tar.gz
pi-bitcoindev-67964c60c1cffe51def873c5c10798695ca0e410.zip
Re: [bitcoin-dev] Trying to patch Core ZMQ "rawtx" topic to only publish unconfirmed transactions: How?
Diffstat (limited to '7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c')
-rw-r--r--7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c130
1 files changed, 130 insertions, 0 deletions
diff --git a/7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c b/7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c
new file mode 100644
index 000000000..74cbba0f5
--- /dev/null
+++ b/7b/b6d2fc7333bf3ea2d19166a3c69df74ecbd16c
@@ -0,0 +1,130 @@
+Return-Path: <prayank@tutanota.de>
+Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
+ by lists.linuxfoundation.org (Postfix) with ESMTP id 37283C000A
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Sat, 27 Nov 2021 13:42:43 +0000 (UTC)
+Received: from localhost (localhost [127.0.0.1])
+ by smtp4.osuosl.org (Postfix) with ESMTP id 0D1B540352
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Sat, 27 Nov 2021 13:42:43 +0000 (UTC)
+X-Virus-Scanned: amavisd-new at osuosl.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.601
+X-Spam-Level:
+X-Spam-Status: No, score=0.601 tagged_above=-999 required=5
+ tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
+ DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001,
+ RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
+ SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
+ autolearn=ham autolearn_force=no
+Authentication-Results: smtp4.osuosl.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=tutanota.de
+Received: from smtp4.osuosl.org ([127.0.0.1])
+ by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
+ with ESMTP id FOnj1CB-nsxJ
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Sat, 27 Nov 2021 13:42:42 +0000 (UTC)
+X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
+Received: from w1.tutanota.de (w1.tutanota.de [81.3.6.162])
+ by smtp4.osuosl.org (Postfix) with ESMTPS id DB70B40350
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Sat, 27 Nov 2021 13:42:41 +0000 (UTC)
+Received: from w3.tutanota.de (unknown [192.168.1.164])
+ by w1.tutanota.de (Postfix) with ESMTP id 8821CFBB3C2;
+ Sat, 27 Nov 2021 13:42:38 +0000 (UTC)
+DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1638020558;
+ s=s1; d=tutanota.de;
+ h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:Sender;
+ bh=xwwlGK3XgXF0aXApGkrn229BIfdou27Sg2xKkRMSOEQ=;
+ b=SjrXBbYP+xjpqtZk1SSy1pa98yuOBEExEyWVqzLH8Xc3rTZsihnS3sfEM8gFIWPi
+ 1v8e+1qJgeliGJkF6em3N8k+CrVUFayp+WOCjgCxQ+tbr8+YRNNKIZNFj3tuYmbsc2q
+ Gr9YGk4rbbWbxpxil9TkBQva8yFuGDQObJfs4pSMGZF3qgH6dacmUv2tcsVGEnpzVlP
+ 968/E/iciQ3tyao2q7lrFKCFBs2JLlkvU4gs3JKhGeIGdkoo+1VzWaHlXGq2yaUf3iz
+ kGVg9ZNnYnprnadakuC2IG4+tWrWdkEj0eE0QMJ1t3y3T6skXW7oX15ruySJl1JmJmg
+ nJy9eLid6A==
+Date: Sat, 27 Nov 2021 14:42:38 +0100 (CET)
+From: Prayank <prayank@tutanota.de>
+To: ali@notatether.com
+Message-ID: <MpWcX_f--F-2@tutanota.de>
+MIME-Version: 1.0
+Content-Type: multipart/alternative;
+ boundary="----=_Part_92765_1100432481.1638020558538"
+X-Mailman-Approved-At: Sat, 27 Nov 2021 16:58:17 +0000
+Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
+Subject: Re: [bitcoin-dev] Trying to patch Core ZMQ "rawtx" topic to only
+ publish unconfirmed transactions: How?
+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
+X-Mailman-Version: 2.1.15
+Precedence: list
+List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
+List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
+List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
+List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
+List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
+List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
+X-List-Received-Date: Sat, 27 Nov 2021 13:42:43 -0000
+
+------=_Part_92765_1100432481.1638020558538
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 7bit
+
+Hi Ali,
+
+Not sure if this is exactly what you are looking for but maybe trying to solve this I might also learn few things:
+
+Save zmqpubsequence=tcp://127.0.0.1:28332 in bitcoin.conf
+
+Run bitcoind
+
+Run this python script: https://pastebin.com/raw/tNp2x5y3
+
+You will see results like this:
+https://i.imgur.com/xKzFJbl.png
+https://i.imgur.com/gpsTTHZ.png
+
+A - Accepted, C- Connect (block) and R- Removal in the above screenshots
+
+If you are looking for unconfirmed transactions printed in sequence I think this should help. Since transactions can be printed twice (accept,remove) in this case as well, python script can be modified to manage this IMO.
+
+Other alternatives can be debug=mempool and reading debug.log for changes without polling.
+
+--
+Prayank
+
+A3B1 E430 2298 178F
+
+------=_Part_92765_1100432481.1638020558538
+Content-Type: text/html; charset=UTF-8
+Content-Transfer-Encoding: quoted-printable
+
+<html>
+ <head>
+ <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
+">
+ </head>
+ <body>
+<div>Hi Ali,<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Not sur=
+e if this is exactly what you are looking for but maybe trying to solve thi=
+s I might also learn few things:<br></div><div dir=3D"auto"><br></div><div =
+dir=3D"auto">Save zmqpubsequence=3Dtcp://127.0.0.1:28332 in bitcoin.conf<br=
+></div><div dir=3D"auto"><br></div><div dir=3D"auto">Run bitcoind<br></div>=
+<div dir=3D"auto"><br></div><div dir=3D"auto">Run this python script: https=
+://pastebin.com/raw/tNp2x5y3<br></div><div dir=3D"auto"><br></div><div dir=
+=3D"auto">You will see results like this: <br></div><div dir=3D"auto">https=
+://i.imgur.com/xKzFJbl.png<br></div><div dir=3D"auto">https://i.imgur.com/g=
+psTTHZ.png<br></div><div dir=3D"auto"><br></div><div dir=3D"auto">A - Accep=
+ted, C- Connect (block) and R- Removal in the above screenshots<br></div><d=
+iv dir=3D"auto"><br></div><div dir=3D"auto">If you are looking for unconfir=
+med transactions printed in sequence I think this should help. Since transa=
+ctions can be printed twice (accept,remove) in this case as well, python sc=
+ript can be modified to manage this IMO.<br></div><div dir=3D"auto"><br></d=
+iv><div dir=3D"auto">Other alternatives can be debug=3Dmempool and reading =
+debug.log for changes without polling.<br></div><div dir=3D"auto"><br></div=
+><div>-- <br></div><div>Prayank<br></div><div><br></div><div dir=3D"auto">A=
+3B1 E430 2298 178F<br></div> </body>
+</html>
+
+------=_Part_92765_1100432481.1638020558538--
+