Bitcoin Forum
May 12, 2024, 06:47:06 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 [321] 322 323 324 325 »
  Print  
Author Topic: [ANN][ENRG]Energycoin - Android Released - Bittrex -  (Read 334544 times)
Harcon
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
March 29, 2015, 12:43:20 PM
 #6401

Next Block: d74b1e8f3d79a68621fb26dd2825d09e19d87caf1d37cdb95f335c09aded212e
a65c806d7e3e49308f3a40cd018a77840259d855388f8b12a14f0c7605187779
02ae652cf94bcc70ab362fd93d054f01dd77b99a6c3775c41fe256961a0a508f
d84ce9e56a57cc99aaec3d6f9a100301c1aa59055ebee2349bbc299f0d01c524
6cc30174f5740641adea1a9daa484c7fa38a40f6971335fe20c03b842c0ad110
ec8ef619483c1c49d79a419fc035a47636b5819f4d02a71394a405ee8e039e4d
dbec3f6f1305c9d11a54505eb5f7401805385aae1386e701d0d0ff7f5e846143
Height: 1051199

From what I see on other blocks, this is not right. All the other blocks I look at, there is only one line in the Next Block. This one has 7 lines.

Energy: eKVg45HYAJub6A363RqamsGJC33eeqAgyb
Nubits:  BGizWdeqr3UEcfficsFnwY9DZu2kLBNVVS
Bitcoin: 1KZcY8hLv1F2Rpgo3QYSpYwd3hhXCwZzBN
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 29, 2015, 01:13:22 PM
Last edit: March 29, 2015, 01:38:22 PM by crypto4jan
 #6402

It looks everythink is running smooth now.
edit: this is a wallet with a new downloaded blockchain!

edit: only the block explorer is not up-to-date: http://explorer.energycoin.pw/chain/EnergyCoin

edit2:
Try to send 100 ENRG to bittrex


If that 100 ENRG is arived I post again.
My home wallet is not sinqing yet.
Try another node-set.

edit3: the nodes from the running wallet:
178.62.243.146
5.250.177.28
212.47.228.217
66.131.233.101
213.46.197.237
Code:
15:28:35

getpeerinfo


15:28:35

[
{
"addr" : "178.62.243.146:22706",
"services" : "00000001",
"lastsend" : 1427635609,
"lastrecv" : 1427635038,
"conntime" : 1427608790,
"version" : 70002,
"subver" : "/EnergyCoin:1.1.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1051199,
"banscore" : 0
},
{
"addr" : "5.250.177.28:22706",
"services" : "00000001",
"lastsend" : 1427635041,
"lastrecv" : 1427635296,
"conntime" : 1427608791,
"version" : 70002,
"subver" : "/EnergyCoin:1.1.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1051199,
"banscore" : 0
},
{
"addr" : "212.47.228.217:22706",
"services" : "00000001",
"lastsend" : 1427635041,
"lastrecv" : 1427635039,
"conntime" : 1427608791,
"version" : 70002,
"subver" : "/EnergyCoin:1.1.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1051199,
"banscore" : 0
},
{
"addr" : "66.131.233.101:22706",
"services" : "00000001",
"lastsend" : 1427634040,
"lastrecv" : 1427635040,
"conntime" : 1427608802,
"version" : 70002,
"subver" : "/EnergyCoin:1.1.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1051199,
"banscore" : 0
},
{
"addr" : "213.46.197.237:22706",
"services" : "00000001",
"lastsend" : 1427635534,
"lastrecv" : 1427635608,
"conntime" : 1427629916,
"version" : 70002,
"subver" : "/EnergyCoin:1.1.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 1034140,
"banscore" : 0
}
]
Maybe I'm on the wrong fork?
The wallet is running on a fresh downloaded blockchain.
The funds are not visble on Bittrex I sended!
Can this be the nodes that caused the problem?

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 29, 2015, 01:40:35 PM
Last edit: March 29, 2015, 04:24:17 PM by crypto4jan
 #6403


We should try to understand the issue, and have more running nodes Wink
Can you try this nodes?
178.62.243.146
5.250.177.28
212.47.228.217
66.131.233.101
213.46.197.237
See my edited post.

edit: With thede nodes no connection on my other pc.
Now renamed the peers.dat file and restart.
See what happend.
btw I backuped the original block chain on my PC.

Edit2;


I'm pretty sure I'm on a fork.

I have an hypothesis:
Is it posible that there is a person or group trying to attack EnergyCoin and created an fork before the original block chain was stuck?
Then they connected their wallets to our network? Maybe a lot of coins involved with a lot of weight and that coused the original block chain stuck?
It is strange that I can't pick up the network on another location and a lot of old transactions in my present wallet are now orthans and very much new POS-transactions and just a few days ago I moved the coins in this wallet.
Can someone investigate the block chain I have localy and compare it with the original one to check if what I asume is correct?
I keep this wallet online but maybe it is the chain of the posibe attackers.


edit3:
This is the wallet stuck on block 1034140

I used a backup energycoin folder for 2 month ago, and now for hours with 10 connections no extra blockes downlaoded.
The totaly clean download had no problem with block 1034140

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
Harcon
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
March 29, 2015, 04:55:37 PM
 #6404

Is there a download for where we can get your local copy of the chain? Im not sure how we could compare blockchain info if we cant see what you have. I might be missing something or misinterpreting what you want though so Im sorry if I misunderstand.

 I had a look at bitrex to see if they have the wallet online or if they listed it as a problem. Indeed, the wallet is listed as "blocked" ( no activity for 60 mins or more ). I thought to check this just in case the coin was hijacked somehow and still being traded on a fork.  

 Correct me if Im wrong,but this coin has hardcoded nodes dose it not? In other words nodes that are coded into the client for clients to use to Sync..I know that you can add nodes, but if you have hard coded nodes and something happens to them, what would be the result?  could something like this happen if those nodes where compromised in some way?

Energy: eKVg45HYAJub6A363RqamsGJC33eeqAgyb
Nubits:  BGizWdeqr3UEcfficsFnwY9DZu2kLBNVVS
Bitcoin: 1KZcY8hLv1F2Rpgo3QYSpYwd3hhXCwZzBN
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 29, 2015, 05:30:40 PM
 #6405

Is there a download for where we can get your local copy of the chain? Im not sure how we could compare blockchain info if we cant see what you have. I might be missing something or misinterpreting what you want though so Im sorry if I misunderstand.

 I had a look at bitrex to see if they have the wallet online or if they listed it as a problem. Indeed, the wallet is listed as "blocked" ( no activity for 60 mins or more ). I thought to check this just in case the coin was hijacked somehow and still being traded on a fork.  

 Correct me if Im wrong,but this coin has hardcoded nodes dose it not? In other words nodes that are coded into the client for clients to use to Sync..I know that you can add nodes, but if you have hard coded nodes and something happens to them, what would be the result?  could something like this happen if those nodes where compromised in some way?
Hi Haron,

I send you and sardokan the downloadlink.
The wallet is now out of sinq, so fork stopt?


e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
Harcon
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
March 29, 2015, 07:16:55 PM
 #6406

Is there a download for where we can get your local copy of the chain? Im not sure how we could compare blockchain info if we cant see what you have. I might be missing something or misinterpreting what you want though so Im sorry if I misunderstand.

 I had a look at bitrex to see if they have the wallet online or if they listed it as a problem. Indeed, the wallet is listed as "blocked" ( no activity for 60 mins or more ). I thought to check this just in case the coin was hijacked somehow and still being traded on a fork.  

 Correct me if Im wrong,but this coin has hardcoded nodes dose it not? In other words nodes that are coded into the client for clients to use to Sync..I know that you can add nodes, but if you have hard coded nodes and something happens to them, what would be the result?  could something like this happen if those nodes where compromised in some way?
Hi Haron,

I send you and sardokan the downloadlink.
The wallet is now out of sinq, so fork stopt?

Yes, if you want, you can link me your copy of the chain and Ill take a look and compare what I have.I had one wallet up and it is still stuck I have my other one restored from a backup of the chain that I made on Feb 18th of 2015. That is currently re syncing but I do not think that is likely to change things. It was important enough for me to try to do it though, just to see.

 At this point, I agree that we need to find a way to a known good snapshot of the chain and fork, but I can make the suggestion and understand the concept better then I understand HOW to make that happen.

 I should point out that I am dedicated to no only finding a solution but sticking with this coin. Even more so if we where just attacked because I will not let a cyber punk win easy. That would just burn me up if I let someone turn me off from something because they felt like coming in and wrecking it.



Energy: eKVg45HYAJub6A363RqamsGJC33eeqAgyb
Nubits:  BGizWdeqr3UEcfficsFnwY9DZu2kLBNVVS
Bitcoin: 1KZcY8hLv1F2Rpgo3QYSpYwd3hhXCwZzBN
liie888coins
Full Member
***
Offline Offline

Activity: 217
Merit: 100

Part-time Altcoin Developer


View Profile
March 29, 2015, 07:56:30 PM
 #6407

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?
Harcon
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
March 29, 2015, 08:27:35 PM
 #6408

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?

 Agreed Thank you sir.

Energy: eKVg45HYAJub6A363RqamsGJC33eeqAgyb
Nubits:  BGizWdeqr3UEcfficsFnwY9DZu2kLBNVVS
Bitcoin: 1KZcY8hLv1F2Rpgo3QYSpYwd3hhXCwZzBN
waecrum
Member
**
Offline Offline

Activity: 97
Merit: 10

Altcom : AZwV4Zh2MdYhvyni4QbR5c2CfsAWkcCXAC


View Profile
March 29, 2015, 08:39:12 PM
 #6409

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?

 Agreed Thank you sir.
Agreed. do i need to stop my Raspberry which are stuck at block 1051199?

crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 29, 2015, 08:55:49 PM
Last edit: March 29, 2015, 09:17:51 PM by crypto4jan
 #6410

Hi all,
Ok what I have to do?
I have two block chains.
I can think I have to use the first one and check first where I am.
How to check!
I put online the 21m wallet and wait then?

I can do this tomorrow in the morning.
Now here 22:55

The attack topic: https://bitcointalk.org/index.php?topic=897493.0

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 30, 2015, 04:13:26 AM
Last edit: March 30, 2015, 07:37:57 AM by crypto4jan
 #6411

Ok, I double post

I have bootstraped blockchain sent by Jan, installed it on my Mac to have speed  Grin

Trying to synch, it moves a little bit, but is very slow

Installed and launched Wireshark and seen bunch of this

Internet Protocol Version 4, Src: 213.46.197.237 (213.46.197.237), Dst: 192.168.0.34 (192.168.0.34)
Transmission Control Protocol, Src Port: 22706 (22706), Dst Port: 52813 (52813), Seq: 378568, Ack: 23167, Len: 0

So I send and receive some SYN from this IP, and receive a lot of Ack(nowledgment)

For me look like a DOS attack, I can be wrong.
It's coming from NL, maybe Jan's wallet have bugged or have been corrupted?

This attack if it is one (and nto a simple bug) could also have left an attacker room to forge is chain with little number of coins

I need to go to sleep, big day tomorow but if you could give a look at this, it would be nice  Wink
Thx all for the hard work.
(I was a bad night, thinkig what to do)

The block chain I uploaded is not the correct one!
Before I went to sleep I had deleted again all the block chain files and started again the wallet so my location is downloading again the block chain. Maybe the trafic you mesure is my download.

What block chain do we have:
- there is an Boodstrap file I used before
- I have my original Block Chain I shall ZIP and upload
- I have the Block Chain @home (in case the other one is infected)

I wait for puting online my 21M wallet, I know a have staked 26 th of March and build waight is mayby better.
Can somone post the protocol for restart?

What about the blockexprorer? that says last block 1052000?

The command getblock gives error:
Code:
getblock 1051199


06:08:51

Block not found (code -5)

Olso this message with olther blocks.
But the help window says 1051199 las block.

Have to go.

Edit1:
My wallet block chain info:


I have send a ZIP with all the block chain ifo to Sardokan and liie888coins.
I somwone else want the downloadlink just PM me.
I provide it only to people I trust.

I just exit the wallet and now only my PI is running but I can close that one later.

Edit2:
I see now on Bittrex:

I hope we can fix this quick!

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
liie888coins
Full Member
***
Offline Offline

Activity: 217
Merit: 100

Part-time Altcoin Developer


View Profile
March 30, 2015, 08:25:19 AM
 #6412

Ok, I double post

I have bootstraped blockchain sent by Jan, installed it on my Mac to have speed  Grin

Trying to synch, it moves a little bit, but is very slow

Installed and launched Wireshark and seen bunch of this

Internet Protocol Version 4, Src: 213.46.197.237 (213.46.197.237), Dst: 192.168.0.34 (192.168.0.34)
Transmission Control Protocol, Src Port: 22706 (22706), Dst Port: 52813 (52813), Seq: 378568, Ack: 23167, Len: 0

So I send and receive some SYN from this IP, and receive a lot of Ack(nowledgment)

For me look like a DOS attack, I can be wrong.
It's coming from NL, maybe Jan's wallet have bugged or have been corrupted?

This attack if it is one (and nto a simple bug) could also have left an attacker room to forge is chain with little number of coins

I need to go to sleep, big day tomorow but if you could give a look at this, it would be nice  Wink

Thx all for the hard work.
(I was a bad night, thinkig what to do)

The block chain I uploaded is not the correct one!
Before I went to sleep I had deleted again all the block chain files and started again the wallet so my location is downloading again the block chain. Maybe the trafic you mesure is my download.

What block chain do we have:
- there is an Boodstrap file I used before
- I have my original Block Chain I shall ZIP and upload
- I have the Block Chain @home (in case the other one is infected)

I wait for puting online my 21M wallet, I know a have staked 26 th of March and build waight is mayby better.
Can somone post the protocol for restart?

What about the blockexprorer? that says last block 1052000?

The command getblock gives error:
Code:
getblock 1051199


06:08:51

Block not found (code -5)

Olso this message with olther blocks.
But the help window says 1051199 las block.

Have to go.

Edit1:
My wallet block chain info:


I have send a ZIP with all the block chain ifo to Sardokan and liie888coins.
I somwone else want the downloadlink just PM me.
I provide it only to people I trust.

I just exit the wallet and now only my PI is running but I can close that one later.

Edit2:
I see now on Bittrex:

I hope we can fix this quick!



Type getblockhash 1051199 in the console. It should return you 0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e

Then to check if it fully conforms to the blockchain explorer, type:

getblock 0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e

The blockchain explorer has last block 1052000 coz it is connecting to other peers which are on forks.

Check PM.
liie888coins
Full Member
***
Offline Offline

Activity: 217
Merit: 100

Part-time Altcoin Developer


View Profile
March 30, 2015, 08:29:12 AM
 #6413

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?

 Agreed Thank you sir.

Agreed. do i need to stop my Raspberry which are stuck at block 1051199?



Check if your block hash for 1051199 matches with the blockchain explorer or not first (just to play safe).

If it does match, just keep your Raspberry running unless Jan asks you to stop.

If it doesn’t match or it already syncs beyond 1051200, stop your Raspberry immediately.


P.S.: Everyone please check block hash now. Don’t just check block height. Block heights are meaningless under the current fork situation. For example we already have at least 7 different block hashes for the same block height 1051200.
Jamil.Kamil
Full Member
***
Offline Offline

Activity: 154
Merit: 100


View Profile
March 30, 2015, 08:32:08 AM
 #6414

Looking such an Energycoin...have get this wallet..... Wink Smiley Wink

liie888coins
Full Member
***
Offline Offline

Activity: 217
Merit: 100

Part-time Altcoin Developer


View Profile
March 30, 2015, 08:50:16 AM
 #6415

I'm not sure

I think it.s possible that a DDOS cause a synch issue and as we use slow raspberry, have little number of nodes, and have fast block generation, the pi is not fast enough to agree on the biggest proof chain. (But I don't clearly understand how is the most difficult chain weighted in POS (think it have to do with coinage, but it's not clear for me) so maybe, what I say is crap.

I understand way much better POW than POS.

in any case, our wallet should go for the most "difficult chain" and it seem not to be happening. Is it a bug in the wallet? Or performance issue with pi?

Because even if we were attacked for a double spend, the network should reach agreement, and it's not the case, so I think we have a bug.

We have so little nodes running that it should be easy to ddos them and cause a synch issue.

If a DDOS is the root cause, forging a new chain won't solve our issue.

But I agree that Jan have enough trust and coins to forge a private chain, I just don't know how to do this, and if this will solve the issue.

If it can help, I have light speed connection and a firewall with some basic DDOS protection somewhere in my basement.


Also, I find strange that I have plugged again my hold PI, and he don't synch anymore, he is stuck 20 days in the past, don't download blocks, and still see last block of the chain as the one where you are stuck 1051199



Very nice and thanks for your analysis.  Smiley

Now Jan has sent you his updated blockchain file. Please continue your analysis with the updated file. At least we'd like to know if there was really any DDOS (if any) on/before block height 1051199. At my end I don’t see any other fork up to block height 1051199.

Would appreciate if you or anyone else can come up with a better solution under the current situation. If the community agrees with that solution we can all go for it.
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 31, 2015, 03:43:38 AM
 #6416

We work on the solution.
No panic.

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
March 31, 2015, 12:17:22 PM
 #6417

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?

 Agreed Thank you sir.

Agreed. do i need to stop my Raspberry which are stuck at block 1051199?



Check if your block hash for 1051199 matches with the blockchain explorer or not first (just to play safe).

If it does match, just keep your Raspberry running unless Jan asks you to stop.

If it doesn’t match or it already syncs beyond 1051200, stop your Raspberry immediately.


P.S.: Everyone please check block hash now. Don’t just check block height. Block heights are meaningless under the current fork situation. For example we already have at least 7 different block hashes for the same block height 1051200.

Block hash:
Code:
getblockhash 1051199 

0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e

Confirm it is the same block as in the blockexplorer.

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
waecrum
Member
**
Offline Offline

Activity: 97
Merit: 10

Altcom : AZwV4Zh2MdYhvyni4QbR5c2CfsAWkcCXAC


View Profile
March 31, 2015, 12:49:55 PM
 #6418

Ok, we are on forks now.

I finally sync to block height 1051199. The block info matches with the blockchain explorer:

{
"hash" : "0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e",
"confirmations" : 1,
"size" : 456,
"height" : 1051199,
"version" : 4,
"merkleroot" : "7c9654256dfcf5df770792291d4c046ec7437259afdb10c947d15ac481027646",
"mint" : 0.44082100,
"time" : 1427468644,
"nonce" : 0,
"bits" : "1d2061fc",
"difficulty" : 0.03088017,
"previousblockhash" : "3ff511bee5c904af9efe85dc468c1bbd93034714f0afd8316af684e913ccf777",
"flags" : "proof-of-stake",
"proofhash" : "00003097b04a19889b8b7f8b877182c7377a060cac47d191abb27e66f4af4e1f",
"entropybit" : 0,
"modifier" : "08c3f63cea5ac37a",
"modifierchecksum" : "f81eee14",
"tx" : [
"81bb88e2761b7c29e4e8d9d25dedafe6ac422f3468e203de0f5dc46426c7695a",
"2285803fc773fb19a9203b81d25d436d2c29bca040c000c19d85941931d3b401"
],
"signature" : "3046022100a43a1a1cd87875c991e6dcaa11bae24ecdd5ae6a20db4902645753e31f217b3c02210 0e9d3e58f1c910ea03378b93830fd3f689e674dad36e4bc50409b18aaa0f60c67"
}


And according to the blockchain explorer, we have at least 7 forks at block height 1051200. Each one has different block hash and different time stamp.

That is why my wallet cannot go further beyond block height 1051199. Bittrex’s wallet should have the same issue.

https://bittrex.com/Status


Since someone raised a concern about potential attack, I’d suggest to have Jan sync to block height 1051199 first (if he has not done so) and have him to mine 1051200 onwards until he feels comfortable he should be the largest chain. This will kill all other forks currently mining from 1051200 along with attacks (if any) on these forks. And more importantly, all funds on Bittrex will be safe. We need to protect investors currently buying this coin too.

Why Jan? Just because everyone here trusts him and I suppose there is no motivation for him to attack the network. Smiley

Everyone agrees with it?

 Agreed Thank you sir.

Agreed. do i need to stop my Raspberry which are stuck at block 1051199?



Check if your block hash for 1051199 matches with the blockchain explorer or not first (just to play safe).

If it does match, just keep your Raspberry running unless Jan asks you to stop.

If it doesn’t match or it already syncs beyond 1051200, stop your Raspberry immediately.


P.S.: Everyone please check block hash now. Don’t just check block height. Block heights are meaningless under the current fork situation. For example we already have at least 7 different block hashes for the same block height 1051200.

Block hash:
Code:
getblockhash 1051199 

0875fb57859d36ce5b9d9744f843b96d1e7af91f2e5d39fc5f77dac26e10980e

Confirm it is the same block as in the blockexplorer.


Same block here.

Harcon
Full Member
***
Offline Offline

Activity: 132
Merit: 100


View Profile
March 31, 2015, 02:08:33 PM
 #6419

I have same block as has been listed here.

Energy: eKVg45HYAJub6A363RqamsGJC33eeqAgyb
Nubits:  BGizWdeqr3UEcfficsFnwY9DZu2kLBNVVS
Bitcoin: 1KZcY8hLv1F2Rpgo3QYSpYwd3hhXCwZzBN
crypto4jan
Legendary
*
Offline Offline

Activity: 2451
Merit: 1025


Energy coin master


View Profile WWW
April 01, 2015, 09:03:02 AM
Last edit: April 01, 2015, 09:14:31 AM by crypto4jan
 #6420

Hi community,

I officially announce I take over the development of EnergyCoin.
Have send several messages to EnergyCR and now I changed the password of EnergyCoin.pw
Behind the scenes I work on fork the block chain but it takes me some time to find out how that works.
Check all of you are on the right block:


This Friday I have a meeting for application of EnergyCoin and if that works out positive it can give development a boost.
Trading on Bittrex is still possible and I appreciate if people trade and put some extra buy orders.
Most of my ENRG is off the market and stays of he market!

If there is some development I inform you.

e2wwnbU8XBcnZxSfMTwZLS7Ru6LdWHunCu
00000a5ac2dc57cfb0b92bc8be7731fe6a94a8c1c49a0d2f32e9e2da4f7d2308
Pages: « 1 ... 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 [321] 322 323 324 325 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!