It's kind of hard to test with something that you're not even sure exists...

Anyway, with sane nTime rolling and adaptive pseudoshare targets, getworks can provide more than enough work to remote hosts with very low bandwidth. Everything for nTime rolling is already there (the HTTP header), and adaptive targets are disabled temporarily, but I'll re-enable them for the next release.


I really don't see any issue with getwork. Why is GBT necessary?

P2Pool can handle reward halving.

EDIT: Getwork does have some problems with timestamp rolling. Depending on how ASIC miners handle it, it could work, but I'll start working on GBT support to allow timestamp rolling.

Because of course no one uses a remote p2pool node for a failover backup. /sarcasm

Sounds like no real testing has been done to verify it will not be an issue.

I'm starting to get the feeling that you are sticking your  head in the sand and hoping that everything will just work.

Well... a while ago, pyramining briefly switched over to my public node while they were working on some stuff.

I ended up having between 200-400GH/s at the time, and everything seemed to go just fine with my bandwidth, so p2pmining should be ok with the added bandwidth of the ASIC traffic.

If p2pmining would let you use higher diff shares, or maybe they can set up a high-hash node too. They're pretty much doing their own sub-share-chain, so maybe they will do something to accommodate the ASICs.

Not sure if they would tho. It sounded like they came into existence mainly to cater to the smaller miner who needed lower-diff shares.

-- Smoov

ps: Krak is in one of the outlying cities/towns that don't have a lot of infastructure to spread around. Rural-ish kind of area. That's where his main bandwidth bottleneck is. They get priced accordingly. Too much demand, not enough supply. So they get capped more.

Depending on the number of outstanding transactions and what transactions AREN'T being ignored, it is possible for GBT to use more bandwidth than GetWork ...

Really? P2Pool uses ~3 GB/month, normally. How much is too much for you?

With a normal pool, one getwork response/submit takes about 800 bytes of data, plus some HTTP stuff, so about 1KB for every 4 GH (2^32). At 1 GH/s, over a month, that's 650 MB (1 * (24*60*60*30) * (1000/4) / 1e6). It's probably a bit higher than that due to miners requesting more work than they need. In addition, that number scales linearly with the amount of hashing power you have, so with 3 GH/s, you're on par with P2Pool's bandwidth usage.

If I'd heard more complaints about bandwidth, I could have added an option to decrease the number of peers. Bandwidth usage is proportional to the number of peers you have, and 5 is probably enough, so you could halve the usage easily.

Well why isn't he paying out merged-mining rewards?

wow. 6 weeks? that is fast.

Can anyone put my anxiety at ease here.

I dl the new cpuminer and this is what came up after the 4th hash



I trust spybot and it never failed me to date. I know some things can be accidentally added to DB's However this has never come up with these miners.

This one is the first miner program that has done this.

Would it be possible to add a check box or something in the accounts page to force pay-outs to have the 0.00001111 formatted ending so that people with linked accounts could start early investment into pyramining asics?  Perhaps even set this as the default behavior at some point (if we aren't there already) as it becomes economically infeasible to buy new fpga hardware?

I expect that the issue will be solved in a few hours. On other computers bitcoind 0.7.1 is running smoothly so I am afraid that this problem depends on the huge wallet.dat (~200MB).

Of course if this problem goes away with the previous release, I will write to the developers in order to let them know about this trouble.

AFAIK this is the only mining company that it's regularly growing and paying dividends to all members, and where investors didn't lose any satoshi.

To the operators of GLBSE (I guess that's just Nefario at this point) -

I would like to request that as soon as you get the opportunity, you re-enable the feature of logging in and downloading a .csv of our individual trade histories.

I have not seen this appeal in any of the million and thirty-seven other GLBSE threads.

That is all.

would it be possible to change my payout address?

I use e3000 - it is fancy but it's the recommended way. However it may break on power loss - I experienced optware's system file partition crash on force switch off.

I haven't decided yet. After Nefario provides a list of investors there are some options:

1. Close down the operation, i.e. move bitcoins from exchanges (including buying bitcoins for current fiat balances) and distribute bitcoins to investors. This is the easier option for me.
2. Move to other exchange. It depends if this can be easily done, if some other exchange owner allows to move asset there and if we will have to pay additional costs for this move. I'm not sure if some other exchange can be safe enough.
3. Administer the dividend payouts by myself. I'm not sure if this option is feasible if there are many small investors. The frequency of payouts would change to once per month or once per 2-3 months maybe. Maybe I would buy back shares from small investors to continue like this if they will agree.

What are opinions of my investors?

Edit: Bots are still working meanwhile and profits are being accumulated.

Yes, existing links are still valid and new links are generated when there are less than 2 active.

I have not been able to check, as I went through the process last night, but I have heard that the AML restrictions have been lifted.

Claim finished
Your claim has been submitted and will be reviewed. You will be contacted (via the email address you provided) to keep you up to date on the status of your account, we will try to get your bitcoin to you as soon as possible.