|
There is concern among bitcoiners, that pool with >50% power can exploit the network with double spending transactions. I think that someone should make a service for monitoring blockchain forks and double spending attempts. I'm pledging 50 BTC for such service; if you are concerned with this problem too, add up your pledge.
To receive award this service should provide at least
1) Real time list of blocks, including orphaned ones
2) Real time list of transactions with double spend attempts
|
|
|
|
I seem to be having an issue with multiple works on deepbit.
I have my main worker which is working fine, then I created a second one with *****@gmail.com_0
on GUIMINER I have a GPU worker and a CPU worker. GPU is using OpenCL and is working fine.
I created a new OTHER miner and selected the CPU Miner "\guiminer\miners\puddinpop\rpcminer-cpu.exe"
put in my second worker ID with the _0. Im getting 5Mhash/s from the CPU however it doesn't appear to be connecting to deepbit account, the accepted rate is not going up and the worker is still showing red on deepbits.net
did I set it up wrong?
No. On average you'll need about 14 minutes and 18 seconds to generate a single share with 5 MH/s hashrate. So may be you just didn't hit it yet. Try to wait a little bit. |
|
|
|
Correct me if I am wrong but isn't the heart of the matter that if somebody controls 50% of the hashing power they can take over the system. There is no way to "take over the system" with just a high hashrate pool/miner. Please read: https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_powerThe attacker can't: - Reverse other people's transactions
- Prevent transactions from being sent at all (they'll show as 0/unconfirmed)
- Change the number of coins generated per block
- Create coins out of thin air
- Send coins that never belonged to him
|
|
|
|
How is deepbit.net hashrate calculated? It varies a lot, while that reported in my client does not. It's a guesstimation based on the number of your shares received per some time. The longer is your averaging window the more precise results you get. |
|
|
|
You pay for every solved block? My Bitcoin has solved 122672 and my balance is, guess what, 0 BTC. Why doesn't this work for me?
122672 is the total number of blocks in the bitcoin chain, they aren't all solved by you or my pool. |
|
|
|
Deepbit.net
3% or 10% fee (pay-per-share vs. proportional)
Fastest Pool
Most users (meaning payments are split more ways)
Long Polling
JSON stats (using API auth token)
Mints it's own transactions into it's own solved blocks I have more important features :) - No need to wait for 120 confirmation blocks, instant payment is possible
- Paying for invalid blocks too
|
|
|
|
This pool sends your bitcoins every 24 hrs automatically & u have one extra chance to take coins manually with in 24 hours. Currently 3 payments per 24 hours are allowed :) Will be more soon. |
|
|
|
I just installed a 6870 video card and want to make sure bitcoin is using it. How do I figure out what my hashrate is? Official bitcoin client can't use your video card. Don't use that client for mining. You should download some GPU mining application like poclbm or guiminer: https://github.com/downloads/Kiv/poclbm/guiminer-20110428.exe |
|
|
|
I seem to be having the very-slow-loading-on-chrome problem again since a few hours :-\
Only in Chrome ? What IP do you see when trying to resolve deepbit.net ? |
|
|
|
Would be nice though if mining pools and miners would implement session tokens which could be used to identify different instances running with the same credentials :) It's already used in the LP mode :) |
|
|
|
how do you activate longpooling? im using phoenix miner and im not sure how to do it?
Phoenix supports LP by default. |
|
|
|
Why with Long Polling it is limited to 10? Is it your pool's internal policy?
Actually the limit is 20, but I said 10 just to be on safe side. It's to detect LP errors caused by possible proxies and other stuff like it. |
|
|
|
For example I have 3 PCs and I set them to get the work from public pool. I have to create 3 different worker username (e.g. user.1, user.2, user.3). It must be exhausting to setup 100 workers because beside I have to create 100 different username, I have to create 100 different script too :(. Can I have my workers to use one worker username (e.g. only user.1)? Thanks
It depends on the pool you are using. With my deepbit.net you can use 10 (may be even 20) miners on single worker account with long polling support. If you don't use long polling then miners number on single worker account is unlimited. |
|
|
|
Я даже суть неполадок поясню чтобы было понятно почему так долго: на бирже сделан подсчёт денег транзакциями без накопления ошибок округления. Это нужно чтобы в любой момент времени можно было сделать ревизию просто просуммировав все приходы расходы - должно совпасть идеально, иначе где-то идёт неверный расчёт и при тысячах транзакций он выльется во вполне конкретный ущерб пользователям. И вот этот механизм сейчас переделываем потому что он дико кривой а новый будет простой и нормальный. А почему бы просто не оставить старый работающим и заменить на новый когда новый будет дописан ? Невозможность вывода биткойнов снижает спрос на них и может привести к снижению местного курса. |
|
|
|
The problem with communism is there's no incentive to work. If I make the same working 80 hours a week that I do working 1 hour a week then why the hell would I work 80 hours a week? Communism can be real, but only when no one will have to work :) For example, if nanomachine assemblers or some other cyber-magic can do all the production, mining (not the bitcoin mining :), recycling and so on. Then only research, art and similar activities will be left to humans. Some of them will do this because they like it anyway. With current conditions it's, of course, impossible. Even now I think that the non-creative job that needs more than ~10% of someone's time is a job for machine :) |
|
|
|
Ok I think this might be a pool problem
I recently bumped up production by a lot and am having problems with my miners doing this:
"Problems communicating with bitcoin RPC"
I have 4 GPUs mining on the same worker name.
Should I be splitting this up? I'm getting very angry with all the small pauses. Is this DNS related or anything? Firewall is disabled.
No, you won't hit the worker limit with only that. If this ever happens with you, you'll see a message in your miner recommending to use no more than 20 LP clients on one worker account. As I understand, you have this problem on one of your mining rigs, but everything works fine on another ? |
|
|
|
Wait, does somebody seriously think Tycho is going to start double spending? I grant you that he might attempt it, in some parallel universe, but that would be the end of Tycho. So I think it's very unlikely.
It may sound crazy, but I've seen governments throughout history do a lot of crazy shit, and for less reason. I'd just rather there not be the potential for such an action. I'll repeat my answer from the previous page, just in case :) To mitigate the possible problems deepbit currently runs on servers located in different jurisdictions and we (deepbit admins) reside in other two different jurisdictions, so pool is relatively protected. So we can move all the mining power from one country to another in a few seconds. And of course I'll have enough time to warn users. |
|
|
|
The fact is, that you [or your pool] is [especially with slush working with you should that be the case] make prime candidates for destroying the the bitcoin economy. Personally, I would like you to close the pool to new members. I can't see how it can be bad for bitcoin economy. Moreover, it would be very good to see how bitcoin network will instantly heal itself in case of something. About closing registration - i'm not going to do something that is bad for my clients. Closing the registration is like trying to hide the problem, not fix it. And if you are going to be directly working with slush, then I suggest that the combination of the two pools not be allowed to exceed the 50% mark. I believe in self-regulation and free market. |
|
|
|
You'd mentioned earlier in this thread that you had no plans to exceed that 50% mark...but that may now be happening regardless. My question is whether or not we would be protected (as a pool) from actually executing the >50% attack on the network ourselves by way of some sort of subversion. Looks like I was wrong about 50%, I thought it was impossible to reach due to pools competition. I'm open to your proposals on handling such situation (even though I still don't think we can reach it permanently), so we could be more transparent to miners. I'm sure that there IS a solution; the fact of being >50% doesn't means that something bad will happen. One of the things I can do right now - I'm going to contact slush and get his phone number, so we could notify each other about pool problems. To mitigate the possible problems deepbit currently runs on servers located in different jurisdictions and we (deepbit admins) reside in other two different jurisdictions, so pool is relatively protected. Also I want to remind you something from https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_powerThe attacker can't: - Reverse other people's transactions
- Prevent transactions from being sent at all (they'll show as 0/unconfirmed)
- Change the number of coins generated per block
- Create coins out of thin air
- Send coins that never belonged to him
|
|
|
|
|
Show Posts
