Well, this event went off as well as the last event.. maybe worse.
I'd suggested previously about the ability to sell deposits, but after running a few rebate events I think the concept can be simplified.
Bounties, similar to rebates, with the difference being that it's a form of distributed payout. Owners configure a per address setting in percent from 0 to 96, where 0 is the default %100 payout and %96 is %0 payout as the remaining 4 is the OP's fee leaving only the miner fee. The bounty consists of the reaming payout. On payout the deposits that went into making the payout possible, making the adjustments for the first and last fractional, split the Bounty using a weighted average on each deposits contribution. This should give an close approximation, where 1/3 Rebate is represented as a %30 Bounty.
The Bounty value for the address is secret until applied to a deposit. When the deposit becomes ??10hrs?? young the Bounty is permanent, this should accelerate the game should it cross this threshold as well as prevent abuse of the Bounty System.
Can you present a example for this. I didn't get it.
The owner of a deposit configure a Bounty for one (or some, or all) of his entries?
10 hours before this deposit expires, the bounty is visible for all players?
But what happens than?
E.g. you have one deposit of 1
BTC (output
BTC1.25)and set a bounty of 20%.
I place a deposit of 0.5. What happens next?
As you can tell, I'm a great programmer so I express myself from that encampment(package). I really don't understand why anyone would have a difficult time taking the above and turning it into a simple program.
Programmatically, when a Bounty is HTTP posted the value is stored to a secret hash keyed by bitcoin address(after validation of a salted bitcoin signature). Each deposit object is extended with a "bounty not applied" bool that is consulted when the timer on the deposit is below 10hrs. If the bounty has not been applied the value is read from the hash and applied to the object, clearing the bool.
When users place a deposit nothing changes, perhaps there is some more accounting data but that depends on the implementation and would not involve or effect users.
Payouts are effected by Bounties, for an non-zero bounty applied to a deposit creates a distributed payout. The payout to each address is calculated taking the Bounty into account per the above.
Thanks Cheako, i am also a programmer since 30 years, but i still didn't get it. Maybe only a problem with my english, maybe not.
It could be helpful to show some examples. The technical part is clear (but not really relevant for us users).
I will try it:
1. The owner of the deposit sets a bounty in percent to his deposit (must be done at least 10 hours before expire and will be fixed then)
-> e.g. deposit of 1 BTC, bounty 30%
-> Question: When will the players see this bounty? Directly? 10 hours before expire? After paiment?
2. If this deposit is paid, the owner will get the rest (without the deposit)
-> 1
BTC x 125% = 1.25
BTC. Minus 30% = 0.875
BTC3. The bounty will be distributed to (all?) ppl, who are "involved". Means their deposits paid the original deposit?
-> Bounty is 30% of 1.25
BTC = 0.375
BTC. This will be distributed to one or some ppl who deposited at the "correct" time. Correct?
Btw: Did you discuss your ideas with the owners? Other then you old idea, this cannot work without them.
