📅 Original date posted:2017-03-15
📝 Original message:Agreed.
In contrast, BIP37 as used today is totally decentralized, and can me
made much more secure, private, and scalable -- without giving up the
utility of unconfirmed transactions.
Please don't read into this statement a belief that all the coffees
should go on the chain, or that the security or privacy of BIP37 compare
favorably to any other particular thing.
https://docs.google.com/presentation/d/13MzUo2iIH9JBW29TgtPMoaMXxeEdanWDfi6SlfO-LlA
On 1/5/2017 6:04 PM, bfd--- via bitcoin-dev wrote:
> 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.
>
Tom Harding [ARCHIVE] /
npub1ms…pmwjy
2023-06-07 17:57:18
in reply to nevent1q…wdsh
Author Public Key
npub1msef5qkfwz4t7qacwxz775wgdtlytph78g2g2z903x90874u263sypmwjyPublished at
2023-06-07 17:57:18Event JSON
{
"id": "05427ec29ea913df496c18b2d529592ade51d498184df435c9126e3f70641d0e",
"pubkey": "dc329a02c970aabf03b87185ef51c86afe4586fe3a148508af898af3fabc56a3",
"created_at": 1686160638,
"kind": 1,
"tags": [
[
"e",
"4b1752cfa8e322a52901f8a73403b24006853bdfbdcea90aaa66fa8a2818d2e6",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-03-15\n📝 Original message:Agreed.\n\nIn contrast, BIP37 as used today is totally decentralized, and can me \nmade much more secure, private, and scalable -- without giving up the \nutility of unconfirmed transactions.\n\nPlease don't read into this statement a belief that all the coffees \nshould go on the chain, or that the security or privacy of BIP37 compare \nfavorably to any other particular thing.\n\nhttps://docs.google.com/presentation/d/13MzUo2iIH9JBW29TgtPMoaMXxeEdanWDfi6SlfO-LlA\n\n\n\nOn 1/5/2017 6:04 PM, bfd--- via bitcoin-dev wrote:\n\u003e You might as well replace Bitcoin with a system where these parties\n\u003e sign transactions and skip mining altogether, it would have the same\n\u003e properties and be significantly more effient.\n\u003e\n\u003e\n\u003e On 2017-01-04 23:06, Chris Priest wrote:\n\u003e\u003e On 1/3/17, Jonas Schnelli via bitcoin-dev\n\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e\u003e\n\u003e\u003e\u003e There are plenty, more sane options. If you can't run your own \n\u003e\u003e\u003e full-node\n\u003e\u003e\u003e as a merchant (trivial), maybe co-use a wallet-service with centralized\n\u003e\u003e\u003e verification (maybe use two of them), I guess Copay would be one of\n\u003e\u003e\u003e those wallets (as an example). Use them in watch-only mode.\n\u003e\u003e\n\u003e\u003e The best way is to connect to the mempool of each miner and check to\n\u003e\u003e see if they have your txid in their mempool.\n\u003e\u003e\n\u003e\u003e https://www.antpool.com/api/is_in_mempool?txid=334847bb...\n\u003e\u003e https://www.f2pool.com/api/is_in_mempool?txid=334847bb...\n\u003e\u003e https://bw.com/api/is_in_mempool?txid=334847bb...\n\u003e\u003e https://bitfury.com/api/is_in_mempool?txid=334847bb...\n\u003e\u003e https://btcc.com/api/is_in_mempool?txid=334847bb...\n\u003e\u003e\n\u003e\u003e If each of these services return \"True\", and you know those services\n\u003e\u003e so not engage in RBF, then you can assume with great confidence that\n\u003e\u003e your transaction will be in the next block, or in a block very soon.\n\u003e\u003e If any one of those services return \"False\", then you must assume that\n\u003e\u003e it is possible that there is a double spend floating around, and that\n\u003e\u003e you should wait to see if that tx gets confirmed. The problem is that\n\u003e\u003e not every pool runs such a service to check the contents of their\n\u003e\u003e mempool...\n\u003e\u003e\n\u003e\u003e This is an example of mining centralization increasing the security of\n\u003e\u003e zero confirm. If more people mined, this method will not work as well\n\u003e\u003e because it would require you to call the API of hundreds of different\n\u003e\u003e potential block creators.\n\u003e",
"sig": "d6342f95f42f0039c15c95a7c044d54bc8d3e370fde26cf1bbc77f4eee91ec97a2f5f5daf72eb4305a6bc94bf29a64b035b42ba2de97c7e817bfeac69fdeaa17"
}