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

[Bgjjj2016]

I remember there were some big BTC donations, 10 BTC, 20+ BTC...... from single wallets. Lucky guys 

[by rallier]

Hello All again,
I created Windows Batch files for easy install & run.

I uploaded to Github For EK :
https://github.com/OrdinaryDude/elastic-core/pull/14/commits/3027ae7642d93b3a4d849bae73322568c75aa14c
https://github.com/OrdinaryDude/elastic-pl/pull/1

@EK can you accept to pull requests both of elastic-pr&elastic-core?

I will update to How to setup XEL on Windows with these files.


edit: for blockchain download halted
@EK & @devking

Got the wireshark traces ... checking now!

EDIT: It does not really make sense, but in the traces you can see many connection errors (triple duplicate acks, etc.) ... even to your local router. Do you have connection issues in general?
Maybe another wireshark trace from someone else with sync issues might help here?

It's my VM, it doesn't have any connection issues. @devking accessed to my node on my Public IP and I did to for his node. I didn't figure out why its not working. I bored. I don't waste anytime, i will create new one node on AWS

[Alondre]

I remember there were some big BTC donations, 10 BTC, 20+ BTC...... from single wallets. Lucky guys 

Big xel whales 

[klintay]

I remember there were some big BTC donations, 10 BTC, 20+ BTC...... from single wallets. Lucky guys 

Big xel whales 

XEL whales show yourselves!!! 

[unvoid]

@EK

https://talk.elasticexplorer.org/t/block-height-1703/85

[Evil-Knievel]

@EK

https://talk.elasticexplorer.org/t/block-height-1703/85

Testnet 1.0.5 ist live!

To freshly checkout, do a:

Code:

git clone https://github.com/OrdinaryDude/elastic-core.git
cd elastic-core
mvn clean compile package

OR To update, do a:

Code:

git stash
git pull
rm -rf elastic_test_db
mvn clean compile package

It might be required to clean the browser cache to have the UI (redeem function) fixed.

THEN: To run, do a:

Code:

mvn exec:java

Changelog:

The block 1703 error is not fixed ... if someone still has the old elastic_test_db, please upload it somewhere. Otherwise we will have to wait for the bug again.
Otherwise:
- New Supernode Task collector, is capable of scheduling work to a real computation backend
- Fixed redeem function in UI
- Supernode announcements are throttled, no supernode can flood the blockchain anymore with "refresh" messages

Faucet:

Filled!

[by rallier]

@EK: We can block time reduced to 30 sec for testing purposes. we never see what happens on 30k blocks
btw, pls import my last changes to repos

[lavayeya]

@EK  Here is the db for the 1703 bug

https://drive.google.com/file/d/0B2f252OTSI1vUmpBMllzN1MtZUU/view?usp=sharing

[by rallier]

@EK can you accept pull request for Elastic-PL (easy install from batch file for windows user)
https://github.com/OrdinaryDude/elastic-pl/pull/1/commits/0678fbc86057a3f13bdea18f977f3679efd32906

[Evil-Knievel]

@EK  Here is the db for the 1703 bug

https://drive.google.com/file/d/0B2f252OTSI1vUmpBMllzN1MtZUU/view?usp=sharing

Thanks! We would need the DB also from someone who had no problem and got past block 1703 or at least a live 1.0.4 peer address.

[devking]

@EK,

Testnet 1.0.4 db without 1703 bug

https://drive.google.com/open?id=0B7mbtbFPzQx5ZFM4NXFYOTh2WFE

[hagie]

After sime time I'll try to keep the public wallet up to date again. Sorry for the lack of updates in the last weeks.

https://elastic.cryptnodes.site/index.html#

feel free to play around.

Is there a filled faucet for 1.0.5 ? or someone could send some testtnet funds to :  XEL-XFMU-85XU-V4S3-EZZY2
What is the procedure to setup a supernode - is it just to enter the passphrase into the config ?

Thanks

[devking]

@EK,

I have updated my node with from 1.0.4, latest version 1.0.5, well known test peers returning errors.  My peer blacklisted. Can you please unblock.

azonaws.com

Getting errors

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.28.123.208 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.57.31.137 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

[jioy]

@EK: We can block time reduced to 30 sec for testing purposes. we never see what happens on 30k blocks
btw, pls import my last changes to repos

reduce block time for test is a good advice

[Evil-Knievel]

@EK,

I have updated my node with from 1.0.4, latest version 1.0.5, well known test peers returning errors.  My peer blacklisted. Can you please unblock.

azonaws.com

Getting errors

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.28.123.208 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.57.31.137 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

Are you sure?
It might be possible that you didn't upgrade because the "git pull" failed due to some conflict. Have you made a "git stash" before?

[tomkat]

Please add system restart at some point after setting up all variables and before running compilations
https://talk.elasticexplorer.org/t/how-to-setup-elastic-core-xel-online-wallet-on-windows-platform/70
Otherwise it will end up with error

[by rallier]

Please add system restart at some point after setting up all variables and before running compilations
https://talk.elasticexplorer.org/t/how-to-setup-elastic-core-xel-online-wallet-on-windows-platform/70
Otherwise it will end up with error

I added new step ty for feedback

[unvoid]

@EK,

I have updated my node with from 1.0.4, latest version 1.0.5, well known test peers returning errors.  My peer blacklisted. Can you please unblock.

azonaws.com

Getting errors

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.28.123.208 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.57.31.137 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

Are you sure?
It might be possible that you didn't upgrade because the "git pull" failed due to some conflict. Have you made a "git stash" before?

I had same error yesterday. In my case I was banned with info that I have version 1.0.3 (of course after git pull and compile). I didn't want to play with it so I deleted all source and cloned fresh from github. Worked like a charm. Just be sure you backup your nxt.properties before that.

[ghoom2]

Stopped on Block 1068

Elastic 1.0.5

[unvoid]

Stopped on Block 1068

Elastic 1.0.5

Same here. Second node wont even connect to the peers but I think it's more like this node fault or hard ban.

https://talk.elasticexplorer.org/t/1-0-5-stuck-at-block-1068/92