GoldCoin Talk
Main Category => Technical Discussion => Topic started by: MicroGuy on June 06, 2013, 10:12:21 AM
-
According to the developer the wallet will not sync until another block is mined. It is still safe to send and receive coins. I will keep this thread updated as more information becomes available.
-
Now synced but we need 170 blocks till we get to diff drop:)
-
Now synced but we need 170 blocks till we get to diff drop:)
Thank you for providing this clarification.
-
My client is stuck at block 20890, and says I have ~350k to go.
-
My client is stuck at block 20890, and says I have ~350k to go.
Just close and open wallet. I have the same problem. You can receive and send coins no problem.
The sync problem is due very low hashrate network. When in the future the hashrat picks up the problem will go away. We are at block 20890 so that is correct.
-
My client is stuck at block 20890, and says I have ~350k to go.
Just close and open wallet. I have the same problem. You can receive and send coins no problem.
The sync problem is due very low hashrate network. When in the future the hashrat picks up the problem will go away. We are at block 20890 so that is correct.
Sync problem I think is due to the new client doing a forking change.
-
My client is stuck at block 20890, and says I have ~350k to go.
Just close and open wallet. I have the same problem. You can receive and send coins no problem.
The sync problem is due very low hashrate network. When in the future the hashrat picks up the problem will go away. We are at block 20890 so that is correct.
Sync problem I think is due to the new client doing a forking change.
Hi twobits and welcome aboard. What corrective action(s) would you recommend at this time?
-
I am still have sync problems even with new client and after the folk. This still due to low hashrate of the network?
-
I am still have sync problems even with new client and after the folk. This still due to low hashrate of the network?
I think you a referring to something which is not a sync problem. The client appears to be attempting to download the wrong blockchain, whilst still being up to date (you will find it works normally at this time as well).
It is due to a rogue node (or two) giving the wrong info : actually offering the wrong chain. It is rejected by good nodes, and is only a problem when network hash is low
-
Ahh right no worries, thanks for the clarification Major.
-
Last received block was 14 hours ago ? That is what my wallet is saying.
And its not synching either.
I was sending some GLDcoins but so far they are not being received by the other person.
As long as it is stuck like this, I am not really able to send or receive GLDcoins, or I mean, I can send gldcoins but they are not received until the client receives the blocks from 14 hours ago, if I am right.
-
close the wallet and re-open it
-
close the wallet and re-open it
On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.
-
close the wallet and re-open it
On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.
I made some posts about blockchain stuffing in the past few weeks.. Is this is a different problem ?
There are currently 3 different rogue nodes which intermittently try to sync the wrong chain, but this has been going on for weeks.
Is your wallet still functioning as if up to date ?
-
Is this something that cant be hard coded in a new client? Also where is BitcoinFX? didnt he have a lot of ideas in regards to this?
-
close the wallet and re-open it
On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.
I made some posts about blockchain stuffing in the past few weeks.. Is this is a different problem ?
There are currently 3 different rogue nodes which intermittently try to sync the wrong chain, but this has been going on for weeks.
Is your wallet still functioning as if up to date ?
If I close the wallet and reopen, it will sync for a few minutes then it goes back out of sync.
We need to get this fixed before we start bringing more users on board. IMO.
-
Is this something that cant be hard coded in a new client? Also where is BitcoinFX? didnt he have a lot of ideas in regards to this?
Not being a coder, I don't know what can be done. A determined attacker could always match any new client, I would guess: or attacks may may simply be linked to blockchain code itself (ie new client won't help).
-
close the wallet and re-open it
On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.
I made some posts about blockchain stuffing in the past few weeks.. Is this is a different problem ?
There are currently 3 different rogue nodes which intermittently try to sync the wrong chain, but this has been going on for weeks.
Is your wallet still functioning as if up to date ?
If I close the wallet and reopen, it will sync for a few minutes then it goes back out of sync.
We need to get this fixed before we start bringing more users on board. IMO.
What I meant was, you should still be able to send and receive because wallet actually is up to date (the sync. information is fake)
-
The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?
-
Guys, there is nothing wrong with the client...
Basically nodes need to be added to the conf file (trusted nodes), and you need to limit the # of connections, and set a high ban time. I'm sure this was in the original thread, because I swapped nodes for this reason with gldcoin.
This occurs when people who offline mined their own large chain try to sync up with the network...
Add this to your conf - if anyone knows of other TRUSTED nodes (If you leave your client/daemon running 24/7 and can forward/open port 8121 on your firewall)
addnode=72.11.149.185
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=6
-
The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?
Its always temporary... Until you have thousands of peers with only a handful being rogue. When there are only hundreds of peers, and a handful rogue, its likely you will always see this unless you use trusted nodes as above and limit the number of node connections.
-
The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?
Its always temporary... Until you have thousands of peers with only a handful being rogue. When there are only hundreds of peers, and a handful rogue, its likely you will always see this unless you use trusted nodes as above and limit the number of node connections.
Thank you for providing us with this invaluable information. I will implement your suggested changes above now. After testing the client using the settings suggested, I will report back with my results.
-
Okay. That didn't work?
-
did you shut the client and restart?
-
did you shut the client and restart?
Yes. And I have already tried this configuration or at least variations of it without success. At present, I do not know of a single user with a client that is able to maintain a network sync.
-
I can no problem... post your config file. Also, what is the full path/location to your conf file?
-
I can no problem... post your config file. Also, what is the full path/location to your conf file?
Path = /appdata/roaming/GLDcoin
File = gldcoin.conf
gen=0
dns=1
checkpoints=1
listen=0
dnsseed=1
banscore=10
bantime=604800
rescan=1
checkblocks=0
checklevel=6
txindex=1
reindex=1
addnode=72.11.149.185
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=6
-
**addnode=72.11.149.185 DELETE THIS LINE ITS GONE
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Get rid of of all the other lines. Its not needed. Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)
If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)
Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.
Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.
-
**addnode=72.11.149.185 DELETE THIS LINE ITS GONE
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Get rid of of all the other lines. Its not needed. Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)
If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)
Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.
Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.
I appreciate this information. I'll make these changes tomorrow after I am rested. Goodnight and thank you. :)
-
also just to be clear, the path to your conf is %appdata%\roaming\gldcoin\gldcoin.conf and not c:\appdata\roaming\glcoin\glcoin.conf?
let me know tomorrow as I haven't gone out of sync in weeks.
-
I now have only the following lines in gldcoin.conf and it is syncing perfectly:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
-
I suppose the documentation should be updated if this works for many people.
Perhaps this is perfect for client only installs but solo miners will need additional parameters?
-
It is a GREAT FEELING to have the client sync and stay that way. It really is.
Hyoshi, I really appreciate what you are doing along with the other devs.
I wish you folks would post a gldcoin address people could send donations to. I am more than willing to make regular donations.
-
I wonder if the installs can be modified to include the necessary conf parameters as they change over time. That would be cool. Anyhow, not too hard to change a text file and it sure does give me a warm and fuzzy not seeing that progress bar at the bottom stuck in the mud.
-
**addnode=72.11.149.185 DELETE THIS LINE ITS GONE
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Get rid of of all the other lines. Its not needed. Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)
If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)
Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.
Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.
I can confirm that so far this is stopped the client resync issue. I have had this running for about 2 hours and normally in this time the client would have tried to re-sync.
-
Client has started to re-sync again.
-
I have my server acting as a node now also.
220.245.246.139
-
The resync problem stays the same even i tried everything you said. why are the other clients not having this issue even with low hashrate?
-
This was just posted as a comment on my most recent YouTube video:
(http://www.gldtalk.org/img/comment.png)
-
This was just posted as a comment on my most recent YouTube video:
(http://www.gldtalk.org/img/comment.png)
If he's right, you should definently thank the guy.
Is the developer still working on this? Notify him. (doesn't seem to be that active to me).
-
This was just posted as a comment on my most recent YouTube video:
(http://www.gldtalk.org/img/comment.png)
If he's right, you should definently thank the guy.
Is the developer still working on this? Notify him. (doesn't seem to be that active to me).
The current developer says there's no problem with the client (see above).
-
Well I haven't seen those problems lately, and I use an old conf file I think.
Should be definently checked out, what this guy wrote.
-
**addnode=72.11.149.185 DELETE THIS LINE ITS GONE
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Get rid of of all the other lines. Its not needed. Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)
If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)
Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.
Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.
I can confirm that so far this is stopped the client resync issue. I have had this running for about 2 hours and normally in this time the client would have tried to re-sync.
This will stop the resync issue, however it also makes it so your client only talks to the nodes you just put in your configuration file. This means the network is now rather limited and can not grow. It is also no longer really peer to peer and instead depends on a few nodes. With this configuration there is no need for this to be a blockchain based, p2p currency, it could just become a centrally controlled currency instead. This also will make testing the real fix harder and make it so you have to get people fix their configuration files when any of these nodes ever go down. Bad suggestion overall.
-
Client started re-syncing again.. :(
-
What are other coins using in their clients that they dont have this resync problem?
-
I have ONLY the following lines on my client and it is working with no problems:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Having said that, it obviously can't stay this way but with the base being small perhaps it should be this way for now. I believe these are the pool addresses and/or the addresses to the daemon run by the exchanges.
Hyoshi recommended getting at least 12 trusted nodes up and putting those in. Sounds like a good game plan to me to start with.
I can't say for certain though, but just because it WILL be a fully functional p2p system doesn't mean it MUST start that way and if we don't trust the pools or the exchanges as a beginning then what do we have?
It would be nice to have comments beside each addnode line saying who they are.
-
**addnode=72.11.149.185 DELETE THIS LINE ITS GONE
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Get rid of of all the other lines. Its not needed. Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)
If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)
Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.
Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.
I can confirm that so far this is stopped the client resync issue. I have had this running for about 2 hours and normally in this time the client would have tried to re-sync.
This will stop the resync issue, however it also makes it so your client only talks to the nodes you just put in your configuration file. This means the network is now rather limited and can not grow. It is also no longer really peer to peer and instead depends on a few nodes. With this configuration there is no need for this to be a blockchain based, p2p currency, it could just become a centrally controlled currency instead. This also will make testing the real fix harder and make it so you have to get people fix their configuration files when any of these nodes ever go down. Bad suggestion overall.
Only "connect" does this - not "addnode". With addnode, if a node goes down, another available node is used that's not trusted. No one runs the wallet with the firewall open so they have 100 connections - most people only use a max of 6 - 12 connections to peers.
Once could easily change the max connections to say 12, and have a 75% change of getting a misbehaving node.
The fix is a larger network. Its impossible for misbehaving nodes to be eliminated. You do understand that right?
This is why it hasn't been fixed in Bitcoin, Litecoin, Novacoin, and the list goes on. the only fix is no wannabe hax0rs trying to force a false blockchain down the network's throat.
Who are you by the way? which btcointalk troll? Why not use your real name?
-
I have ONLY the following lines on my client and it is working with no problems:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Having said that, it obviously can't stay this way but with the base being small perhaps it should be this way for now. I believe these are the pool addresses and/or the addresses to the daemon run by the exchanges.
Hyoshi recommended getting at least 12 trusted nodes up and putting those in. Sounds like a good game plan to me to start with.
I can't say for certain though, but just because it WILL be a fully functional p2p system doesn't mean it MUST start that way and if we don't trust the pools or the exchanges as a beginning then what do we have?
It would be nice to have comments beside each addnode line saying who they are.
Trust me, its still p2p. the network is way too small to function without trusted nodes.
He claims it can be fixed - but it can't. Trust me, if it could, coblee would have done so in Litecoin - same with BTC - and this is Litecoin - with slight modifications to the reward and difficulty systems.
-
I would also very much like to spread some gld to those that honestly help this grow. I don't need as much gld as I have and my miners keep plugging away making more.
-
Quoting something from our recent talk in our group:"if there is code that is being used by other coins to resolve these issues, why don't we find it and copy it".
Obviously you can't just copy it, but you can modify it and make it work for gld.
We don't know what's causing syncing problems right?
-
According to Hyoshi the problem is:
This occurs when people who offline mined their own large chain try to sync up with the network...
His solution is in the comments above. It is working for me and I think should be posted on the default instructions. He says we should also try to get 12 trusted nodes put up that have the daemon running 24/7 and add those to the gldcoin.conf file.
I agree with him.
-
In other words, the code is solid. It's just where we are at right now with the state of the network and nodes/miners on it.
-
Since adding the following configuration file suggested above, my client has remained in sync continuously for several hours. This will serve as the temporary workaround until we have a better solution.
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
I will update the OP of the main bitcointalk thread now.
-
maybe i am doing something wrong but changing the conf. file as said didnt help for me. After 5 minutes the client started resyncing.
-
Paste your conf file here without any passwords. Also, are you solo mining?
If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta. Paste your version.
Also, what is the full path to your gldcoin.conf file?
Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf Yes, my real name is tadspoles. :P
You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier. Just make sure you have a good backup.
-
Paste your conf file here without any passwords. Also, are you solo mining?
If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta. Paste your version.
Also, what is the full path to your gldcoin.conf file?
Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf Yes, my real name is tadspoles. :P
You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier. Just make sure you have a good backup.
I am not solo mining.
I am running same Client version v0.6.4.0-gd5eb490-beta.
My full path to gldcoin.conf file is C:\Users\NZXT\AppData\Roaming\GLDcoin\gldcoin.conf
Conf. file:
rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
-
If it were me, I'd delete the following:
rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0
leaving only:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Then I'd save the file, shutdown GLDCoin-QT and restart it. See how that goes first. Then we'll go from there. First we'll get it working with just:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
-
Paste your conf file here without any passwords. Also, are you solo mining?
If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta. Paste your version.
Also, what is the full path to your gldcoin.conf file?
Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf Yes, my real name is tadspoles. :P
You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier. Just make sure you have a good backup.
I am not solo mining.
I am running same Client version v0.6.4.0-gd5eb490-beta.
My full path to gldcoin.conf file is C:\Users\NZXT\AppData\Roaming\GLDcoin\gldcoin.conf
Conf. file:
rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Try commenting out everything except this:
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Then close and reopen the client.
-
conf. file now looks like this.
bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4
Deleted Gldcoin totally and removed all files. Installed the client again, placed wallet and conf file back. And testing the client to look if it starts to resync.
-
i think the sync problem for me is solved for now and hope it stays so.
-
Thanks for the verification AZIZ.
Now maybe we can get a good ol' Bitcoin Ranger video with high vibration. Maybe he can go deeper in that zone of positivity and chug down at least a quarter of one of those beers.
-
Thanks for the verification AZIZ.
I need to thank you and others for helping me.
-
Only "connect" does this - not "addnode". With addnode, if a node goes down, another available node is used that's not trusted. No one runs the wallet with the firewall open so they have 100 connections - most people only use a max of 6 - 12 connections to peers.
While Addnode does not restrict the connection directly, if all the nodes are up, and you addnode exactly the same number of nodes as you set maxconnections as all the sample config files I was commenting on did, then it does. You could also get much of the same effect with a better dns seeding routine, and changing the logic to use dns seeds for more then just the bootstrap (this is an example of another way to fix it, not what should be done).
Once could easily change the max connections to say 12, and have a 75% change of getting a misbehaving node.
Except that was not what was being shown.
The fix is a larger network. Its impossible for misbehaving nodes to be eliminated. You do understand that right?
Sure, though the block chain itself should be ok also long as your are not being 51%ed.
This is why it hasn't been fixed in Bitcoin, Litecoin, Novacoin, and the list goes on. the only fix is no wannabe hax0rs trying to force a false blockchain down the network's throat.
That is not what is happening though. I never followed NVC, but the same issue has not been present for BTC and LTC so far. I am wondering if it will hit LTC due in reverse when coins like GLD outgrow it block number wise. I am thinking probably not due to the less difficulty, but one of these days I need to reread that part of the code to see.
Who are you by the way? which btcointalk troll? Why not use your real name?
This does not seem to be a real name forum. Who on here is using their real name? Have not seen many that are.
-
Trust me, its still p2p. the network is way too small to function without trusted nodes.
He claims it can be fixed - but it can't. Trust me, if it could, coblee would have done so in Litecoin - same with BTC - and this is Litecoin - with slight modifications to the reward and difficulty systems.
It can be fixed. It is not a problem in Litecoin. It is a problem with gldcoin, because of exactly what you just said! The problem is that the real fix would be a forking change.
-
Removing everything from your GLDcoin.conf file and leaving only the bantime and addnodes doesnt work if you solo mine, so this isnt a great solution IMO.
Is there another method for solo miners to have their wallets maintain sync?
-
I would think it would work for solo miners if you just put in the rpcuser password and ports stuff. Try it and see what happens. Let us know.
-
I would think it would work for solo miners if you just put in the rpcuser password and ports stuff. Try it and see what happens. Let us know.
Will do this within the next few hours and test. Will report back
-
I'm sure GoldCoin will need more development in the future so I welcome anyone to work with Hyoshi in the private section of this forum on that. I am willing to put up a considerable amount of gld for that and I'm sure others are as well.
Behavior such as attacking a current dev here doesn't seem like something a real dev interested in the success of goldcoin would do and is counterproductive to the very success of this coin. Hence, it appears to me that it is FUD.
This is being addressed currently tadspoles. If we can all refrain from arguing that would be great :) We all want what is best for the coin and as such conversations like this are important however when they get into a slanging match they are not. Please let me be known that things behind the scenes are being done.
-
Thank you sir. I agree. Sorry.
-
Submit code or a formula else FUD.
Still wrong.
Can you read code then? Go take a look at the code. Do a diff against litecoin. Now see what the block data shows when it will not sync. Now read the code where that block count comes from. You will see it. If you can't read the code, then stop calling for it.
When it won't sync, the block count comes from the node/peer with the larger chain. The count is not the same always, but its a handful of nodes. Not sure what your insinuating, but its not the LTC network trying to sync with GLD because he used the same pefix numbers and/or public/private signing keypair. the other networks connect via defined ports, which do not overlap with these.
I can and have easily replicated with with Litecoin itself - forcing my client to connect to my self mined blockchain causes the very same issue.
Again, you come here, talking non-sensical things, but don't reveal your big secret on how to fix it just shows 1) your here just to troll/spy, and have no interest in the coin 2) you have nothing
You are in fact a person from bitcointalk, and I will let you reveal your more commonly used name on that forum (you have several) to the masses. Its obvious because you said the very same thing in the GLD or Nibble threads last month. Pretty much to the letter.
-
Also, please all devs put up a GLDcoin address so I can send you some damn money. :P
-
I've deleted all my posts on this thread that were counterproductive. My evil twin brother gained access to my account and made me look bad. Argghh...I hate that guy! :P
-
I've deleted all my posts on this thread that were counterproductive. My evil twin brother gained access to my account and made me look bad. Argghh...I hate that guy! :P
lol