Re: [bitcoin-dev] Block solving slowdown question/poll

[ZmnSCPxj via bitcoin-dev]

Good morning Andrew,

> Here's a better explanation than I could write of the phenomenon I'm talking
> about:
>
> > As a thought experiment, let’s consider aquaculture (fish farming) in a 
> > lake.
> > Imagine a lake with a thousand identical fish farms owned by a thousand
> > competing companies. Each fish farm earns a profit of $1000/month. For a
> > while, all is well.
> > But each fish farm produces waste, which fouls the water in the lake. Let’s
> > say each fish farm produces enough pollution to lower productivity in the
> > lake by $1/month.
> > A thousand fish farms produce enough waste to lower productivity by
> > $1000/month, meaning none of the fish farms are making any money. Capitalism
> > to the rescue: someone invents a complex filtering system that removes waste
> > products. It costs $300/month to operate. All fish farms voluntarily install
> > it, the pollution ends, and the fish farms are now making a profit of
> > $700/month – still a respectable sum.
> > But one farmer (let’s call him Steve) gets tired of spending the money to
> > operate his filter. Now one fish farm worth of waste is polluting the lake,
> > lowering productivity by $1. Steve earns $999 profit, and everyone else 
> > earns
> > $699 profit.
> > Everyone else sees Steve is much more profitable than they are, because he’s
> > not spending the maintenance costs on his filter. They disconnect their
> > filters too.
> > Once four hundred people disconnect their filters, Steve is earning
> > $600/month – less than he would be if he and everyone else had kept their
> > filters on! And the poor virtuous filter users are only making $300. Steve
> > goes around to everyone, saying “Wait! We all need to make a voluntary pact
> > to use filters! Otherwise, everyone’s productivity goes down.”
> > Everyone agrees with him, and they all sign the Filter Pact, except one
> > person who is sort of a jerk. Let’s call him Mike. Now everyone is back 
> > using
> > filters again, except Mike. Mike earns $999/month, and everyone else earns
> > $699/month. Slowly, people start thinking they too should be getting big
> > bucks like Mike, and disconnect their filter for $300 extra profit…
> > A self-interested person never has any incentive to use a filter. A
> > self-interested person has some incentive to sign a pact to make everyone 
> > use
> > a filter, but in many cases has a stronger incentive to wait for everyone
> > else to sign such a pact but opt out himself. This can lead to an 
> > undesirable
> > equilibrium in which no one will sign such a pact.
>
> Won't a thousand bitcoin-spenders, individually paying for their transactions
> but collectively paying for their security, end up falling into the same
> dynamic?

Fortunately in our case, only the top 4,000,000 weight worth of transactions 
gets in a block.
Every bitcoin spender has an incentive to spend as little as possible to get 
into this top 4,000,000 weight and no more, but they still have to outbid every 
other user who wants the same security.
Some bitcoin spender will then decide that overpaying slightly to ensure that 
they do not drop out of the top 4,000,000 weight even in case of a "slow" block.

Thus, there will always be a need for *some* block weight limit, and that is 
what ensures that miners can get paid.

Now it was brought up earlier that people are moving transactions offchain, but 
that is perfectly fine, because every offchain mechanism first needs an onchain 
setup, and will at some point need an onchain teardown.
This allows increasing the effective capacity, while still ensuring that 
onchain fees remain at a level that will still ensure continued healthy 
operation of the blockchain layer.
Basically, the offchain mechanism does not remove onchain fees, it only 
amortizes the onchain fees to multiple logical transactions.

Regards,
ZmnSCPxj
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[Andrew Cann via bitcoin-dev]

> To change the supply is far too big a change.

It would also be a big change if bitcoin became unusable due to mining profits
dropping low enough for a state actor with a warehouse full of asics to mount a
51% attack and mine empty blocks all day.

> What happens if I own a few million Bitcoin and then accidentally lose my
> private keys in a tragic ear-cleaning accident?
> Then the vote of that UTXO containing a few million Bitcoins will remain
> forever fixed and unable to change according to whatever you believe would
> make us as a community decide to change the inflation rate.

All that matters is whether the long-term rate of deflation due to lost coins
is less or greater than the rate of inflation. This determines whether the
proportion of coins whose signaled inflation rate is fixed in time would tend
towards zero or one. I think it's /fairly/ safe to assume that it would remain
less. People obviously have a pretty strong incentive to not lose their coins -
particularly people who are holding massive amounts of bitcoin - and as bitcoin
becomes more mainstream, regular users will necessarily be using forms of
protection against losing their coins (whatever they might be). Contrast this
against the inflation rate which should remain high enough to prevent very
wealthy entities from being able to mount a 51% attack. What proportion of the
total market cap of bitcoin do you think your least favorite government could
plausibly be willing to spend to take down bitcoin for a month? And do you
think it's less or greater than the proportion of all bitcoins that get lost in
a month?

> It is helpful to remember that as a UTXO gets buried deeper, its security is
> inevitably better, and once I have a sufficient level of security in my
> ownership of the coin, I will not particularly care about any improved
> security and will not be interested in paying for more.

If we're talking about the possibility of your coin becoming worthless because
someone out there can unwind transactions at will and prevent you from spending
it then you should definitely be interested.

> If I want to *spend* my Bitcoins on something --- and nothing has value until
> I actually utilize it --- then I *will* pay transaction fees. The receiver of
> the coin would want to ensure that the received UTXO is deeply buried to the
> point that it has sufficient security for the receiver, before releasing or
> providing me with whatever I am exchanging the coin for.
>
> Thus, if I find that there are no miners at all, I could offer a high fee to
> get my transaction mined. Of course, you might say that this only pays for
> one block.
>
> But in most cases I will have more value remaining beyond what I spend to the
> receiver, i.e. I have a change output from that transaction.
>
> In such a case, I can  pay for more blocks by re-spending the change output
> to myself, paying a transaction fee each time, until the original transaction
> that spends to the receiver is deeply buried and the receiver credits it and
> then releases the product or service I am exchanging *for*. Alternately the
> receiver can do the same for its *own* UTXO, and will increase the payment it
> demands from me in order to perform this itself; thus I still end up paying
> for the security of the *transaction* and not the security of the *holding*.

In your example though it's just you or the receiver paying for blocks. In that
case you're only paying for your own security and so there's no tragedy of the
commons and the system works. But once you have a thousand people putting
transactions in every block and everyone is collectively paying for everyone's
collective security then, without some mechanism to force everyone to pay their
fair share, you're inviting Moloch to the party.

Here's a better explanation than I could write of the phenomenon I'm talking
about:

> As a thought experiment, let’s consider aquaculture (fish farming) in a lake.
> Imagine a lake with a thousand identical fish farms owned by a thousand
> competing companies. Each fish farm earns a profit of $1000/month. For a
> while, all is well.
> 
> But each fish farm produces waste, which fouls the water in the lake. Let’s
> say each fish farm produces enough pollution to lower productivity in the
> lake by $1/month.
> 
> A thousand fish farms produce enough waste to lower productivity by
> $1000/month, meaning none of the fish farms are making any money. Capitalism
> to the rescue: someone invents a complex filtering system that removes waste
> products. It costs $300/month to operate. All fish farms voluntarily install
> it, the pollution ends, and the fish farms are now making a profit of
> $700/month – still a respectable sum.
> 
> But one farmer (let’s call him Steve) gets tired of spending the money to
> operate his filter. Now one fish farm worth of waste is polluting the lake,
> lowering productivity by $1. Steve earns $999 profit, and everyone else earns
> $699 profit.
> 
> Everyone else 

Re: [bitcoin-dev] Block solving slowdown question/poll

[Andrew Cann via bitcoin-dev]

Hi, noob question here: Is there a long-term plan for if the block reward drops
too low to ensure the security of the network?

IIUC miners only make profit from block rewards and transaction fees, and once
the block reward drop to zero we're merely hoping that transaction fees will
keep mining expensive enough to stop a state actor or someone from buying
enough hash power to attack the network. If that's the case, should we start
making plans now to change the protocol to allow an adjustable block reward?

Here's a half-baked idea I had of how that could work: Since the block reward
dilutes the value of the currency bitcoin holders have an incentive to keep the
reward low. However, since the block reward is also (partly) what incentivizes
mining, bitcoin holders also have an incentive to keep the reward high enough
to keep the network secure. So if bitcoin holders were able to vote to decide
the block reward they "should", hypothetically, reliably choose a value that
balances these two concerns. You could implement this voting by adding an
optional extra field to every txout that signals what the holder thinks the
inflation rate should be. If the field is missing you just assume the default
value based on the current protocol. Then, whenever a new block is mined, you
take the median inflation rate of all the pre-existing utxos, weighted by the
utxo value, to calculate the block's reward.

Is this idea fundamentally broken somehow? Or are there already better ideas
for how to tackle this problem (I don't follow this list very closely)? Or is
this actually a non-issue to start with?

 - Andrew



signature.asc
Description: Digital signature
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[Andrew Cann via bitcoin-dev]

Hi, thanks for the replies.

> Anyway, yes, your idea is fundamentally broken because a zero block reward
> happens because creating even one more satoshi will push the amount of
> bitcoin over 21,000,, breaking the meaning of "bitcoin," or, if you
> like, creating a fundamental contradiction in our use of the term. 

I wouldn't really consider that fundamentally broken. It changes the meaning of
"bitcoin", but so does every upgrade to the protocol. The worst problem I can
see with this is that there's probably a lot of software out there which
assumes a cap of 21M. But we'd have years to find and fix those bugs.

> They already do so, via an implicit "field", known as the transaction fee.
> This makes the vote for how much security is needed to be costly to the
> voter, which is appropriate: you pay for your security.

This isn't the same thing though, economically / game-theoretically speaking.
Transaction fees are only paid when bitcoins get moved. There's no on-going
cost for people holding bitcoins (assuming they're doing their day-to-day
transactions almost entirely off-chain, which is something that's only going to
become more common). More to the point, the transaction fee is only set by the
current demand for block space. If transaction fees drop too low to maintain a
secure hash rate then people *could* willingly pay more than they need to to
get their transactions mined, but it's unlikely they will since it'd be cheaper
to just pay the minimum and hope that everyone else covers the costs of keeping
the network secure for them.

With the voting idea everyone decides what everyone pays (via dilution) to keep
the network secure. Choosing to signal a high inflation rate doesn't mean you
pay more than everyone else, just that you might shift the median, so there's
no tragedy-of-the-commons problem. Also, votes are weighted by the value of
the utxo, so people both vote and pay in proportion to the amount of bitcoin
they're holding.

Does this make sense? Or is there some game-theoretic reason I'm not seeing for
why transaction fees can never drop dangerously low in the first place?

 - Andrew



signature.asc
Description: Digital signature
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[ZmnSCPxj via bitcoin-dev]

Good morning Andrew,

>
> > Anyway, yes, your idea is fundamentally broken because a zero block reward
> > happens because creating even one more satoshi will push the amount of
> > bitcoin over 21,000,, breaking the meaning of "bitcoin," or, if you
> > like, creating a fundamental contradiction in our use of the term.
>
> I wouldn't really consider that fundamentally broken. It changes the meaning 
> of
> "bitcoin", but so does every upgrade to the protocol. The worst problem I can
> see with this is that there's probably a lot of software out there which
> assumes a cap of 21M. But we'd have years to find and fix those bugs.

There are changes of meaning, and then there are changes of meaning.
Smaller changes that puny humans can understand are better than larger changes 
beyond the ken of mortal man.
To change the supply is far too big a change.

> > They already do so, via an implicit "field", known as the transaction fee.
> > This makes the vote for how much security is needed to be costly to the
> > voter, which is appropriate: you pay for your security.
>
> This isn't the same thing though, economically / game-theoretically speaking.
> Transaction fees are only paid when bitcoins get moved. There's no on-going
> cost for people holding bitcoins (assuming they're doing their day-to-day
> transactions almost entirely off-chain, which is something that's only going 
> to
> become more common). More to the point, the transaction fee is only set by the
> current demand for block space. If transaction fees drop too low to maintain a
> secure hash rate then people could willingly pay more than they need to to
> get their transactions mined, but it's unlikely they will since it'd be 
> cheaper
> to just pay the minimum and hope that everyone else covers the costs of 
> keeping
> the network secure for them.
>
> With the voting idea everyone decides what everyone pays (via dilution) to 
> keep
> the network secure. Choosing to signal a high inflation rate doesn't mean you
> pay more than everyone else, just that you might shift the median, so there's
> no tragedy-of-the-commons problem. Also, votes are weighted by the value of
> the utxo, so people both vote and pay in proportion to the amount of bitcoin
> they're holding.
>
> Does this make sense? Or is there some game-theoretic reason I'm not seeing 
> for
> why transaction fees can never drop dangerously low in the first place?

What happens if I own a few million Bitcoin and then accidentally lose my 
private keys in a tragic ear-cleaning accident?

Then the vote of that UTXO containing a few million Bitcoins will remain 
forever fixed and unable to change according to whatever you believe would make 
us as a community decide to change the inflation rate.

If you enforce that only "recently-created" UTXOs get to vote, then in order 
for me to affect the vote (in the happy case where I do **not** lose all my 
privkeys in a tragic ear-cleaning accident), I would have to make a synthetic 
self-paying transaction.
How is it so different from me having to make up a synthetic transaction in 
order to pay fees and thus affect the current security of the blockchain?

--

It is helpful to remember that as a UTXO gets buried deeper, its security is 
inevitably better, and once I have a sufficient level of security in my 
ownership of the coin, I will not particularly care about any improved security 
and will not be interested in paying for more, hence why should I support any 
fork which makes me pay for my security continuously when I can simply support 
a fork that retains the current supply and does *not* make me pay for continued 
security?

--

If I want to *spend* my Bitcoins on something --- and nothing has value until I 
actually utilize it --- then I *will* pay transaction fees.
The receiver of the coin would want to ensure that the received UTXO is deeply 
buried to the point that it has sufficient security for the receiver, before 
releasing or providing me with whatever I am exchanging the coin for.

Thus, if I find that there are no miners at all, I could offer a high fee to 
get my transaction mined.
Of course, you might say that this only pays for one block.

But in most cases I will have more value remaining beyond what I spend to the 
receiver, i.e. I have a change output from that transaction.
In such a case, I can  pay for more blocks by re-spending the change output to 
myself, paying a transaction fee each time, until the original transaction that 
spends to the receiver is deeply buried and the receiver credits it and then 
releases the product or service I am exchanging *for*.
Alternately the receiver can do the same for its *own* UTXO, and will increase 
the payment it demands from me in order to perform this itself; thus I still 
end up paying for the security of the *transaction* and not the security of the 
*holding*.

So there is really no need for any mechanism beyond transaction fees.

Regards,
ZmnSCPxj

Re: [bitcoin-dev] Block solving slowdown question/poll

[ZmnSCPxj via bitcoin-dev]

Good morning Andrew,


> > Hi, noob question here: Is there a long-term plan for if the block reward 
> > drops
> > too low to ensure the security of the network?
> >
> > IIUC miners only make profit from block rewards and transaction fees, and 
> > once
> > the block reward drop to zero we're merely hoping that transaction fees will
> > keep mining expensive enough to stop a state actor or someone from buying
> > enough hash power to attack the network. If that's the case, should we start
> > making plans now to change the protocol to allow an adjustable block reward?
> >
> > Here's a half-baked idea I had of how that could work: Since the block 
> > reward
> > dilutes the value of the currency bitcoin holders have an incentive to keep 
> > the
> > reward low. However, since the block reward is also (partly) what 
> > incentivizes
> > mining, bitcoin holders also have an incentive to keep the reward high 
> > enough
> > to keep the network secure. So if bitcoin holders were able to vote to 
> > decide
> > the block reward they "should", hypothetically, reliably choose a value that
> > balances these two concerns.

They already do so, via an implicit "field", known as the transaction fee.
This is "implicit" since it is only the difference of the sum of all inputs 
with the sum of all outputs, but any Bitcoin HODLer spending their coins always 
need to make this decision.

This makes the vote for how much security is needed to be costly to the voter, 
which is appropriate: you pay for your security.

This mechanism is the same mechanism as well that is the long-term plan for the 
lowered block rewards in the future, and is already the best known idea to 
tackle this problem as well.


Regards,
ZmnSCPxj
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[Dave Scotese via bitcoin-dev]

I believe this isn't something we need to address.  The fact is that every
byte stored in the blockchain is already valuable to everyone who downloads
the blockchain because of what it allows them to prove - by adding more
bytes to it.  Over time, the value per byte will increase.  Perhaps there
will be holding companies with specialized scripts that cost $500 - $1000
to add to the blockchain and allow those companies to handle transactions
for thousands of customers, kind of like a community lightning channel.

Anyway, yes, your idea is fundamentally broken because a zero block reward
happens because creating even one more satoshi will push the amount of
bitcoin over 21,000,, breaking the meaning of "bitcoin," or, if you
like, creating a fundamental contradiction in our use of the term.

On Mon, Mar 23, 2020 at 5:59 AM Andrew Cann  wrote:

> Hi, noob question here: Is there a long-term plan for if the block reward
> drops
> too low to ensure the security of the network?
>
> IIUC miners only make profit from block rewards and transaction fees, and
> once
> the block reward drop to zero we're merely hoping that transaction fees
> will
> keep mining expensive enough to stop a state actor or someone from buying
> enough hash power to attack the network. If that's the case, should we
> start
> making plans now to change the protocol to allow an adjustable block
> reward?
>
> Here's a half-baked idea I had of how that could work: Since the block
> reward
> dilutes the value of the currency bitcoin holders have an incentive to
> keep the
> reward low. However, since the block reward is also (partly) what
> incentivizes
> mining, bitcoin holders also have an incentive to keep the reward high
> enough
> to keep the network secure. So if bitcoin holders were able to vote to
> decide
> the block reward they "should", hypothetically, reliably choose a value
> that
> balances these two concerns. You could implement this voting by adding an
> optional extra field to every txout that signals what the holder thinks the
> inflation rate should be. If the field is missing you just assume the
> default
> value based on the current protocol. Then, whenever a new block is mined,
> you
> take the median inflation rate of all the pre-existing utxos, weighted by
> the
> utxo value, to calculate the block's reward.
>
> Is this idea fundamentally broken somehow? Or are there already better
> ideas
> for how to tackle this problem (I don't follow this list very closely)? Or
> is
> this actually a non-issue to start with?
>
>  - Andrew
>
>

-- 
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy  and Meme Racing
 (in alpha).
I'm the webmaster for The Voluntaryist  which
now accepts Bitcoin.
I also code for The Dollar Vigilante .
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[Dave Scotese via bitcoin-dev]

The software currently allows up to a two hour difference between the
system clock and the time implied by a fresh block's timestamp (if I
remember correctly).  This reliance on realtime system clocks can be used
in a much weaker form to justify a plan for a difficulty adjustment to be
built into the software for when the expected block production rate is far
enough behind its expected value.

We would have to agree on how far behind mining should be to justify
expediting the adjustment.  The sooner we decide on and implement this
second difficulty adjustment trigger, the better.  It cuts off a nightmare
scenario made possible by collusion between states through regulation and
fiat, as well as any other external factors.  I propose that miners
detecting that the expected 2016 blocks have not been mined after twice the
expected wait time (4032 * 10 minutes = 28 days) ought to signal their
recognition in any block they produce, to be rejected by any miner whose
clock disagrees (after taking into account the 2-hour leeway), and that any
block produced on top of one with such a signal should reflect an expedited
difficulty adjustment (and also include the signal), which is then in
effect for the rest of the 2016 blocks and the entire following difficulty
period.  Every block from there until the modulo 2016 block should have the
same signal, which not only indicates that a difficulty adjustment was
expedited, but also that the next modulo 2016 block should not make one,
but rather turn off the signal.

If anyone thinks it's a good enough idea for a BIP, I will consider writing
one unless someone else wants to.

Dave.

On Sun, Mar 22, 2020 at 9:54 AM Eric Voskuil via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Mining is a lottery.
>
> e
>
> On Mar 22, 2020, at 07:10, LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> 
> There seems to be the real possibility that miners are simply trying to
> optimise mining profit by limiting the average hash rate during the
> retargeting, saving some electricity but poorly considering the overall
> situation where they give opportunity to other miners probably raising the
> hashrate for the next period. It is far more profitable for the ecosystem
> considering the whole to hold a lottery for minig as has been discussed
> elsewhere some time ago.
>
> Regards,
> LORD HIS EXCELLENCY JAMES HRMH
>
>
> --
> *From:* bitcoin-dev  on
> behalf of David A. Harding via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org>
> *Sent:* Sunday, 22 March 2020 6:54 PM
> *To:* Dave Scotese ; Bitcoin Protocol Discussion
> 
> *Subject:* Re: [bitcoin-dev] Block solving slowdown question/poll
>
> On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scotese via bitcoin-dev
> wrote:
> > [Imagine] we also see mining power dropping off at a rate that
> > suggests the few days [until retarget] might become a few weeks, and
> > then, possibly, a few months or even the unthinkable, a few eons.  I'm
> > curious to know if anyone has ideas on how this might be handled
>
> There are only two practical solutions I'm aware of:
>
> 1. Do nothing
> 2. Hard fork a difficulty reduction
>
> If bitcoins retain even a small fraction of their value compared to the
> previous retarget period and if most mining equipment is still available
> for operation, then doing nothing is probably the best choice---as block
> space becomes scarcer, transaction feerates will increase and miners
> will be incentivized to increase their block production rate.
>
> If the bitcoin price has plummeted more than, say, 99% in two weeks
> with no hope of short-term recovery or if a large fraction of mining
> equipment has become unusable (again, say, 99% in two weeks with no
> hope of short-term recovery), then it's probably worth Bitcoin users
> discussing a hard fork to reduce difficulty to a currently sustainable
> level.
>
> -Dave
> ___
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
> ___
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


-- 
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[Eric Voskuil via bitcoin-dev]

Mining is a lottery.

e

> On Mar 22, 2020, at 07:10, LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev 
>  wrote:
> 
> 
> There seems to be the real possibility that miners are simply trying to 
> optimise mining profit by limiting the average hash rate during the 
> retargeting, saving some electricity but poorly considering the overall 
> situation where they give opportunity to other miners probably raising the 
> hashrate for the next period. It is far more profitable for the ecosystem 
> considering the whole to hold a lottery for minig as has been discussed 
> elsewhere some time ago.
> 
> Regards,
> LORD HIS EXCELLENCY JAMES HRMH
> 
> 
> From: bitcoin-dev  on behalf 
> of David A. Harding via bitcoin-dev 
> Sent: Sunday, 22 March 2020 6:54 PM
> To: Dave Scotese ; Bitcoin Protocol Discussion 
> 
> Subject: Re: [bitcoin-dev] Block solving slowdown question/poll
>  
> On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scotese via bitcoin-dev wrote:
> > [Imagine] we also see mining power dropping off at a rate that
> > suggests the few days [until retarget] might become a few weeks, and
> > then, possibly, a few months or even the unthinkable, a few eons.  I'm
> > curious to know if anyone has ideas on how this might be handled
> 
> There are only two practical solutions I'm aware of:
> 
> 1. Do nothing
> 2. Hard fork a difficulty reduction
> 
> If bitcoins retain even a small fraction of their value compared to the
> previous retarget period and if most mining equipment is still available
> for operation, then doing nothing is probably the best choice---as block
> space becomes scarcer, transaction feerates will increase and miners
> will be incentivized to increase their block production rate.
> 
> If the bitcoin price has plummeted more than, say, 99% in two weeks
> with no hope of short-term recovery or if a large fraction of mining
> equipment has become unusable (again, say, 99% in two weeks with no
> hope of short-term recovery), then it's probably worth Bitcoin users
> discussing a hard fork to reduce difficulty to a currently sustainable
> level.
> 
> -Dave
> ___
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev]

There seems to be the real possibility that miners are simply trying to 
optimise mining profit by limiting the average hash rate during the 
retargeting, saving some electricity but poorly considering the overall 
situation where they give opportunity to other miners probably raising the 
hashrate for the next period. It is far more profitable for the ecosystem 
considering the whole to hold a lottery for minig as has been discussed 
elsewhere some time ago.

Regards,
LORD HIS EXCELLENCY JAMES HRMH



From: bitcoin-dev  on behalf of 
David A. Harding via bitcoin-dev 
Sent: Sunday, 22 March 2020 6:54 PM
To: Dave Scotese ; Bitcoin Protocol Discussion 

Subject: Re: [bitcoin-dev] Block solving slowdown question/poll

On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scotese via bitcoin-dev wrote:
> [Imagine] we also see mining power dropping off at a rate that
> suggests the few days [until retarget] might become a few weeks, and
> then, possibly, a few months or even the unthinkable, a few eons.  I'm
> curious to know if anyone has ideas on how this might be handled

There are only two practical solutions I'm aware of:

1. Do nothing
2. Hard fork a difficulty reduction

If bitcoins retain even a small fraction of their value compared to the
previous retarget period and if most mining equipment is still available
for operation, then doing nothing is probably the best choice---as block
space becomes scarcer, transaction feerates will increase and miners
will be incentivized to increase their block production rate.

If the bitcoin price has plummeted more than, say, 99% in two weeks
with no hope of short-term recovery or if a large fraction of mining
equipment has become unusable (again, say, 99% in two weeks with no
hope of short-term recovery), then it's probably worth Bitcoin users
discussing a hard fork to reduce difficulty to a currently sustainable
level.

-Dave
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] Block solving slowdown question/poll

[David A. Harding via bitcoin-dev]

On Sat, Mar 21, 2020 at 11:40:24AM -0700, Dave Scotese via bitcoin-dev wrote:
> [Imagine] we also see mining power dropping off at a rate that
> suggests the few days [until retarget] might become a few weeks, and
> then, possibly, a few months or even the unthinkable, a few eons.  I'm
> curious to know if anyone has ideas on how this might be handled

There are only two practical solutions I'm aware of:

1. Do nothing
2. Hard fork a difficulty reduction

If bitcoins retain even a small fraction of their value compared to the
previous retarget period and if most mining equipment is still available
for operation, then doing nothing is probably the best choice---as block
space becomes scarcer, transaction feerates will increase and miners
will be incentivized to increase their block production rate.

If the bitcoin price has plummeted more than, say, 99% in two weeks
with no hope of short-term recovery or if a large fraction of mining
equipment has become unusable (again, say, 99% in two weeks with no
hope of short-term recovery), then it's probably worth Bitcoin users
discussing a hard fork to reduce difficulty to a currently sustainable
level.

-Dave


signature.asc
Description: PGP signature
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

[bitcoin-dev] Block solving slowdown question/poll

[Dave Scotese via bitcoin-dev]

It seems that many on this list think deeply enough to imagine the scenario
where we have  few days left before a difficulty adjustment comes up but we
also see mining power dropping off at a rate that suggests the few days
might become a few weeks, and then, possibly, a few months or even the
unthinkable, a few eons.  I'm curious to know if anyone has ideas on how
this might be handled because I'm sure we're not going to let it happen.
___
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev