[ANN] "Cubits" V2 (QBT) Sha256D POW

[daemonfox]

need to fix the cash out  in the pool..
cannot use the paste address option

Paste as in you cannot paste your address into the field?

I just did this myself and got paid so... lost?

[dreamwatcher]

what do you want to know abot difficulty?

Not me..The software for the pool front end, it was originally designed around scrypt coins.

It is really a matter of going through all the modules to find where the calculations are and correct them. Though the front end is a very nice piece of software, the developers did hard code into individual modules quite a bit when it comes to difficulty calculations for the stats on the website.

[LeilaD.]

At last, what's curent hashrate of Cubits network?

[daemonfox]

At last, what's curent hashrate of Cubits network?

You can only calc a rough estimate based on difficulty since the client has no nethashrate call.

[dreamwatcher]

Well, I have some good news!!

I am in the middle of updating one of my other pools and I discovered the latest version of the font-end software now offers the option to operate under scrypt or SHA256.

Sometime tonight I will be bringing the pool down for a bit to update it and change out the back-end.

[ryanb]

I am selling some QBT coins

10k QBT coins for 0.1 BTC

send me pm

[poplolnman]

selling 10k qbt for 0.095 btc

[5Dzz]

I really like the idea of sci fi coins.  The Galactica theme is cool 

[freecoins]

28k Cubits - 0.2 BTC

[fenix79]

60k QBT = 0,4 BTC

[ryanb]

i have plenty of coins send me your offers.

[daemonfox]

I think there is an issue here with difficulty calc and block target in relation to halving expectations... we are 83% of the way to the first halving (block 78500) and its only been 7 days... plus I have been watching as I solo... and diff swings wildly at times... from where it feels correct in the upper 400s to mid 600s for the GH/s on the pool, myself and estimation of others, to dropping below 100 causing tons of orphans and my client saying I went on a solving spree (at one point my immature was in the 4K range).

In just the last 12 hours of mining solo... I solved 150K QBT worth of blocks. 12 hours at 33 second block target should have only yielded about 196K total QBT to everyone who solved in that time period... no way my 30 GH/s racked up 75% of the blocks... ill bet at least 1 million QBT generated in the last 12 hours...

... something is off...

EDIT: 2:10 PM EST

I updated my CGWatcher and set an ASIC profile for QBT and have been collecting data for the last hour.

AVG time for blocks is around 6 seconds

AVG find for me is every 56 seconds

Watched diff skyrocket to over 1.5K then sink back into the 600s before starting to rise to 900s right now. Pool is showing 150 GH/s and I am averaging 31 GH/s solo.

[gorgorom]

OP are you going to do anything with this coin? Hand over the development to me if not -.-

[Aspen]

OP are you going to do anything with this coin? Hand over the development to me if not -.-

+ 1
I will help you!

[dreamwatcher]

I have not heard from cassie in few days.

If it comes down to it, I can/will take over the development, Hopefully with cassies' blessing. I may make it part of a larger development of coins. There are a couple of things going on behind the scenes, but rest assured, one way or the other I will make sure this coin continues to develop.



Question for the miners on the Pool:

How many of you that are seeing high invalid rates are using BFGminer?

I have noted some interesting stats last night  and I want to see if part of them are true.

[mogrith]

I'm getting about a 15% reject rate with BFG 3.4.0 and 333 MH/s usb erupters

[poplolnman]

43,000 QBT for 0.25 BTC

[theprofileth]

Orphans are pretty intense, I remember at one point I had around 8K immature solo mining then ALL of them were orphaned lol I might of been mining on my own chain with those kinds of numbers. Only problem is that the pool gives me terrible reject rates so I don't know what is worse, losing 8k coins to orphans or losing more to wasted shares on the pool. Furthermore I vote that the development be handed over to someone who actually knows what the fuck they are doing so we can relaunch this coin without stupid mistakes. Also I propose that we hardfork the coin at the approacing halving day, set that as the new base amount of coins per block and use the ACTUAL block time proposed being 33 seconds rather than this ungodly 6 seconds plus give actual info regarding the remaining coins and halving dates. Also someone needs to fix the message for when you lock your coins it says you will lose all your ZETA COINS if you forget your password   either way I like this coin I just want it to get launched properly and not like how it is so far.

[daemonfox]

From what I know, and I may be wrong since it has been some time since the conversation, this was developed by someone who does know what they are doing.

That said... it is entirely possible this was their first attempt at a Sha256d coin.

I do not see a need for a "relaunch" but I would agree that an update to correct the block target so it matches 33 seconds is needed.

To ask for that to be done by the time we reach the block halving is absurd... there is not enough time... that is going to be reached in under 24 hours at this rate of block generation.

Cassie... you should speak up and let everyone know what is going to happen... no one should be forced to forfeit coins at this juncture so a relaunch is not the answer... but a hard fork with a forced update on a hard check point is definitely a must to fix this.

[dreamwatcher]

Orphans are pretty intense, I remember at one point I had around 8K immature solo mining then ALL of them were orphaned lol I might of been mining on my own chain with those kinds of numbers. Only problem is that the pool gives me terrible reject rates so I don't know what is worse, losing 8k coins to orphans or losing more to wasted shares on the pool. Furthermore I vote that the development be handed over to someone who actually knows what the fuck they are doing so we can relaunch this coin without stupid mistakes. Also I propose that we hardfork the coin at the approacing halving day, set that as the new base amount of coins per block and use the ACTUAL block time proposed being 33 seconds rather than this ungodly 6 seconds plus give actual info regarding the remaining coins and halving dates. Also someone needs to fix the message for when you lock your coins it says you will lose all your ZETA COINS if you forget your password   either way I like this coin I just want it to get launched properly and not like how it is so far.

I am currently working on the pool invalids. Are you using BFGminer? I only ask as it seems that the miners with the high invalids seem to have that in common.

This is strange as the back-end is Eloipool. Both Eloipool and BFGminer are developed by Luke-jr. I have tried a vanilla stratum back end, but I start to get errors of a different sort (Non-fatal, but concerning nevertheless)

I will continue to look for a back-end that does not produce the level of invalids, but for now if you can, change the parameter to submit stales to off. Many of the invalids are in fact stales submitted after the new block is triggered.

AS for the coin itself, I am working with another developer and if in fact Cassie wants to give up the coin, either directly or by silence, the coin will become part of a larger project. The development of these coins is special in the sense that eventually they will need to be licensed. This means development will need to come under an official business with limited liability and I can provide that along with my experience in the cryptocoin world in both development and the community.

There are talks going on the background. This coin will not fall into abandonment.