BitShares Forum

Other => Graveyard => MemoryCoin => Topic started by: luke997 on January 27, 2014, 09:58:31 pm

Title: Idea for a new unique feature - pool spread
Post by: luke997 on January 27, 2014, 09:58:31 pm
Have an idea - this would be crypto first, so another unique feature of the coin.

Could we implement solution to the algorithm which would favour smaller pools?
This would be great in preventing 51% attacks and 1 or 2 big pools.

Not sure how hard that would be, but could we do something like that:

Block reward = lower to - let's say 90%
Remaining 10% would be spread evenly between first 10 pools (so the less people in pool, the more in reward per person, encouraging  equilibrium).

It's just first idea, I'm sure you'll think of better implementation
Title: Re: Idea for a new unique feature - pool spread
Post by: MaxPWR on January 28, 2014, 06:15:27 am
I prefer a community / private attempt first.

I'm making Max's Mine to promote smaller pools.  You mine for me at a sponsored pool, I donate back to the pool operator or mining community. 

Currently running a "follow us in the leaderboards" for dwarfpool users to donate to dwarfpool development:

https://bitsharestalk.org/index.php?topic=2535.
Title: Re: Idea for a new unique feature - pool spread
Post by: luke997 on January 28, 2014, 07:17:08 am
I prefer a community / private attempt first.

I'm making Max's Mine to promote smaller pools.  You mine for me at a sponsored pool, I donate back to the pool operator or mining community. 

Currently running a "follow us in the leaderboards" for dwarfpool users to donate to dwarfpool development:

https://bitsharestalk.org/index.php?topic=2535.

How that's working? Check spread history.
Only minority cares, rest will follow better payouts.

Lot of coins have this problem, this could be special if built in the protocol.
Title: Re: Idea for a new unique feature - pool spread
Post by: FreeTrade on January 28, 2014, 09:05:33 am
Lot of coins have this problem, this could be special if built in the protocol.

Don't think there is any way to build this into the protocol. Big pools could just pretend to be small ones.

What we're looking at, at the moment, is implementing p2pool - hopefully building it into the GUI.