📅 Original date posted:2017-01-06
📝 Original message:You might as well replace Bitcoin with a system where these parties
sign transactions and skip mining altogether, it would have the same
properties and be significantly more effient.
On 2017-01-04 23:06, Chris Priest 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. If more people mined, this method will not work as well
> because it would require you to call the API of hundreds of different
> potential block creators.
bfd at cock.lu [ARCHIVE] /
npub1md…gy6y7
2023-06-07 17:55:11
in reply to nevent1q…udhj
Author Public Key
npub1mdmqmt0prpddcexkljfzd40uf7nvrc56c7gsg2spn3lgcjghguxqwgy6y7Published at
2023-06-07 17:55:11Event JSON
{
"id": "350ee62a9abb327136fc44e96c149d514116ba52f9b89eb15bae63ba75205882",
"pubkey": "db760dade1185adc64d6fc9226d5fc4fa6c1e29ac791042a019c7e8c4917470c",
"created_at": 1686160511,
"kind": 1,
"tags": [
[
"e",
"12de089a3e4ccbe31128a134586c26b5a984bf25231ca8b54e0116dac53ecb14",
"",
"root"
],
[
"e",
"9d866a5f2c7043f4dec49c40443a0645ee6af573aee4404a516bb0754c24ac26",
"",
"reply"
],
[
"p",
"82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e"
]
],
"content": "📅 Original date posted:2017-01-06\n📝 Original message:You might as well replace Bitcoin with a system where these parties\nsign transactions and skip mining altogether, it would have the same\nproperties and be significantly more effient.\n\n\nOn 2017-01-04 23:06, Chris Priest 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 \n\u003e\u003e full-node\n\u003e\u003e as a merchant (trivial), maybe co-use a wallet-service with \n\u003e\u003e 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. If more people mined, this method will not work as well\n\u003e because it would require you to call the API of hundreds of different\n\u003e potential block creators.",
"sig": "6be6fe031d1c9d47a6dc4b5c24730eaa0708fd24e3eda907c646eb240bc76a0c2d78f591c474016e35c2bee1be84ef92d3230223feee5d196209d1ef04f9e8c2"
}