100% dead? because I can buy today on Nova for 0.00000001 sat
Nova looks like it has GILL
This thread is about GIL, a coin that died 3+ years ago.
Topic: [ANN] GIL, fun and fast. Now accepted at Coingas!! Difficulty Fix! Upgrade ASAP! (Read 33634 times)
May 30, 2017, 06:29:12 AM
Nova looks like it has GILL
This thread is about GIL, a coin that died 3+ years ago.
May 29, 2017, 09:04:23 AM
100% dead? because I can buy today on Nova for 0.00000001 sat
February 11, 2014, 08:33:25 AM
Any differences from the vast array of existing alt-coins?
This one is dead an buried
)). January 30, 2014, 08:41:51 AM
I think GIL may have run into the negative retarget block issue too. This is where a block is generated with a timestamp lower than the previous one (ie going back in time), which causes the difficulty retargeting algorithm to fail.
If this is the case (I haven't checked the code) mining will not be possible, and nodes may be banning peers if they receive a block they don't think is right. For example:
The retarget issue can only be fixed with a client update (hard fork)
I can't easily see what has happened to recent blocks because both my nodes refuse to sync past the very first 3 blocks...
BTW, anyone note that "RETARGET" was changed to "RETGILET" in the above debug output? Indiscriminate search & replace ARG->GIL in the source.
If this is the case (I haven't checked the code) mining will not be possible, and nodes may be banning peers if they receive a block they don't think is right. For example:
ProcessBlock: ACCEPTED
received block c917ebe57e73f3b2db34
nActualTimespan = 106327 before bounds
GetNextWorkRequired RETGILET
nTargetTimespan = 160 nActualTimespan = 640
Before: 1e0ffff0 00000ffff0000000000000000000000000000000000000000000000000000000
After: 1e0fffff 00000fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 192.241.136.248:64574
The retarget issue can only be fixed with a client update (hard fork)
I can't easily see what has happened to recent blocks because both my nodes refuse to sync past the very first 3 blocks...
BTW, anyone note that "RETARGET" was changed to "RETGILET" in the above debug output? Indiscriminate search & replace ARG->GIL in the source.
January 29, 2014, 05:09:56 PM
We need a new client version
January 29, 2014, 04:39:05 PM
lol GIL
January 29, 2014, 04:35:16 PM
Ok, so as the client somehow went cactus, basically all existent coins in GIL are frozen, this goes as well for GIL balances on Cryptsy,
I myself still have a rather big frozen amount of them on there, is there anything we can do about this at this point. -.-
Do we know what exactly went wrong with the client, why it isn't syncing right now?
Maybe new Nodes would fix the problem?
I myself still have a rather big frozen amount of them on there, is there anything we can do about this at this point. -.-
Do we know what exactly went wrong with the client, why it isn't syncing right now?
Maybe new Nodes would fix the problem?
October 25, 2013, 09:19:54 PM
You know this how?
~BCX~
Eli0t was trying to sync with 203.45.89.214,
the only node every mentioned by Hydroponica is 207.12.89.80.
October 20, 2013, 12:31:06 PM
Would you expect less from Hydroponica?
~BCX~
October 20, 2013, 12:27:02 PM
managed to sync with this node BUT BE WARNED if you try and mine on it, it will steal your blocks by blocking your ip, it then checks every 2mins to see if your online until you quit. it will then work again after 5-10mins orphaning your confirmed blocks.
203.45.89.214
203.45.89.214
October 18, 2013, 01:04:37 PM
shame the coin was saved from delisting only to be jumped on by bad nodes and people left unable to sync
It was actually killed by a poor fork and bad development.
October 17, 2013, 01:47:07 PM
shame the coin was saved from delisting only to be jumped on by bad nodes and people left unable to sync
October 17, 2013, 05:27:14 AM
I deposit GIL to cryptsy , and that transaction is confirmed ( complete ) .
But my account of cryptsy did not credit it .
But my account of cryptsy did not credit it .
October 16, 2013, 12:31:16 AM
any active peers? I have 0 connections
October 13, 2013, 04:21:07 PM
As some of You noticed pool gil.netcoin.pl has been down for some time. I had server problems and now I just can't sync. i will not continure this service.
If You have some coins left on my pool please PM with username, password and gil coin address.
If You have some coins left on my pool please PM with username, password and gil coin address.
October 09, 2013, 10:13:40 PM
October 09, 2013, 07:59:10 PM
yep cant sync either
October 09, 2013, 03:07:47 PM
Hmm , from today Gil client become not sync . ( Out of sync )
There is 9 active connection .
But client not connected to the node 207.12.89.80 .
And one more .
I think GIL client is using the port 64575 for P2P .
But first post in this thread is saying 64574 is testnet port .
There is 9 active connection .
But client not connected to the node 207.12.89.80 .
And one more .
I think GIL client is using the port 64575 for P2P .
But first post in this thread is saying 64574 is testnet port .
October 02, 2013, 12:04:37 PM
where to put gil.conf under linux?
September 30, 2013, 10:13:44 PM
Any functioning pools for this coin. The ones I have tried aren't working.
Jump to: