bgroff at lavabit.com [ARCHIVE] on Nostr: 📅 Original date posted:2011-08-07 🗒️ Summary of this message: Discussion on ...
📅 Original date posted:2011-08-07
🗒️ Summary of this message: Discussion on mining non-standard transactions and the importance of propagation. IsStandard part is uncontroversial and could be implemented quickly.
📝 Original message:> On Wed, Aug 3, 2011 at 2:10 AM, <bgroff at lavabit.com> wrote:
>> Thank you! Â (I think you mean 319 here)
>
> Correct.
>
>> With Eligius mining !IsStandard transactions and probably other pools
>> open
>> to the idea, I am hopeful that we can quickly get 30%+ of mining power
>> to
>> upgrade, which means that we could still mine these in a reasonable time
>> frame (under 1 hour).
>
> It's not just a matter of mining power, it's also a question of
> propagation. Matt and I tried to perform a non-standard transaction
> weeks ago and weren't able to get in mined after many hours. (we
> eventually double spent the input with a normal transaction in order
> to make it go away, interestingly one point about non-propagating txn
> is that they're extra vulnerable to double spending by a standard txn,
> as the non-standard one won't preclude the propagation of the standard
> one)
Right, the user would have to connect directly to miners accepting
non-standard transactions.
> From discussion on IRC it seemed clear enough that the current focus
> on maturity/bugfixes is probably going to delay your full patch, but
> the IsStandard part is uncontroversial and could go in quickly.
With the latest high profile security breaches, I am hoping that the whole
things can be pulled relatively soon. Building secure deposit systems
will improve trust in the ecosystem.
I've included a significant amount of unit tests to "pay" for the
additional feature, and I can add more if needed.
--
Bobby Groff
Published at
2023-06-07 02:10:22Event JSON
{
"id": "f629ea54ef965b25432fb7f04feb8151725fe1fb5342992d2fbca0b6d8c33bb2",
"pubkey": "fc38630711a8b1bf175abe9b428bbb6dec25a39bf3d75a91a411f204942572a4",
"created_at": 1686103822,
"kind": 1,
"tags": [
[
"e",
"26d2b12d74cc7eda50d225d370e6d62d72bcd36ed8521a48c7131e351bf9a32f",
"",
"root"
],
[
"e",
"fad7000c06b52eb71c640ad931c33881a981d9701bde7d59f02532cdb4733fee",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2011-08-07\n🗒️ Summary of this message: Discussion on mining non-standard transactions and the importance of propagation. IsStandard part is uncontroversial and could be implemented quickly.\n📝 Original message:\u003e On Wed, Aug 3, 2011 at 2:10 AM, \u003cbgroff at lavabit.com\u003e wrote:\n\u003e\u003e Thank you! Â (I think you mean 319 here)\n\u003e\n\u003e Correct.\n\u003e\n\u003e\u003e With Eligius mining !IsStandard transactions and probably other pools\n\u003e\u003e open\n\u003e\u003e to the idea, I am hopeful that we can quickly get 30%+ of mining power\n\u003e\u003e to\n\u003e\u003e upgrade, which means that we could still mine these in a reasonable time\n\u003e\u003e frame (under 1 hour).\n\u003e\n\u003e It's not just a matter of mining power, it's also a question of\n\u003e propagation. Matt and I tried to perform a non-standard transaction\n\u003e weeks ago and weren't able to get in mined after many hours. (we\n\u003e eventually double spent the input with a normal transaction in order\n\u003e to make it go away, interestingly one point about non-propagating txn\n\u003e is that they're extra vulnerable to double spending by a standard txn,\n\u003e as the non-standard one won't preclude the propagation of the standard\n\u003e one)\n\nRight, the user would have to connect directly to miners accepting\nnon-standard transactions.\n\n\u003e From discussion on IRC it seemed clear enough that the current focus\n\u003e on maturity/bugfixes is probably going to delay your full patch, but\n\u003e the IsStandard part is uncontroversial and could go in quickly.\n\nWith the latest high profile security breaches, I am hoping that the whole\nthings can be pulled relatively soon. Building secure deposit systems\nwill improve trust in the ecosystem.\n\nI've included a significant amount of unit tests to \"pay\" for the\nadditional feature, and I can add more if needed.\n\n--\nBobby Groff",
"sig": "1a896db5cb2a6431cdd134b72da513b5a8a1fd217f88998b9e0bfc1eda79eca41346fa8c1c0a60348a59a0f7b7aa463a16bac7c7a604d21d46c741d9d8e5f349"
}