From: Billy Tetrud <billy.tetrud@gmail•com>
To: Karl <gmkarl@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reducing block reward via soft fork
Date: Mon, 24 May 2021 22:01:07 -1000 [thread overview]
Message-ID: <CAGpPWDbDg+N72ce8ird_A_=vY-DHP87E+WCH-d40MnWasbk-6g@mail.gmail.com> (raw)
In-Reply-To: <CALL-=e5BKBBkw3EkeYhHgzvEBuRdOOS1QnXpwh5qF1J6TEK3Hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2683 bytes --]
> It seems to me bitcoin's biggest vulnerabilities are either covert
compromise of mining pool operations, or widespread compromise of networked
mining systems and client node
Stratum v2 will solve the mining pool problem. Widespread compromise of
mining systems seems far fetched. That would involve compromising hundreds
of thousands or perhaps millions of systems in disparate areas with
disparate operating systems and security procedures, run by people who
probably understand computer security better than most (given their
involvement in bitcoin).
I think the biggest vulnerability bitcoin has is a sybil attack draining
the resources of public full nodes. We only have like 10,000 public full
nodes serving the whole network. It wouldn't take that much money to create
a sybil botnet of 100,000 or 1 million nodes that connect to the bitcoin
network and simply take up public node resources, denying service to most
people's full nodes.
> I don't see why it would necessarily be made public if a government
compromised their nation's mining farms. Governments have skilled
operatives for things like that.
Skilled operatives have their limits. It could be kept secret if spies were
hired as employees and then systematically infected all the machines in a
mining operation's machines. But spies aren't magic, no matter how skilled.
One mistake and the jig is up. It would be more likely to be a backroom
deal, which would be harder to keep secret, especially in large operations.
Propaganda has its limits too, sure you could convince some people things
are fine, but sophisticated people like miners? I doubt it.
On Mon, May 24, 2021 at 2:55 PM Karl <gmkarl@gmail•com> wrote:
> If bitcoin were to ever consider changing their PoW algorithm a
> little, it seems that would immediately make purchased ASIC mining
> equipment partially or wholly unusable to compromise the chain (and
> temporarily reduce energy usage without necessarily reducing
> security). One possible plan to deter a multibillionaire attack.
>
> Also regarding the word "security" here, a 51% attack impacts some
> parts of chain operations, but not others.
>
> It seems to me bitcoin's biggest vulnerabilities are either covert
> compromise of mining pool operations, or widespread compromise of
> networked mining systems and client nodes. Far easier than
> outcompeting the mining network with hardware.
>
> I don't see why it would necessarily be made public if a government
> compromised their nation's mining farms. Governments have skilled
> operatives for things like that. People would guess it happened, and
> the government would cover up the guesses with more powerful stories.
>
[-- Attachment #2: Type: text/html, Size: 3244 bytes --]
next prev parent reply other threads:[~2021-05-25 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 1:00 James Lu
2021-05-23 10:42 ` Anton Ragin
[not found] ` <CANQHGB2pD57cZzcuTqr25Pg-Bvon_=G=_5901to2esrcumk-GA@mail.gmail.com>
2021-05-23 14:40 ` [bitcoin-dev] Fwd: " James Lu
2021-05-23 11:26 ` [bitcoin-dev] " ZmnSCPxj
2021-05-23 12:08 ` Karl
2021-05-23 13:35 ` ZmnSCPxj
2021-05-23 19:44 ` Karl
2021-05-24 20:28 ` Billy Tetrud
2021-05-24 21:55 ` Erik Aronesty
2021-05-25 0:55 ` Karl
2021-05-25 8:01 ` Billy Tetrud [this message]
2021-05-25 8:35 ` Jorge Timón
2021-05-25 8:53 ` Melvin Carvalho
2021-05-25 19:40 ` Billy Tetrud
2021-05-24 22:03 ` Phuoc Do
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGpPWDbDg+N72ce8ird_A_=vY-DHP87E+WCH-d40MnWasbk-6g@mail.gmail.com' \
--to=billy.tetrud@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gmkarl@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox