Topic: [ANN][QUIT] Quit Dough, Real Products (e-cigs) +Multi-Vendor Vape Site (Read 61430 times)

QUIT dropped from Cryptopia. Looks like the coin really "quit" finally. Thats a pity. It was so promising project.

Is there a pool..? Is anybody here?

Yes, it is trading on Cryptopia: https://www.cryptopia.co.nz/Exchange/?market=QUIT_BTC.
There are also LTC/DOGE/Other markets for QUIT.

Is Quit Dough trading on an exchange?

pineapples are you the dev now? if so the one way to make this coin profitable could be to greatly decrease the pow and increase the pos followed by a site that does not accept fiat. bite the bullet on a few sales but with the right marketing for the site you could hypothetically bump up the price.

dead again

I've found occasionally clearing the dead weight out by reducing addnodes in the .conf and deleting peers.dat can assist with connections.

I've lodged a ticket with cryptopia and am waiting to hear back, has anyone else done so?

Mine was down for a bit today, it is up again, now Cryptopia shows 3 connections now.

That is better than UIS , which has only 2 and is forked to hell, (They only added it a week ago lol)

Perhaps this is enough to make Hex happy for now...


If you compiled it, I assume you are using linux, may be just that, networking behaves so much better..

I still have no clue why changing the ordering of lines in my config file made it happy, I had essentially the same thing you posted, but in a different order....weirdness

Interestingly, the Staking weight is way up now, looks like some lurkers have fixed their wallets ;P

Ok, so I did that. Compiled the daemon and started it on another VPS from the scratch. It isn't completely synchronised yet, but Cryptopia already sees it!
So now they have two connections. I used exactly the conf settings listed above, nothing else. I am unsure why Cryptopia sees only my machines, and ignores everyone else?  

It should be related to the way I am starting them.

If there is a firewall, its important to open the port 60237 on that server! I don't see other reason why it could not see other servers...

I will try to install one more node on different machine. Cannot promise I'll keep it though...

Its really interesting whether Cryptopia will see that one.

It should , and I really don't know why it doesn't.

For giggles, I copied exactly what you posted, deleted the peer database.

Looking at the the logs, it grabbed 7 seed address, and 4 more from the node above.

But nobody tries to connect inbound....

I stuck another copy of the wallet on another machine on my internal lan and it connects instantly, tho it is conencting to the lan address...
It does tell ne it is listening tho

I can also connect to the external network address from inside with telnet, tho I don't speak wallet, but it logged the connection and disconnect..

Kind of out of ideas here


Edit: and suddenly, after an hour, I have 3 connections...
(Cryptopia however still has only 1)

Not sure if thats the case..

I have made a small test using separate wallet on my PC:

1. Removed all "addnode=" entries from "quitdough.conf", except a single one : 104.207.131.249, which is my node.
2. Deleted the "peers.dat", so my wallet can work like it was started from the scratch and does not know any peers.
3. Started my wallet.

The result: it connected to my node and after 1 minute has a lot of connections:


02:23:55

[
{
"addr" : "104.207.131.249:60237",
"services" : "00000001",
"lastsend" : 1457216578,
"lastrecv" : 1457216579,
"conntime" : 1457216330,
"pingtime" : 0.07812500,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : false,
"startingheight" : 367448,
"banscore" : 0
},
{
"addr" : "108.113.85.117:53989",
"services" : "00000001",
"lastsend" : 1457216584,
"lastrecv" : 1457216584,
"conntime" : 1457216335,
"pingtime" : 0.53125000,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 367448,
"banscore" : 0
},
{
"addr" : "70.168.206.2:12879",
"services" : "00000001",
"lastsend" : 1457216584,
"lastrecv" : 1457216584,
"conntime" : 1457216338,
"pingtime" : 0.25000000,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 367448,
"banscore" : 0
},
{
"addr" : "84.234.52.190:53716",
"services" : "00000001",
"lastsend" : 1457216584,
"lastrecv" : 1457216584,
"conntime" : 1457216341,
"pingtime" : 0.12500000,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 367448,
"banscore" : 0
},
{
"addr" : "178.157.251.50:14444",
"services" : "00000001",
"lastsend" : 1457216587,
"lastrecv" : 1457216587,
"conntime" : 1457216347,
"pingtime" : 0.17187500,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 367448,
"banscore" : 0
},
{
"addr" : "162.255.117.105:63208",
"services" : "00000001",
"lastsend" : 1457216618,
"lastrecv" : 1457216618,
"conntime" : 1457216377,
"pingtime" : 0.32812500,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 367448,
"banscore" : 0
}
]

So I am not sure why some other wallets cannot get peers from the node... Maybe the settings on the other wallets are different?
Here is my "quitdough.conf" on the PC wallet. You can try it, if it worked for me, should work for everyone else too...

I don't really think all those settings are needed, but better to try with them as in my config.

Part of the issue seems to be the wallet itself, it is not doing a very good job of telling nodes about other nodes.
It really needs an update, it doesn't even support console addnode

My node will accept inbound, it has for quite some time, but nobody connects to it, so your node isn't telling other nodes about it at all


addnode=108.113.85.117:60237

Unfortunatly my IP is not fixed, so it will only work for a little while

So what?

Will this coin be finally delisted from its only exchange (Cryptopia), or someone will care to setup a node? The deadline is very close. I have seem someone trying to pump this coin last month, its strange that *someone* is going to let it die...

Currently there is still just one node - mine. Its apparently not enough, so if there is still somebody here, and is willing to save this coin - would be nice to setup one more node and contact Cryptopia.

As far as I understand, there is no specific requirements for the node, except for the following:

1. It should have listen=1 set in the .conf file.
Try this .conf settings, they should be ok:

2. The node should be maintained, i.e. someone should ensure it runs all the time, without going on and off.

I actually have something like a node running (my node is typically the only one visible at aikapool.com). But *sometimes* I switch it off for some time (to offload the server when I need that), then run again.

If you run your node, please do not forget to explicitly inform Cryptopia owners about that, as otherwise they can easily miss your node and close the market.

can anyone tell me how i run the node for this coin
need help whit the conf to run the node

hi can anyone plz set op a node for QuitDough coin so it can be runing. so we can trade it at cryptopia

Strange. I just run my wallet on PC and get the following:

[
{
"addr" : "24.220.150.22:60237",
"services" : "00000001",
"lastsend" : 1451130934,
"lastrecv" : 1451130962,
"conntime" : 1451130932,
"pingtime" : 0.96875000,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : false,
"startingheight" : 293985,
"banscore" : 0
},
{
"addr" : "104.207.131.249:60237",
"services" : "00000001",
"lastsend" : 1451130962,
"lastrecv" : 1451130963,
"conntime" : 1451130933,
"pingtime" : 0.23437500,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : false,
"startingheight" : 293985,
"banscore" : 0
},
{
"addr" : "84.234.52.190:54937",
"services" : "00000001",
"lastsend" : 1451130962,
"lastrecv" : 1451130964,
"conntime" : 1451130937,
"pingtime" : 0.43750000,
"version" : 100051,
"subver" : "/Satoshi:1.2.0.1/",
"inbound" : true,
"startingheight" : 293985,
"banscore" : 0
},
{
"addr" : "46.73.180.133:57395",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1451130962,
"conntime" : 1451130962,
"pingtime" : 0.00000000,
"version" : 0,
"subver" : "",
"inbound" : true,
"startingheight" : -1,
"banscore" : 0
}
]

So there are at least 3 working nodes.

EDIT: but wait I just looked on Aikapool, and can see your QuitDough wallet is perfectly synced now and has two connections!
Even more, it has the correct height, so it is now on correct fork finally!! Congratulations!

The only problem now is - you show the big red "FORK!" text near the coin name
The text should be removed, because finally this coin is NOT on a fork, and it is possible now to mine at your pool!

Aikapool have new wallet!
0 nodes work!

Yup, I stopped my node as there were others running. I rerun it now and easily got few connections:

        "addr" : "162.255.117.105:64310",
        "addr" : "176.193.208.209:65505",

I will repeat once more - your is on wrong fork most probably. And maybe even the old version of wallet used.
If you care to completely re-sync (delete the blockchain and sync it again), I promise to leave my node running for some time

Your nodes not work!