public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Zac Greenwood <zachgrw@gmail.com>
To: Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>, Karl <gmkarl@gmail.com>
Subject: Re: [bitcoin-dev] Proposal: Force to do nothing for first 9 minutes to save 90% of mining energy
Date: Mon, 17 May 2021 11:34:38 +0200	[thread overview]
Message-ID: <CAJ4-pEDSkLTWOHjZCbLFAkAxsgpX2EGkaQV5LSgT8M_fHQqShQ@mail.gmail.com> (raw)
In-Reply-To: <CALL-=e65rRCSHjcLsh1z-+9Ypvqr47G9EkVSsXxHYdqrdW6Z8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

>
>
> Are there people who can freely produce new mining equipment to an
> arbitrary degree?
>

Close. Bitmain for example produces their own ASICs and rigs which they
mine with. Antpool is controlled by Bitmain and has a significant amount of
the hash power. The marginal cost of an ASIC chip or mining rig is low
compared to R&D and setting up of the production lines etc. For Bitmain
it’s relatively cheap to produce an additional mining rig.

Unfortunately I failed to make sense of your other remarks which looked
rather confused so I take the liberty to disregard them.

Zac


_______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 1589 bytes --]

  reply	other threads:[~2021-05-17  9:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 21:41 [bitcoin-dev] Proposal: Force to do nothing for first 9 minutes to save 90% of mining energy Michael Fuhrmann
2021-05-15 22:14 ` René Pickhardt
2021-05-15 22:19 ` Pavol Rusnak
2021-05-16 15:30 ` Zac Greenwood
2021-05-16 18:10 ` Karl
2021-05-16 20:31   ` Anton Ragin
2021-05-16 22:06     ` Eric Voskuil
2021-05-16 23:29       ` Karl
2021-05-16 21:15   ` Zac Greenwood
2021-05-16 22:05     ` Karl
2021-05-17  9:34       ` Zac Greenwood [this message]
2021-05-17  2:58 ` Luke Dashjr
2021-05-17 12:39   ` Anton Ragin
2021-05-18  7:46     ` ZmnSCPxj
2021-05-17 19:17   ` Michael Fuhrmann
2021-05-18  8:04     ` ZmnSCPxj
2021-05-17  5:17 ` yanmaani
2021-05-17 13:14 befreeandopen
2021-05-17 13:53 ` Anton Ragin
2021-05-17 17:28   ` Keagan McClelland
2021-05-17 23:02     ` Anton Ragin

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=CAJ4-pEDSkLTWOHjZCbLFAkAxsgpX2EGkaQV5LSgT8M_fHQqShQ@mail.gmail.com \
    --to=zachgrw@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=gmkarl@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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