📅 Original date posted:2014-08-23
📝 Original message:On Sat, Aug 23, 2014 at 04:50:30PM +0000, Justus Ranvier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 08/23/2014 04:17 PM, xor wrote:
> > On Tuesday, August 19, 2014 07:40:39 PM Jeff Garzik wrote:
> >> Encryption is of little value if you may deduce the same
> >> information by observing packet sizes and timings.
> >
> > Instead of spawning a discussion whether this aspect is a reason to
> > NOT encrypt, you should do the obvious:
> >
> > Fix that as well. X being broken is not a reason for not fixing Y.
> > Pad the then encrypted packets with random bytes. The fact that
> > they are encrypted makes them look like random data already, so the
> > padding will not be distinguishable from the rest. Also, add some
> > random bias to their timing.
>
> The packet size and timing issue will become less of an issue as the
> network grows anyway.
>
> One transaction inserted into a 3 transaction-per-second encrypted
> stream is more obvious than the same transaction inserted into a 100
> or 1000 TPS stream.
The requirement for anonymity and privacy is lawyers and a Bitlicense.
If you want privacy and anonymity, then do high-frequency trading on
a centralized exchange, and if you want to go over-the-top, run some
arbitrage bots as well, and hide in the millions of transactions per
second that go on.
But make sure you get a Bitlicense and have a good securities lawyer.
Trying to solve a legal/legislative/social problem with more crypto is
only going to serve the people who created the legal/legislative/social
problem in the first place, because they can hire a hacker who will
find a misplaced (} in your crypto code, and all the work you did to
encrypt wire protocols becomes silently worthless.
Troy Benjegerdes [ARCHIVE] /
npub1m6…rdjn5
2023-06-07 15:25:24
in reply to nevent1q…ddnj
Author Public Key
npub1m6p5kgcd428x6pxyfege98zjmlwrdhp0gyz6pdnsvrvalscddnxqurdjn5Published at
2023-06-07 15:25:24Event JSON
{
"id": "06dc0dfc8cf014ca09c44ea3c81d67a8646862ed49ef5abd61dbae193e79cb72",
"pubkey": "de834b230daa8e6d04c44e51929c52dfdc36dc2f4105a0b67060d9dfc30d6ccc",
"created_at": 1686151524,
"kind": 1,
"tags": [
[
"e",
"f7d80207f3f3e09247c97d3e8c17b8e8b9ffc855be5e4ac09f019815084b2528",
"",
"root"
],
[
"e",
"a957e530ceab746bd49293372f5faf5066986c5eb33dd74836065deb8b9d30bc",
"",
"reply"
],
[
"p",
"b2b39b6f2c86908d3da9f500193abd5757b21cac328f838800a48c4d557c10dd"
]
],
"content": "📅 Original date posted:2014-08-23\n📝 Original message:On Sat, Aug 23, 2014 at 04:50:30PM +0000, Justus Ranvier wrote:\n\u003e -----BEGIN PGP SIGNED MESSAGE-----\n\u003e Hash: SHA256\n\u003e \n\u003e On 08/23/2014 04:17 PM, xor wrote:\n\u003e \u003e On Tuesday, August 19, 2014 07:40:39 PM Jeff Garzik wrote:\n\u003e \u003e\u003e Encryption is of little value if you may deduce the same\n\u003e \u003e\u003e information by observing packet sizes and timings.\n\u003e \u003e \n\u003e \u003e Instead of spawning a discussion whether this aspect is a reason to\n\u003e \u003e NOT encrypt, you should do the obvious:\n\u003e \u003e \n\u003e \u003e Fix that as well. X being broken is not a reason for not fixing Y. \n\u003e \u003e Pad the then encrypted packets with random bytes. The fact that\n\u003e \u003e they are encrypted makes them look like random data already, so the\n\u003e \u003e padding will not be distinguishable from the rest. Also, add some\n\u003e \u003e random bias to their timing.\n\u003e \n\u003e The packet size and timing issue will become less of an issue as the\n\u003e network grows anyway.\n\u003e \n\u003e One transaction inserted into a 3 transaction-per-second encrypted\n\u003e stream is more obvious than the same transaction inserted into a 100\n\u003e or 1000 TPS stream.\n\nThe requirement for anonymity and privacy is lawyers and a Bitlicense.\n\nIf you want privacy and anonymity, then do high-frequency trading on\na centralized exchange, and if you want to go over-the-top, run some\narbitrage bots as well, and hide in the millions of transactions per\nsecond that go on.\n\nBut make sure you get a Bitlicense and have a good securities lawyer.\n\nTrying to solve a legal/legislative/social problem with more crypto is\nonly going to serve the people who created the legal/legislative/social\nproblem in the first place, because they can hire a hacker who will \nfind a misplaced (} in your crypto code, and all the work you did to\nencrypt wire protocols becomes silently worthless.",
"sig": "c6f32438a74c2184094d737a690d81e42d07ab48947b6d7aaf0887f737ae7b91724e37565dc553060605eb0b9bd0f5388fb47fe8b4703cafd5b1cfa4d5c92fb6"
}