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

[jjj0923]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.


and it's been 500 blocks since that pool has even found a block so how would you know?

[ocminer]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

[jjj0923]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

I have refreshed and I see what it's not doing.

please post your nodes.

Code:

root@ns500637:/home/wallets/.quatloo# quatlood getpeerinfo
[
    {
        "addr" : "72.78.100.5:17012",
        "services" : "00000003",
        "lastsend" : 1410470532,
        "lastrecv" : 1410470536,
        "bytessent" : 1777589,
        "bytesrecv" : 21659468,
        "blocksrequested" : 0,
        "conntime" : 1410463419,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "72.78.100.7:17012",
        "services" : "00000003",
        "lastsend" : 1410470536,
        "lastrecv" : 1410470536,
        "bytessent" : 155967,
        "bytesrecv" : 1908224,
        "blocksrequested" : 0,
        "conntime" : 1410463419,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "72.78.100.13:17012",
        "services" : "00000003",
        "lastsend" : 1410470536,
        "lastrecv" : 1410470536,
        "bytessent" : 159551,
        "bytesrecv" : 1893337,
        "blocksrequested" : 0,
        "conntime" : 1410463421,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "46.105.118.15:17012",
        "services" : "00000003",
        "lastsend" : 1410470532,
        "lastrecv" : 1410470536,
        "bytessent" : 234921,
        "bytesrecv" : 1939933,
        "blocksrequested" : 0,
        "conntime" : 1410463427,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "82.226.151.241:17012",
        "services" : "00000003",
        "lastsend" : 1410470671,
        "lastrecv" : 1410470672,
        "bytessent" : 2138686,
        "bytesrecv" : 5060105,
        "blocksrequested" : 0,
        "conntime" : 1410463432,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "192.99.167.159:17012",
        "services" : "00000003",
        "lastsend" : 1410470532,
        "lastrecv" : 1410470536,
        "bytessent" : 150263,
        "bytesrecv" : 1883949,
        "blocksrequested" : 0,
        "conntime" : 1410463514,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "162.243.118.225:17012",
        "services" : "00000003",
        "lastsend" : 1410470536,
        "lastrecv" : 1410470536,
        "bytessent" : 156816,
        "bytesrecv" : 1900687,
        "blocksrequested" : 0,
        "conntime" : 1410463533,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46405,
        "banscore" : 0
    },
    {
        "addr" : "54.244.118.104:17012",
        "services" : "00000003",
        "lastsend" : 1410470536,
        "lastrecv" : 1410470531,
        "bytessent" : 19943,
        "bytesrecv" : 21870,
        "blocksrequested" : 0,
        "conntime" : 1410469120,
        "version" : 70002,
        "subver" : "/Satoshi:0.1.1.2/",
        "inbound" : false,
        "startingheight" : 46455,
        "banscore" : 0
    }
]
root@ns500637:/home/wallets/.quatloo# 

[ocminer]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

I have refreshed and I see what it's not doing.

please post your nodes.

lots of nodes, currently 42 connections:

http://pastebin.com/EHVkU5WF

[jjj0923]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

I have refreshed and I see what it's not doing.

please post your nodes.

lots of nodes, currently 42 connections:

http://pastebin.com/EHVkU5WF

Version   Protocol Version   Wallet Version   Connections   Errors
10102   70002   10000   8   OK

I compiled the wallet from the source posted in the OP - is there newer source?

[SamWalters]

There is good node support

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

I have refreshed and I see what it's not doing.

please post your nodes.

lots of nodes, currently 42 connections:

http://pastebin.com/EHVkU5WF

[jjj0923]

There is good node support

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

I have refreshed and I see what it's not doing.

please post your nodes.

lots of nodes, currently 42 connections:

http://pastebin.com/EHVkU5WF

I will try your node list

thanks

ps: does this coin need "txMessages": true in the stratum - some coins do - like syscoin...

and thanks your posted nodes are much better - this is the only wallet that has been giving me problems. but it's humming along fine now

[jjj0923]

Mr_MarKus,

Can you guys update the list of pools? 

Some of those pools don't seem to live anymore.

Also, what pools are other people using?

i'm mining on suprnova - as usual - and mostly alone - all coins for me ^^:)

I'll be throwing 275MH at the coin tomorrow on qtl.lifeforce.info if you want to find more blocks and join me.

[jjj0923]

No problems at all at suprnova... mining works.. blocks are running as usual.. logs have nothing special..

no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.

i just did that.. nothing special mate.

also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.

I suspect your server, your connectivity or your pool wallet has a problem, not the network.

look here:
https://qtl.suprnova.cc/index.php?page=dashboard

and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected

actually - I have been comparing dashboards and I am right - often it does not refresh every two to three minutes - sometime it can be 10 to 15 minutes or longer because a new block is released into the block chain.

http://qtl.lifeforce.info/index.php?page=dashboard

same mpos software - same block chain - the block chain freezes from time to time....and then all of a sudden a bunch of blocks are released.


46501, 502, 503, 504 and 505 were all released into the chain within 1 minute of each other.


these two blocks were 9 seconds apart

2014-09-11 22:04:14 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:04:20 received block b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88
2014-09-11 22:04:20 Committing 1 changed transactions to coin database...
2014-09-11 22:04:20 SetBestChain: new best=b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88  height=46503  log2_work=53.199544  tx=59785  date=2014-09-11 22:03:38 progress=0.999992
2014-09-11 22:04:20 ProcessBlock: ACCEPTED
2014-09-11 22:04:20 CreateNewBlock(): total size 1000
2014-09-11 22:04:38 ThreadRPCServer method=getblockhash
2014-09-11 22:04:42 AcceptToMemoryPool: 192.99.167.159:17012 /Satoshi:0.1.1.2/ : accepted e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d (poolsz 1)
2014-09-11 22:04:42 CreateNewBlock(): total size 1193
2014-09-11 22:04:42 received getdata for: tx e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d
2014-09-11 22:04:55 AcceptToMemoryPool: 72.78.100.12:17012 /Satoshi:0.1.1.2/ : accepted 2a84cb58b45ca9cda1d0b839791d9284af90518992980f72aea715fbbdd08343 (poolsz 2)
2014-09-11 22:04:55 CreateNewBlock(): total size 1385
2014-09-11 22:05:01 ThreadRPCServer method=getinfo
2014-09-11 22:05:01 keypool reserve 2
2014-09-11 22:05:01 keypool return 2
2014-09-11 22:05:01 ThreadRPCServer method=listsinceblock
2014-09-11 22:05:02 ThreadRPCServer method=help
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:10 received block c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd
2014-09-11 22:05:10 Committing 3 changed transactions to coin database...
2014-09-11 22:05:10 SetBestChain: new best=c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd  height=46504  log2_work=53.199598  tx=59786  date=2014-09-11 22:03:47 progress=0.999984
2014-09-11 22:05:10 ProcessBlock: ACCEPTED
2014-09-11 22:05:10 CreateNewBlock(): total size 1385
2014-09-11 22:05:10 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:17 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:32 received block 018f32f6ab2aad1ab432eab4615b5005439c562da7da3ac46414fd9e8eac3ec6

[MarKusRomanus]

It has nothing to do with nodes.  The big hashers and multipools jump on it and drive the difficulty high then they drop off.. there will be a pause until that difficult block it solved.  Then its low difficulty again.. its how darkwave gravity works.

[jjj0923]

Marcus - thank you for the explanation. That make sense to me. I see the number of blocks is correct per hour but they are no evenly spaced like other coins.

[RonMank]

Marcus - thank you for the explanation. That make sense to me. I see the number of blocks is correct per hour but they are no evenly spaced like other coins.

jjj are you running a pool for it?

[jjj0923]

Marcus - thank you for the explanation. That make sense to me. I see the number of blocks is correct per hour but they are no evenly spaced like other coins.

jjj are you running a pool for it?

no wallet is too fickle with those sudden bursts of blocks - I have decided against it for the time being.

[mem_co]

Quatloo and Key are the two coins destined for higher prices over the next few months. That's just a fact. Buy and hold. 4000 QTL and 2000 KEY popped aside in cold storage for the future - everything else is just play money ;-p

In Quatloo case, there is one very easy way to make panic buy. Just increase price of Quatloo Trader.

[CryptoJohn]

This is painful to watch yes but it is opening up buying opportunities that most did not think they would see again.

Want to stop the bleeding? Pull your sells. Force those monkeys that have progressively cheaper buy orders posted to pay a reasonable price.

Psychology is the #1 determining factor to success in any traded market. If you show confidence that what you own has value the price goes up. If you show fear of losing the price plummets.

Don't be a sucker! It always amazes me how people continue to undersell each other like there is a prize at the bottom. Selling now is ludicrous, your giving away the cookie.
Are these your first trades or something? If you are still holding then you missed your chance to profit. I know, you bought below 3500sat when I did but I'm talking real profit....Hold the Line!

Exchanges don't like bots but they live because of volume so bots will survive.

Don't worry grasshopper, QTL will not disappoint unless you out and want back in on the rise.

[kb4scv]

Relatively small coin count at this point.  Only way to lower price is not to place buy support.  I think that is exactly what is happening.  And I also hope next update comes with larger amount of coins needed.  The Trader will progressively get better over time and should end up being expensive for what it does.  Want the rewards, buy in early or else, pay or be priced out!  The fewer amount of people in the Trader a year from now, the better for us!

[CryptoJohn]

Quatloo and Key are the two coins destined for higher prices over the next few months. That's just a fact. Buy and hold. 4000 QTL and 2000 KEY popped aside in cold storage for the future - everything else is just play money ;-p

In Quatloo case, there is one very easy way to make panic buy. Just increase price of Quatloo Trader.

One thing I love about QTL is the price of the trader is only the amount you hold...genius.
I think the 1000 QTL is too low. Make a tool this advantageous available only to those serious enough to own 2500 or 5000 QTL or the btc equivalent.

This does 2 things:
1) Drives QTL price up
2) eases the obnoxious amount of bot traffic that is obviously getting under the skin of the exchanges. When every Joe has a bot they lose their effectiveness anyway.

[kb4scv]

I agree, be serious now about what Markus will make this or lose out.  No harm in rewarding early investors.

For all those that are serious investors in this kind of stuff, I see no way you look at where this is going and don't see upside.  All these coins where even the good Devs have to spend months on features the community comes up with, and this one gets suggestions built into it and they get to be used immediately.  I realize it will become harder and harder to integrate complicated routines into the program, but just think about how powerful they will get as it builds.  It will be worth the wait, and even more so, worth the early investment.

I keep saying it, but the Trader has already bought itself for me.  It would for anyone else too at this point.  Buy in people, or watch those of us who did have all the fun later!

 

[MarKusRomanus]

Hey, everyone.  I want to chime in with an update on where things are going with the Quatloo Trader.  I have tweeted that the auto arbitration functions are in the works and the major update will be released October 1st .. a conservative estimate.. could be sooner.  This feature will require larger QTL holdings.  More details soon.

[RonMank]

Hey, everyone.  I want to chime in with an update on where things are going with the Quatloo Trader.  I have tweeted that the auto arbitration functions are in the works and the major update will be released October 1st .. a conservative estimate.. could be sooner.  This feature will require larger QTL holdings.  More details soon.

looking forward to it

Thanks!