[ANN][XEL] Elastic Project - The Decentralized Supercomputer

[unvoid]

Ok. I'll try to delete blockchain and try to go to right chain. Blockchain explorer will be dummy for ~15min.

[1713308837]

1713308837

[ImI]

sent some to unvoid

Recived! But why you're not forging?

i think i was. just logged in again and started forging again. everytime i login forging stops for some reason and i have to restart it...

edit:

1887   16.09.2016 22:37:57   0   0   0   You   0 B   0199 %
1886   16.09.2016 22:36:23   0   0   0   You   0 B   0195 %
1885   16.09.2016 22:36:07   0   0   0   You   0 B   0195 %
1884   16.09.2016 22:34:54   0   0   0   You   0 B   0183 %

[unvoid]

Did @EK submitted some work to the network from his Amazon nodes? Maybe he is on a fork as a fault of his submissions that was banned by the rest of the network? And since we are all trying to connect to the @EK peers from config file we are all ending in few forks?

Just some thoughts. @EK?

EDIT: 5 more minutes and I'll try to start my node connected to explorer. (need to wait default 10 minutes in all nodes to blacklist expire)

[unvoid]

Redownload and I ended in some dead chain with height 1506:

Code:

1506 6 hours, 20 minutes, 9 seconds ago

So I think that @EK submitted some work to the network in behalf of his AWS nodes and that nodes was banned by all network and we all ended in a few forks.

@EK, long sleep, pretty woman, good coffe and back to polishing XEL I'm going to bed, goodnight everyone.

[trader19]

i just logged in at XEL-9HQ9-BXCV-TARZ-BRDNA and checked. forging seems OK.

well i think me or you forked, and are forging in own chain. try moving some coins around pls.

I think that you're on the forked chain because I started up my node about hour ago (with testnet peers from config) and my node downloaded blockchain from testnet peers. So we assume that if we downloaded blockchain from @EK testnet peers we are on a right fork. Please try to stop your node, delete blockchain and start it again (since blockchain is young you should download it in two minutes) and see if you are on @EK fork again. If not, I'm on the wrong chain and node which forging right now also.

Give me a result. Thanks.

did like u suggested. now i can see all my forged blocks are gone and ImI blocks appeared, also transaction of 100000 tXEL (sent to you by ImI) was processed by my node is also gone!! hmm strange spooky things happening.  

one interesting error i saw before rebuilding:

Code:

2016-09-16 20:43:39 FINE: Did not accept peer's blocks, back to our own fork

one more error i saw in my logs after rebuilding (again ImI work getting rejected IMO):

Code:

2016-09-16 20:55:37 FINE: Blacklisting 52.57.31.137 because of: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
        at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
        at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
        at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
        at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

EDIT: now i started forging again.. banned all other peers, wooooh, try sending coins around pls.

[unvoid]

Some may say that by far we not created decentralized computer and we currently can't prove that they are wrong. But we can prove that we created awesome banning hammer and they can't abolish that sentence Goodnight everyone!

[coralreefer]

Can someone please send a few test xel to XEL-8DES-WHKN-M6SZ-8JRP5

[Evil-Knievel]

Got it! Coralreefer, please wait! I am fixing things.

EDIT:
git pull and compile, the forking should be fixed and the longest chain should survive!
The reason was dumb and simply my mistake ... sorry! I forgot to attach the prunable source code appendix when broadcasting the TX in a hand full of cases. Of course, the signature did not match as the transaction was not "complete".

Also, forgive me the excessive debug output now! Will remove it soon!

@ImI: The forging-restart issue is scheduled for tomorrow  

[coralreefer]

Thx guys for the test xel.  Got the new version compiled and running w/o issues.

[Evil-Knievel]

Just wanted to take a few minutes and thank you all for your time and your involvement. I really appreciate for your excessive testing. Alone, or with 1 or 2 other people, its nearly impossible to evaluate all possible side cases.

Good to have you all! 

[ImI]

Just wanted to take a few minutes and thank you all for your time and your involvement. I really appreciate for your excessive testing. Alone, or with 1 or 2 other people, its nearly impossible to evaluate all possible side cases.

Good to have you all! 

Good to have you! 

Seriously.

[wpalczynski]

Just wanted to take a few minutes and thank you all for your time and your involvement. I really appreciate for your excessive testing. Alone, or with 1 or 2 other people, its nearly impossible to evaluate all possible side cases.

Good to have you all! 

You seem to be working really hard on the testnet version which is awesome but I have to ask, has Lannister given up on this project?  He seems to be MIA for a while.

[densmirnov]

I have also set up a node! I will be glad if anybody can share some testate xel for testing. My ID is XEL-MSJU-ENL3-GFX6-FFPX3. Thanks a lot in advance!

[EDIT] That was blazingly fast! Thanks a lot!

[coralreefer]

Been a while since I've used a NXT wallet, but i'm having an issue.  I keep getting the error "Could not validate unsigned bytes returned by the server".   This happens if I try to update my account, send xel, or submit work.  Screenshot below:

http://imgur.com/a/q37Hx

My account is XEL-8DES-WHKN-M6SZ-8JRP5.  I am using EK's AWS node to connect my browser.

Also, I am running a node which I can see in the Block Explorer / Peers page, but I don't see on EK's AWS peers page.  I've deleted the db and restarted but it still doesn't show up on EK's node.

[unvoid]

Fixed explorer. Mainly account view as new XEL version isn't supporting getAccountTransactions anymore. Hope now will be fine.

EDIT: http://elasticexplorer.org/ for those that didn't know about explorer.

[josegines]

why still listed my ip here
http://elasticexplorer.org/peers/

if I have closed my server?

is not real time?

[unvoid]

why still listed my ip here
http://elasticexplorer.org/peers/

if I have closed my server?

is not real time?

You're right. It's even showing banned nodes (I think all nodes below < 0.3.2 are banned). I'll fix that in a few minutes.

EDIT: fixed

[josegines]

why still listed my ip here
http://elasticexplorer.org/peers/

if I have closed my server?

is not real time?

You're right. It's even showing banned nodes (I think all nodes below < 0.3.2 are banned). I'll fix that in a few minutes.

EDIT: fixed

Good work! Felititations for your job in XEL

[Evil-Knievel]

Been a while since I've used a NXT wallet, but i'm having an issue.  I keep getting the error "Could not validate unsigned bytes returned by the server".   This happens if I try to update my account, send xel, or submit work.  Screenshot below:

This one is also fixed!

[Evil-Knievel]

There are these two little missing pieces before we can say that the testnet is stable!


1. Netsplits

Imagine that I generate a lot of POW for the current block's target! A different node then generates a block and I, before I get notified about the new block, rebroadcast my pending, unconfirmed POW.
Since the target value changed for the new block (that the other peer is aware of) the unconfirmed transactions that I sent him will be invalid, because they do not meat the new block's target value!
He, and possible others, then ban us and sends us on a fork!

2. Malicious retarget

The POW difficulty retarget scales with every block, and averages a sliding window over the last 3 blocks and how many POW submissions they had.
However, after there was a short period without work, there will be of course 3 consecutive blocks without POW submissions, and as a consequence the target value will be "minimal" again once a work will be created. This will cause bursts of HUGE numbers of POW submissions. We need a solution for that!

I thought maybe we could only average over the last blocks that HAD at least on POW included, but not sure if this is the right way to go.