great work，I can't update 1.0.12.
rm -rf elastic_test_db
Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 70. (Read 450520 times)
rm -rf elastic_test_db
Great work ek, you're our sato 
great work，I can't update 1.0.12.
Sorry for the late post, but I spent the entire day today getting the storage pruning functionality straight. The more we can prune from the actual blockchain without losing integrity, the bigger our jobs can become without bloating the blockchain itself.
But so you can see that things are going forward quickly, here one example how to use Elastic directly from within Python. Since I changed several things, and since I was pretty tied up in the storage handling, this is just a very dumb example. But since Elastic PL is a very powerful language, one can easily come up with something better. I will post my GA algorithms tomorrow.
Also, we seriously lack a documentation and a centralized place where everything is collected. So maybe someone likes this and start digging a bit deeper.
Here we go:
First of all, it has to be ensured that a local instance of Elastic is running and at least one connection to a supernode is established. Of course, you can find a "public API peer" as well, but this way is just easier:
In a next step, we have to create our Elastic PL program. This one here is super stupid.
You have to know that:
m[0] to m[11] are random integers that are filled in by the blockchain
m[12] to m[43] are free to use, but the content will be written back to the blockchain (a storage basically) when a bounty is submitted
m[44] to m[44+32*BOUNTY_PER_ITERATION] are the "combined storage values". So let us say you want 2 bounties per iteration, each of them supplying a storage of 32 integers (m12-m43) then, 2*32 integers containing the storage of all bounties from the last iteration are put from m[44] onwards.
Pretty lowlevel, let's take a look at the stupidest program ever:
Self explaining: if random integer m[7] is beteen 0 and 30 then set m[1000]=10, otherwise 11.
Then, if m[1000]==10 then take the first element from the combined storage (means the first int from the storage of the first bounty from the last iteration), add one, and store it back in m[12] - the first integer of the storage that will be reported back to the blockchain.
It's very easy actually, if you explain it better than I do.
Last but not least, take your python program which uses the Elastic API bindings to control your work. The example I have written will monitor the blockchain, push the work automatically, and automatically report back the result once finished.
You can take a look at the code on github yourself, for completeness - this is how it looks:
Now comes the magic - just start your program and your python program will use the elastic network to compute the result.
As you can see below, the result is correct ;-) The tricky ones of you can try to understand why this is correct. I always say, the best way to learn is try to understand every single step ;-) And I am pretty tired after just another 13 hours of work straight.
Nothing useful, but something that shows: it works! And it works good
Example and API is here by the way: https://github.com/OrdinaryDude/elastic-api
But so you can see that things are going forward quickly, here one example how to use Elastic directly from within Python. Since I changed several things, and since I was pretty tied up in the storage handling, this is just a very dumb example. But since Elastic PL is a very powerful language, one can easily come up with something better. I will post my GA algorithms tomorrow.
Also, we seriously lack a documentation and a centralized place where everything is collected. So maybe someone likes this and start digging a bit deeper.
Here we go:
First of all, it has to be ensured that a local instance of Elastic is running and at least one connection to a supernode is established. Of course, you can find a "public API peer" as well, but this way is just easier:
In a next step, we have to create our Elastic PL program. This one here is super stupid.
You have to know that:
m[0] to m[11] are random integers that are filled in by the blockchain
m[12] to m[43] are free to use, but the content will be written back to the blockchain (a storage basically) when a bounty is submitted
m[44] to m[44+32*BOUNTY_PER_ITERATION] are the "combined storage values". So let us say you want 2 bounties per iteration, each of them supplying a storage of 32 integers (m12-m43) then, 2*32 integers containing the storage of all bounties from the last iteration are put from m[44] onwards.
Pretty lowlevel, let's take a look at the stupidest program ever:
Self explaining: if random integer m[7] is beteen 0 and 30 then set m[1000]=10, otherwise 11.
Then, if m[1000]==10 then take the first element from the combined storage (means the first int from the storage of the first bounty from the last iteration), add one, and store it back in m[12] - the first integer of the storage that will be reported back to the blockchain.
It's very easy actually, if you explain it better than I do.
Last but not least, take your python program which uses the Elastic API bindings to control your work. The example I have written will monitor the blockchain, push the work automatically, and automatically report back the result once finished.
You can take a look at the code on github yourself, for completeness - this is how it looks:
Now comes the magic - just start your program and your python program will use the elastic network to compute the result.
As you can see below, the result is correct ;-) The tricky ones of you can try to understand why this is correct. I always say, the best way to learn is try to understand every single step ;-) And I am pretty tired after just another 13 hours of work straight.
Nothing useful, but something that shows: it works! And it works good
Example and API is here by the way: https://github.com/OrdinaryDude/elastic-api
Great job, very impressive!
Sorry for the late post, but I spent the entire day today getting the storage pruning functionality straight. The more we can prune from the actual blockchain without losing integrity, the bigger our jobs can become without bloating the blockchain itself.
But so you can see that things are going forward quickly, here one example how to use Elastic directly from within Python. Since I changed several things, and since I was pretty tied up in the storage handling, this is just a very dumb example. But since Elastic PL is a very powerful language, one can easily come up with something better. I will post my GA algorithms tomorrow.
Also, we seriously lack a documentation and a centralized place where everything is collected. So maybe someone likes this and start digging a bit deeper.
Here we go:
First of all, it has to be ensured that a local instance of Elastic is running and at least one connection to a supernode is established. Of course, you can find a "public API peer" as well, but this way is just easier:
In a next step, we have to create our Elastic PL program. This one here is super stupid.
You have to know that:
m[0] to m[11] are random integers that are filled in by the blockchain
m[12] to m[43] are free to use, but the content will be written back to the blockchain (a storage basically) when a bounty is submitted
m[44] to m[44+32*BOUNTY_PER_ITERATION] are the "combined storage values". So let us say you want 2 bounties per iteration, each of them supplying a storage of 32 integers (m12-m43) then, 2*32 integers containing the storage of all bounties from the last iteration are put from m[44] onwards.
Pretty lowlevel, let's take a look at the stupidest program ever:
Self explaining: if random integer m[7] is beteen 0 and 30 then set m[1000]=10, otherwise 11.
Then, if m[1000]==10 then take the first element from the combined storage (means the first int from the storage of the first bounty from the last iteration), add one, and store it back in m[12] - the first integer of the storage that will be reported back to the blockchain.
It's very easy actually, if you explain it better than I do.
Last but not least, take your python program which uses the Elastic API bindings to control your work. The example I have written will monitor the blockchain, push the work automatically, and automatically report back the result once finished. I configured 5
You can take a look at the code on github yourself, for completeness - this is how it looks:
Now comes the magic - just start your program and your python program will use the elastic network to compute the result.
As you can see below, the result is correct ;-) The tricky ones of you can try to understand why this is correct. I always say, the best way to learn is try to understand every single step ;-) And I am pretty tired after just another 13 hours of work straight.
Nothing useful, but something that shows: it works! And it works good
And since we have an actual programming language, let me say it with Golem's words: sky is the limit
Example and API is here by the way: https://github.com/OrdinaryDude/elastic-api
But so you can see that things are going forward quickly, here one example how to use Elastic directly from within Python. Since I changed several things, and since I was pretty tied up in the storage handling, this is just a very dumb example. But since Elastic PL is a very powerful language, one can easily come up with something better. I will post my GA algorithms tomorrow.
Also, we seriously lack a documentation and a centralized place where everything is collected. So maybe someone likes this and start digging a bit deeper.
Here we go:
First of all, it has to be ensured that a local instance of Elastic is running and at least one connection to a supernode is established. Of course, you can find a "public API peer" as well, but this way is just easier:
In a next step, we have to create our Elastic PL program. This one here is super stupid.
You have to know that:
m[0] to m[11] are random integers that are filled in by the blockchain
m[12] to m[43] are free to use, but the content will be written back to the blockchain (a storage basically) when a bounty is submitted
m[44] to m[44+32*BOUNTY_PER_ITERATION] are the "combined storage values". So let us say you want 2 bounties per iteration, each of them supplying a storage of 32 integers (m12-m43) then, 2*32 integers containing the storage of all bounties from the last iteration are put from m[44] onwards.
Pretty lowlevel, let's take a look at the stupidest program ever:
Self explaining: if random integer m[7] is beteen 0 and 30 then set m[1000]=10, otherwise 11.
Then, if m[1000]==10 then take the first element from the combined storage (means the first int from the storage of the first bounty from the last iteration), add one, and store it back in m[12] - the first integer of the storage that will be reported back to the blockchain.
It's very easy actually, if you explain it better than I do.
Last but not least, take your python program which uses the Elastic API bindings to control your work. The example I have written will monitor the blockchain, push the work automatically, and automatically report back the result once finished. I configured 5
You can take a look at the code on github yourself, for completeness - this is how it looks:
Now comes the magic - just start your program and your python program will use the elastic network to compute the result.
As you can see below, the result is correct ;-) The tricky ones of you can try to understand why this is correct. I always say, the best way to learn is try to understand every single step ;-) And I am pretty tired after just another 13 hours of work straight.
Nothing useful, but something that shows: it works! And it works good
And since we have an actual programming language, let me say it with Golem's words: sky is the limit
Example and API is here by the way: https://github.com/OrdinaryDude/elastic-api
I would love to buy some cheap coins so don't hesitate to dump hard, guys )
Me too, I'm looking to raise my stake to 1m at least.
I would love to buy some cheap coins so don't hesitate to dump hard, guys )
lol,me too.waiting low price. 
I would love to buy some cheap coins so don't hesitate to dump hard, guys )
Yo, I want to buy some Elastic. Does anybody know how can I do that?
After mainnet has launched you will be able to buy XEL via OTC and escrow.
Too bad I missed the first token release. Will wait for mainnet
I think that you quite not missed anything. There are a lot of whales in XEL, I think its a bad sign for first days/months of trading. If one of that whale will sell at once drop in price will be significant. I myself want to buy at release and I think (and hope) that there should be quite low prices at beginning.
I think that we will see a substantial market cap for xel in view of general market sentiments and comparable projects in the same field. Perhaps we will see dumps to lower the price, but we will also see buy pressure to consume these coins. Elastic is going to be a very prominent player and will no doubt draw big trading volume.
I wish good luck to everyone who wants to pickup some more coins cheap while they can
Yo, I want to buy some Elastic. Does anybody know how can I do that?
After mainnet has launched you will be able to buy XEL via OTC and escrow.
Too bad I missed the first token release. Will wait for mainnet
I think that you quite not missed anything. There are a lot of whales in XEL, I think its a bad sign for first days/months of trading. If one of that whale will sell at once drop in price will be significant. I myself want to buy at release and I think (and hope) that there should be quite low prices at beginning.
Yo, I want to buy some Elastic. Does anybody know how can I do that?
After mainnet has launched you will be able to buy XEL via OTC and escrow.
Too bad I missed the first token release. Will wait for mainnet
Something tells me that 6M guy after all will chose logo. I hope he has good gfx taste
Maybe the 6M share guy is not one person, maybe a company, exchange,...
Something tells me that 6M guy after all will chose logo. I hope he has good gfx taste
Yo, I want to buy some Elastic. Does anybody know how can I do that?
After mainnet has launched you will be able to buy XEL via OTC and escrow.
Yo, I want to buy some Elastic. Does anybody know how can I do that?
Yes build a time machine.
Yo, I want to buy some Elastic. Does anybody know how can I do that?
It's impossible, you have to wait for exchanges.
I'm pretty sure there are some people who would be interested seling a small portion of their XEL stock for an acceptable price?
love this project too and totally agree this is true crypto and the more i think about it the more i like it.
i can feel there is somethign very special in the building here.
about mainnet i have no problem to wait as long as needed so take your time all and keep up this nice mood here;)
just an idea but could it also be possible to handle elasticracy that you can also vote with part of your stack?
like 70% of my stack to orange 30% to apple, or 60% of my elastic to vote for orange and the rest i dont use to vote?
just think about this as sometimes there are questions or things where you tend in a direction. in this case it could be possible (very unlikely) the decissions tend to a 50% 50% then the most fair should be to "flip a coin" in the programm and let the accident decide.
another thing that came into my mind is if its possible to cut your vote before the deadline and do a vote again.
or you can have voting with 2 possibilities: 1 vote is super safe cannot be cut, or you vote and have the ability to change your vote before the deadline. The percentage of votes that cannot be changed or votes that can be changed should be shown then in puplic.
sometimes the voted things can change when you have a question and people have voting time for 2 weeks many things can change in that time.
this ideas are not complete and could be totally wrong thought i might just write it here down (have many more but this should be enough for now haha)
i can feel there is somethign very special in the building here.
about mainnet i have no problem to wait as long as needed so take your time all and keep up this nice mood here;)
just an idea but could it also be possible to handle elasticracy that you can also vote with part of your stack?
like 70% of my stack to orange 30% to apple, or 60% of my elastic to vote for orange and the rest i dont use to vote?
just think about this as sometimes there are questions or things where you tend in a direction. in this case it could be possible (very unlikely) the decissions tend to a 50% 50% then the most fair should be to "flip a coin" in the programm and let the accident decide.
another thing that came into my mind is if its possible to cut your vote before the deadline and do a vote again.
or you can have voting with 2 possibilities: 1 vote is super safe cannot be cut, or you vote and have the ability to change your vote before the deadline. The percentage of votes that cannot be changed or votes that can be changed should be shown then in puplic.
sometimes the voted things can change when you have a question and people have voting time for 2 weeks many things can change in that time.
this ideas are not complete and could be totally wrong thought i might just write it here down (have many more but this should be enough for now haha)
I think you raised some good ideas there! better flexibility in the voting mechanism can enable a more precise representation of the will of the majority when casting votes on various topics.
timing is important, but products count more.
let's wait for mainnet release.
hopefully in 2 months.
I think any days ! I might be wrong though.let's wait for mainnet release.
hopefully in 2 months.
most important thing is have some real usecase, what i can feel is the bubble is growing,
everything is similar as 2013
earlier, people released thousands of tokens and asset on mastercoin and NXTcoin
then nothing.
XEL is much much better than that ERC 20 tokens (.......they are just a token. )
timing is important, but products count more.
let's wait for mainnet release.
hopefully in 2 months.
I think any days ! I might be wrong though. let's wait for mainnet release.
hopefully in 2 months.
timing is important, but products count more.
let's wait for mainnet release.
hopefully in 2 months.
let's wait for mainnet release.
hopefully in 2 months.
Jump to: