node for Quatloo[QTL]:(2014)
addnode=185.87.149.61:17012
Topic: [ANN][QTL] Quatloo, A DarkWaveGravity Scrypt Coin Mandatory UPDATE to v1.2.1 (Read 408469 times)
June 27, 2022, 11:49:07 PM
March 15, 2021, 02:30:04 PM
EXCHANGE ADD TO https://freiexchange.com/
Are you saying it's been added to Freiexchange? I don't see it there.
March 15, 2021, 12:36:04 PM
EXCHANGE ADD TO https://freiexchange.com/
October 26, 2019, 02:16:55 AM
Is this coin still alive? Looking around for overlooked OG coins that still have a community lurking and a working blockchain. Might be able to get listed on an exchange -- no promises -- but needs to have some community AND a functioning network. Please reply if you're interested.
probably best to just assume this one is dead.
You may be right
October 25, 2019, 05:19:51 PM
Is this coin still alive? Looking around for overlooked OG coins that still have a community lurking and a working blockchain. Might be able to get listed on an exchange -- no promises -- but needs to have some community AND a functioning network. Please reply if you're interested.
probably best to just assume this one is dead.
October 07, 2019, 07:00:15 PM
Is this coin still alive? Looking around for overlooked OG coins that still have a community lurking and a working blockchain. Might be able to get listed on an exchange -- no promises -- but needs to have some community AND a functioning network. Please reply if you're interested.
March 18, 2019, 04:23:40 AM
Block Explorers are not working. Can anyone please help me to verify the block height for hash 709b88b8eef31b0e1e1d08525885bc313843e14e563466174b32b019fe30a748? Someone running the native wallet can help 
{
"hash" : "709b88b8eef31b0e1e1d08525885bc313843e14e563466174b32b019fe30a748",
"confirmations" : 239,
"size" : 250,
"height" : 790538,
"version" : 2,
"merkleroot" : "311cbf763007c98dd33d323e42945495ad30bb52fc5b06ac726fbff8114e7fad",
"tx" : [
"311cbf763007c98dd33d323e42945495ad30bb52fc5b06ac726fbff8114e7fad"
],
"time" : 1552662223,
"nonce" : 985514195,
"bits" : "1c208afb",
"difficulty" : 7.86642103,
"previousblockhash" : "de26da3dd32a3152fa3c9886f35402a3f389063a54be26c3a0c657be6ec46bfc",
"nextblockhash" : "0108aeb3b697959719e6f1dadd92668098fb2536a71de5520298879733cc7298"
}
March 17, 2019, 10:38:37 AM
Block Explorers are not working. Can anyone please help me to verify the block height for hash 709b88b8eef31b0e1e1d08525885bc313843e14e563466174b32b019fe30a748? Someone running the native wallet can help
January 10, 2019, 09:03:22 AM
If anyone is interested in this concept i am considering this model please check out the thread here- https://bitcointalksearch.org/topic/pre-ann-discussion-blockworkz-trader-and-arbitrage-bot-input-required-5095480
January 04, 2019, 07:01:31 PM
Is this coin traded on any exchange. Cryptopia will delist- is there a paperwallet or somewhere to store coins?
Try what I mentioned just above your post Cryptocracker, it worked for me.
January 04, 2019, 05:03:30 AM
Is this coin traded on any exchange. Cryptopia will delist- is there a paperwallet or somewhere to store coins?
https://novaexchange.com/market/BTC_QTL/
Use original wallet, it works well.
January 03, 2019, 04:46:18 PM
Is this coin traded on any exchange. Cryptopia will delist- is there a paperwallet or somewhere to store coins?
December 28, 2018, 10:46:49 PM
Hi my wallet is not syncing as well I tried all above.
Wallet on Windows? In the logs change nodes? What is the name of the configuration file?
Dude lostsoul86 try this cause I was having the same problem. In case it matters, I have a windows 10 computer. I looked on Cryptopia coin info QTL and clicking the green connections tab and found
addnode=173.249.60.242:17012
addnode=45.32.207.94:17012
addnode=37.59.53.125:17012
addnode=46.105.127.109:17012
addnode=164.40.246.244:17012
and copied it for later.
Then I deleted all of my previous quatloo folders that were in the folder downloads and the Quatloo Roaming folder (that I guess your computer creates when you open the wallet), then I downloaded the quatloo windows wallet on google chrome http://quatloos.org/
Then opened the folder, extracted the files opened the wallet then closed the wallet. I created an edify text editor file and pasted those 5 addnodes (I believe I downloaded the edify text editor on the microsoft app store but you may also be able to do this with notepad). Then I saved a type CONF file in this directory on file explorer This PC > C Drive > Users > (username) > Appdata > Roaming > Quatloo (in fact today I just learned that I had unhide folders so that I can see the Appdata folder) or search for this file explorer %appdata% roaming finding and place in the quatloo folder
December 24, 2018, 03:36:31 PM
It's funny the original BTC address in OP for donations had two which were never touched:
https://www.blockchain.com/btc/address/19Y2cY3e9sPzJUKdG576paDvKrr56aLCeB
https://www.blockchain.com/btc/address/19Y2cY3e9sPzJUKdG576paDvKrr56aLCeB
December 22, 2018, 06:31:03 AM
Hi my wallet is not syncing as well I tried all above.
December 22, 2018, 05:27:48 AM
anywhere for mac users to store coins or any other exchange that trades this coins and has working wallet?
December 16, 2018, 10:53:11 AM
Does your machine have a public IP address? And did you open the port 17012 in the firewall? If you do open it, you have much better chances of finding a peer.
Also you need to make sure your wallet indeed finds and opens the "quatloo.conf" file. Change some settings in the file, restart the wallet and look into the logs to see if they are applied.
Also you need to make sure your wallet indeed finds and opens the "quatloo.conf" file. Change some settings in the file, restart the wallet and look into the logs to see if they are applied.
My IP is determined through Internet services, so I think I have an external IP))) I don't have a firewall. The version of my wallet is 0.1.2.1. Maybe it is outdated?
The logs constantly repeat 2 lines:
2018-12-15 18:59:52 connection timeout
2018-12-15 18:59:53 trying connection 72.78.100.7:17012 lastseen=106.6hrs
Wallet settings are as follows:
server = 1
daemon = 1
listen = 1
...
Try the following conf, working for me:
Code:
proxy=127.0.0.1:9050
addnode=37.59.53.125:17012
addnode=46.105.127.109:17012
addnode=45.32.207.94:17012
addnode=164.40.246.244:17012
addnode=142.93.100.247:17012
addnode=173.249.60.242:17012
addnode=37.59.53.125:17012
addnode=46.105.127.109:17012
addnode=45.32.207.94:17012
addnode=164.40.246.244:17012
addnode=142.93.100.247:17012
addnode=173.249.60.242:17012
Obviously you'll need running tor for that.
December 15, 2018, 04:21:31 PM
My daemon version is the same, so it should not be the issue.
You should see in the logs your wallet trying to connect to all the nodes in your config. If you see it trying to connect only to 72.78.100.7:17012, your wallet most probably cannot read the config file (at least part of it). Try to shorten it, and remove all the spaces (" "), because I am not sure it can parse them correctly. Make a very small 10-line config file (add only fours full nodes below), stop the wallet, delete the "peers.dat", and start wallet again. You should see the wallet trying to connect to all those 4 nodes.
addnode=204.68.122.40
addnode=173.249.60.242
addnode=94.130.16.85
addnode=188.165.217.216
You should see in the logs your wallet trying to connect to all the nodes in your config. If you see it trying to connect only to 72.78.100.7:17012, your wallet most probably cannot read the config file (at least part of it). Try to shorten it, and remove all the spaces (" "), because I am not sure it can parse them correctly. Make a very small 10-line config file (add only fours full nodes below), stop the wallet, delete the "peers.dat", and start wallet again. You should see the wallet trying to connect to all those 4 nodes.
addnode=204.68.122.40
addnode=173.249.60.242
addnode=94.130.16.85
addnode=188.165.217.216
December 12, 2018, 01:53:57 PM
You did not change the other settings of the wallet? I added all the nodes that are on the last pages of this topic, but still no sync starts.
The only appropriate additional changes are these:
Code:
server=1
daemon=1
listen=1
daemon=1
listen=1
Does your machine have a public IP address? And did you open the port 17012 in the firewall? If you do open it, you have much better chances of finding a peer.
Also you need to make sure your wallet indeed finds and opens the "quatloo.conf" file. Change some settings in the file, restart the wallet and look into the logs to see if they are applied.
December 06, 2018, 09:39:48 AM
Did you created conf-file?
Yes, sure, I put all of the peers in there (quatloo.conf) like this
Code:
addnode=85.25.197.148:36457
addnode=5.101.96.124:41115
addnode=144.217.73.92:43416
...
I don't think the ports are really necessary, but anyway. In fact I believe it makes sense to add only those which use port 17012 (quatloo default port).addnode=5.101.96.124:41115
addnode=144.217.73.92:43416
...
Hi , is there a link for working windows wallet??
By the way.. Cryptopia is getting more and more ridicules.
I will sent support ticket morning.
The way how they delisting the coins is not right.
In first place,they must inform all traders that they will delist. And AFTER a some days, stop the trade ,like the others.I think ,more people will complain better
Thank you.
By the way.. Cryptopia is getting more and more ridicules.
I will sent support ticket morning.
The way how they delisting the coins is not right.
In first place,they must inform all traders that they will delist. And AFTER a some days, stop the trade ,like the others.I think ,more people will complain better
Thank you.
I use Linux, sorry. As to the delisting way - yes, I would agree. Doing it like Bittrex does (more gracefully - like announce the removal of the market 2 weeks prior to the market closure), seems to be much better. But I guess Cryptopia may have their own opinion on that...
Jump to: