Topic: [GLBSE] DEEPBIT Miner Variance Protection (Read 5251 times)
see you soon on marketcap
Hope this coin will be growed in the future.
MEI.DEEPBIT.B to date: + 8.4 % compared to proportional, and the ROI is + 17.4% compared to DeepBit PPS.
Code:
Payment date | Total paid | Shares paid | Payment per share
2012-07-21 07:34 4.79608 200 0.02398039
2012-07-25 04:04 5.06473 200 0.02532365
2012-07-28 05:05 4.99036 200 0.0249518
2012-07-28 05:18 0.55628 200 0.0027814
2012-08-02 05:25 6.27643 200 0.03138215
MEI.DEEPBIT.A1 is now active and asks have been removed. If you wish to purchase any bonds you will need to place a bid. If anyone wants to find out what I will accept for a bid at any point, please PM me.
Unfortunately some MEI.DEEPBIT.A bonds were not returned so I created a new ticker with a new contract. MEI.DEEPBIT.A1 is available now will start paying coupons from blockheight 191520 for 488 DeepBit rounds, at intervals of every 122 rounds, at 0.1016 per bond. It is also properly callable, with a return of one satoshi for each bond on expiry.
Those people buying and selling MEI.DEEPBIT.A bonds, please stop it. This bond has expired and will pay no more coupons. Please send me your bonds so I can retire the security.
Those people buying and selling MEI.DEEPBIT.A bonds, please stop it. This bond has expired and will pay no more coupons. Please send me your bonds so I can retire the security.
MEI.DEEPBIT.B to date: + 2.7 % compared to proportional, and the ROI is + 11.1% compared to DeepBit PPS.
The fourth coupon is the extra to get us up to date.
The fourth coupon is the extra to get us up to date.
Code:
Payment date | Total paid | Shares paid | Payment per share
2012-07-21 07:34 4.79608 200 0.02398039
2012-07-25 04:04 5.06473 200 0.02532365
2012-07-28 05:05 4.99036 200 0.0249518
2012-07-28 05:18 0.55628 200 0.0027814
Due to a problem obtaining data from blockchain info, my script has been assessing DeepBit round length data from two days early. The correct payment to date should be + 4.171% greater than expected. This means a bonus of 0.00278145 btc per bond will be paid at the next coupon.
The script that checks DeepBit now uses blockexplorer to find start blocks, and is working correctly. I apologise for this error, and in order to ensure it doesn't happen again, I will be performing a code audit and manually checking all results until I'm confident that data from blockexplorer fails gracefully.
Note: MEI.DEEPBIT.A was not affected by this error.
Below is the actual data for this bond so far:
The script that checks DeepBit now uses blockexplorer to find start blocks, and is working correctly. I apologise for this error, and in order to ensure it doesn't happen again, I will be performing a code audit and manually checking all results until I'm confident that data from blockexplorer fails gracefully.
Note: MEI.DEEPBIT.A was not affected by this error.
Below is the actual data for this bond so far:
MEI.DEEPBIT.B to date: - 0.79537 % compared to proportional, + 9.20% compared to DeepBit PPS.
Code:
Payment date | Total paid | Shares paid | Payment per share
2012-07-21 07:34 4.79608 200 0.02398039
2012-07-25 04:04 5.06473 200 0.02532365
MEI.DEEPBIT.B Coupon 1 claim: 0.02398039 Btc per bond ( - 4.08 % compared to proportional, + 5.92% compared to DeepBit PPS, and - 5.59% ROI )
MEI.DEEPBIT.A Claims paid / 100 starting bonds: 9.944681 Btc ( - 0.55319 % of expected and -2.10319% ROI).
MEI.DEEPBIT.A is now inactive; MEI.DEEPBIT.B will start paying claims at the end of this quarter.
MEI.DEEPBIT.A is now inactive; MEI.DEEPBIT.B will start paying claims at the end of this quarter.
Whoever it is with a bid of 1 for 0.05 on DeepBit.A, you're offering too much. The expected remaining value is 0.025, and the coupon will pay out shortly after which the bond expires and has a value of zero on recall. I would certainly accept that bid, but you'd be guaranteed a ~ -50% ROI.
A good guide is 0.075 btc after the first coupon, 0.05btc after the second and 0.025 after the third. However, because risk is increased and also some of the blocks in the quarter will have already been solved, you need to take that into account. PM me if you want a quote, and please be careful if you're using bots to buy MEI securities.
A good guide is 0.075 btc after the first coupon, 0.05btc after the second and 0.025 after the third. However, because risk is increased and also some of the blocks in the quarter will have already been solved, you need to take that into account. PM me if you want a quote, and please be careful if you're using bots to buy MEI securities.
MEI.DEEPBIT.B has activated, and will start paying coupons at 123 DeepBit.net rounds solved.
I have removed my asks now, so if you wish to purchase bonds, place a bid or pm me..
I expect DeepBit to finish the 530 round run (which started with the last Difficulty period) later today. If this is the case MEI.DEEPBIT.A will pay its last coupon and expire, at which point I will call the bonds for 0 Btc (the expected bond value - the expected coupon value).
I hope all users are finding the insurance useful.
I have removed my asks now, so if you wish to purchase bonds, place a bid or pm me..
I expect DeepBit to finish the 530 round run (which started with the last Difficulty period) later today. If this is the case MEI.DEEPBIT.A will pay its last coupon and expire, at which point I will call the bonds for 0 Btc (the expected bond value - the expected coupon value).
I hope all users are finding the insurance useful.
MEI.DEEPBIT.B will activate in about 36 hours, and after this point no more insurance will be sold for the Difficulty period. MEI.DEEPBIT.A will soon pay its last coupon and retire until the following Difficulty period.
MEI.DEEPBIT.A Coupon 6 claim: 0.02347875 Btc per bond ( - 6.09 %)
MEI.DEEPBIT.A Claims paid / 100 starting bonds: 7.455261 Btc ( - 0.597 %)
MEI.DEEPBIT.A Claims paid / 100 starting bonds: 7.455261 Btc ( - 0.597 %)
MEI.DEEPBIT.B available now at GLBSE.com for 0.1016 btc. They will be removed from sale at block height 189503, after which we will start paying coupons.
The bonds will be valid for 492 rounds, and pay coupons every 123 DeepBit rounds.
The bonds will be valid for 492 rounds, and pay coupons every 123 DeepBit rounds.
We're exactly mid way through at the moment, with 5 payments out of 10 done. Unless any other customers want the original payment scheme, I'll make two more payments, each for 2.5 of the usual payment.
In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
If it is easier do one more on the current schedule then move to the every other schedule, so three more. Then from then on just do every other one. Might make the math easier. In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
It's ok. I rewrote the code last night. Next coupon pays 132 rounds, the final one pays 133 rounds.
We're exactly mid way through at the moment, with 5 payments out of 10 done. Unless any other customers want the original payment scheme, I'll make two more payments, each for 2.5 of the usual payment.
In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
If it is easier do one more on the current schedule then move to the every other schedule, so three more. Then from then on just do every other one. Might make the math easier. In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
We're exactly mid way through at the moment, with 5 payments out of 10 done. Unless any other customers want the original payment scheme, I'll make two more payments, each for 2.5 of the usual payment.
In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
In the meantime I'll contact GLBSE support to see what can be done about voting and the contract.
I would say doubling the current period (or maybe 4x the current period) would be just fine. Your current payout comes way faster than my mining payouts.
You should be able to edit your OP and add a poll
Yes, I thought I'd done it before but I can't find the option.but better yet you might put it up as a vote on the asset itself on GLBSE.
And this would be the best option by far. However, since the bond would only last about two weeks at a time, I didn't think I'd need to make it a voting type of security, so the "Motions" button does nothing for me.
I'll email GLBSE Support and see if I can organise a vote regardless.
At any rate I would vote for the longer payout period since it is a lot of book keeping with the current frequency.
What would your preferred payout period be? Here are some options for you and others (to make it a bit easier):
1. On the expiry of the bond (1 payment only)
2. Weekly (two payments)
3. Every three to four days
4. Keep as is (every 1.4 days or so).
MEI.DEEPBIT.B goes on sale tomorrow, 14th July 0:00 UTC. It will become active from block 189504 onwards for two weeks, when A will be active again. Any changes in payout frequency for A will also hold for B.
Jump to: