Bitcoin Forum
May 04, 2024, 02:58:09 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 [82] 83 »
1621  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 07:37:12 AM
So you mean something similar to RSMPPS but also favor unpaid shares from miners who are still active. So if miner A worked on block 1 (a long block) and didn't get fully paid. And miner B worked on block 2 (another long block) and didn't get fully paid. Miner B stopped mining with the pool, but miner A continued mining. When the pool finally starts to get lucky and has enough BTC to pay the unpaid shares from block 2, we might favor paying miner A for his work on block 1 because he's still active instead of paying miner B for his work on block 2.

I think seems ok. It will give people incentive to keep mining and stick with the pool. But I can't think of a good formula that makes this simple to understand and implement. It might turn away miners due to it being too complicated even though the idea behind it is valid.
1622  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 06:23:54 AM
Just throwing out an idea here as well... it's quite unpolished, as I came up with it a couple of minutes ago...  Wink

Would a "tax" on old Max rewards be some sort of compromise? I'm thinking of some sort of system that moves accumulated unpaid PPS during longer streaks of bad luck and pays it forward to the the current round... let's say that with two rounds it proceeds as normal, but when the pool goes into the third bad block it starts taking a percentage of the unpaid shares from the first round and adds those to the current round, and if there's a fourth bad round it takes a cut from both round one and two and so on.

That way, the unpaid PPS from those who jump to another pool would gradually be shifted over to those who continue mining.

Not exactly sure what you mean by this. What does moving unpaid PPS from previous unlucky rounds to current round mean?
1623  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 05:49:47 AM
RSMPPS was something I considered when I was coming up with SMPPS. The key problem with it is, that cheaters (that is, people who only submit useless valid shares) can avoid taking any of the damage from their cheating. Solve that, and we have a winner Wink
Can you elaborate on the submitting useless valid shares? Does SMPPS solve this?
Only the one share that gets the pool a block is actually useful. Cheaters can reduce pool luck by refusing to submit those. With PPS, the liability is held entirely by the pool operator. With proportional, MPPS, and SMPPS, the liability is distributed among everyone in the pool. With RSMPPS, that liability is distributed among everyone except the cheater.

I don't get it. If the cheater refuses to submit the winning share, would he be able to submit it elsewhere and get the 50 BTC? If not, is he just doing this to screw over the pool? Why would the liability not be distributed to the cheater in case of RSMPPS?
Yep, pretty much just to screw the pool. So long as the cheater is careful going about it, he gets paid full PPS with no penalty under RSMPPS. I won't elaborate, as I don't care to encourage it.

With RSMPPS, the liability will be distributed among everyone including the cheater also. Let say if the cheater/saboteur finds a winning share after an average length and decides to not submit that share. The pool goes on and keeps looking. And let say it takes another average length to find another winning share. So because of the sabotage, the cheater turns 2 average rounds into a double length round. And he will only get half his work paid. Whereas if he didn't sabotage, he will get paid his full work for the 2 blocks. So the cheater is being penalized for cheating in the case of RSMPPS also, right?

In the end, I think this is an edge case that we don't need to worry about. In order for a cheater to really have a real effect on a block by sabotaging it this way, he needs to have quite big of a hashrate. I can't imagine someone with such a hashrate spend his time throwing away winning blocks just to sabotage a pool. Just imagine... all those winning shares are worth 50 BTC to himself if he solo mined! Who in there right mind would be so stupid.
1624  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 05:30:04 AM
RSMPPS was something I considered when I was coming up with SMPPS. The key problem with it is, that cheaters (that is, people who only submit useless valid shares) can avoid taking any of the damage from their cheating. Solve that, and we have a winner Wink
Can you elaborate on the submitting useless valid shares? Does SMPPS solve this?
Only the one share that gets the pool a block is actually useful. Cheaters can reduce pool luck by refusing to submit those. With PPS, the liability is held entirely by the pool operator. With proportional, MPPS, and SMPPS, the liability is distributed among everyone in the pool. With RSMPPS, that liability is distributed among everyone except the cheater.

I don't get it. If the cheater refuses to submit the winning share, would he be able to submit it elsewhere and get the 50 BTC? If not, is he just doing this to screw over the pool? Why would the liability not be distributed to the cheater in case of RSMPPS?
1625  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 12:57:16 AM
And at round 4, you wouldn't leave either because it wouldn't affect whether your unpaid reward from earlier rounds will be paid or not. Your chance of getting paid in full for he new work is the same as when you joined in rd 1.
1626  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 11, 2011, 12:53:15 AM
There's no solution for having a long unlucky streak. But in your example, at round 1, you wouldnt know that you will have 3 more long rounds coming, so why would you leave? Any more work you put in rd 1 will be the first to be paid when pool gets lucky again.
1627  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 10, 2011, 11:59:57 PM
Ewal, you got it wrong. Any work you do now will be the newest shares and will be paid out first. So no reason for you to quit if pool is unlucky.
1628  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 10, 2011, 11:13:25 PM
RSMPPS was something I considered when I was coming up with SMPPS. The key problem with it is, that cheaters (that is, people who only submit useless valid shares) can avoid taking any of the damage from their cheating. Solve that, and we have a winner Wink

Can you elaborate on the submitting useless valid shares? Does SMPPS solve this?
1629  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 10, 2011, 11:10:00 PM
cheat-proof seems too complex though. plus i like having near real time (or just 5 mins) delayed stats if possible.
1630  Bitcoin / Pools / Re: A proposal for Recent Shared Maximum PPS on: July 10, 2011, 10:35:03 PM
Which cheat-proof method? The one that delays stats do you don't know you are in a long round?
1631  Bitcoin / Pools / Re: [130 GH/s 0% fee SMPPS] Ars Technica community mining pool! on: July 10, 2011, 10:33:07 PM
I have a proposal for a better SMPPS payout system. See: http://forum.bitcoin.org/index.php?topic=27698
1632  Bitcoin / Pools / A proposal for Recent Shared Maximum PPS on: July 10, 2011, 10:27:16 PM
Recently, I've been trying to find a pool that has the most fair payout system that deters pool hopping. Slush system works ok but it's really bad for people that are not doing this 24/7. Deepbit deters pool hopping but the delayed statistics is annoying. I came across Eligius' Shared Maximum Pay Per Share (SMPPS - http://eligius.st/wiki/index.php/Shared_Maximum_PPS) model. This model works well but I believe there is a flaw. When the pool is running lucky, all is good. But when the pool is running unlucky, there is less incentives for people to join the pool because they know that they will not get their full PPS reward because a part of the earnings will need to be shared with other users that were owed rewards from previous unlucky blocks. This could potentially lead to a vicious cycle where if the difficulty increases and the pool's hashrate does not increase to match, the pool will earn less BTC and would not be able to cover the previous debt.

For example, imagine if a SMPPS pool is unlucky and currently running a 100 BTC deficit. Why would I want to join this pool? For every 1 share I contribute, I would have to likely share it with 2 others for the 50 BTC earned. Let's say the next round is an average round. The pool earns 50 BTC, but since the deficit is now 150 BTC, I will only get a third of the payout right away and need to wait for the rest… assuming I will eventually get them. So why not just join a SMPPS pool that is currently lucky? That way, I will get all the PPS rewards that I contribute. I believe this leads to pool hopping not due to long rounds, but due to lucky/unlucky pools.

I have a proposal for a better PPS system that I'm calling Recent Shared Maximum PPS or RSMPPS. The idea is simple. It's basically SMPPS, but instead of paying out the reward to all unpaid PPS proportionally, RSMPPS will favor recent blocks. So it will first proportionally pay out the unpaid PPS for the current block (the one that was just found). If there are any remaining rewards, it will pay them out to the next recent block that has unpaid PPS shares. It will keep doing that by paying out unpaid PPS shares from earlier and earlier blocks until all 50 BTC are paid out. If there are any left, it will keep those for the next unlucky round. This system will have no disadvantage for new miners joining the pool, because rewards will be first paid to the people that actually worked on the current block. So there's no debt burden on new users. And old unpaid PPS shares will get paid out if the pool gets lucky enough. With this system, it's possible for the pool to never get lucky enough to pay out really old unpaid shares. I think that's fair.

What do people think?
1633  Bitcoin / Bitcoin Discussion / Re: FirstBits.com - remember and share Bitcoin addresses on: July 10, 2011, 09:36:47 PM
Though in theory, the system is sound. In practice, things can happen. As we saw when they were using bad blocks data, the firstbits address given out may be wrong. You can never be sure that this won't happen again, right?
1634  Bitcoin / Bitcoin Discussion / Re: Use Google Spreadsheets to automatically keep track of your wallet balance on: July 04, 2011, 11:05:15 PM
BTW, this system will only work if you are careful when you take money out of this "savings" account. Since if you create a transaction that has change, the change will go to a random wallet address. You will need to add that wallet address to this spreadsheet in order for it to stay accurate.

So the way I plan to use it is for each address I have in this account, I plan to put the same number of bitcoins in them. So for example, if I have 10 BTC in each of the 12 addresses, I will have 120 BTC total. If I need to transfer money out, I do it in a multiple of 10s. That way, there won't be any change. For anything less than 10 BTC, I just keep in my checking account.

I hope in the future, the client will let me choose which account I want the change in.
1635  Bitcoin / Bitcoin Discussion / Re: Use Google Spreadsheets to automatically keep track of your wallet balance on: July 04, 2011, 10:31:40 PM
Thanks! I didn't realize theymos added it. I made the change to the spreadsheet. Should be much better now... no more html scraping.
1636  Bitcoin / Bitcoin Discussion / Re: FirstBits.com - remember and share Bitcoin addresses on: July 01, 2011, 02:54:51 AM
Hey, this is an awesome concept. I applaud you guys for coming up with it.

Removing the cases is a good thing because it would be hard for people to have to deal with upper and lower cases. There might be one gotcha though. Do you handle 2 addresses with the same characters but different cases properly. I know this is a rare edge case, but make sure you handle it. For example, 1abcdefghijklmnopqrstuvwxyz and 1abcdefghijklmnopqrstuvwXYZ should not both match to the same firstbits 1abcd. The first one in the block chain should match to 1abcd and then second one should match to 1abcde. Just a thought.
1637  Economy / Marketplace / Re: Show your firstbits - get 2 bitcents on: July 01, 2011, 02:39:43 AM
done!
1638  Bitcoin / Pools / Re: Triple your income from mining with mini-pools! on: June 29, 2011, 05:56:31 PM
The people not giving their 1% to the jackpot shouldn't be able to win the jackpot! Otherwise, one will effectively earn extra money, over time, if they are a mini-pool owner, and the rest lose out on their 1%, as even those not donating to the jackpot can win it!

You are reading it wrong, %1 of 50BTC is taken every time a block is found. Some of that is divided under people who started a mini pool and the rest goes to the jackpot.

So everyone is allways participating.

It is offcourse in your best interest to convice people to join your minipool, but if you don't and you 'solo mine' you still have the chance of winning the jackpot.

Keep in mind that there are currently only 28 people mining so your chance is 1/28 to win 0.5 BTC, that's not so bad is it ? Smiley

I will say it again. This is a zero-sum game. (see http://en.wikipedia.org/wiki/Zero_sum_game)
If someone in this pool (minipool owners) has a better expected value mining in this pool than otherwise, then someone else (non minipool owners) must have a worse expected value. Not everyone in this pool will benefit! No matter how much the jackpot is or how enticing it is, there still an expected value for it. And for non minipool owerners, that expected value is less than 1%.
1639  Bitcoin / Pools / Re: Triple your income from mining with mini-pools! on: June 29, 2011, 11:17:02 AM
Secondly, IMO theres no investment or payment required to enter the pool.
Great! Where do I sign up to get the free miner hardware and electricity?

LOL.

MrSam, it's true that it's not a full pyramid scheme. But it's still a 2 level pyramid scheme, where you benefit from all the people you got to sign up under you. Pooled mining is a zero-sum game. It's about how the 50 BTC (minus fees) are shared among the miners. Other pools share this 50 BTC bases on shares or score. Your pool adds another twist where 0.5 BTC is only shared among minipool owners. Because it's a zero-sum game, in order for minipool owners earn more, someone has to lose out. And the losers are those without any friends.

This system (like any other pyramid scheme) will collapse in time. In the beginning as people are joining your pool and getting others to join, they will see that they are making more with your pool than other pools. As your miners are able to find less and less people to join, the non minipool owners will realize that they are not benefiting b/c they are not minipool owners (they can't find people to join under them). Those miners will quit the pool. Then their minipool owners will find their mining to be not quite as good and they will quit. Sooner or later, the whole thing will collapse.
1640  Bitcoin / Pools / Re: Triple your income from mining with mini-pools! on: June 29, 2011, 10:03:18 AM
It seems like there's no money required to join your pool. But in reality, the "cost" is the lost earnings of the 1% of the 50 BTC found in a block.

This is just like the pyramid emails I get where they ask me to send them $100 and then I can forward the email to 3 of my friends that will each give me $100. The people at the bottom of this pyramid scheme will always lose, because they won't have friends to help them make back the 1% they are losing out on.

Anyways, just my take.
Pages: « 1 ... 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 [82] 83 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!