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

[wizzardTim]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

Thanks for the update!

[unvoid]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

Great @EK! 1.4.5 indeed is quite old. When you will be trying to merge with 1.9.2 please also look at differences in .js files.

When you launched testnet did you changed genesis block ID in .js? Some guys have this problem with signature so I thought it might be related to fact that in js we have still old genesis block ID.

Still it's strange that some nodes are fine other not.

Yesterday I wrote a bitmessage to @Lannister from my local bitmessage client but all day long there was info that message can't be sent because client can't request for @Lannister encryption key. So I copied it to bitmsg.me so it can stay there untill @Lannister start his client.

Sent it to this address (hope it's correct): BM-2cXXoFkRtXKvV4oiJcJjBXyYBiqo8Eibmc

Happy coding

[unvoid]

@EK why not 1.10.1?

From the changelog I see some security improvements they added:

This release adds transaction replay protection, to be enabled at the hard fork
scheduled for block 1,000,000. Upgrading to 1.10.1 or later before that block
is mandatory for all.

The ecBlockId and ecBlockHeight transaction fields, previously populated but
not used, will begin to be used for enforcing that a transaction submitted on
one blockchain or fork will not be accepted on another blockchain or fork that
shares the same code. These fields by default will be set to a block 720 blocks
behind the last block at the time the transaction is created, and transactions
will only be accepted if their ecBlockId and ecBlockHeight values point to an
existing block when they are included in the blockchain. This default setting
provides protection against replaying the transaction on a hard fork that has
diverged more than 720 blocks from the one where the transaction was created.

Light clients that have no way of verifying the ecBlock values returned by a
remote node will use hardcoded values, to be updated manually at some releases.
Transactions from legacy light clients that leave eBlockId and height set to 0
will still be accepted, but cannot benefit from such replay protection.

All CreateTransaction APIs now accept additional ecBlockId and ecBlockHeight
parameters, allowing the default values to be overridden by the client.

Minor bugfixes and UI improvements.

Updated Jetty to version 9.3.11, delete the old lib folder before unpacking on
top.

[xxxgoodgirls]

Sent it to this address (hope it's correct): BM-2cXXoFkRtXKvV4oiJcJjBXyYBiqo8Eibmc

Yep it's correct.

[.m.]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

Thanks for the update!

Seems like a big promise of great things to come

[hagie]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

This is great - if you need help with 24/7 nodes I can provide 4 hosts with dedicated ip/address.

regards

[unvoid]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

This is great - if you need help with 24/7 nodes I can provide 4 hosts with dedicated ip/address.

regards

Could you give me one of that hosts? If you can, can I run on it miner? (it could have 100% CPU usage 24/7). I would like to test on your host. Hope I'll get root/sudo access on it.

You can send me PM here or bitmessage.

My bitmessage address: BM-2cXBfGPnZCkEQQnK6GVCUDNySEP6HExsr1

[BigBoom3599]

Is there no work available on the network? I'm running the miner and node 24/7

[unvoid]

Is there no work available on the network? I'm running the miner and node 24/7

I submitted 3 works just minutes ago. I think your miner took most of computation because I got nothing from it

[unvoid]

We could have next bug. I submitted 2 works in a row. And network can't cancel first to start another. I have to leave my computer for now but once I'll be back I'll try to recreate this issue.

EDIT: first job already finished so I think it's fine. Anyway I'll submit more of test scripts once I'll back in front of my machine.

[BigBoom3599]

Can the submitter of the work choose the difficulty of the PoW packets? I'm currently submitting a PoW packet every +-10 seconds, and there's quite a backlog of transactions that are still unconfirmed.

[hagie]

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.

This is great - if you need help with 24/7 nodes I can provide 4 hosts with dedicated ip/address.

regards

Could you give me one of that hosts? If you can, can I run on it miner? (it could have 100% CPU usage 24/7). I would like to test on your host. Hope I'll get root/sudo access on it.

You can send me PM here or bitmessage.

My bitmessage address: BM-2cXBfGPnZCkEQQnK6GVCUDNySEP6HExsr1

Hi,

all 4 hosts are rented vps and are used for other projects as well. If you need your own login I could create on one a login for you.
Are 2 cores enough for the test (you won't have much computation but can run 24/7)

regrads

[Evil-Knievel]

@EK why not 1.10.1?

Let's take 1.10.2! 

I am half way through porting everything. At the protocol level, we're done! It's just that I need to update the UI to support the slightly different API.
I thing we should make use of the already-there PrunableData functionality for our work source code as well as the corresponsing PoW and Bounty submissions, so this will be one more little change (which will cause a testnet reset) but which will natively give us sort-of a "mini blockchain" taste and avoid blockchain bloating.

[hagie]

@EK why not 1.10.1?

Let's take 1.10.2! 

I am half way through porting everything. At the protocol level, we're done! It's just that I need to update the UI to support the slightly different API.
I thing we should make use of the already-there PrunableData functionality for our work source code as well as the corresponsing PoW and Bounty submissions, so this will be one more little change (which will cause a testnet reset) but which will natively give us sort-of a "mini blockchain" taste and avoid blockchain bloating.

Great news - I'm happy to provide a 24/7 Wallet and a 24/7 miner if the migration is over.

Regards

[Evil-Knievel]

Great news - I'm happy to provide a 24/7 Wallet and a 24/7 miner if the migration is over.

That sounds awesome!!
By the way, we are almost through porting to the latest NXT branch. Just a few more things are missing (like the work control functions from the old UI)! it's not that much!
The UI has also been improved a lot, I think. But the biggest benefit is coming from under the hood! 

[anhpt192]

Can somebody send me XEL to XEL-8W58-L2DS-CA3B-CDCRH

[ImI]

Can somebody send me XEL to XEL-8W58-L2DS-CA3B-CDCRH

sent

[anhpt192]

If you want to try XEL:

Download testnet client https://github.com/OrdinaryDude/elastic-reference-client.
Best if you download it trough git for future easy updates. Install git on your machine and:

git clone https://github.com/OrdinaryDude/elastic-reference-client.git

Watch this video for instructions how to run it https://player.vimeo.com/video/178616474?quality=1080p and paste your address here to receive some XEL for testing and fun.


If you want to try out a miner:

1. Download it from: https://github.com/OrdinaryDude/elastic-miner
Best if you download it trough git for future easy updates. Install git on your machine and:

git clone https://github.com/OrdinaryDude/elastic-miner.git

2. ./compile.sh
3. ./run.sh
4. Give it your passphrase (after you hit a key make sure visible XEL address is yours)
5. Give it a XEL running daemon IP address (default localhost)
6. Hit enter and submit work to the network in your XEL client UI as shown here https://player.vimeo.com/video/178616474?quality=1080p. If someone else will submit work to the network your miner will automatically start working on it.
7. Example work are here https://github.com/OrdinaryDude/elastic-reference-client/tree/master/elasticpl_examples. no_bounties_found.epl will not found any bounty! Be warned that this is debug job that will just expire after 250 blocks without any submissions.

Suggestions:

run miner with lower cpu priority for optimal experience. Especialy if you running miner on the same machine that you running XEL node.

i. e.

Code:

screen nice -n 20 ./run.sh

20 is lowest possible priority in most linux env.


If you want to update XEL to the newest version:

Stop your node (CTRL + C)
Go to main directory of XEL and:

Code:

git pull origin master
./compile.sh
rm -rf nxt_test_db/
screen ./run.sh

If you want to update miner to the newest version:

Stop your miner (CTRL + C)
Go to main directory of miner and:

Code:

git pull origin master
./compile.sh
screen nice -n 20 ./run.sh

when i run ./compile.sh
it returns ./compile.sh: line 8: javac: command not found

pls help, need i install anything?

[BigBoom3599]

when i run ./compile.sh
it returns ./compile.sh: line 8: javac: command not found

pls help, need i install anything?

You need to install java jdk

Code:

sudo apt-get install default-jdk

[trader19]

i was all this time on my own fork, took my node down until new update is up  great work @EK