[ANN][QTL] Quatloo, A DarkWaveGravity Scrypt Coin Mandatory UPDATE to v1.2.1

[ocminer]

Release is not too far away!  0400 GMT on June 25th.

aah thats in the middle of the night for europeans :-(

[Bitcycle]

Release is not too far away!  0400 GMT on June 25th.

Cool.

Who are you?  Who else is on your team?  What are your track records?

[MarKusRomanus]

Release is not too far away!  0400 GMT on June 25th.

Cool.

Who are you?  Who else is on your team?  What are your track records?

Well, I've been a member of this forum for over a year, I have a degree in engineering physics, and I have been programming for 11 years.  I'm not hiding behind some noob name.  This is my first shot at a cryptocurrency fork , but I have spent the better half of 6 months familiarizing myself with every detail so I could do this without any oversights. There is  one other developer, but I am the main one.  I hope to partner with others in the future.  I did the coding, graphics , and the compiling of the windows app for Quatloo.  

[Tuwie2]

You definitely need to do some about that difficulty re-target.

The coin will get raped to start and you dont want to hastily throw something in.

Take care of it now, before the launch, and avoid the headache in a couple days.

[MarKusRomanus]

You definitely need to do some about that difficulty re-target.

The coin will get raped to start and you dont want to hastily throw something in.

Take care of it now, before the launch, and avoid the headache in a couple days.

I will announce my decision regarding the difficulty re targeting concerns in 24 hours.

[MarKusRomanus]

Difficulty re target every 6 hours. KGW to be implemented in first update... maybe before release.  Possible delay of release by a day or 2 as I'm leaning towards a launch with KGW re target every block.. TBA

[MarKusRomanus]

Release date has been changed to 6/27 to give me time to finish up code modifications and tests for the new difficulty re target model.

[ocminer]

Release date has been changed to 6/27 to give me time to finish up code modifications and tests for the new difficulty re target model.

Keeps us informed, looks very good, I'll surely add it

[MarKusRomanus]

Release date has been changed to 6/27 to give me time to finish up code modifications and tests for the new difficulty re target model.

Keeps us informed, looks very good, I'll surely add it

Thanks!  I'm done with the code and about to perform some tests to verify the KGW is working as expected for when Quatloo switches to this mode at block 17011 (testnet 1701)

[MarKusRomanus]

Ok The code changes are done and the tests show it will work fine.  Fixed retargeting until block 17011 , then retargeting every block afterwards using Kimoto Gravity Well.  Now I'm wondering one thing.. the new 6 hour retargeting until block 17011 may be too fast maybe? essentially that means for 2.25 min blocks.. 160 blocks.  That would be quick retargeting in the early mining of the coin, wouldn't it?  I think it will be interesting.. but should be fine.  At least there won't be a huge grab in the beginning at very low difficulty.

update- difficulty retargeting has been changed to DGWv3

[ocminer]

Ok The code changes are done and the tests show it will work fine.  Fixed retargeting until block 17011 , then retargeting every block afterwards using Kimoto Gravity Well.  Now I'm wondering one thing.. the new 6 hour retargeting until block 17011 may be too fast maybe? essentially that means for 2.25 min blocks.. 160 blocks.  That would be quick retargeting in the early mining of the coin, wouldn't it?

Yes.. Why KGM so late ? Why not do like 100 blocks with fixed retargeting, then KGM or DGW ?

KGM effectively fights any instamine as it adjusts very quick but if you introduce it so late, it's, in my opinion, pretty useless as someone with lots of hashes could try to grab many blocks until it kicks in

[MarKusRomanus]

Ok The code changes are done and the tests show it will work fine.  Fixed retargeting until block 17011 , then retargeting every block afterwards using Kimoto Gravity Well.  Now I'm wondering one thing.. the new 6 hour retargeting until block 17011 may be too fast maybe? essentially that means for 2.25 min blocks.. 160 blocks.  That would be quick retargeting in the early mining of the coin, wouldn't it?

Yes.. Why KGM so late ? Why not do like 100 blocks with fixed retargeting, then KGM or DGW ?

KGM effectively fights any instamine as it adjusts very quick but if you introduce it so late, it's, in my opinion, pretty useless as someone with lots of hashes could try to grab many blocks until it kicks in

Well that is a good point.  17011 isn't all that late and the prospect of getting a decent chunk of coin in its early days is what attracts people to mine it sometimes... well at least in the beginning.  I'm trying to get the best of both worlds.  I'm conflicted on the exact way to settle on, but i do want it to follow normal difficulty retargeting for a short while then convert to KGW.  Suggestions?  Changes now are really easy to implement without delay of the launch date.

[ocminer]

Ok The code changes are done and the tests show it will work fine.  Fixed retargeting until block 17011 , then retargeting every block afterwards using Kimoto Gravity Well.  Now I'm wondering one thing.. the new 6 hour retargeting until block 17011 may be too fast maybe? essentially that means for 2.25 min blocks.. 160 blocks.  That would be quick retargeting in the early mining of the coin, wouldn't it?

Yes.. Why KGM so late ? Why not do like 100 blocks with fixed retargeting, then KGM or DGW ?

KGM effectively fights any instamine as it adjusts very quick but if you introduce it so late, it's, in my opinion, pretty useless as someone with lots of hashes could try to grab many blocks until it kicks in

Well that is a good point.  17011 isn't all that late and the prospect of getting a decent chunk of coin in its early days is what attracts people  to mine it sometimes.  I'm conflicted on the exact way to settle on, but i do want it to follow normal difficulty retargeting for a short while then convert to KGW.  Suggestions?  Changes now are really easy to implement without delay of the launch date.

I hate 0 Reward Blocks.. So don't do a Blocks 2-1000 are 0 Reward, 1001-17011 are 5 and afterwards are "normal" reward - that kills the coin.

KGW is pretty old and - for me as a miner - kills the fun @ mining especially with so long block times as it adapts really fast and literally "works too well". But maybe that is what attracts people - we should hear other opinions.

I like DGWv2, it has all the features from KGW; but nicer "to the miner" as it does not adapts SO fast and let "swings" work, so if you throw lots of hashes at it, you get at least a decent chunk before it adapts back.. so there is at least a chance to get your investment back. I think that attracts more people.

But .. We need more opinions

[MarKusRomanus]

I have to also remind you that a premine of only .1% would bring us to near 10000 block at launch anyways.

[MarKusRomanus]

I will review DGWv2 as well, yes.  And I believe there is a v3  i'm looking at right now.

[MarKusRomanus]

These different re targeting algorithms are fascinating and i've enjoyed digging into the code behind them... makes me want to create my own!  Eh, but that'll have to be for a future project. I was wary to implement them due to the talk about KGW and the time warp exploits.

[ocminer]

I have to also remind you that a premine of only .1% would bring us to near 10000 block at launch anyways.

Why not make Block 1 as big as the whole premine sum, so you dont need so roll so many blocks...

[MarKusRomanus]

I have to also remind you that a premine of only .1% would bring us to near 10000 block at launch anyways.

Why not make Block 1 as big as the whole premine sum, so you dont need so roll so many blocks...

I thought about that.. and people just cry about it being a sly way to hide premine then accuse the dev of dishonesty.

[ocminer]

I have to also remind you that a premine of only .1% would bring us to near 10000 block at launch anyways.

Why not make Block 1 as big as the whole premine sum, so you dont need so roll so many blocks...

I thought about that.. and people just cry about it being a sly way to hide premine then accuse the dev of dishonesty.

wat ? :-) premine is premine ^^

I don't care about premines < 1 %, so i'd like to see a "clean" blockchain without having 10.000 blocks already mined before the first pool fires up..

You're the dev.. you decide

[MarKusRomanus]

Well... True!  You'll never please everyone anyways.  I'm glad I didn't just launch and waited a week.. This all has been helpful!  Yes , I'm thinking I will just have the premine out of the way in the first block.