Topic: [ANN] "Cubits" V2 (QBT) Sha256D POW - page 11. (Read 14284 times)

I will get it changed today, I haven't got to altering the back pages yet. The mining address and port has been on the front  (home page) since the start.

Me and friend both having problems syncing the cubit wallet (blockchain).  Unable to connect to peers to sync up.  We're on different networks, never had this prob with any other alt coin wallet (and we've used a good few).  Any ideas?  Does this coin re-implement the peer sync in any different way then bitcoin or any of the alts?

that fixed it.

Dreamwatcher uou have bad port number on getting started page of pool

stratum+tcp://qbtcoin.com:17000

I'm not sure what I'm doing wrong. But I can't connect to the cubits pool

.\bfgminer.exe -o stratum+tcp://qbtcoin.com:3333 -u mogrith.mogrith_1 -p xxxx -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

I want to yet again apologize for the Downtime on the pools, since my last post that they are up.

The issues were all on the VPS end, however I now have a direct contact with them so in the future i will not have to wait for support tickets to be answered.

All pools are back up. 

The CCE4 test server is still down (Block Explorers).

quick FYI:

I have three VPS down, including all the pools. I have a ticket in, awaiting response.

The coin works great, diff adjustment is very smooth.

Will be nice to see it on the SciFi exchange

Pool Update:

The dashboard works, note the network hash rate is 0, this is because of the lack of network hash rate command on the coin daemon RPC.

Everything else on the DASHBOARD page looks accurate.

On the pool stat page, pool hash, est avg time, est shares and QBT per day are not accurate. However the same accurate information is on the dashboards page (Except QBT per day).

The going is slow as I have to go through each modules code by hand and change the equations where inaccurate. MANY of the equations are hard coded.

Over the next few days, I will dedicate time to getting the stats on the pool page and block listing (percentages), working.

I am now confident enough to give the complete green light to mining on the pool.

QBTCOIN.COM

YOU WILL NEED TO REGISTER!!! IF YOU DO NOT, THE POOL WILL NOT KNOW WHAT TO DO WITH YOUR SHARES!

Tues or Wed when I get my new set of Block Erupters in I will point them towards the pool indefinitely. For rite now I am solo mining with my main rig till the difficulty becomes to high so I can get enough coins for a few give aways.

Getting the dashboard working will be nice.

It's working well for me. I have my miner on a ~1hr rotation on 3 pools so I will be on and off all day. I can remote in and switch in or out of the pool if you need me to.

Pool Update:

It looks like I have solved the 150/50 coin base issue. It was a pool back-end issue that involved some hard coded values buried in the code.

The next step is to fix the dashboard issues. As I mentioned earlier, the dashboard issues do not effect share counting and payout.

There will be no network hash rate display as there is no network hash rate RPC command in the daemon. The pool hash rate and miner stats do need to be fixed by correcting the sha256 difficulty issue.

Setup and connected to pool.
collecting shares, building towards a payout.

Receiving Payouts.

Needs more miners in pool I'm only one on ATM.

So join and give it a try.

Every block I have found solo mining has been 150 qbt. 

Only found 2 blocks so far solo but both were 150.00

Will try pool

UPDATE:

I have the basic pool up. However, it is still in an very early state. It runs and can be mined  but with a couple of caveats.

1. All the statistics as far as hash rates and estimates are off. The front end software I use does not understand SHA256 difficulties, as it was primary written for scrypt coins. THIS DOES NOT EFFECT SHARE COUNTING AND PAYOUT. A share is a share, the back end checks that validity of a share and marks it good or not. The front end does not need to understand the hash itself, it is just looking for shares marked good and/or marked accepted blocks(solved blocks). The back-end (stratum) takes care of submitting blocks and validating shares.

2. That being said, I have found an issue not related to the Front-end, but have not determined what exactly is the issue. Since both local and server testing with my rigs were done using a stratum back-end, I need to determine if the following issue is due to block template or the stratum back-end itself.

I am getting blocks with the correct coin base (reward) of 150 qbt, but I am also getting blocks with a 50 qbt coin base.

Is anybody else seeing this while regular solo mining directly through the client/daemon? I am testing direct mining  now with my rigs to see if it happens.

All that being said, I really like the layout of the latest version of the front end. Feel free to sign-up and check it out. You can mine if you want, the important tasks of counting shares and payout work, but the dash statistics are inaccurate and I still have to hunt down the 150/50 coin base issue.

If worse comes to worse, I will set up a LP port if the 150/50 qbt issue turns out to be between stratum and block template. I will continue to work on getting the difficulty calculations to understand SHA256 difficulties to get the pool looking proper. Afterwords I will apply a nice Galactica theme to the pool.

Pool address: http://qbtcoin.com

I really like the basis for this coin.  I am going to solo mine this coin for a while.

Thank you Dream you R - D > Best!