Is that then still an issue?
A max diff of around 20 would be nice.  |
|
|
|
If everything runs perfectly I could perhaps enable Stratum and GBT with var diff on the main pool before the weekend is over. But perhaps delay var diff on getwork a bit longer until hashpower.com supports it.
My only other concern with vardiff is that when you enabled it on the main pool, it was done per worker. Does vardiff now work by used the x-mining-hashrate header if available? |
|
|
|
This stuff really only makes sense averaged over a multi-week period. http://blockorigin.pfoe.be/chart.phppfoe.be shows it pie chart over the last 2016 blocks to try and get rid of the noise. They also track blocks by parsing individual pool websites instead of guessing ip addresses like blockchain. |
|
|
|
"Expected per block" on website corrected to take the reward halving into account.
I also added MPoolMonitor under "tools" -> "third party apps" on the website.
Hi Doc, When can we expect vardiff and stratum support on the main pool? Thanks, gigavps |
|
|
|
EMC is being upgraded as we speak, BTW. I haven't mentioned it yet, because I don't have anything I want to show just yet, but there's a lot of changes coming in the near-to-mid term future. I think people are going to be surprised and pleased.
Nice. |
|
|
|
You should not punnish 65% of your shareholders, the ones that did everything right.
Put yourself in my shoes for a minute. If I send out 65% of 3,500 coins (2,275) and 10% of the coins go to the wrong address, someone they shouldn't have gone to, etc. I've just made a $2,750 mistake and am still liable. Does that sound like fun to you? You are basically telling me to not worry about my liabilities because nefario is getting it right. Only, he can't even send over a properly formatted yaml file which means he probably put the file together by hand. There is also the issue of people who have filled out the GLBSE claims form and didn't receive a double payment, yet still aren't on the list. Is this still a situation of "your not on the list, o well"? As to trusting nefario now vs. later, you can't do better until you know better. |
|
|
|
You mention that there are 10% of claims not on the list. My issue is that you are claiming you cant pay back the 90% of people because of this.
What exactly is preventing you paying out to the 90% who ARE ON THE LIST?
The solution is if you're not on the list you dont get paid yet. Youre holding 90% of people coins hostage because 10% of people claimed who arent on the list. If you cant see an issue with that I dont know how to explain it more clearly.
Less than 65% of the shares are on the list..... so that means more than 35% wouldn't get paid. The claimants of the over 4k are very well respected and well know in the community. Can you see the conundrum here? Why do you condone trusting nefario after he destroyed your entire investment in GLBSE? Do you also condone nefario's inability to do the most simplest things as a reason for someone to not be able to make a claim and get paid? |
|
|
|
Breaking contracts and changing the rules of the game while playing not.
Please help me understand how else I should handle this situation? Maybe you have some insight that will help make the situation all better. |
|
|
|
GLBSE is unwilling to give the entire list of 40k.
Then why is the total number of shares on the list 40697 ? Because I have added dummy accounts into the list. |
|
|
|
To make it easier to submit a claim, I will be creating a PDF file that you can print, fill out, sign and notarize. Multiple people have asked for this and I will certainly provide it.
Thank you. Will you post the link to download here, or should we be expecting an email from your legal counsel again? I will post it on the website and I'll announce it here. |
|
|
|
I (and as I see on the list many others) have 1 single share in Gigamining.
The numbers you see in the list are inflated because of the number of dummy accounts shown. Don't you think your proposal is a bit much to go through to claim 1 Share.
GLBSE is unwilling to give the entire list of 40k. This is because of 3 reasons I can see: - Someone did not fill out the claims form on GLBSE.
- Someone received a double payment, which they might not even know about.
- An unknown error on GLBSE's end.
As I have stated before, I am liable for all issues that arise from incorrect payments or fraud. I take this liability very seriously. Wouldn't it make sense to apply those rules only, if you hold at least an amount that equals a worth of 100+ $ ?
So I do something like this, nefario gives me an updated list with a bunch of small accounts and I get scammed. Now I'm still liable for what quickly turns into thousands of dollars. As it doesn't make sense for you or me to put effort in managing tiny shareholder amounts, I would basically agree in any given buyback proposal that doesn't result in a total loss.
I am working on some ideas to make it easier for smaller account to claim. Please be patient. |
|
|
|
Gigavps == gigascammer  If I'm scamming then why did I send certified mail to get the lists? If I'm scamming then why do I hold 100% of the coins, over 3,500 at this point, to pay out per the 5Mh/s contract. If I'm scamming, they why I am asking for people to verify their claim so I can pay them? Not one person in this thread as quoted anything I wrote in my previous posts and has taken issue with it. I'll quote it for you, so you can read it again. To the bitcoin community:
We are all in the very unenviable position of riding in the wake of the aftermath of James McCarthy. I have been placed in a very bad spot in this wake, and my only goal is to protect and serve Gigaminers as I have over the last half year.
I would like to point out that I am the only asset issuer on GLBSE, as far as I am aware, who is trying to move forward and abide by all the laws of local, state, federal and international law. I am the only asset issuer, as far as I am aware, to hire legal counsel and to send via certified mail, a demand letter to James McCarthy after multiple unanswered emails and phone calls. I am fairly confident that the asset lists only started arriving once the letter was received.
Further more, how exactly would you like me to handle situations where claims are made against gigamining that are not in the list provided from GLBSE? Should I and all Gigaminers just keep trusting nefario? This is the exact reason to have a claims process in the first place. Nefario is withholding information for a mistake he made, Gigaminers should not have to suffer because of Nefario's mistakes any longer.
I have received claims for over 10% of Gigamining that are NOT on the lists given to me by GLBSE. This is a significant percentage and it warrants the claims process.
Finally, what should happen if I pay the wrong individual a large amount of the held coins? Guess what, I'm still on the hook according to the law. It is only right to protect the interests of all Gigaminers by making sure I have legal recourse should such a situation occur.
I hope it is clear that I am only trying to clean up and move forward from the situation at hand.
Best regards,
James
|
|
|
|
I have also added an sha256 hashed version of the lists given to me by GLBSE. The list has been obfuscated so that you can easily find your record but not know others records.
I'm not sure this is a great idea. With such a list. If you know someone's email address you can know his number of bonds. What's worse, even without knowing someone's email address, you can sometimes find his email address and the number of bonds. Emails don't have that much entropy and SHA256 is fast. With a GPU working the case you should be able to deanonymize many of the claimants. Bitcoin addresses also have very little entropy once they're in the blockchain. Once those addresses are paid by anyone, you can run over all 7M addresses and match them to the hashes. The Bitcoin address - shares association is likely to become public knowledge anyway. The Email - Bitcoin, however, shouldn't be, and the way this list is written it makes it easy to find in many cases. I have removed the emails from the list. |
|
|
|
To all Gigaminers: First, thanks to everyone who has submitted a claim. We will be reviewing then and verifying them against the list provided by GLBSE to start making payments. To make it easier to submit a claim, I will be creating a PDF file that you can print, fill out, sign and notarize. Multiple people have asked for this and I will certainly provide it. I have also added an sha256 hashed version of the lists given to me by GLBSE. The list has been obfuscated so that you can easily find your record but not know others records. I will update this list as GLBSE sends me more information. http://gigamining.com/glbse-records.htmlI want to make this process as easy as possible for all Gigaminers. With over 5,000 contracts claimed that are not in the GLBSE lists, I see no other way to proceed. Best, James |
|
|
|
Can we still mine at the "normal" pool? The 98%?
I would guess that everything is on the "normal" pool now? Coinlab? |
|
|
|
Another warning against using Martingale betting: Mon Nov 26 02:04:30 2012 <24000 209602 06c629e6b4f6d861:3 1LCi44X9VRG7dAXsj2PrtGHJHVgmns1qux BET 16.00000000 LOSE -15.92050000
Mon Nov 26 02:04:30 2012 <24000 209602 64ba98a15d44366d:1 1CZqiT5PYo6o6xEHFmcWEqQtQD1bQvhhRC BET 32.00000000 LOSE -31.84050000
Mon Nov 26 02:04:30 2012 <24000 209602 a754398a09a0a908:1 16Yd7C1HiHm5NykgoiVgjHuVnS3vexJLZo BET 64.00000000 LOSE -63.68050000
Mon Nov 26 02:04:30 2012 <24000 209602 f13db1bfcf818673:1 18MYLtQr2dqo2qvZAcsmPYWouGBDKyDZ2N BET 125.00000000 LOSE -124.37550000
Mon Nov 26 02:04:30 2012 <24000 209602 769a0b77a680eed5:1 14y3sG28j1Xz7X2AhMQCLZJzzr8PJSLcDr BET 250.00000000 LOSE -248.75050000
Mon Nov 26 02:04:30 2012 <32000 209602 720dd0e796546a6d:1 1DukQ8aUkDm4UQFXqiQHAdGzNCxdKiXZfG BET 250.00000000 LOSE -248.75050000 Ouch. |
|
|
|
|
I've had the same experiences as Meni and the mywallet API is much simpler and cleaner to use.
It's probably overkill but I am also generating records in a database and have a small interface to pull up contract holders with a list of payments.
I'm sure this accounting can be done through the blockchain, but it is nice having a simple interface to refer to.
|
|
|
|
I usually follow the mod's decision without question but in this case, from what Gigavps has said, he issued a contract on GLBSE in full knowledge he would never keep it -- as he had retained legal counsel from the beginning.
Can you please quote me where I have ever said this. |
|
|
|
|
Show Posts
