Bitcoin Forum
May 13, 2024, 06:15:13 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Development - Thought - Change Block payout amount and lower difficulty  (Read 677 times)
LanceRushing (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 10, 2011, 01:27:59 AM
 #1

(I would post this in Development, but apparently I've just been lurking too much and not posting.)

Has the development team considered decreasing the number of coins earned for solving a block versus increasing the difficulty?

Reason: It would be better to decentralize the network's computational power. With the DDOS of the mining pools and the 50%+1 problem, distributed would be better.

Example: If blocks were only worth 1 BTC, then the difficulty could be lowered, and bitcoin production would still achieve the same rate of generation.

Even with my 1Gh/s (total) mining rigs, I really can't mine on my own and expect a payout, so I have to join a pool(s), where I earn around 1BTC per day.  But I'd happily mine on my own if I could achieve the same rate of return.

Just thinking.

-Lance
1715624113
Hero Member
*
Offline Offline

Posts: 1715624113

View Profile Personal Message (Offline)

Ignore
1715624113
Reply with quote  #2

1715624113
Report to moderator
The Bitcoin software, network, and concept is called "Bitcoin" with a capitalized "B". Bitcoin currency units are called "bitcoins" with a lowercase "b" -- this is often abbreviated BTC.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715624113
Hero Member
*
Offline Offline

Posts: 1715624113

View Profile Personal Message (Offline)

Ignore
1715624113
Reply with quote  #2

1715624113
Report to moderator
1715624113
Hero Member
*
Offline Offline

Posts: 1715624113

View Profile Personal Message (Offline)

Ignore
1715624113
Reply with quote  #2

1715624113
Report to moderator
99Percent
Full Member
***
Offline Offline

Activity: 402
Merit: 100


🦜| Save Smart & Win 🦜


View Profile WWW
July 10, 2011, 01:46:07 AM
 #2

This isn't a development "problem", its a protocol problem, it a problem at all. The protocol is set in solid stone, and cannot be changed.

The 50+1% problem is not really that bad. To begin with it would only disrupt the last block, at the most two while the network reorganizes itself when people (actual people, not machines) realize something is amiss. Secondly it would be extremely hard to reach this state even with a huge pool in operation.

What would be more feasable is that the deep bit pool agrees to divide itself in two or three entities ('deepbit1, deepbit2, etc).


JoelKatz
Legendary
*
Offline Offline

Activity: 1596
Merit: 1012


Democracy is vulnerable to a 51% attack.


View Profile WWW
July 10, 2011, 01:53:07 AM
 #3

Has the development team considered decreasing the number of coins earned for solving a block versus increasing the difficulty?
There are so many disadvantages to this, they completely outweigh the advantages.

First, many more blocks would be generated. That would tremendously increase the network, CPU, and storage overhead of operating the bitcoin network.

Second, a change in the protocol would upset settled expectations of how bitcoins behave. They would increase fears that future changes would upset other settled expectations. (By analogy, how would you feel if you worked hard for years to save up $75,000 and then next year the government prints $250,000 for each family? You'd be kind of pissed, wouldn't you?)

Third, the speed of block generation would not be much closer to the speed of network propagation. Many more blocks that are generated would fail to become part of the public block chain. Many more confirmations would be needed before a transaction could be considered stable. The number of reorganizations would go up by orders of magnitude.

I am an employee of Ripple. Follow me on Twitter @JoelKatz
1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!