I've been mining for the last few hours and your site tells me I have no shares. Anyone else having this issue?
Switching away until issue resolved. Lost eight hours (at least) already. Unless you can find a minimum of 1 share per 5 minutes (the timedelta), hashrate.php will always misreport. I see a balance of 0.165 BTC on your address, which will be paid out when it reaches 1 BTC or after 1 week of not mining on the pool. Another idea I had, was to put it back to paying out tiny coins again, but also accepting transactions using those coins at no fee. The two problems with this plan would be: 1) the clients will still think they need to pay a fee unless you hack them, and 2) it leaves less space in our blocks for normal with-fee transactions. Currently undecided. It also wouldn't be very easy to write. |
|
|
|
Since addresses are per-transaction and not per-user, it really doesn't make sense to do it in just DNS. A simple HTTP protocol could query http://domain/bitcoinaddress?comment=hi+there and get a text/plain address back (while the server-side script makes a db entry of the comment) |
|
|
|
|
Asynchronous wouldn't solve it for me. I have JSON-RPC requests blocking on loopback JSON-RPC requests. My current code is working so long as I build without SSL support, so I guess it's good enough for now.
|
|
|
|
If you're on Linux this script will display info about one address: alias poolinfo='curl -s http://luke.dashjr.org/programs/bitcoin/pool/balances.json|python -c "import json,sys,time;d=json.load(sys.stdin)[sys.argv[1]];print \"Oldest: %s\nNewest: %s\nBalance: %s\" % (time.ctime(d[\"oldest\"]),time.ctime(d[\"newest\"]),d[\"balance\"]/1e8)"' poolinfo YourAddress |
|
|
|
Should each miner have its own address? Does it confuse the code at all if they don't? I can't think of any reason it would be a problem, but I'm not overly familiar with that part, and make no guarantees. I'm lost. How do I read the 3 fields? Balance is how much the pool considers owed to you if a block is found "now" (that is, it includes the payout of the currently-in-progress block); it is (as all data should be) denominated in raw bitcoin units aka Satoshis: divide by 100,000,000 to get the BTC equivalent. Oldest is the time your balance went positive originally. In case there are more due for payout than the generation has to distribute, those waiting the longest get paid first. Newest is the most recent time your balance was increased. If this gets to be over a week old, you will be paid your balance regardless of its value. |
|
|
|
It ends with ,"":null}, but otherwise it seems fine. Yeah, stupid JSON won't let me just leave a trailing comma at the end of an object, and I'd rather throw that in than slow it down even a little with a stupid check every address... |
|
|
|
Could someone having trouble with ufasoft come on #bitcoin-dev so we can troubleshoot it? |
|
|
|
What's the reasoning for not paying out under 1 BTC? If it's part of the generation transaction, then I wouldn't expect it would add much overhead to pay out less. I'm assuming most people don't want to get bunches of tiny coins. It's fine for the pool, but you'll have to pay a hefty transaction fee when you want to spend them, simply due to the data size of the transaction. Maybe you could have the password be the minimum amount you want paid? I could, but then anyone random could hijack your address and change it easily. Better to find a happy medium, IMO. What's the reasoning for the pool keeping all transaction fees? I'm certainly fine with a pool that takes a cut, since running a pool takes quite a bit of effort, but it feels weird to me to mine on a pool that requires transactions to have fees, but then not get any of them. Originally, it was because the code had no way to know how much the fees added up to. With version 2 that changes, but the transactions are more or less work done by the pool, not the miners, so it makes more sense (to me) to have the pool simply keep those fees rather than taking a sizable percent out of the miners' fair work. Just curious. I don't really do mining now that CPU mining is pretty much useless, but I fired up minerd at this for a bit until it submitted a few shares to test it. Thanks. I'll try to get some kind of "what is my balance" online soon after I do the upgrade (which is mainly waiting on reactions and comments before I do it). |
|
|
|
a few minutes ago v1.3 miner reported upstream RPC error and failed to reconnect to pool, I had to kill app and start it again
Sorry about that, I restarted bitcoind in preparation for the new pool script. It shouldn't happen again, when I do the real upgrade. |
|
|
|
So far how many blocks generated?
As of now it looks like 4! Seems we're a bit on the lucky side right now. I count 5. I'm about to push out an update that makes it a lot more accurate with payouts. It will also recalculate the entire history of payouts. As a result, you may have extra rewards in the next block (as soon as there are fees to cover paying them out), or you might have your payout "docked" a little because it overpaid you. In any case, the margin of error from the old code was small, under 0.02 BTC total. Another change is that the pool will no longer make payouts for amounts under 1 BTC. It will manage a virtual balance for your address until you have that much and make a single 1 BTC payout as soon as possible. On the other hand, if your address doesn't earn anything for a whole week, it will assume you've stopped mining on the pool and payout whatever is owed. As always, I am open to constructive criticism and suggestions. I still don't have code to display these balances anywhere (they're basically calculated during block creation every time, to avoid any problems from orphaned blocks), but I hope to soon. |
|
|
|
Question. The 'shares' field in hashrate.php output, is that the number of accepted shares for this work unit? Or accepted shares in a period of time? Accepted shares over timedelta. Is there a way for me to see how many accepted shares there are for the current work unit? Isn't that what we are paid on? There is no way to see this data right now. |
|
|
|
So, I have to set the "Pay transaction fee" to 0.00016392 for your pool to process a payment I make? 0.00004096 BTC. The only thing I'm really missing is long polling. I wonder, has anyone confirmed long-polling is working for this? We found our first block overnight. |
|
|
|
- Transactions are included in blocks based on my policies: non-standard transactions accepted, but a flat transaction fee required of 0.00008196 BTC per 512 bytes
I can't imagine why you think limiting transaction inclusion is wise at this point, particularly for an unestablished pool with no system of checks and balances (read: a web interface like slush's). Two words: transaction spam. And again, a web interface can easily lie-- it's nice to have, but provides no security. |
|
|
|
Hmm, really in my opinion you are going to need some way of showing when you got a block and what the payout to everyone is. Without that, I don't think people will trust the pool. I've never seen this from the current pools. Besides, if a pool operator wanted to cheat, they could just silently withhold/lie about blocks found... I agree statistics are nice, but I'm not sure it's a trust-related issue. I'd particularly like to know the total pool hashrate. Me too. Any idea how to calculate it? I figure at least 912 MH/s from what people have told me they're running on it. |
|
|
|
Where to see the results?
Any website address to see my money & shares... Results will show up immediately in your client when one of us finds a block. No website or anything setup right now, I'd like to minimize my time spent on it to minimize the fees I have to charge. Maybe when this part is good and tested, it might be worth looking into... dunno yet. |
|
|
|
So I finally got my pool "working". But it needs testing  Website: http://eligius.st/Basic concepts:Pool keeps all transaction fees to itself, plus 0.00000001 BTC per second since last-found block and 1 share per block.Remaining reward is divided equally among ALL shares contributed since its last-found block.When a block is found, you receive your payout for that block immediately as a Generated transaction, but only if your total balance is over 1 BTC (new, to help you avoid huge fees).If a block is orphaned, its shares become part of the next block's reward distribution.No registration. Just send username with the address you want payouts to (password can be anything).Transactions are included in blocks based on my policies: non-standard transactions accepted, but a flat transaction fee required of 0.00004096 BTC per 512 bytes
Edit: Please see our website for all the latest details. To test, point your miner to http://mining.eligius.st:8337 with username set to the same address you want paid. WARNING: Generations won't show up on your MtGox/MyBitcoin/etc. balance, so make sure you use the address of a standalone client for payouts. (thanks theymos!) Donations for pool may be sent to: 1RNUbHZwo2PmrEQiuX5ascLEXmtcFpooL
poclbm: poclbm.exe -d1 --host=mining.eligius.st --port=8337 --user= YourAddress --pass=x phoenix: phoenix.exe -u http:// YourAddress:x@mining.eligius.st:8337 -k poclbm DEVICE=0 VECTORS BFI_INT* FASTLOOP AGGRESSION=6 DiabloMiner: DiabloMiner-Windows.exe -u YourAddress -o mining.eligius.st -r 8337 ufasoft: bitcoin-miner.exe -a 5 -o http://mining.eligius.st:8337 -u YourAddress -p x This thread is locked and replaced with a new thread here. |
|
|
|
So I finally got my pool "working". But it needs testing Basic concepts: - Pool keeps all transaction fees to itself, plus 0.00000001 BTC per second since last-found block.
- Remaining reward is divided equally among ALL shares contributed since its last-found block.
- When a block is found, you receive your payout for that block immediately as a Generated transaction, but only if your total balance is over 1 BTC (new, to help you avoid huge fees).
- If a block is orphaned, its shares become part of the next block's reward distribution.
- No registration. Just send username with the address you want payouts to (password can be anything).
- Transactions are included in blocks based on my policies: non-standard transactions accepted, but a flat transaction fee required of 0.00004096 BTC per 512 bytes
To test, point your miner to http://pool.bitcoin.dashjr.org:8337 with username set to the same address you want paid. WARNING: Generations won't show up on your MtGox/MyBitcoin/etc. balance, so make sure you use the address of a standalone client for payouts. (thanks theymos!) Donations for pool may be sent to: 1RNUbHZwo2PmrEQiuX5ascLEXmtcFpooL
poclbm: poclbm.exe -d1 --host=pool.bitcoin.dashjr.org --port=8337 --user= YourAddress --pass=x phoenix: phoenix.exe -u http:// YourAddress:x@pool.bitcoin.dashjr.org:8337 -k poclbm DEVICE=0 VECTORS BFI_INT* FASTLOOP AGGRESSION=6 DiabloMiner: java -cp target\libs\*;target\DiabloMiner-0.0.1-SNAPSHOT.jar -Djava.library.path=target\libs\natives\windows com.diablominer.DiabloMiner.DiabloMiner -u YourAddress -p x -o pool.bitcoin.dashjr.org -r 8337 -g 5 ufasoft: bitcoin-miner.exe -a 5 -o http://pool.bitcoin.dashjr.org:8337 -u YourAddress -p x |
|
|
|
|
Show Posts
