Search content
Sort by
Showing 20 of 22 results by Cellcote
Looks cool. But how exactly do you decrypt md5?
+1, md5 isn't a form of encryption, it's hashing. Same with SHA btw.FYI, the Mining Comparison wiki page isn't useful except for general comparison. Insufficient information regarding OS/drivers/kernel/sdk is provided to reproduce many of the numbers quoted.
Well, it may not be an exact source of information but it will give a general idea of what a GPU could of will be able to achieve
money is not free. get over it!
Well, the hashes aren't useless if I understand it correctly. With each hash you will not only search for blocks but also confirm other transactions. If you are going to spend all that computing power to solving problems, you will not be able to have so much transactions (or with less confirmations) than you have now. Also these kind of investments defeat the purpose of bitcoin I think.
4 Mhash/s is nearly 0, It will take you a while to get a share. Speed on the website is always a little higher than you will see in GUI Miner.
As for your problem, I don't think it's anything you can fix. It are the pools that are unstable at times. If I check my logs from BTCguild, I have the same error from 17:30 onwards to 18:42. Not much you can do about it except for switching to another pool.
As for your problem, I don't think it's anything you can fix. It are the pools that are unstable at times. If I check my logs from BTCguild, I have the same error from 17:30 onwards to 18:42. Not much you can do about it except for switching to another pool.
every 2 seconds
As I recall correctly, MT Gox only allow you to acces their API once per 15 minutes.I would suggest to stay away from bitcoinplus, even with 1000 of clients to generate for you, it still takes a long time. Hell, it's not even worth it to mine with a CPU with current difficulty.
Remember to check your balance. It looks like transfers that occurred a day or two before mybitcoin went down are now showing up in your balance eventhough block-explorer confirms the money was transferred to the address.
On a side know, do you know where one reports such issues?
On a side know, do you know where one reports such issues?
No idea, he didn't leave his email anywhere.
You can now file your claim at Mybitcoin.com. You will receive 49% of your account.
Link: https://www.mybitcoin.com/claim.php
Link: https://www.mybitcoin.com/claim.php
There is a new announcement on the page:
Quote
Friday, August 5th, 2011
From the desk of Tom Williams, operator of MyBitcoin.com
For immediate release.
SECURITY BREACH DISCLOSURE
After careful analysis of the intrusion we have concluded that the software that waited for Bitcoin confirmations was far too lenient. An unknown attacker was able to forge Bitcoin deposits via the Shopping Cart Interface (SCI) and withdraw confirmed/older Bitcoins. This led to a slow trickle of theft that went unnoticed for a few days. Luckily, we do keep a percentage of the holdings in cold storage so the attackers didnt completely clean us out. Just to clarify, we werent fully hacked aka rooted. You can still trust our PGP, SSL, and Tor public keys.
It appears to be human error combined with a misunderstanding of how Bitcoin secures transactions into the next block. Our programmer was under the assumption that one block was good enough to secure a transaction. Two years ago when the software was written, this single confirm myth was a popular belief.
In hindsight we should have credited deposits after one confirmation so they would show up in the transaction history, and held the deposit until it reached at least 3 confirmations. Keeping track of two balances and displaying them in the login area would have been trivial.
CLAIM PROCESS DISCLOSURE
We are in the process of building a claim procedure for the remainder of the holdings now. We expect that we will have it online soon.
The claim process will consist of a online form where the claimant will be required to enter their MyBitcoin username and password. Their balance will be displayed along with the percentage of remaining Bitcoins that we still have in our holdings. That percentage will be paid to a Bitcoin address of their choosing. This percentage will be based on our current total liabilities vs. our existing assets. We will disclose these figures as soon as they have been totaled.
Each online claim will be written to a ledger and will be manually approved within 48 hours of being filed online. We have decided to have a manual claim approval process for better security. The last thing we all need right now is for someone to breach the claim form. We are confident clients will find this satisfactory.
RECEIVERSHIP
After some research and careful consideration regarding the appointment of a receiver we have concluded that it would be very costly and slow.
Also, finding a receiver that even understands what a Bitcoin is or how to handle the claim process online would be troublesome, and would only end up in increasing our costs. Receivers are typically paid from the remaining assets and wed like to maximize the amount that we can disperse to our clients.
We have been trying to figure out a way to appoint a 3rd party to certify the asset/liability figures, but there are many risks involved. It would involve having us trust some unknown agent that could possibly just steal the rest of the holdings out from under us. Or, we could be accused of bribing the 3rd party to agree with our figures, and on and on. Trust is a real problem with an anonymous and irrevocable currency.
It is true that we could disclose all of the Bitcoin payment addresses we manage and let everyone look them up and track the lineage of the coins. This is also troublesome due to the way that we defragment small payments to keep the processing engine speedy. Also there are the moral implications of disclosing our clients finances. We are sure that, unknowingly to us, that our processing system has been used for nefarious purposes.
A GIFT TO THE COMMUNITY
After the claims have all been filed and dealt with we will be releasing the entire MyBitcoin processing engine into the public domain. Our only hope is that the community can improve and adapt the software to all sorts of new and interesting Bitcoin-related things.
Tom Williams
From the desk of Tom Williams, operator of MyBitcoin.com
For immediate release.
SECURITY BREACH DISCLOSURE
After careful analysis of the intrusion we have concluded that the software that waited for Bitcoin confirmations was far too lenient. An unknown attacker was able to forge Bitcoin deposits via the Shopping Cart Interface (SCI) and withdraw confirmed/older Bitcoins. This led to a slow trickle of theft that went unnoticed for a few days. Luckily, we do keep a percentage of the holdings in cold storage so the attackers didnt completely clean us out. Just to clarify, we werent fully hacked aka rooted. You can still trust our PGP, SSL, and Tor public keys.
It appears to be human error combined with a misunderstanding of how Bitcoin secures transactions into the next block. Our programmer was under the assumption that one block was good enough to secure a transaction. Two years ago when the software was written, this single confirm myth was a popular belief.
In hindsight we should have credited deposits after one confirmation so they would show up in the transaction history, and held the deposit until it reached at least 3 confirmations. Keeping track of two balances and displaying them in the login area would have been trivial.
CLAIM PROCESS DISCLOSURE
We are in the process of building a claim procedure for the remainder of the holdings now. We expect that we will have it online soon.
The claim process will consist of a online form where the claimant will be required to enter their MyBitcoin username and password. Their balance will be displayed along with the percentage of remaining Bitcoins that we still have in our holdings. That percentage will be paid to a Bitcoin address of their choosing. This percentage will be based on our current total liabilities vs. our existing assets. We will disclose these figures as soon as they have been totaled.
Each online claim will be written to a ledger and will be manually approved within 48 hours of being filed online. We have decided to have a manual claim approval process for better security. The last thing we all need right now is for someone to breach the claim form. We are confident clients will find this satisfactory.
RECEIVERSHIP
After some research and careful consideration regarding the appointment of a receiver we have concluded that it would be very costly and slow.
Also, finding a receiver that even understands what a Bitcoin is or how to handle the claim process online would be troublesome, and would only end up in increasing our costs. Receivers are typically paid from the remaining assets and wed like to maximize the amount that we can disperse to our clients.
We have been trying to figure out a way to appoint a 3rd party to certify the asset/liability figures, but there are many risks involved. It would involve having us trust some unknown agent that could possibly just steal the rest of the holdings out from under us. Or, we could be accused of bribing the 3rd party to agree with our figures, and on and on. Trust is a real problem with an anonymous and irrevocable currency.
It is true that we could disclose all of the Bitcoin payment addresses we manage and let everyone look them up and track the lineage of the coins. This is also troublesome due to the way that we defragment small payments to keep the processing engine speedy. Also there are the moral implications of disclosing our clients finances. We are sure that, unknowingly to us, that our processing system has been used for nefarious purposes.
A GIFT TO THE COMMUNITY
After the claims have all been filed and dealt with we will be releasing the entire MyBitcoin processing engine into the public domain. Our only hope is that the community can improve and adapt the software to all sorts of new and interesting Bitcoin-related things.
Tom Williams
Thanks so much
And Xephan, Thanks as well, this solution is good for now but ill look into the dummyplug idea