Bitcoin Forum
May 03, 2024, 10:22:54 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 [68] 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 ... 171 »
1341  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 14, 2012, 07:44:43 AM
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.
1342  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 14, 2012, 07:43:48 AM
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.
1343  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 14, 2012, 07:41:31 AM
Well crap.
Now I'm having another issue. Sad
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...
1344  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 10, 2012, 06:48:58 PM
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%.
1345  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 09, 2012, 11:53:13 AM
wow, 12mil shares, incredible... I hope that we'll have better luck now...
1346  Bitcoin / Pools / Re: [1437 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 06, 2012, 01:44:46 PM
Yeah tell me about it..7 hours  Shocked 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 :-)
1347  Bitcoin / Mining software (miners) / Re: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards, 200+ MH/s on LX150 on: February 06, 2012, 12:58:28 PM
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.

Quote
I will add an extra check so that BTCMiner recognizes full URL's too.

Thank you for the fix.
1348  Bitcoin / Pools / Re: [1366 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 04, 2012, 10:16:22 PM
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...
1349  Bitcoin / Mining / Re: Problem with Guiminer on: February 04, 2012, 10:14:50 PM
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...
1350  Economy / Trading Discussion / Re: MtGox/TradeHill SierraChart bridge - Realtime Bitcoin charts [v0.4] on: February 02, 2012, 11:28:38 AM
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 ;-).
1351  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 02, 2012, 11:25:06 AM
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...

Quote
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.
1352  Bitcoin / Pools / Re: [1366 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 02, 2012, 10:53:56 AM
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.
1353  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 02, 2012, 10:28:28 AM
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...


Quote
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.

Quote
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.

Quote
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.

Quote
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.

Quote
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 :-)
1354  Bitcoin / Pools / Re: [1366 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 02, 2012, 10:12:31 AM
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).
1355  Bitcoin / Pools / Re: [1366 GH/s] Slush's Pool (mining.bitcoin.cz); supporting p2sh! on: February 02, 2012, 10:09:51 AM
The last 3 blocks (10416, 10417, 10418) have been marked as invalid ... is something wrong?  Shocked

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.
1356  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 01, 2012, 04:41:10 PM
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.

Quote
Finally, if you want to see ideas on how to monetize Tor relays, you should really take a look on the thread started by Mike Hearn that I linked above. Here's the link again: https://bitcointalk.org/index.php?topic=53551.0;all

What exactly you want to apply from Mike's proposal here? I think he's solving slightly different problem.
1357  Bitcoin / Bitcoin Discussion / Re: The way US government can crack down Silk Road, Tor and Bitcoin on: February 01, 2012, 04:25:49 PM
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?
1358  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 01, 2012, 04:23:18 PM
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...
1359  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 01, 2012, 04:20:38 PM
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.
1360  Bitcoin / Bitcoin Discussion / Re: Tor Idea. on: February 01, 2012, 03:03:58 PM
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.

Quote
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".
Pages: « 1 ... 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 [68] 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 ... 171 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!