public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
* [bitcoin-dev] ossification and misaligned incentive concerns
@ 2023-11-03 18:24 Erik Aronesty
  2023-11-05 14:39 ` JK
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Erik Aronesty @ 2023-11-03 18:24 UTC (permalink / raw)
  To: Bitcoin Protocol Discussion

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

currently, there are providers of anonymity services, scaling services,
custody, and other services layered on top of bitcoin using trust-based and
federated models.

as bitcoin becomes more popular, these service providers have increasingly
had a louder "voice" in development and maintenance of the protocol

holders generally want these features

but service providers have an incentive to maintain a "moat" around their
services

in summary, making privacy, scaling and vaulting "hard" for regular users,
keeping it off-chain and federated...  is now incentivised among a vocal,
but highly technical, minority

is anyone else worried about this?

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

^ permalink raw reply	[flat|nested] 8+ messages in thread
* Re: [bitcoin-dev] ossification and misaligned incentive concerns
@ 2023-11-07  8:58 vjudeu
  2023-11-07 12:24 ` JK
  0 siblings, 1 reply; 8+ messages in thread
From: vjudeu @ 2023-11-07  8:58 UTC (permalink / raw)
  To: JK, Bitcoin Protocol Discussion, Erik Aronesty,
	Bitcoin Protocol Discussion

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

> Imagine a system that tries to maintain a constant level of difficulty and reacts flexibly to changes in difficulty, by modulating the block reward level accordingly (using negative feedback).
 
This is exactly what I did, when experimenting with LN-based mining. CPU power was too low to get a full block reward out of that. But getting single millisatoshis from a channel partner? This is possible, and I started designing my model from that assumption. Also, because channel partner usually don't want to explicitly pay, I created it in a form of "LN transaction fee discount". Which means, a CPU miner just received cheaper LN transactions through the channel partner, instead of getting paid explicitly. Which also caused better network connectivity, because then you have an upper bound for your mining (it won't be cheaper LN transaction than for free). Which means, if you mine so many shares, that you have free LN transactions, then you have to sell them, or open another channel, and then instead of having "one channel with free transactions", you have many.
 
> The free market is more important than finite supply.
 
I would say, the backward compatibility is more important than increased (no matter if still constant or not) supply. Which means, you can "increase" the supply, just by introducing millisatoshis on-chain. Or add any "tail supply", or anything like that, what was discussed in the past. The only thing that matters is: can you make it compatible with the current system? Hard-fork will be instantly rejected, without any discussion. Soft-fork will be stopped at best, exactly in the same way, how other soft-fork proposals were stopped, when achieving consensus was hard, and the topic was controversial. So, what is left? Of course no-forks and second layers. This is the only way, that is wide-open today, and which requires no support from the community. And that's why Ordinals are so strong: because they are a no-fork. Better or worse designed, it doesn't matter, but still a no-fork. Which means, they exist in the wild, no matter if you like them or not.

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

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2023-11-07 12:24 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-03 18:24 [bitcoin-dev] ossification and misaligned incentive concerns Erik Aronesty
2023-11-05 14:39 ` JK
2023-11-05 14:59   ` Erik Aronesty
2023-11-05 17:25     ` JK
2023-11-05 18:43 ` alicexbt
2023-11-05 21:00 ` Ryan Grant
2023-11-07  8:58 vjudeu
2023-11-07 12:24 ` JK

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox