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

[cryptodv]

How about ELP 

[-Greed-]

SCAM ALERT: https://bitcointalk.org/index.php?topic=1426466.0

TLDR: Lannister is a bought account from an asian kid, self-mod topic to remove any 'unwanted' posts, no demo/working prototype and less 2 months until the release, no funds/team to build the project, empty repo / copycat fork with 4 commits (mirror).

This message constantly gets removed. So please quote repost it.

I will keep posting the message on a daily basis because I consider it as my duty.

[MadCow]

SCAM ALERT: https://bitcointalk.org/index.php?topic=1426466.0

TLDR: Lannister is a bought account from an asian kid, self-mod topic to remove any 'unwanted' posts, no demo/working prototype and less 2 months until the release, no funds/team to build the project, empty repo / copycat fork with 4 commits (mirror).

This message constantly gets removed. So please quote repost it.

I will keep posting the message on a daily basis because I consider it as my duty.

E-K dealt with you previously, his account is not bought from anyone, and he's in charge, and he's the core dev.

[xibeijan]

I like esc, but it will get lost in search because of all the escrow topics, so xel is better.

as in the ESC key?

I vote for ELC.  Much better than all suggestions.

[BigBoom3599]

I like esc, but it will get lost in search because of all the escrow topics, so xel is better.

as in the ESC key?

I vote for ELC.  Much better than all suggestions.

ELC is already taken by another coin.

[xcurry]

I like esc, but it will get lost in search because of all the escrow topics, so xel is better.

as in the ESC key?

I vote for ELC.  Much better than all suggestions.

ESC is not bad, "apple" most people connect with iphone, not with fruit. When Elastic will become huge same will happen with "ESC"

[Evil-Knievel]

E-K dealt with you previously, his account is not bought from anyone, and he's in charge, and he's the core dev.

Thanks for your support.
I have no idea what it is, but Greed has some serious mental issues. I honestly believe that.

For example he keeps claiming that Elastic has an empty repo, even though people told him something different multiple times in one of his idiotic threads.

This is the official repo: https://github.com/elastic-project/elastic-mini-blockchain

As you can see, there are many commits and a daily progress. Everyone can verify that.
I have no idea how this troll can still claim that there is an empty repo and not feel like a complete idiot lol.
Maybe the reason could be, that people with no competence simply lack the ability to see that.

The rest of what he writes is just as stupid, if not more.
Nobody has ever written that the launch is in 2 months (never, nowhere),
he claims that nobody works on the project while you can clearly see that I am,
and he claims that the project had no funds.

I have no idea what to do anymore, he comes back every few hours and spams this thread with his stupidity.

BTW: If you are as annoyed of him as I am, please consider giving him a negative feedback as I did.
In my opinion, full time trolls should be tagged red for the rest of their live.

[provenceday]

it's a interesting project.

[ttookk]

I like esc, but it will get lost in search because of all the escrow topics, so xel is better.

as in the ESC key?

I vote for ELC.  Much better than all suggestions.

ESC is not bad, "apple" most people connect with iphone, not with fruit. When Elastic will become huge same will happen with "ESC"

ESC is the abbreviation for "European Song Contest", if that plays a role at all

[YNWA2806]

How many users invested so far? By accounts

[xxxgoodgirls]

How many users invested so far? By accounts

245 donations. Unique users might be less.

[Sam123]

We have not heard comments from Dazza for a while, I hope his fine 

[notsofast]

How many users invested so far? By accounts

245 donations. Unique users might be less.

I'm pretty sure I was the first one. Just catching up on the thread. Wish I knew more(/anything) about coding so I could evaluate the progress in github commits. Evil Knievel, how's it going?

[TheDR]

If nothing more I think there should be a minimal viable product with modular adaptability released this summer. Something possible to elaborate later and be delivered relatively soon.

[bitbite111]

I'm new to ICOs and want to invest.

How exactly do I receive my tokens after the ICO? Can I send my bitcoin deposit via my blockchain.info wallet? Will my tokens be sent to blockchain.info?

[Evil-Knievel]

http://icocountdown.com has listed the project as having potential risk due to code not being adequate in the github repository or demo software.

Please what? How can you say something like that?
This is absolutely untrue.

And by the way, your "reference" is a thread from an annoying well-known troll. Unbelievable.

[Evil-Knievel]

Again I'm happy to take the warning off if there is software demonstrated, I have read through the whitepaper. I cannot see the correlation with the whitepaper and the core code currently. If you want to correct me I will happily eat my words as I don't want to put any project on potential risk. I liked the project but there has been people asking me why I haven't looked at particular assets. This is a conditional thing and will be removed if it's false, I have to help the userbase.

This is simply not true. I have just given you a red negative feedback as you seem to repeat the same false spam accusations from the well-known troll named "-Greed-".
For example you, just as him, claim that the github repository contains something entirely different than the actual coin.

You wrote yourself:

http://icocountdown.com has listed the project as having potential risk due to code not being adequate in the github repository or demo software.

This is not true and everyone here can verify that the Github repository contains the actual coin implementation (in its current stage of course) and that commits are frequently made to the code.
Here, you can see all commits: https://github.com/elastic-project/elastic-mini-blockchain/commits/master.

In fact, we have spent hours of discussions about the architecture of this coin. We have agreed on a mini-blockchain based approach (easy pruning) which secures the blockchain using proof-of-stake (for now we have settled with an adaptation of NXT's model using an exponentially increasing target value). The "proof-of-work" itself (meaning people being paid to contribute computational resources to user provided tasks/programs/etc.) is independent from the blockchain security because of the famous "Faster Algorithm Attack" (you probably know that one if you, as you claim, have read the whitepaper). Of course, we are at an early stage of development, but if you claim that you do not see any connection between the github repository and the whitepaper, than you have simply failed doing your job.

I am willing to remove my feedback if you explain to us, why you exactly claim that the "code (is) not being adequate in the github repository".

Note: I would never give anyone a red feedback who just expresses his doubts or criticizes parts of the project.
I only do so, if he bases his criticism on provably false, made-up facts from either himself or some other well-known troll.

[ICOcountdown.com]

Again I'm happy to take the warning off if there is software demonstrated, I have read through the whitepaper. I cannot see the correlation with the whitepaper and the core code currently. If you want to correct me I will happily eat my words as I don't want to put any project on potential risk. I liked the project but there has been people asking me why I haven't looked at particular assets. This is a conditional thing and will be removed if it's false, I have to help the userbase.

This is simply not true. I have just given you a red negative feedback as you seem to repeat the same false spam accusations from the well-known troll named "-Greed-".
For example you, just as him, claim that the github repository contains something entirely different than the actual coin.

You wrote yourself:

http://icocountdown.com has listed the project as having potential risk due to code not being adequate in the github repository or demo software.

This is a lie and everyone here can verify that the Github repository contains the actual coin implementation (in its current stage of course) and that commits are frequently made to the code.
Here, you can see all commits: https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mits/master.

I am willing to remove my feedback if you explain to us, why you exactly claim that the "code (is) not being adequate in the github repository".

Note: I would never give anyone a red feedback who just expresses his doubts or criticizes parts of the project.
I only do so, if he bases his criticism on provably false, made-up facts from either himself or some other well-known troll.

Firstly I am not a troll and I do not like when others condemn projects. I am not in collusion with these people, I got around 10 emails about this so I had to check it out.

Secondly I do not know why you are giving me negative feedback when the issue was just raised and I'm simply doing analysis and asking for information on behalf of my userbase.

Thirdly it could be FUD anyway and I want all projects to succeed.

Fourthly my main concern was the proof of stake integration in the whitepaper I can see here that you are trying to use an adaptive POS method:
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/Makefile.include
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/3bc7ba837897f3a12f888ed8f1cf56409b235ce1
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/wallet.h

Ffithly my other concern was your use of CPU processing how to categorize it and contain it, it seems you are working on a solution here:
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/44bb8f9b96bad0b02619459d1607cf4aa53830ae

Sixthly whoever the manager of this project is, if it is not yourself there is uncertainty in the community who controlled the funds.

I would ask you kindly to dispell "the controlling of the funds" since you are a capable developer and are clearly an asset to the community, and I have never said otherwise. I do not doubt your ability and have personally agrandized you.

Reference:https://www.reddit.com/r/ethtrader/comments/4e0yg4/upcoming_crowdsales/d1x8tfs

However, I would say if you are giving others control of the funds for this project potentially use an escrow. Or you solely control the funds because of the respect and trust you have with the community.

Again, the risk warning is only until the issue is cleared up.

Congratulations on the coding, I also really like the whitepaper. I just had to check it to see what was going on and why people were asking these questions.

So tl:dr all the active tech is there, but not fully developed yet the only thing in dispute is who is prime controller of these funds yourself or another party.

Thanks again for your understanding and to reiterate there is no offense intended I'm just doing my due dilligence.
Not everyone is out to get you.

[Evil-Knievel]

Fourthly my main concern was the proof of stake integration in the whitepaper I can see here that you are trying to use an adaptive POS method:
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/Makefile.include
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/3bc7ba837897f3a12f888ed8f1cf56409b235ce1
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/wallet.h

Neither the "Makefile.include" nor "wallet.h" have any sort of relevance for the proof-of-stake scheme.
You rather want to take a look into https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/main.cpp (lines 2079 and following) including all sub-functions as well as into https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/miner.cpp .

Ffithly my other concern was your use of CPU processing how to categorize it and contain it, it seems you are working on a solution here:
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/44bb8f9b96bad0b02619459d1607cf4aa53830ae

This is work done by the Cryptonite team and is something entirely different.
This is not the part, which constitutes the decentralized computational power market.

However, I would say if you are giving others control of the funds for this project potentially use an escrow. Or you solely control the funds because of the respect and trust you have with the community.

There will be no escrow: not now and not in the future. This has been stated by Lannister multiple times, transparently for everyone (read page 1 of this thread).
People can decide themselves if this is a problem for them or not, how much of red flag that is and how much risk they are willing to take.
If you do not feel good with that, then just stay away from this project. It is not that hard.

Again, the risk warning is only until the issue is cleared up.

What issue? You mean that Lannister controls the funds? Well, this is no general issue.
But if its an issue for you and you do not feel good with that, then just stay away from this project. Luckily everyone has the right to decide himself which project he feels comfortable with and which not.

Congratulations on the coding, I also really like the whitepaper.

Thank you very much. I appreciate that.

So tl:dr all the active tech is there, but not fully developed yet.

Of course not, as the devlopment is still ongoing.

[ICOcountdown.com]

Fourthly my main concern was the proof of stake integration in the whitepaper I can see here that you are trying to use an adaptive POS method:
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/Makefile.include
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/3bc7ba837897f3a12f888ed8f1cf56409b235ce1
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/wallet.h

Neither the "Makefile.include" not "wallet.h" have any sort of relevance for the proof-of-stake scheme.
You rather want to take a look into https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/main.cpp (lines 2079 and following) including all sub-functions as well as into https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/miner.cpp .

Ffithly my other concern was your use of CPU processing how to categorize it and contain it, it seems you are working on a solution here:
https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/44bb8f9b96bad0b02619459d1607cf4aa53830ae

This is work done by the Cryptonite team and is something entirely different.
This is not the part, which constitutes the decentralized computational power market.

However, I would say if you are giving others control of the funds for this project potentially use an escrow. Or you solely control the funds because of the respect and trust you have with the community.

There will be no escrow: not now and not in the future. This has been stated by Lannister multiple times, transparently for everyone (read page 1 of this thread).
People can decide themselves if this is a problem for them or not, how much of red flag that is and how much risk they are willing to take.
If you do not feel good with that, then just stay away from this project. It is not that hard.

Again, the risk warning is only until the issue is cleared up.

What issue?

Congratulations on the coding, I also really like the whitepaper.

Thank you very much. I appreciate that.

So tl:dr all the active tech is there, but not fully developed yet.

Of course not, as the devlopment is still ongoing.

Code:

https://github.com/elastic-project/elastic-mini-blockchain/tree/master/src/test
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/Makefile.am
https://github.com/elastic-project/elastic-mini-blockchain/blob/master/src/test/rpc_tests.cpp

Code:

https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/1d3aa7340a2e798aefead45f85cce200b40da34d

I assume with these and ones above they are to do with testing difficulty of POS and POW as they are marked as nxt retargeting tests, and I know nxt is a POS only system. So my assumption was tests are being conducted on new POS and POW functions, perhaps these are incorrect but this is what I assumed. These are the same ones with links that are marked above as retargeting tests. As I delve deeper into the main source I believe serious work is being done: /elastic-mini-[Suspicious link removed]mit/

Code:

https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/3bec3f53c4b3e9161b7fd2d8fb742c4b48bc13ed

Code:

https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/4fb0fd986466441ce8b225fa648e4bef796b358f

Code:

https://github.com/elastic-project/elastic-mini-[Suspicious link removed]mit/1d3aa7340a2e798aefead45f85cce200b40da34d

I will remove the warning I am happy that there is big work being done here and hopefully this dispells the myths of that this is just a "clone" of some sort.

No idea why the commits aren't showing and showing suspicious links, but I advice anyone to look through the github and see the ongoing tests and development.