We can succeed without exchanges. I am currently developing an escrow service with automatic withdrawal and deposits (XEL/BTC). Also Mobile apps and a windows lite wallet without any full node elastic install.
Nice work devking. I think this helps illustrate what several of us have been saying. Elastic is a community project...people are contributing in the ways they feel are best. Yes, ultimately it will be nice if there is a foundation w/ a couple of community leaders, but the bulk of the work will probably continue to be done by people that volunteer their time. |
|
|
|
|
As the exchange discussion continues to grow, I just want to reiterate something....Elastic is not like other coins. We are not (or at least should not be) marketing Elastic to the crypto community, our target user is University Faculty, Scientific Community, Researchers, Data Analyst, etc.
We are still a ways from being ready for them. Behind the scenes we are working hard to finalize various parts of the design. I just hope that the recent push to shove Elastic into the spotlight is not pre-mature...to me it is.
Edit: These target users probably have no idea what crypto coins are. They expect the highest quality papers, communications, etc that are on par with the professionals they are used to working with.
|
|
|
|
I would suggest to simply renaming it to "Elastic". The fact that we think about it "Light wallet" is because of historical reasons, and what we have now IS "Elastic" wallet on some early version. As far as I know, the compute part will also be added to the same software (the wallet). @EK, @coralreefer, please correct me if I'm wrong. Thanks I believe you are correct. I too think just calling it "Elastic Wallet" is fine. |
|
|
|
|
I just want to again caution about the push for exchanges (everyone already knows I'd prefer if we weren't pursuing them right now). Just keep in mind that there are still many parts of the project that are in flux and we don't have a solid whitepaper at this time. We already took a risk by releasing the Lite Wallet w/o the compute functionality...so we need to make sure that whatever is being put out to the public is professional, accurate, and complete. I just have a feeling that we are rushing to the exchanges and new people looking at Elastic may see these gaps in the project and get a negative impression that stick with them and possibly spread to others.
|
|
|
|
Are there any developments in progress right now for the code base?
Yes, I am currently working on a POC for the ElasticPL engine which includes - A new memory model to allow the use of all the primitive data types instead of just unsigned ints - Additional features to the language such as user defined functions, declaring state storage, etc - Creating the SN validation engine on the C side - Update the OpenCL logic to incorporate the above changes We are still working through the design around: - Most efficient way to verify a miner has actually fully executed the ElasticPL code and earned their POW reward - Storage solution for the storage of state data between iterations These are just the pieces I'm working on right now...of course EK is working on a ton of stuff |
|
|
|
Again, thank you all for your generosity...I honestly did not expect to be rewarded as I have been. I guess I'll have to eat my words because I'm now feeling pretty obligated to keep my head down and focused on coding  |
|
|
|
Wow I stepped away for an hour and all this  What a generous community! I just hope that my contribution to the Elastic code helps make this project a huge success. |
|
|
|
|
Thanks Clivemy, but I didn't mean to imply I needed more donations. My post was in reference to comments I've seen here and on slack that the devs shouldn't be anon, and that they need to do this or that, etc...And Dumple's diagram implying that investors have the right to make death threats against dev's does not sit well with me.
|
|
|
|
Here's one for all you shitposters out there:
< image >
I need to point out a big difference between the devs of these projects in your diagram....there are NO paid devs in Elastic, and the devs of Elastic don't owe the investors or anyone anything. I hold 21,000 XEL due to some very generous community members...and I received one small bounty from Lannister back in October...I don't feel I owe the investors of this project anything. |
|
|
|
Dear Elastic team, we would like to bring to your attention that you recently made a change to your source code and license agreement which violates the GPLv2 license under which the NXT code has been released.
The problematic commit is SHA 74138264 by myalcin81, 04/09/2017 01:15 AM "missing NXT strings converted to XEL strings on relevated Web API." which replaced all copyright messages from Nxt to XEL.
We kindly ask you to revert this change as soon as possible.
You are of course free to add a separate copyright notice for your work.
@EK @coralreefer - I know it wasn't you guys that made these changes, but do you know how to reverse it? I'm sure EK will get it corrected. I think in the NXT code there is a copyright notice that says the NXT developers or something like that. It probably got accidentally changed when they went in to remove the references to NXT in the user facing code. |
|
|
|
|
I have added my XEL address to my signature. As most of you know I work on Elastic because I find the concept interesting, not to earn a paycheck, but I certainly appreciate any donations.
But please keep in mind there is no guarantee of future work...I will continue to work on the project as long as I find the work interesting.
|
|
|
|
This seems to be a tutorial for testnet?!
I am not that technical but my question was: is installing the node software the same as having a desktop wallet or is having a desktop wallet something else?
To make it short: Yo need the web client. From link: (".... XEL node helping the network as relay node even if not forging so e very node with opened port (7874) is helping the network!" ....." I assume you know how to buy and how to login trough SSH to that server..... I'll not explain this......") No, i dont want a webwallet (assuming that you mean the online wallet at https://wallet.elasticexplorer.org). I want a desktop wallet, because i think it is more reliable/secure. Just like you have a bitcoin qt wallet. So i see only one alternative and that is to install the node software. Maybe because of my limited knowledge i associate 'node software' as being more then just a desktop wallet. A node has other functions too then just being a wallet. But then again i may be wrong. You don't need all the node software...I'm not running a node. You just need Java 8....clone the github...compile using ./compile.sh....then run using ./run.sh All the details are in the various links at https://talk.elasticexplorer.org/ |
|
|
|
|
If anyone is attempting to write a use case in ElasticPL, feel free to contact me for tips on how to use the language.
Also, be aware that ElasticPL is undergoing a major revision...the main github does not have the majority of these changes. They are only in my github.
|
|
|
|
Why in the world would anyone pay 3 BTC to get on Bittrex, or any other exchange. Unfortunately, to me it looks like all the Lite Wallet launch is doing is drawing in the money hungry people trying to make a quick buck. I had hoped it would have a different affect...oh well. Guess there's no need to focus on the tech when there is money to be made  |
|
|
|
I saw this question on the Slack... it didn't get any answers and I have the same question myself so I thought I'd copy and paste it here: hi all, i am really interested in this project but i am wondering - who "owns" elastic, i.e. not just who's the dev but who is going to be the "face" for elastic. the reason i ask is because i know that to get on bittrex, someone will need to verify their identity I doubt Elastic devs will allow to disclose their identities, so if that's the requirement from exchange, then the exchange will probably lose their part of the precious fees from Elastic trading. If Elastic market will be big enough I'm pretty sure such exchange will have to make an exception and list Elastic anyway, or they will just earn nothing. After all, no one was requiring Satoshi ro reveal himself in order to get BTC listed right? no body "owns" elastic...it is an open source project..anyone can join, contribute or be a part of it It's gonna be kinda hard to hit that 100 million dollar marketcap trading on Yobit and Bitcointalk threads. One of the reasons I volunteered to work on Elastic was that there was no "owner". I enjoyed going back and forth w/ EK over various design solutions knowing that both of us were just interested in coming up with the best solution to the problem at hand w/o either of us pushing any certain agenda...we were just working on something fun and innovative. I'm sorry if that doesn't work well with a lot of these poster's get rich quick goals, but exactly what you are criticizing as a flaw w/ Elastic is the exact reason it was able to get this far w/o any funding. |
|
|
|
## Website Updated
-ElasticPL readme.md file updated with more information
-added more Elastic PL button to website
-added new press item
- fixed explorer url
What you have in your github for elastic_pl is outdated and no longer used as far as I know. For now, all the ElasticPL code is now embedded in the miner. |
|
|
|
##Website updated - new posts added - more information - style revised ** let me know if we need to fix something (typo,grammer etc) AND I created Youtube Channel to Elastic Community for Our Videos(EK's videos) I am moving videos to Youtube from Vimeo Please Subscribe Our Youtube Channel: https://www.youtube.com/channel/UCN58yaAzUmkYXZ-GdOhJqkA @By Rallier - Great work! :-) If anyone wants new articles added to the website and can send me the basic info, I can turn it into an article for by rallier to add to the site. Nice work guys. Not sure who wrote the "What can Elastic do?" section but it looks great and provides an excellent summary of Elastic. |
|
|
|
The very short version: A job requester would annotate an SSA form program (in a specific machine model resulting in a particularly structured (binary) flow graph) with a simple liveness/reachability model so that miners could (quickly, and without running any example case inputs) verify the necessary complexity bound of the job's individual work task before selecting. PoW solutions would operate a little differently (still using "per user" generated inputs incl nonce data, but basically hashing/checking "instruction by instruction" instead of at the end of each input run) so that PoW solution rates become uniform across jobs, being able to be found at any point mid-execution. (PoW prize pool would probably also need to work a little differently, with any amount of proof-of-work certificates able to be submitted before a bounty is found, and the PoW pool being divided proportionally after.) Bounty solutions would include an annotation of the original model with information about the eventual I/O relation, such that verifying the output submission can be reduced to an instance of a satisfiability problem. Nodes (all of them) would validate solutions against this model. (They would still need to "re-run the program" by a symbolic interpretation, but could know that they are doing so in an optimally efficient way - effectively skipping any "unrelated loops" encountered.) Jobs would always end after one bounty is found.
I'm summarizing a lot, but that is the basic idea.
Thank you for the contribute HunterMinerCrafter. I wonder has anyone of the contribuitor explorer further this concept? I haven't really had time to look into this yet....but here are my initial thoughts... @HunterMinerCrafter, I think the latest version of the ElasticPL language sets us up well for something like this because it requires the job author to create a "verify" function with logic for a similar purpose (right now it's just to verify the final Bounty solution...but could easily be expanded)...so I don't see this as being difficult to implement technically. What I don't have a good feel for is this...a job author may be quite successful in expressing their primary algorithm to be solved in ElasticPL, but if they don't know how to (or just get lazy) express the verification logic in SSA form they may leave lots of room for miners to exploit their POW rewards without actually working on the Bounty solution. My concern is that they may not know where these intermediate checkpoints need to be within the flow in order to keep the processing time to a minimum while ensuring the value checked truly demonstrates that the miner performed the work they say they did. Of course, I may be completely mis-understanding what you were suggesting...any additional thoughts would be appreciated. |
|
|
|
ImI, on the OP can you please remove the reference to FPGAs in the "What is elastic" section. I don't see any scenario right now where Elastic will be integrating with FPGAs. Although they are flexible...converting ElasticPL to a bitstream would be nearly impossible |
|
|
|
|
Show Posts
