📅 Original date posted:2014-02-28
📝 Original message:To each his own, but if I say "Please don't charge me for YOUR privacy
by putting junk like stealth addresses in the blockchain", I think I'd
get laughed out of most rooms.
Either the transaction fees are sufficient to pay the cost for whatever
random junk anyone wants to put there, or they are not, and if they are
not, then I suggest you re-think the fee structure rather than trying
to pre-regulate me putting 80 character pithy quotes in the blockhain.
On Mon, Feb 24, 2014 at 09:23:12AM -0800, Mark Friedenbach wrote:
> Given our standardization on 128-bit security / 256-bit primitives, I
> can't think of any crypto related data payload which requires more than
> 40 bytes. Even DER encoded compressed public keys will fit in there. A
> signature won't fit, but why would you need one in there?
>
> There's no need to design for 64-byte hashes, and the 80-char line
> length comparison is a good point. As an Engineer I'd want to have a
> little more room as a 32-byte hash or EC point + 8 bytes identifying
> prefix data is the bare minimum, but it is also very important that we
> send a message: This is for payment related applications like stealth
> addresses only. Don't burden everybody by putting your junk on the block
> chain.
>
> On 02/24/2014 08:39 AM, Wladimir wrote:
> >
> > On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik <jgarzik at bitpay.com
> > <mailto:jgarzik at bitpay.com>> wrote:
> >
> > A common IRC proposal seems to lean towards reducing that from 80.
> > I'll leave it to the crowd to argue about size from there. I do think
> > regular transactions should have the ability to include some metadata.
> >
> >
> > I'd be in favor of bringing it down to 40 for 0.9.
> >
> > That'd be enough for <8 byte header/identifier><32 byte hash>.
> >
> > 80, as the standard line length, is almost asking for "insert your
> > graffiti message here". I also see no need for 64 bytes hashes such as
> > SHA512 in the context of bitcoin, as that only offers 256-bit security
> > (at most) in the first place.
> >
> > And if this is not abused, these kind of transactions become popular,
> > and more space is really needed, the limit can always be increased in a
> > future version.
> >
> > Wladimir
> >
> >
> > ------------------------------------------------------------------------------
> > Flow-based real-time traffic analytics software. Cisco certified tool.
> > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> > Customize your own dashboards, set traffic alerts and generate reports.
> > Network behavioral analysis & security monitoring. All-in-one tool.
> > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> >
> >
> >
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
>
> ------------------------------------------------------------------------------
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
----------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer at hozed.org
7 elements earth::water::air::fire::mind::spirit::soul grid.coop
Never pick a fight with someone who buys ink by the barrel,
nor try buy a hacker who makes money by the megahash
Troy Benjegerdes [ARCHIVE] /
npub1m6…rdjn5
2023-06-07 15:13:58
in reply to nevent1q…qn3p
Author Public Key
npub1m6p5kgcd428x6pxyfege98zjmlwrdhp0gyz6pdnsvrvalscddnxqurdjn5Published at
2023-06-07 15:13:58Event JSON
{
"id": "49df77d69d2bec33878a1c723df1640aa5cfe43d26b1e5704cb149bd5960134b",
"pubkey": "de834b230daa8e6d04c44e51929c52dfdc36dc2f4105a0b67060d9dfc30d6ccc",
"created_at": 1686150838,
"kind": 1,
"tags": [
[
"e",
"1ef870aa2080d76066b16301e94316a8cf8557aa7768e48cc4c5664289bfd14e",
"",
"root"
],
[
"e",
"1a15f789ccb4efda74480f35c7723e17500e2f24a42cbc9d103d3ca4f20c7d6c",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2014-02-28\n📝 Original message:To each his own, but if I say \"Please don't charge me for YOUR privacy\nby putting junk like stealth addresses in the blockchain\", I think I'd\nget laughed out of most rooms.\n\nEither the transaction fees are sufficient to pay the cost for whatever\nrandom junk anyone wants to put there, or they are not, and if they are\nnot, then I suggest you re-think the fee structure rather than trying\nto pre-regulate me putting 80 character pithy quotes in the blockhain.\n\n\nOn Mon, Feb 24, 2014 at 09:23:12AM -0800, Mark Friedenbach wrote:\n\u003e Given our standardization on 128-bit security / 256-bit primitives, I\n\u003e can't think of any crypto related data payload which requires more than\n\u003e 40 bytes. Even DER encoded compressed public keys will fit in there. A\n\u003e signature won't fit, but why would you need one in there?\n\u003e \n\u003e There's no need to design for 64-byte hashes, and the 80-char line\n\u003e length comparison is a good point. As an Engineer I'd want to have a\n\u003e little more room as a 32-byte hash or EC point + 8 bytes identifying\n\u003e prefix data is the bare minimum, but it is also very important that we\n\u003e send a message: This is for payment related applications like stealth\n\u003e addresses only. Don't burden everybody by putting your junk on the block\n\u003e chain.\n\u003e \n\u003e On 02/24/2014 08:39 AM, Wladimir wrote:\n\u003e \u003e \n\u003e \u003e On Mon, Feb 24, 2014 at 5:03 PM, Jeff Garzik \u003cjgarzik at bitpay.com\n\u003e \u003e \u003cmailto:jgarzik at bitpay.com\u003e\u003e wrote:\n\u003e \u003e \n\u003e \u003e A common IRC proposal seems to lean towards reducing that from 80.\n\u003e \u003e I'll leave it to the crowd to argue about size from there. I do think\n\u003e \u003e regular transactions should have the ability to include some metadata.\n\u003e \u003e \n\u003e \u003e \n\u003e \u003e I'd be in favor of bringing it down to 40 for 0.9.\n\u003e \u003e \n\u003e \u003e That'd be enough for \u003c8 byte header/identifier\u003e\u003c32 byte hash\u003e.\n\u003e \u003e \n\u003e \u003e 80, as the standard line length, is almost asking for \"insert your\n\u003e \u003e graffiti message here\". I also see no need for 64 bytes hashes such as\n\u003e \u003e SHA512 in the context of bitcoin, as that only offers 256-bit security\n\u003e \u003e (at most) in the first place.\n\u003e \u003e \n\u003e \u003e And if this is not abused, these kind of transactions become popular,\n\u003e \u003e and more space is really needed, the limit can always be increased in a\n\u003e \u003e future version.\n\u003e \u003e \n\u003e \u003e Wladimir\n\u003e \u003e \n\u003e \u003e \n\u003e \u003e ------------------------------------------------------------------------------\n\u003e \u003e Flow-based real-time traffic analytics software. Cisco certified tool.\n\u003e \u003e Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer\n\u003e \u003e Customize your own dashboards, set traffic alerts and generate reports.\n\u003e \u003e Network behavioral analysis \u0026 security monitoring. All-in-one tool.\n\u003e \u003e http://pubads.g.doubleclick.net/gampad/clk?id=126839071\u0026iu=/4140/ostg.clktrk\n\u003e \u003e \n\u003e \u003e \n\u003e \u003e \n\u003e \u003e _______________________________________________\n\u003e \u003e Bitcoin-development mailing list\n\u003e \u003e Bitcoin-development at lists.sourceforge.net\n\u003e \u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \u003e \n\u003e \n\u003e ------------------------------------------------------------------------------\n\u003e Flow-based real-time traffic analytics software. Cisco certified tool.\n\u003e Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer\n\u003e Customize your own dashboards, set traffic alerts and generate reports.\n\u003e Network behavioral analysis \u0026 security monitoring. All-in-one tool.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=126839071\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-- \n----------------------------------------------------------------------------\nTroy Benjegerdes 'da hozer' hozer at hozed.org\n7 elements earth::water::air::fire::mind::spirit::soul grid.coop\n\n Never pick a fight with someone who buys ink by the barrel,\n nor try buy a hacker who makes money by the megahash",
"sig": "83bdf4810994dec3882b7b6f3e7550553616dcbb00909bd768992bf1f1c19382c7cd903edb9f68889bc972b55306e0ef8d02424b2e246797b77d3c0ba1736aae"
}