The returning getwork hashes are passed to both nmc & btc clients. Either or both can find a block. To describe the whole process would be very lengthy.
Hmm... It seems I'll have to read up on that at some point, thanks. This doesn't solve the matter of the stats though. Either there are lots of missing blocks on the stats page or something is broken. Compare the list of recent blocks for the PPLNS pool here with with, for example, the list of recent blocks for masterpool.eu. In the last 24 hours we've had only 8 blocks and they've had 61. This simply cannot be explained by luck or the difference in hashing power (they've had about 140% more hashing power than us for this period). I don't know what to tell you.... except to check out the new transaction log. It's broken down to the last 100 transactions for each currency. It's all there, and in a much more readable format this time. http://simplecoin.us/transactionlog.phpAs for possible "missed" blocks, that's only if the namecoin client missed them. The balance is perfect for user balances and promotions, an extra 50 NMC would stick out like a sore thumb. If you like, I'll also post the Wallet balance, beside overall user balances & promotional balances. (Although, I'm not thrilled about announcing wallet info) |
|
|
|
Perhaps I've misunderstood something here. By matching Bitcoin and Namecoin block I'm thinking of an SHA-256 hash of [a list of Bitcoin transactions, some Bitcoin address information, and Namecoin data in a merkle tree] which happens to be a particularly low number (begins with quite a lot of 0s). It was my understanding that any hash small enough to generate a Bitcoin block would also be small enough to generate a Namecoin block and consequently I expected any merged mining Bitcoin block to have a corresponding Namecoin block (at least while Namecoin difficulty is less than Bitcoin difficulty). This belief was made stronger by posts such as this: https://bitcointalk.org/index.php?topic=42667.msg566146#msg566146where slush proudly announced the first Bitcoin merged mining block (which had a Namecoin counterpart) Bitcoin 148744 = Namecoin 19274. Can you guys explain why Bitcoin and Namecoin block generation events are not linked in this way? Are the corresponding random variables independent (in the sense of probability) and if so why? Thanks. The returning getwork hashes are passed to both nmc & btc clients. Either or both can find a block. To describe the whole process would be very lengthy. |
|
|
|
I noticed that you put GamingG's missing Bitcoin block (149249) on the list. Shouldn't there be a Namecoin block that coincides with this Bitcoin block? There is no Namecoin block on this list within a 1 hour radius of this Bitcoin block.
Also, what is the matching Namecoin block of trasp's Bitcoin block (149155)? Is it trasp's adjacent Namcoin block (19893) which is reported appearing more than a day earlier? Is it your Namecoin block (20125) reported 12 seconds after? Is it perhaps some other missing Namecoin block?
For anyone else out there trying to piece this together there was (and still may be) a +-1 offset bug to the reported block numbers here.
That's not how merged mining works. Bitcoin blocks and Namecoin blocks are found independently of one another. The site wallet balance is perfectly in sync with each client, any missing blocks would show up as a discrepancy in the site balance (client balance - user balances - promotional funds) in my admin panel. If I'm not mistaken, there is a way to match which btc blocks and nmc blocks we've solved by looking at our solved btc & nmc blockchains. |
|
|
|
Right now my account is showing an unconfirmed balance of 1.52413899 BTC but the stats report no unconfirmed BTC blocks. I have a separate confirmed balance of 1.61780172 BTC which I believe is down to trasp's block (149155).
Is there a PPLNS bitcoin block which is not yet on the stats chart Mike?
Might this "1.52413899" actually be unconfirmed namecoins from ericwmson's Namecoin block (20599)? (this block is currently unconfirmed and I have 0 unconfirmed namecoins).
I'd love to start encouraging people to come to this pool again but I'm personally finding the stats very concerning.
PPLNS has another unconfirmed BTC block  not sure why it isn't showing on the blocks page though. UPDATE: It was looking for the time on the network block (which missed entry due to solidcoin timing out). You can see it in stats now. |
|
|
|
ah ok, im mining tbx here. and the website i get a "502 Bad Gateway"
Yeah, website was trying to get info from solidcoin client. Speaking of solidcoin. I no longer have plans now or in the future to support it. Anyone with a remaining solidcoin balance PM me. TBX pool is back online. |
|
|
|
and the pool is down again...
Solidcoin locked up the test server. Never again. BTC/NMC/GG pools should still be up. |
|
|
|
Man, that was some serious downtime!
It's good to see that the pool was scoring blocks that weren't being shown. We already had bad luck but since the first outage things quickly became suspiciously bad. With the backdated blocks in place we are back to simply experiencing bad luck.
Caution: I would strongly recommend that if you mine here that you have a good backup pool configured for yourselves. I've been saying that this pool is good for it's server reliability and uptime, and indeed over the past month it's been excellent, but having two recent serious outages in the last 3 days is very poor. The simplecoin.us servers are certainly not reliable now and it will take a long time for this reputation to return.
Please keep us updated on the data centre madness Mike.
I'm told the issue is resolved and the responsible machine decommissioned. Even still I'm watching closely. |
|
|
|
The pool server is unreachable. Working with the hosting company. UPDATE: It seems one of the other hosted machines at the datacenter was binding itself to all the available datacenter IPs as well as being used to attack them. Hopefully, they will have the issue sorted shortly. UPDATE: Pool is back up! UPDATE 3: As for SAC, rather than spend time wasted rebutting you. I'm taking the time to add more auditing calculations. In turn, it will be easy enough for anyone to see their historical stats & payouts. In special cases like yours, it could even show said stats publicly. UPDATE 4: Looks like the stats sql replication server hung with the first outage.... And during that time, we found some blocks (BTC included)! |
|
|
|
|
Previous Solidcoin balances have been restored and can now be withdrawn. If you were a member of solidcoin.simplecoin.us previously and do not have a matching account, please either setup a matching account at simplecoin.us or contact me via PM.
Please note there is a 5% tax on SC coins currently. Until I have a way to calculate the SC client fees (likely once the pool is up), it will remain in effect.
|
|
|
|
Did we find a BTC PPLNS block? My shares just reset!
No, That's just the trailing shares (looks like I missed a MM stat). I'll get it fixed, payouts won't be affected. |
|
|
|
I very much expect you won't risk server reliability with solidcoin this time.
The SC client is living on the test machine until I see source code. That said, I haven't finished the SC pool just yet. The framework works fine, but pushpool is still mad at solidcoin. |
|
|
|
Just a heads up, there may be a slight outage as I move to Juke-Jrs MM solution.
UPDATE: Done!
There was an outage? Hardly noticed anything. Thanks. Yeah, about a minute or two for btc to stop and reload. UPDATE: Had to restart again, slight change to the client and config. |
|
|
|
|
Just a heads up, there may be a slight outage as I move to Juke-Jrs MM solution.
UPDATE: Done!
UPDATE 2: IPv6 should be working for the pool now as well.
|
|
|
|
Good work on the Namecoin block trasp! You and dookdook are really boosting this pool.
Cheers!
Cheers indeed! Also, I'm testing Luke-Jr's implementation of Merged Mining on the test server. If all goes well I'll be moving it over later today. If I'm lucky I'll also finish up the solidcoin pushpool and have it up as well. |
|
|
|
I'm still not sure if I'll be supporting solidcoin2. It would require a specialized new framework and a whole host of new software. I will however gladly load up the wallet and database to send out the coins that were previously acquired. Yes, please. I think its time for me to drop my SCs for now. Working on it. How about including the rest of your broken payout system in that work as well. I am looking at unconfirmed bitcoin in my account for 170 blocks now since I started keeping track and namecoin that has a hell of a lot more confirms than that on it too. No offense, but I'm starting to think you're just trolling this pool. When you first blew up in this thread, I found an issue. I corrected it. I even checked your stats specifically. Every one was exact for your share count. As for unconfirmed BTC.... are you in the SMPPS pool? If so, there hasn't been a BTC block found yet. Every found block has been paid out completely. The only existing balance is the promotional funds. |
|
|
|
Are you going to display share count for BTC? I saw that you fixed it yesterday I think but now it is back on the NMC share count. Thanks
Masterpool and NMCbit are showing BTC and I am mining there now...wanna come back once you fix it
Looks like BTC share count to me in the stats page.... |
|
|
|
I'm still not sure if I'll be supporting solidcoin2. It would require a specialized new framework and a whole host of new software. I will however gladly load up the wallet and database to send out the coins that were previously acquired. Yes, please. I think its time for me to drop my SCs for now. Working on it. |
|
|
|
Any particular reason my account was banned?
Too many bad password attempts. Just use password recovery to unban it. |
|
|
|
I'm still not sure if I'll be supporting solidcoin2. It would require a specialized new framework and a whole host of new software. I will however gladly load up the wallet and database to send out the coins that were previously acquired. |
|
|
|
Sweet, Im mining again woot! love the pool dude!
Thank you! And sorry about the outtage. That shouldn't happen again, and shouldn't have happened this time. |
|
|
|
|
Show Posts
