đ
Original date posted:2013-05-09
đ Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
After some consultation with affected sites by myself and Peter we have decided
to release an initial replace-by-fee implementation and setup a server using
those rules on testnet. This implementation does not include recursive fee
evaluation, and is therefore vulnerable to DoS attack, so hopefully that will
continue to allow adoption to proceed gradually. We can-not recommend mining on
mainnet with it. It does not include an "undo" RPC command or an adjust fees,
and Peter says he has not implemented one yet. Patches are welcome.
Specifically there were requests from vulnerable parties, which interestingly
included a site that knew they had bugs related to replacement but not
financial vulnerabilities, to put up a server on testnet to check wallet code.
The vulnerable requested to remain undisclosed. An additional consideration was
the upcoming anti-dust rules which are yet another example of why zero-conf is
so much more dangerous to accept than single-conf. Two of the people contacting
us brought up that issue in fact.
The code is on github:
https://github.com/petertodd/bitcoin/tree/replace-by-fee
and a replace-by-fee server operating on testnet is available at
testnet-replace-by-fee.bitcoin.petertodd.org To test you will need to use the
raw transaction API and manually create the replacement transaction. Do note
that your wallet will retain the existing one and no mechanism yet exists to
delete the old transaction from your wallet. Again, a certain amount of
"cludgyness" to this is intentional to discourage premature non-testing use.
Regarding the reward, I've decided Peter will collect the full amount even
though the work is not %100 complete (the mempool aspect) due to his concern
about staging an implementation properly, working with vulnerable sites, and
overall genuine interest in the actual issues at hand rather than the reward.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJRi3LeAAoJEEWCsU4mNhiPwscH/2CI0d3h/3jix3iyz2I9I8Sz
6nbP8eA01l9kzG37cH1rFAbt7C+fL/nardV4U1qmiwC0MN7NPpX6BFn5eQ2PUKbu
41+AnjgWicB2tnCC07ngboQ1JCeZ+RTfATepuMxEdWFBsc8ZQXs0apWS01FT+TDq
J/a7QkhNfTaAQzXyqmLp0TQO7/Z7ysmCftOhtGbfvfhF2o23BuphQiRVA9IOoUuj
Fgb5wrfQqJ8TjvXRXAUQ7SUlzfN9BlPxMkTc6NhbcgIpuq1Kb43mLoDl3s2irH4A
GtjRtobV5Cfozm1r+8KPtIYEoQoj0PqTjO5YMwD/vTaRfNzdS4Tse5LQLGT6Jug=
=M1mj
-----END PGP SIGNATURE-----
John Dillon [ARCHIVE] /
npub15zâŚkn0zr
2023-06-07 15:01:35
in reply to nevent1qâŚ49w3
Author Public Key
npub15z6e9t07ugx267aj3s3c487pln852ydytzlgu0vkkqxfznyvx4jq4kn0zrPublished at
2023-06-07 15:01:35Event JSON
{
"id": "3040ddd468ab977ec402706e874cf6adab96fb6340e773fa298af4410c98413c",
"pubkey": "a0b592adfee20cad7bb28c238a9fc1fccf4511a458be8e3d96b00c914c8c3564",
"created_at": 1686150095,
"kind": 1,
"tags": [
[
"e",
"40d9c2fb5f1f6fcca44f40d7ce89bcbc444b20146c8dc1bf81a61e997fa6df55",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "đ
Original date posted:2013-05-09\nđ Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\nAfter some consultation with affected sites by myself and Peter we have decided\nto release an initial replace-by-fee implementation and setup a server using\nthose rules on testnet. This implementation does not include recursive fee\nevaluation, and is therefore vulnerable to DoS attack, so hopefully that will\ncontinue to allow adoption to proceed gradually. We can-not recommend mining on\nmainnet with it. It does not include an \"undo\" RPC command or an adjust fees,\nand Peter says he has not implemented one yet. Patches are welcome.\n\nSpecifically there were requests from vulnerable parties, which interestingly\nincluded a site that knew they had bugs related to replacement but not\nfinancial vulnerabilities, to put up a server on testnet to check wallet code.\nThe vulnerable requested to remain undisclosed. An additional consideration was\nthe upcoming anti-dust rules which are yet another example of why zero-conf is\nso much more dangerous to accept than single-conf. Two of the people contacting\nus brought up that issue in fact.\n\nThe code is on github:\n\n https://github.com/petertodd/bitcoin/tree/replace-by-fee\n\nand a replace-by-fee server operating on testnet is available at\ntestnet-replace-by-fee.bitcoin.petertodd.org To test you will need to use the\nraw transaction API and manually create the replacement transaction. Do note\nthat your wallet will retain the existing one and no mechanism yet exists to\ndelete the old transaction from your wallet. Again, a certain amount of\n\"cludgyness\" to this is intentional to discourage premature non-testing use.\n\n\nRegarding the reward, I've decided Peter will collect the full amount even\nthough the work is not %100 complete (the mempool aspect) due to his concern\nabout staging an implementation properly, working with vulnerable sites, and\noverall genuine interest in the actual issues at hand rather than the reward.\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.11 (GNU/Linux)\n\niQEcBAEBCAAGBQJRi3LeAAoJEEWCsU4mNhiPwscH/2CI0d3h/3jix3iyz2I9I8Sz\n6nbP8eA01l9kzG37cH1rFAbt7C+fL/nardV4U1qmiwC0MN7NPpX6BFn5eQ2PUKbu\n41+AnjgWicB2tnCC07ngboQ1JCeZ+RTfATepuMxEdWFBsc8ZQXs0apWS01FT+TDq\nJ/a7QkhNfTaAQzXyqmLp0TQO7/Z7ysmCftOhtGbfvfhF2o23BuphQiRVA9IOoUuj\nFgb5wrfQqJ8TjvXRXAUQ7SUlzfN9BlPxMkTc6NhbcgIpuq1Kb43mLoDl3s2irH4A\nGtjRtobV5Cfozm1r+8KPtIYEoQoj0PqTjO5YMwD/vTaRfNzdS4Tse5LQLGT6Jug=\n=M1mj\n-----END PGP SIGNATURE-----",
"sig": "da3905e7e45974beae2888fa6efb3a65f51c99f0f49c01eeacb3844cb907aa88db1caf0b93c7d2043420128bc4e7f1133b99a64b8380ff885944230328496469"
}