I have created an automatic delete bot that will constantly and automatically remove posts from certain unwanted users:
Link: https://github.com/OrdinaryDude/XXLTerminate
(It is mostly based on XSTerminate but slightly changed and adapted to work flawlessly with the current version of the forum.
But the credits go to https://bitcointalksearch.org/topic/xsterminate-a-bitcointalk-deletebot-to-rid-unwanted-visitors-from-your-threads-850210)
I will add some more fancy features to it if requested.
Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 325. (Read 450551 times)
The poll is over (https://bitcointalksearch.org/topic/m.14468226).
Looks like we have agreed on a new ticker: XEL
I will adapt the source code shortly.
@Lannister: Please also make sure to update the thread title soon.
Thanks to everybody who participated.
Looks like we have agreed on a new ticker: XEL
I will adapt the source code shortly.
@Lannister: Please also make sure to update the thread title soon.
Thanks to everybody who participated.
I likes it!! XEL.
Is there no way to ban someone from a moderated thread? So lame.
It should be not that hard to build a small script that constantly scans this thread for messages from a certain user and remove it.
Maybe we have to accept that some time has to be invested into troll defense and just build it.
I will keep posting the message on a daily basis because I consider it as my duty.
You are retarded, and it is YOU who is scamming. But thank you for keeping this coin cheap for the ICO participants!
Is there no way to ban someone from a moderated thread? So lame.
SCAM ALERT: https://bitcointalksearch.org/topic/scam-alert-elastic-project-the-decentralized-supercomputer-1426466
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.
Are you Greed SICK ? You sound like either a paid basher or a fired employee. Just get the hell out and let these guys do their work. 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.
Daily rebuttal: this is NOT a scam go away with that...
The poll is over (https://bitcointalksearch.org/topic/m.14468226).
Looks like we have agreed on a new ticker: XEL
I will adapt the source code shortly.
@Lannister: Please also make sure to update the thread title soon.
Thanks to everybody who participated.
Looks like we have agreed on a new ticker: XEL
I will adapt the source code shortly.
@Lannister: Please also make sure to update the thread title soon.
Thanks to everybody who participated.
Hey Dev's what was your last Crypto project? any relations to Qora?
No, I don't think that anyone who is involved with Elastic has any connection to Qora.
The last Crypto project that I was more or less involved in was indeed Bitcoin itself.
Hey Dev's what was your last Crypto project? any relations to Qora?
How many donations where collected so far? when is the final day to invest?
Quote
Holy guacamole! We are currently giving away Elastic Coins to all of our donators. Want some? Be quick! The coin distribution ends when Bitcoin block 425920 has passed.
http://www.elastic.pro/
Is very long time! After the Bitcoin halving.
Below is the graph of commits at a glance during March and April,
How many donations where collected so far? when is the final day to invest?
We have not heard comments from Dazza for a while, I hope his fine 
I am, thank you, though I continue to suffer migraines from time to time.
Also my real-world friends have seem to be taking it in turns to have personal crises of various kinds which I need to help with, which has been taking up a lot of my time.
People can submit work where they are interested in many many output, but they as well may submit a work which is impossible to be solved (like factor a 256bit number).
You are behind the times, my friend. A modern PC can easily factor a 256-bit number in just a few minutes. You wouldn't even need to use the Number Field Sieve method. The old Quadratic Sieve has no trouble dealing with numbers of this size.
The current integer factorization record for numbers of a general form is 768 bits. Such factorisations would make an interesting use case for the Elastic Network.
RSA-1024 may be years or perhaps decades away, but be in no doubt, it will fall. 2048 keys ought to be safe until quantum computers arrive.
Following with interest.
Thanks for ICOcountdown to take the time to dig into the source code.
E-k Hat's off to you
You have to spend a lot of time coding and also worried about the fud ...
Continue your excellent work.
I'm going now to invest more
Take care
E-k Hat's off to you
You have to spend a lot of time coding and also worried about the fud ...
Continue your excellent work.
I'm going now to invest more
Take care
Quote
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.
Yes, this is indeed some myth. I am happy that you took your time to take a deeper look into Elastic's source code to bust this myth.
I am removing my negative feedback as well.
I have moved Elastic ICO to the top of http://icocountdown.com it should give the project more exposure. I have also removed the warning and prior posts about the warning. Good to work with you and sorry if there is any offense you are talented and I wish that your project succeeds. To anyone else that wants to fud this project I have actively looked into it and some serious development is going on.
Quote
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.
Yes, this is indeed some myth. I am happy that you took your time to take a deeper look into Elastic's source code to bust this myth.
I am removing my negative feedback as well.
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
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 .
Quote
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
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.
Quote
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.
Quote
Again, the risk warning is only until the issue is cleared up.
What issue?
Quote
Congratulations on the coding, I also really like the whitepaper.
Thank you very much. I appreciate that.
Quote
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
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.
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
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 .
Quote
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
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.
Quote
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.
Quote
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.
Quote
Congratulations on the coding, I also really like the whitepaper.
Thank you very much. I appreciate that.
Quote
So tl:dr all the active tech is there, but not fully developed yet.
Of course not, as the devlopment is still ongoing.
Jump to: