📅 Original date posted:2017-01-05
📝 Original message:On 01/04/2017 11:06 PM, Chris Priest via bitcoin-dev wrote:
> On 1/3/17, Jonas Schnelli via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>
>> There are plenty, more sane options. If you can't run your own full-node
>> as a merchant (trivial), maybe co-use a wallet-service with centralized
>> verification (maybe use two of them), I guess Copay would be one of
>> those wallets (as an example). Use them in watch-only mode.
>
> The best way is to connect to the mempool of each miner and check to
> see if they have your txid in their mempool.
>
> https://www.antpool.com/api/is_in_mempool?txid=334847bb...
> https://www.f2pool.com/api/is_in_mempool?txid=334847bb...
> https://bw.com/api/is_in_mempool?txid=334847bb...
> https://bitfury.com/api/is_in_mempool?txid=334847bb...
> https://btcc.com/api/is_in_mempool?txid=334847bb...
>
> If each of these services return "True", and you know those services
> so not engage in RBF, then you can assume with great confidence that
> your transaction will be in the next block, or in a block very soon.
> If any one of those services return "False", then you must assume that
> it is possible that there is a double spend floating around, and that
> you should wait to see if that tx gets confirmed. The problem is that
> not every pool runs such a service to check the contents of their
> mempool...
>
> This is an example of mining centralization increasing the security of
> zero confirm.
A world connected up to a few web services to determine payment validity
is an example of a bitcoin security catastrophe.
e
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170104/4df3d1a9/attachment.sig>;
Eric Voskuil [ARCHIVE] /
npub1sg…ppx3c
2023-06-07 17:55:10
in reply to nevent1q…zf0j
Author Public Key
npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3cPublished at
2023-06-07 17:55:10Event JSON
{
"id": "5b7d013d5e55fab671593690b93eb20e7982e9d50755bc5e62ab3f21b46b03bf",
"pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e",
"created_at": 1686160510,
"kind": 1,
"tags": [
[
"e",
"12de089a3e4ccbe31128a134586c26b5a984bf25231ca8b54e0116dac53ecb14",
"",
"root"
],
[
"e",
"818bb05ed4e91483248412d87580375ab9e99b3a17e397deb2dfe44409fc1f9c",
"",
"reply"
],
[
"p",
"3b5311200328974edeaa105b1a8f60d243e653cc63b6bb29f61dc696e04189ed"
]
],
"content": "📅 Original date posted:2017-01-05\n📝 Original message:On 01/04/2017 11:06 PM, Chris Priest via bitcoin-dev wrote:\n\u003e On 1/3/17, Jonas Schnelli via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\n\u003e\u003e There are plenty, more sane options. If you can't run your own full-node\n\u003e\u003e as a merchant (trivial), maybe co-use a wallet-service with centralized\n\u003e\u003e verification (maybe use two of them), I guess Copay would be one of\n\u003e\u003e those wallets (as an example). Use them in watch-only mode.\n\u003e \n\u003e The best way is to connect to the mempool of each miner and check to\n\u003e see if they have your txid in their mempool.\n\u003e \n\u003e https://www.antpool.com/api/is_in_mempool?txid=334847bb...\n\u003e https://www.f2pool.com/api/is_in_mempool?txid=334847bb...\n\u003e https://bw.com/api/is_in_mempool?txid=334847bb...\n\u003e https://bitfury.com/api/is_in_mempool?txid=334847bb...\n\u003e https://btcc.com/api/is_in_mempool?txid=334847bb...\n\u003e \n\u003e If each of these services return \"True\", and you know those services\n\u003e so not engage in RBF, then you can assume with great confidence that\n\u003e your transaction will be in the next block, or in a block very soon.\n\u003e If any one of those services return \"False\", then you must assume that\n\u003e it is possible that there is a double spend floating around, and that\n\u003e you should wait to see if that tx gets confirmed. The problem is that\n\u003e not every pool runs such a service to check the contents of their\n\u003e mempool...\n\u003e \n\u003e This is an example of mining centralization increasing the security of\n\u003e zero confirm.\n\nA world connected up to a few web services to determine payment validity\nis an example of a bitcoin security catastrophe.\n\ne\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 490 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170104/4df3d1a9/attachment.sig\u003e",
"sig": "d82e3b9580bd45b0e09dffb2ea9e3ed3ed3fc89fb37de88c9eee454a579f094a11619cbb804faa3fece6ad30d6ab3e3e44241650b32a3cd7667b142784f1bd48"
}