https://www.cryptopia.co.nz/Home/Voting
Topic: [TGC][ANN] Relaunch Tigercoin - Official thread - page 6. (Read 31374 times)
New Tigercoin pool at
http://www.xaxamining.com/pool/TGC/
Point your miner at:
stratum+tcp://162.208.11.59:3340
username= (yourtigercoinaddress)
password= anything
Mine with xaxamining!!!
Vote TCG at free voting on cryptopia!!!
http://www.xaxamining.com/pool/TGC/
Point your miner at:
stratum+tcp://162.208.11.59:3340
username= (yourtigercoinaddress)
password= anything
Mine with xaxamining!!!
Vote TCG at free voting on cryptopia!!!
i'mma going with cryptopia first and will try to match any DOTs voted ... 500k is super cheap (was 5M)
i like nova ... but new guy exchange ... but can be the 2nd exchange we pickup ... but i don't see add coin feature there
Try novaexchange.com
we can buy a listing for 500K DOTs ... or 1/10th the price it was before
also Tiger seems to poll well we will lose this months election but if we are luck likely could win the June election
also Tiger seems to poll well we will lose this months election but if we are luck likely could win the June election
I use this node list, (in part i see that some are the same) but i don't specify the port number....
from my .conf :
addnode=194.135.91.150
addnode=193.192.37.135
addnode=108.61.10.90
addnode=193.33.237.189
addnode=198.27.81.114
addnode=91.121.221.92
addnode=192.169.6.169
Verify also that an eventually firewall you have don't stop communications for the wallet.....
from my .conf :
addnode=194.135.91.150
addnode=193.192.37.135
addnode=108.61.10.90
addnode=193.33.237.189
addnode=198.27.81.114
addnode=91.121.221.92
addnode=192.169.6.169
Verify also that an eventually firewall you have don't stop communications for the wallet.....
I am not able to get my tiger coin wallet to sink version v1.2.0.3 keeps on saying no block source. I tried to all all the nodes here i found online. I deleted everything and added nodes still no good.
addnode=194.135.91.150
addnode=82.161.253.248:25967
addnode=108.61.10.90:15660
addnode=73.9.181.217:55021
addnode=193.107.92.153:34640
addnode=91.210.123.5:54219
here is some of the log file under debug.
123.5:15660
trying connection 54.146.80.130:15660 lastseen=133.4hrs
connected 54.146.80.130:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=54.146.80.130:15660, peer=54.146.80.130:15660
socket recv error 10054
disconnecting node 198.96.90.226:48695
trying connection 73.9.181.217:1616 lastseen=375663.1hrs
connected 73.9.181.217:1616
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=73.9.181.217:1616, peer=73.9.181.217:1616
socket recv error 10054
disconnecting node 23.95.95.154:49558
trying connection 78.47.150.66:15660 lastseen=360.0hrs
connected 78.47.150.66:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=78.47.150.66:15660, peer=78.47.150.66:15660
socket recv error 10054
disconnecting node 54.146.80.130:15660
socket recv error 10054
disconnecting node 78.47.150.66:15660
trying connection 162.248.102.117:15660 lastseen=1914.1hrs
connected 162.248.102.117:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=162.248.102.117:15660, peer=162.248.102.117:15660
trying connection 188.0.46.102:52475 lastseen=375663.1hrs
connected 188.0.46.102:52475
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=188.0.46.102:52475, peer=188.0.46.102:52475
socket recv error 10054
disconnecting node 162.248.102.117:15660
trying connection 5.189.161.164:15660 lastseen=207.1hrs
connected 5.189.161.164:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=5.189.161.164:15660, peer=5.189.161.164:15660
socket recv error 10054
disconnecting node 5.189.161.164:15660
trying connection 188.163.83.75:3206 lastseen=375663.1hrs
connected 188.163.83.75:3206
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=188.163.83.75:3206, peer=188.163.83.75:3206
socket recv error 10054
disconnecting node 73.9.181.217:1616
trying connection 69.179.87.38:15660 lastseen=138.6hrs
connected 69.179.87.38:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=69.179.87.38:15660, peer=69.179.87.38:15660
socket recv error 10054
disconnecting node 188.0.46.102:52475
trying connection 152.250.184.87:64114 lastseen=375663.1hrs
connected 152.250.184.87:64114
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=152.250.184.87:64114, peer=152.250.184.87:64114
socket recv error 10054
disconnecting node 188.163.83.75:3206
trying connection 66.90.144.173:15660 lastseen=610.9hrs
connected 66.90.144.173:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=66.90.144.173:15660, peer=66.90.144.173:15660
socket recv error 10054
disconnecting node 69.179.87.38:15660
trying connection 73.214.64.147:15660 lastseen=223.4hrs
connected 73.214.64.147:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=73.214.64.147:15660, peer=73.214.64.147:15660
socket recv error 10054
disconnecting node 152.250.184.87:64114
trying connection 72.220.83.227:15660 lastseen=150.0hrs
connected 72.220.83.227:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=72.220.83.227:15660, peer=72.220.83.227:15660
socket recv error 10054
disconnecting node 66.90.144.173:15660
trying connection 178.62.223.150:15660 lastseen=161.2hrs
connected 178.62.223.150:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=178.62.223.150:15660, peer=178.62.223.150:15660
socket recv error 10054
disconnecting node 73.214.64.147:15660
trying connection 100.70.114.194:15660 lastseen=23.6hrs
socket recv error 10054
disconnecting node 72.220.83.227:15660
socket recv error 10054
disconnecting node 178.62.223.150:15660
connection timeout
maybe some body can tell me how can i fix it to sink.
addnode=194.135.91.150
addnode=82.161.253.248:25967
addnode=108.61.10.90:15660
addnode=73.9.181.217:55021
addnode=193.107.92.153:34640
addnode=91.210.123.5:54219
here is some of the log file under debug.
123.5:15660
trying connection 54.146.80.130:15660 lastseen=133.4hrs
connected 54.146.80.130:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=54.146.80.130:15660, peer=54.146.80.130:15660
socket recv error 10054
disconnecting node 198.96.90.226:48695
trying connection 73.9.181.217:1616 lastseen=375663.1hrs
connected 73.9.181.217:1616
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=73.9.181.217:1616, peer=73.9.181.217:1616
socket recv error 10054
disconnecting node 23.95.95.154:49558
trying connection 78.47.150.66:15660 lastseen=360.0hrs
connected 78.47.150.66:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=78.47.150.66:15660, peer=78.47.150.66:15660
socket recv error 10054
disconnecting node 54.146.80.130:15660
socket recv error 10054
disconnecting node 78.47.150.66:15660
trying connection 162.248.102.117:15660 lastseen=1914.1hrs
connected 162.248.102.117:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=162.248.102.117:15660, peer=162.248.102.117:15660
trying connection 188.0.46.102:52475 lastseen=375663.1hrs
connected 188.0.46.102:52475
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=188.0.46.102:52475, peer=188.0.46.102:52475
socket recv error 10054
disconnecting node 162.248.102.117:15660
trying connection 5.189.161.164:15660 lastseen=207.1hrs
connected 5.189.161.164:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=5.189.161.164:15660, peer=5.189.161.164:15660
socket recv error 10054
disconnecting node 5.189.161.164:15660
trying connection 188.163.83.75:3206 lastseen=375663.1hrs
connected 188.163.83.75:3206
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=188.163.83.75:3206, peer=188.163.83.75:3206
socket recv error 10054
disconnecting node 73.9.181.217:1616
trying connection 69.179.87.38:15660 lastseen=138.6hrs
connected 69.179.87.38:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=69.179.87.38:15660, peer=69.179.87.38:15660
socket recv error 10054
disconnecting node 188.0.46.102:52475
trying connection 152.250.184.87:64114 lastseen=375663.1hrs
connected 152.250.184.87:64114
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=152.250.184.87:64114, peer=152.250.184.87:64114
socket recv error 10054
disconnecting node 188.163.83.75:3206
trying connection 66.90.144.173:15660 lastseen=610.9hrs
connected 66.90.144.173:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=66.90.144.173:15660, peer=66.90.144.173:15660
socket recv error 10054
disconnecting node 69.179.87.38:15660
trying connection 73.214.64.147:15660 lastseen=223.4hrs
connected 73.214.64.147:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=73.214.64.147:15660, peer=73.214.64.147:15660
socket recv error 10054
disconnecting node 152.250.184.87:64114
trying connection 72.220.83.227:15660 lastseen=150.0hrs
connected 72.220.83.227:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=72.220.83.227:15660, peer=72.220.83.227:15660
socket recv error 10054
disconnecting node 66.90.144.173:15660
trying connection 178.62.223.150:15660 lastseen=161.2hrs
connected 178.62.223.150:15660
send version message: version 70001, blocks=870140, us=67.44.192.75:15660, them=178.62.223.150:15660, peer=178.62.223.150:15660
socket recv error 10054
disconnecting node 73.214.64.147:15660
trying connection 100.70.114.194:15660 lastseen=23.6hrs
socket recv error 10054
disconnecting node 72.220.83.227:15660
socket recv error 10054
disconnecting node 178.62.223.150:15660
connection timeout
maybe some body can tell me how can i fix it to sink.
gRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR!
dev your gonna need to talk with Hex
PM me or post here
Quote
Cryptopia Listing Policy
Coins may only be submitted for review by an active developer of the coin.
The coin's network must be able to sustain a network of at least 4 active nodes.
The coin must be able to fully sync on its own from the network without the use of 3rd party bootstraps of the blockchain.
We must be able to get the coin to compile locally from source from a public source repository, preferably github.
An active member of the coin team should give us optimally 30 days advance notice via support ticket of upcoming mandatory coin updates such as forks.
We do not list ICO or IPO coins.
Premines will be evaluated and justified on a case by case basis, we reserve the right to reject any premined coin.
An active dev of the team should ideally be available to assist with issues with the coin's network outside of Cryptopia's control.
A coin must be able to maintain a network sufficient enough to consistently process blocks at the average target time.
The coin must have an up to date forum thread on the Cryptopia Forums maintained by an active member of the coin's team.
Any coin violating any of these requirements for longer than a period of 30 days may be subject to delisting.
Voting is final, votes will not be refunded, please ensure you vote for coins that meet all of the listed requirements.
As each coin is reviewed on a case by case basis there is no guaranteed ETA on how long the review process will take. If you do not want to wait, provided your coin meets all requirements for listing you may pay the listing fee of 5,000,000 DOT upfront to get listed immediately.
The voting page is a way for the community of a coin to crowdfund the listing fee of their coin, there are no rounds, votes do not expire, every coin that reaches 5,000,000 DOT votes will be listed provided the coin meets all of the listed requirements.
Any coin rejected or delisted can start the listing process over provided it now meets the requirements for listing.
If you would like to submit a coin to the vote you must raise a support ticket and be able to verify that you are an active dev for the coin.
Coins may only be submitted for review by an active developer of the coin.
The coin's network must be able to sustain a network of at least 4 active nodes.
The coin must be able to fully sync on its own from the network without the use of 3rd party bootstraps of the blockchain.
We must be able to get the coin to compile locally from source from a public source repository, preferably github.
An active member of the coin team should give us optimally 30 days advance notice via support ticket of upcoming mandatory coin updates such as forks.
We do not list ICO or IPO coins.
Premines will be evaluated and justified on a case by case basis, we reserve the right to reject any premined coin.
An active dev of the team should ideally be available to assist with issues with the coin's network outside of Cryptopia's control.
A coin must be able to maintain a network sufficient enough to consistently process blocks at the average target time.
The coin must have an up to date forum thread on the Cryptopia Forums maintained by an active member of the coin's team.
Any coin violating any of these requirements for longer than a period of 30 days may be subject to delisting.
Voting is final, votes will not be refunded, please ensure you vote for coins that meet all of the listed requirements.
As each coin is reviewed on a case by case basis there is no guaranteed ETA on how long the review process will take. If you do not want to wait, provided your coin meets all requirements for listing you may pay the listing fee of 5,000,000 DOT upfront to get listed immediately.
The voting page is a way for the community of a coin to crowdfund the listing fee of their coin, there are no rounds, votes do not expire, every coin that reaches 5,000,000 DOT votes will be listed provided the coin meets all of the listed requirements.
Any coin rejected or delisted can start the listing process over provided it now meets the requirements for listing.
If you would like to submit a coin to the vote you must raise a support ticket and be able to verify that you are an active dev for the coin.
dev your gonna need to talk with Hex
PM me or post here
vote or this happens
a tiger will lick you
... to the BONE!
VOTE
https://www.cryptopia.co.nz/Home/Voting
And please keep up the voting on Cryptopia. Tigercoin is giving us a real run for our money, but I'm sure there's more of us than there are of them!
https://www.cryptopia.co.nz/Home/Voting
https://www.cryptopia.co.nz/Home/Voting
R U moins or are you Tigers!
down by 5!
#1 still UP BY 10!
vote everyday this next 3-5 days is crucial as Tiger can make a solid breakout
12 days to VICTORY!
vote everyday this next 3-5 days is crucial as Tiger can make a solid breakout
12 days to VICTORY!
BOAT!
TQ Steve ... I do think he'll take tiger tips 
---------
VOTE
https://www.cryptopia.co.nz/Home/Voting
running @ #2
Moin 216
Tiger 197
KLondikes 084
17 days left
---------
VOTE
https://www.cryptopia.co.nz/Home/Voting
running @ #2
Moin 216
Tiger 197
KLondikes 084
17 days left
Tigercoin blockchain snapshot available at CryptoChainer.com for fast wallet sync.
tiger down by 4
17 days to go
17 days to go
VOTE
https://www.cryptopia.co.nz/Home/Voting
running @ #2
Tiger 170
▲ Moin 175
#3coin 070
18 days left
M O I N ――― is promoting hard in their forum too ――― have a feeling we are going to the wire head 2 head ――― VOTE everyday!
https://www.cryptopia.co.nz/Home/Voting
running @ #2
Tiger 170
▲ Moin 175
#3coin 070
18 days left
M O I N ――― is promoting hard in their forum too ――― have a feeling we are going to the wire head 2 head ――― VOTE everyday!
VOTE
https://www.cryptopia.co.nz/Home/Voting
running @ #1 tied
Tiger 145
Moin 145
#3coin 061
19 days left
https://www.cryptopia.co.nz/Home/Voting
running @ #1 tied
Tiger 145
Moin 145
#3coin 061
19 days left
Jump to: