Bitcoin Forum
December 18, 2017, 06:44:59 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 ... 159 »
  Print  
Author Topic: ⚒[CGA] Cryptographic Anomaly - The Elusive Coin⚒  (Read 224557 times)
tertius993
Hero Member
*****
Online Online

Activity: 669


View Profile
February 09, 2014, 07:27:21 PM
 #861

We just found and banned two more nodes running the old client:
123.150.156.38
134.249.208.95

We're working on a new client in IRC right now that will require everyone to update. For now, you can also add this checkpoint to checkpoint.cpp and recompile:
http://pastebin.com/r1hyMxbJ

And before anyone asks, I'm sorry but I cannot make a guide right now for how to do that.
More info coming soon. If you're a dev and think you can help, join us in #cganomaly on freenode. It's not the place to chat right now, but please join if you think you can contribute programming skill and have knowledge of the client.

If it is helpful helpful I will update the little guide I wrote, as soon as I can after the new client is available.

May I suggest that the new client identifies itself (by version number) both in the help and in the download file itself?  That way it'll be easy for people to know what they are getting and whether to download it.
1513622699
Hero Member
*
Offline Offline

Posts: 1513622699

View Profile Personal Message (Offline)

Ignore
1513622699
Reply with quote  #2

1513622699
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513622699
Hero Member
*
Offline Offline

Posts: 1513622699

View Profile Personal Message (Offline)

Ignore
1513622699
Reply with quote  #2

1513622699
Report to moderator
rfe3
Member
**
Offline Offline

Activity: 66


View Profile
February 09, 2014, 07:30:17 PM
 #862

My second Wallet that I use for monitoring my remote Just forked again at block 12656. I just reloaded this Chain about 1 hour ago.
mycointr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
February 09, 2014, 07:31:47 PM
 #863

this situation is not seem normal.
hardcoded nodes does not have same chain.
my suggestion is forking back to very first mandatory update.

EDIT: omg, i'll loose 8 coin :S
wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 07:36:05 PM
 #864

Well, it looks like I'm having a problem with the Internet connection in my Lab... Angry Can't seem to reconnect with my Remote....Wzttide, can you see if my miner is still running on your Pool? My wallet address is:AT1es8mXUf2uW8LaXLy7nwLMVS5owX2Yor. Thanks...


Edit to Previous Post: I have been using the updated config with built in nodes.

No, your address shows no shares since 30 to 60 min.
tf2honeybadger
Full Member
***
Offline Offline

Activity: 189


View Profile
February 09, 2014, 07:41:27 PM
 #865

this situation is not seem normal.
hardcoded nodes does not have same chain.
my suggestion is forking back to very first mandatory update.

EDIT: omg, i'll loose 8 coin :S

We're testing the new code now. The situation definitely is not 'normal', but we're working on it. s4w3d0ff was in our IRC, but his connection dropped a while ago and he hasn't come back, so his node is offline, but my node is up and on the right chain right now. We're going to be adding AnomalyPool's nodes to the code as seeds in this update, but for now, you can add this node to your client:
node1.cga.anomalypool.com
(node 2 is currently offline, will be back up soon).

Stay tuned....
mycointr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
February 09, 2014, 07:44:47 PM
 #866

this situation is not seem normal.
hardcoded nodes does not have same chain.
my suggestion is forking back to very first mandatory update.

EDIT: omg, i'll loose 8 coin :S

We're testing the new code now. The situation definitely is not 'normal', but we're working on it. s4w3d0ff was in our IRC, but his connection dropped a while ago and he hasn't come back, so his node is offline, but my node is up and on the right chain right now. We're going to be adding AnomalyPool's nodes to the code as seeds in this update, but for now, you can add this node to your client:
node1.cga.anomalypool.com
(node 2 is currently offline, will be back up soon).

Stay tuned....

i'm loosing my 2 coins mined today with anomalypools nodes..
pool takes coins to itself  Roll Eyes
rfe3
Member
**
Offline Offline

Activity: 66


View Profile
February 09, 2014, 07:44:51 PM
 #867

Well, it looks like I'm having a problem with the Internet connection in my Lab... Angry Can't seem to reconnect with my Remote....Wzttide, can you see if my miner is still running on your Pool? My wallet address is:AT1es8mXUf2uW8LaXLy7nwLMVS5owX2Yor. Thanks...


Edit to Previous Post: I have been using the updated config with built in nodes.

No, your address shows no shares since 30 to 60 min.

Ok thanks, BUT...I just reloaded the blockchain again in my Monitoring Wallet (not on the remote Miner) and a whole bunch of coin pieces showed up that were mined over the last Hour...Strange...Maybe it's still mining on a Fork...Unfortunately, I still can't log in to my Remote to see...As of 4 min. ago this Wallet is showing 12699.
mycointr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
February 09, 2014, 07:49:07 PM
 #868

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..
Molitor
Member
**
Offline Offline

Activity: 70



View Profile
February 09, 2014, 07:52:11 PM
 #869

Well, it looks like I'm having a problem with the Internet connection in my Lab... Angry Can't seem to reconnect with my Remote....Wzttide, can you see if my miner is still running on your Pool? My wallet address is:AT1es8mXUf2uW8LaXLy7nwLMVS5owX2Yor. Thanks...


Edit to Previous Post: I have been using the updated config with built in nodes.

No, your address shows no shares since 30 to 60 min.

Ok thanks, BUT...I just reloaded the blockchain again in my Monitoring Wallet (not on the remote Miner) and a whole bunch of coin pieces showed up that were mined over the last Hour...Strange...Maybe it's still mining on a Fork...Unfortunately, I still can't log in to my Remote to see...As of 4 min. ago this Wallet is showing 12699.

Would it be helpful if I uploaded the blockchain? (the zipped /roaming directory). I've been mining consistently in anomalypool since yesterday evening.
wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 07:52:52 PM
 #870

Well, it looks like I'm having a problem with the Internet connection in my Lab... Angry Can't seem to reconnect with my Remote....Wzttide, can you see if my miner is still running on your Pool? My wallet address is:AT1es8mXUf2uW8LaXLy7nwLMVS5owX2Yor. Thanks...


Edit to Previous Post: I have been using the updated config with built in nodes.

No, your address shows no shares since 30 to 60 min.

Ok thanks, BUT...I just reloaded the blockchain again in my Monitoring Wallet (not on the remote Miner) and a whole bunch of coin pieces showed up that were mined over the last Hour...Strange...Maybe it's still mining on a Fork...Unfortunately, I still can't log in to my Remote to see...As of 4 min. ago this Wallet is showing 12699.

This is normal p2pool behaviour, even if you don't mine you have "good shares" left you get payed for. So you'll probably get smaller and smaller payouts and in some time they will go to zero.
tf2honeybadger
Full Member
***
Offline Offline

Activity: 189


View Profile
February 09, 2014, 07:53:47 PM
 #871

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..


This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.


wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 07:54:39 PM
 #872

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..

sawedoff's node is down, we are taking node1.cga.anomalypool.com as main node now.

If you mine on anomalypool.com your mining will count and will be payed out, even if they don't show up in your (forked) wallet!
rfe3
Member
**
Offline Offline

Activity: 66


View Profile
February 09, 2014, 07:55:45 PM
 #873

Well, it looks like I'm having a problem with the Internet connection in my Lab... Angry Can't seem to reconnect with my Remote....Wzttide, can you see if my miner is still running on your Pool? My wallet address is:AT1es8mXUf2uW8LaXLy7nwLMVS5owX2Yor. Thanks...


Edit to Previous Post: I have been using the updated config with built in nodes.

No, your address shows no shares since 30 to 60 min.

Ok thanks, BUT...I just reloaded the blockchain again in my Monitoring Wallet (not on the remote Miner) and a whole bunch of coin pieces showed up that were mined over the last Hour...Strange...Maybe it's still mining on a Fork...Unfortunately, I still can't log in to my Remote to see...As of 4 min. ago this Wallet is showing 12699.

This is normal p2pool behaviour, even if you don't mine you have "good shares" left you get payed for. So you'll probably get smaller and smaller payouts and in some time they will go to zero.


Thanks, I see that now in the payouts...
mycointr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
February 09, 2014, 08:03:57 PM
 #874

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..


This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.




problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..
awesomeperson451
Newbie
*
Offline Offline

Activity: 28


View Profile
February 09, 2014, 08:06:47 PM
 #875

Guys, I just removed all the addnodes from my .conf file and started the v1.1.1.2 binary with just the hardcoded nodes to connect to. Then I let it connect and typed "getpeerinfo" into the debug console.

I think I found the culprit:




getpeerinfo


15:00:18


{
"addr" : "70.176.73.232:13931",
"services" : "00000003",
"lastsend" : 1391975633,
"lastrecv" : 1391975637,
"bytessent" : 1943,
"bytesrecv" : 14644,
"blocksrequested" : 0,
"conntime" : 1391975633,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "64.188.167.211:13931",
"services" : "00000003",
"lastsend" : 1391975661,
"lastrecv" : 1391975663,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975661,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "162.243.225.132:13931",
"services" : "00000003",
"lastsend" : 1391975691,
"lastrecv" : 1391975869,
"bytessent" : 229,
"bytesrecv" : 7226,
"blocksrequested" : 0,
"conntime" : 1391975690,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "50.147.39.37:13931",
"services" : "00000003",
"lastsend" : 1391975697,
"lastrecv" : 1391975704,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975696,
"version" : 70002,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 8211,
"banscore" : 0
}
,
{
"addr" : "68.43.46.243:13931",
"services" : "00000003",
"lastsend" : 1391975949,
"lastrecv" : 1391975974,
"bytessent" : 6515,
"bytesrecv" : 111250,
"blocksrequested" : 0,
"conntime" : 1391975702,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12713,
"banscore" : 0
},
{
"addr" : "78.130.202.203:13931",
"services" : "00000003",
"lastsend" : 1391975975,
"lastrecv" : 1391975975,
"bytessent" : 5395,
"bytesrecv" : 7531,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12714,
"banscore" : 0
},
{
"addr" : "71.105.130.10:13931",
"services" : "00000003",
"lastsend" : 1391975772,
"lastrecv" : 1391975773,
"bytessent" : 229,
"bytesrecv" : 6925,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0
},
{
"addr" : "149.210.168.71:13931",
"services" : "00000003",
"lastsend" : 1391975974,
"lastrecv" : 1391975974,
"bytessent" : 473,
"bytesrecv" : 11981,
"blocksrequested" : 0,
"conntime" : 1391975871,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12716,
"banscore" : 0
}


BTC: 1GamwSZQ91eap3XED8u7XQmDPxbjU7xjoR | CGA: AFnYPruQpNqzi4UEquWPmA4vV2xf6gNGa1
wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 08:07:52 PM
 #876

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..


This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.




problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..


anomalypool's chain is the only one with hashpower, sawedoff's node didn't have any. And is down. So his chain is broken anyway.

We can't build a coin on a node which is down.

@awesomeperson451: We have a list of all "old" nodes, checking your finding against it now, thanks!
wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 08:08:57 PM
 #877

some quick update: we think that 50.147.39.37 is on the right chain.
mycointr
Jr. Member
*
Offline Offline

Activity: 56


View Profile
February 09, 2014, 08:13:19 PM
 #878

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..


This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.




problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..


anomalypool's chain is the only one with hashpower, sawedoff's node didn't have any. And is down. So his chain is broken anyway.

We can't build a coin on a node which is down.

@awesomeperson451: We have a list of all "old" nodes, checking your finding against it now, thanks!

problem is: your pool has 0 latency to your node.
all blocks found by pools-people other than your pool are not accepted by your node i think.
wzttide
Full Member
***
Offline Offline

Activity: 238


View Profile
February 09, 2014, 08:17:06 PM
 #879

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..


This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.




problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..


anomalypool's chain is the only one with hashpower, sawedoff's node didn't have any. And is down. So his chain is broken anyway.

We can't build a coin on a node which is down.

@awesomeperson451: We have a list of all "old" nodes, checking your finding against it now, thanks!

problem is: your pool has 0 latency to your node.
all blocks found by pools-people other than your pool are not accepted by your node i think.

There will be 5 nodes hardcoded.

make a ping to node1.cga.anomalypool.com and then make a ping to anomalypool.com, these are 2 different IP addresses, in fact they are 2 different physical machines.

node1.cga.anomalypool.com will be hardcoded, NOT anomalypool.com
MMos
Full Member
***
Offline Offline

Activity: 140


View Profile
February 09, 2014, 08:20:18 PM
 #880

How come I cannot withdraw from http://cga.poolnetwork.org/....and cga.altcoinpool.org is down as well...
Have I lost all my CGA?!??! =(

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 ... 159 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!