any info to the massiv invalid namecoin blocks?
It was caused by broken namecoin explorer. I reported it to Namecoin developers and few minutes ago I also fixed namecoin rewards. Everything is fine again.
|
|
|
BinoX is right, pool luck is calculated only from finished blocks from intervals now()-1 day, now()-7days, now()-30 days. That explains why pool luck can be high even when pool is working on ugly long round.
|
|
|
Well crap. Now I'm having another issue. It's all up and running, but whenever I try to check the balance, it says "bad response from server". What gives? This makes me worried that I'm not getting credit for the mining I'm doing in this pool. This is bug in GUIminer, it's broken since I added SSL support for profile page...
|
|
|
Im pretty sure this is the worst (all three combined) luck ever (documented).
Afaik there was ~30% daily luck and ~80% monthly luck few months again. Luck in last few days is really strange, damn variance. However, long term luck (90 days and all time) is still 100%.
|
|
|
wow, 12mil shares, incredible... I hope that we'll have better luck now...
|
|
|
Yeah tell me about it..7 hours That has got to be the longest round evah! :p Longest round on the pool was 12+mil shares, so we (fortunately) didn't make the record today :-)
|
|
|
The Long Polling address returned by the server is usually a path, not a full URL.
From the official LP specification (provided by deepbit, who firstly implemented LP) it can be full URL as well, so my pool isn't breaking any specification. I will add an extra check so that BTCMiner recognizes full URL's too.
Thank you for the fix.
|
|
|
I don't have an idea why GUI miner is failing, but the bug appear also on other pools and I didn't modified pool core in last few days. I think it is something strange in gui miner...
|
|
|
Some people reported me issues with GUI miner on my pool, but I don't have an idea why it is doing that failure. I didn't modified pool software and also only guiminer is having issues. I think it is something strange in gui miner...
|
|
|
im getting a disconnection notice saying i need to pay. and the prices are absolutely redic! something like $45 for 2 months wtf!
Message from Sierrachart? You can ignore it, sierrachart bridge runs even on unpaid SC version. Otherwise you're doing something wrong. Also keep in mind that SierraChart is charting software for stock and commodity markets. 45$ for two months is really wtf - because it's the cheapest professioinal platform with trading data I've ever seen ;-).
|
|
|
Why? Even CPU mining will generate a result in under a minute. GPU mining would have you going in seconds.
Who said that one submitted share per minute will be enough for premium bandwidth? It's less likely with rising difficulty... Also, "even CPU mining" - say this to people who have one share per one hour. And I don't believe chinese disidents have strong GPU rigs in their basement :-). Actually redeemable codes have two main advantages: * You can premine them, no need to wait to mining submits during tor session * Price for transfer don't need to be same as "submit rate on common computer" to keep Tor running. Disadvantages: * There's some central entity (anonymous pool). However some pool will be still necessary, as relays don't want to mine solo, probably. And routing getworks and shares between pool and tor user over the relay is just another complication and overhead... How will you prevent double-spending the codes without accounting?
Of course relay redeem the code on issuer application, but it's very easy to implement. Actually my "no accounting" was related to issuing side; tor users don't need any account on pool issuing redeemable codes.
|
|
|
So I'd expect an increase in variance, but no change in expected value of a share due to the length of a round and miner hashrate.
...and did you asked those users how large dataset they're comparing? Those +20% in hashrate was my tip, pool knows only 30min average hashrate so I don't know exactly what's the boost on the beginning of the round.
|
|
|
I imagine it as an incompatible fork of TOR. When you go to build the circuit, nested tunnels are created to each successive relay node. At that time you're already communicating with those nodes, so adding getwork/submit results into the protocol wouldn't be hard.
I can imagine that my proposal can be compatible with current Tor and it's even less complex than "every relay is mining pool". Actually the only chance in your idea is "premine" traffic in every circuit, so you'll need to wait long time (hours?) before you'll be able to actually use the circuit. Don't forget that circuits are usually short-time constructs... This would require centralized accounting. If the codes are completely independent it would be a LOT of bookkeeping. No... why? getwork() -> mining -> submit() -> redeemable code received. Miner can even choose target difficulty of getwork, so one redeemable code can be the equivalent of 100 shares, for example (with target in getwork set to 100). No bookkeeping, no accounts, no identity revealed. Every getwork can be as anonymous as in your proposal, except that you can freely premine codes independently on the circuits you'll want use in the future. If the codes are pooled on an account that's used for a few minutes at a time, each account could only be used with one relay node, AND only when connecting to that relay node through a specific path. That's a lot of complexity to add. ...because you didn't catch the idea of redeemable codes. No account is needed on the pool. Every getwork can be isolated, so you can get completely unlinked pieces of value (=redeemable codes, which are equivalent of some well-defined work on the pool). However you're right that once you'll use redeemable code on one relay, you should not use it on another. But it's ok, because one code can be 100kB of transferred data. It would increase setup time since you would have to mine for several minutes to connect to the first node, then several minutes for the next node and so on.
No; that's the basic improvement against "mine on the relay". You can mine overnight for codes and then use them all during your one-hour session when you actually need it. If you allow premining or saving unused credits, it would also eliminate one of TOR's protections: forward secrecy. If you save the account number on your computer, someone who logged your connection from an exit node would then be able to prove it was yours after seizing your computer.
No, once you redeem the code, you drop it, because it is useless; relay will redeem it's whole value. For all those reasons I think it's better to mine in realtime for each node, only accumulating credits for as long as your tunnel is up.
I hope that I explained it better now :-)
|
|
|
Littleshop, Epoch - your payout in short rounds is lower, because there's more hashpower on the beginning of the round (yes, thanks to pool hopers). There's around 10-20% of increase in pool rate, which explains your math (because your own hashrate is smaller portion of total hashrate).
|
|
|
The last 3 blocks (10416, 10417, 10418) have been marked as invalid ... is something wrong? Cross-check for block validity on blockexplorer failed for some reason (I think BE was down for a moment). I fixed it manually right now.
|
|
|
AFAIK, the great firewall had blocked bridges. Tor is unusable inside of China.
Maybe, but there's simply no algorithm how to spread entry IPs between honest people and don't give it to China government :-). Paying for entry IPs isn't a solution, China still have much more money than chinese disidents. What exactly you want to apply from Mike's proposal here? I think he's solving slightly different problem.
|
|
|
If you want weapons in USA you just go in a shop and buy whatever you want...
Then the question is: who needs overpriced guns from SR when normal people can buy guns in the US freely?
|
|
|
seems like this could be sortof implemented by the tor exit nodes putting up a donation address on the webserver tehy run on the exit IP. Then people who use the service could donate to them.
Yes, donating exit nodes is in my opinion the most important, because it's much harder to run exit nodes than classic relay (you need to fight all those DMCA calls, for example). If you simply want to donate for building better Tor infrastructure, then feel free to send few coins to torservers.net, they're doing really good job for Tor. But if you want to "donate" for specific exit and then use some premium bandwidth, you still need changes in Tor protocol to auth yourself as a donator...
|
|
|
Is it possible to only pay the tor entrance node in bitcoin? That one already knows your IP anyway…
Yes, it is possible, but there's no big benefit in it, because usually the bottleneck is exit node, not entry node. Also by paying only for entry nodes, you're revealing that you're the client, which is leaking useful information for malicious nodes.
|
|
|
In addition to the problem of not enough relays there is the problem that relays announced publicly can be found by those that would wish to block them, which is regluarly done and effects users e.g. behind the great firewall.
There are Tor bridges, private relays who're not published on tor router list. They're acting as entry nodes and it works for users behind Great Firewall pretty well. Btw it is possible to ask them directly for "premium bandwidth contract" even without extending the Tor protocol. By charging a small amount for the relay info such attempts to block access to sites from TOR exit nodes or to block people connecting to relays would become more expensive.
That won't work, it will just block regular users from using Tor if they won't be able to "pay" for router list. Once you have some access to Tor network, you can detect all exit node IPs in one hour using simple script. That's also the reason why Tor relay list is publicly accessible, because every attempt to hide it is "security by obscurity".
|
|
|
|