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

[unvoid]

i updated newest elastic-miner, but when i run ./compile.sh it shows


anhpt192@ta-ubu:~/elastic-miner$ ./compile.sh
javac: file not found: src/evil/ElasticPL/*.java
Usage: javac <options> <source files>
use -help for a list of possible options

Please overwrite your compile.sh content with this:

Code:

#!/bin/sh
CP=classes/:lib/*
SP=src/

/bin/rm -rf classes
/bin/mkdir -p classes

javac -sourcepath ${SP} -classpath ${CP} -d classes/ src/elastic_miner/*.java src/ElasticPL/*.java  || exit 1

echo "elastic-miner class files compiled successfully"

And report back if compilation was successful.

[1714176456]

1714176456

[1714176456]

1714176456

[1714176456]

1714176456

[anhpt192]

Please overwrite your compile.sh content with this:

Code:

#!/bin/sh
CP=classes/:lib/*
SP=src/

/bin/rm -rf classes
/bin/mkdir -p classes

javac -sourcepath ${SP} -classpath ${CP} -d classes/ src/elastic_miner/*.java src/ElasticPL/*.java  || exit 1

echo "elastic-miner class files compiled successfully"

And report back if compilation was successful.

./compile.sh                         /*done
./run.sh                                 /* wait to see how it work, some firs lines show below

Your account id is: 12095907256428884070, the REED SOLOMON code is: XEL-8W58-L2DS-CA3B-CDCRH
Now please enter the IP/Hostname of the Elastic instance, or leave blank for localhost:

Great! ... Mining will begin in 5 seconds.
If your account ID is wrong, cancel and try again! Otherwise you mine for someone else.
Server has no work at the moment, retrying in 15s.
Server has no work at the moment, retrying in 15s.

[unvoid]

Please overwrite your compile.sh content with this:

Code:

#!/bin/sh
CP=classes/:lib/*
SP=src/

/bin/rm -rf classes
/bin/mkdir -p classes

javac -sourcepath ${SP} -classpath ${CP} -d classes/ src/elastic_miner/*.java src/ElasticPL/*.java  || exit 1

echo "elastic-miner class files compiled successfully"

And report back if compilation was successful.

./compile.sh                         /*done
./run.sh                                 /* wait to see how it work, some firs lines show below

Your account id is: 12095907256428884070, the REED SOLOMON code is: XEL-8W58-L2DS-CA3B-CDCRH
Now please enter the IP/Hostname of the Elastic instance, or leave blank for localhost:

Great! ... Mining will begin in 5 seconds.
If your account ID is wrong, cancel and try again! Otherwise you mine for someone else.
Server has no work at the moment, retrying in 15s.
Server has no work at the moment, retrying in 15s.

It's perfectly fine. Just submit some work to the network in Elastic UI. Currently there isn't any job to do in network (I'll submit one in few minutes).

[HunterMinerCrafter]

I fixed the error now, by only allowing repeat statements with "Block()" as the second parameter. An empty block should be safe here.

The same problem is also for "if" nodes.  Passes parser but chokes in RuntimeEstimator.

[HunterMinerCrafter]

However, you are right, the same computation power does not correspond to the same chance to "shuffle" the correct solution.
When I know which input numbers constitute a correct solution *before*, I can screen the entire random number stream without actually evaluating a single line of the program allowing a speedup by a factor of at most WCET. That would be a variant of the "Faster Algorithm Attack" outlined earlier. This is one problem, that would be great to eliminate (somehow) ... I think noone has come up with a solution to the FAA so far   But after all, this attack is just a "race" where the the "attacker" can merely increase his chances to find Bounty certificates.

Correct, without being able to pre-compute it just becomes, on its own, a variant of FAA.  It is worth noting that, currently, the ratio by which the publisher can increase his chances is quite significant.

I think in combination with another attack it might still have some implications.  I'm still working on a "useful" approach, however.

[HunterMinerCrafter]

I fixed the error now, by only allowing repeat statements with "Block()" as the second parameter. An empty block should be safe here.

The same problem is also for "if" nodes.  Passes parser but chokes in RuntimeEstimator.

P.S.

It looks like this might be the last "significant" parser bug.  I'll be focusing almost 100% on the WCET calculation and interpreter for now.

[ttookk]

I'm going to write another stupid thing:

What if, before the miner sends the block out, he_she signs and hashes it, then sends the hash out and only after a small delay, the block follows. If this is done frequently and with random inputs, no one knows if a hash is of importance, until the miner sends the block. He_she would be able to prove that he_she is the original miner, kinda like a proof-of-existence.

[unvoid]

If you want to try XEL ( Elastic ):

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

git clone https://github.com/OrdinaryDude/elastic-core.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.

Also you can get some XEL through faucet: http://elasticexplorer.org/faucet/

For Windows you have to run compile.bat to compile and run.bat to start XEL.


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
./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
./compile.sh
screen nice -n 20 ./run.sh

[meeekz]

How does Elastic Project differ from Golem?

[Evil-Knievel]

How does Elastic Project differ from Golem?

Its entirely different. From what I understand, Golem is not cryptographically ensuring that a task is carried out correctly. It's more like submitting work, waiting until someone takes and actually does the work, and then get the result back (be it wrong or right). After that, you can vote if you were happy and want to release the payment or not (REJECT or APPROVE)! In my eyes, you don't need an own system for that ... you can very well use a simple forum to have the same functionality! I am baffled how much publicity they got for that.

In Elastic, the computation of tasks is ENSURED by means of "proof of work", all cryptographically secure and tamper proof. This is, at least in my eyes, innovative and unique (with all its little yet-to-be-figured-out problems that we all are working on).

[ImI]

How does Elastic Project differ from Golem?

Its entirely different. From what I understand, Golem is not cryptographically ensuring that a task is carried out correctly. It's more like submitting work, waiting until someone takes and actually does the work, and then get the result back (be it wrong or right). After that, you can vote if you were happy and want to release the payment or not (REJECT or APPROVE)! In my eyes, you don't need an own system for that ... you can very well use a simple forum to have the same functionality! I am baffled how much publicity they got for that.

In Elastic, the computation of tasks is ENSURED by means of "proof of work", all cryptographically secure and tamper proof. This is, at least in my eyes, innovative and unique (with all its little yet-to-be-figured-out problems that we all are working on).

They published a list of issues they see for themselves down the road, maybe could be of interest for us.

https://blog.golemproject.net/the-challenges-ahead-933f040cba95#.5wf6dubct

[Bgjjj2016]

How does Elastic Project differ from Golem?

Its entirely different. From what I understand, Golem is not cryptographically ensuring that a task is carried out correctly. It's more like submitting work, waiting until someone takes and actually does the work, and then get the result back (be it wrong or right). After that, you can vote if you were happy and want to release the payment or not (REJECT or APPROVE)! In my eyes, you don't need an own system for that ... you can very well use a simple forum to have the same functionality! I am baffled how much publicity they got for that.

In Elastic, the computation of tasks is ENSURED by means of "proof of work", all cryptographically secure and tamper proof. This is, at least in my eyes, innovative and unique (with all its little yet-to-be-figured-out problems that we all are working on).

hi EK, we have a great project but not much publicity. Could we have a clear webpage, road map, FAQ,...... ?

[HunterMinerCrafter]

Time for "HMC Bug #9" aka "0 WCET programs, part two" where arbitrarily large programs can be executed for 0 cost:

Currently, the cost of the verify step is not included in the WCET calculation.  Further, any program body without use of the hashes/curves can be transformed and put into the expression for the verify... "if (a) b else c" can become "((a && b) || c)" and "repeats" can just be unrolled.

The verify statement cost certainly needs to be included in WCET!

EDIT: By "0 cost" I mean calculated as 0 WCET.

[ImI]

hi EK, we have a great project but not much publicity. Could we have a clear webpage, road map, FAQ,...... ?

publicity will be given the exact moment XEL is added to an exchange and exactly then a webpage and FAQ will be needed. at the moment we are still in the developing and testing stage so publicity would come to soon as you cannot buy any XEL anyways.

justmy2xel.

[HunterMinerCrafter]

Time for "HMC Bug #9" aka "0 WCET programs, part two" where arbitrarily large programs can be executed for 0 cost:

Currently, the cost of the verify step is not included in the WCET calculation.  Further, any program body without use of the hashes/curves can be transformed and put into the expression for the verify... "if (a) b else c" can become "((a && b) || c)" and "repeats" can just be unrolled.

The verify statement cost certainly needs to be included in WCET!

EDIT: By "0 cost" I mean calculated as 0 WCET.

On a loosely related note - is it just me or is the "weight" of the tiger hash statement way off?

[unvoid]

I'll spam with this every new page untill @Lannister will be awaken.

If you want to try XEL ( Elastic ):

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

git clone https://github.com/OrdinaryDude/elastic-core.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.

Also you can get some XEL through faucet: http://elasticexplorer.org/faucet/

For Windows you have to run compile.bat to compile and run.bat to start XEL.


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
./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
./compile.sh
screen nice -n 20 ./run.sh

[wpalczynski]

I'll spam with this every new page untill @Lannister will be awaken.

If you want to try XEL ( Elastic ):

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

git clone https://github.com/OrdinaryDude/elastic-core.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.

Also you can get some XEL through faucet: http://elasticexplorer.org/faucet/

For Windows you have to run compile.bat to compile and run.bat to start XEL.


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
./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
./compile.sh
screen nice -n 20 ./run.sh

+1 OP really needs to be updated/changed.

[HunterMinerCrafter]

Still some bool/int cast exceptions popping up in the interpreter...

For example:

Code:

verify m[(1==1)]==0;

[Evil-Knievel]

Time for "HMC Bug #9" aka "0 WCET programs, part two" where arbitrarily large programs can be executed for 0 cost:

Currently, the cost of the verify step is not included in the WCET calculation.  Further, any program body without use of the hashes/curves can be transformed and put into the expression for the verify... "if (a) b else c" can become "((a && b) || c)" and "repeats" can just be unrolled.

The verify statement cost certainly needs to be included in WCET!

EDIT: By "0 cost" I mean calculated as 0 WCET.

This leaves the question what to specify as the "weight". The base weight is 0, and "costful" operations such as inserting a variable into the symtab, or doing some elliptic curve arithmetics have some positive weight.

Putting everything into the verify routine is of course one possibility to circumvent WCET calculation. This leaves us with the question what to account for in the weight? Should we consider 1 as the base weight? Making every operation worth 1 credit, and overriding that value for "more complex operations" which in fact require more operations internally?

I would have to think about it, I have no feeling yet for the correct definition on "weight"  
Using a base weight of 1 and accounting for the verification weight in the WCET calculation would mitigate this attack for now! Let's do it.

[Evil-Knievel]

Still some bool/int cast exceptions popping up in the interpreter...

For example:

Code:

verify m[(1==1)]==0;

Fixed! I am so glad that we have you here, helping us with all these nasty bugs!