Regarding the intro, I think it would be better to go a bit deeper into the functions of distributed computing (scientific and economic). Another thing I would suggest for the project is to drop the 'Coin' or rebrand completely, by its concept this isn't another coin, but something in the ranks of ethereum/augur etc. so calling it a coin really devalues it, and hides it in the multitude of all the clonecoins.
Very good point, I have never looked at it this way.
If you have a particular idea in mind feel free to apply your changes to the introduction and post it for reviewing. Also feel free to attach some sort of affiliation/acknowledgement.
Otherwise I would first finish the rest on the paper and then start polishing the introduction.
Thank you very much for your suggestions for now.
I don't know enogh to be able to tell you what to add to the introduction, but I have some considerations.
Distributed computing dedicated to solve a single task is a virtual supercomputer, composed of many computers working together for a single purpose. Scientific projects harness the power of voulenteer computers to solve computational tasks, the scale of such virtual supercomputers is limited by beeing voulenteer projects, profitable cryptocurrencies on the other hand produce larger networks of computation, yet waste their power on competing for profit and can't be harnessed to solve useful tasks. Grid projects need to be made profitable to scale up and PoW needs to be made useful for arbitrary computational tasks, Elastic makes PoW useful, but grid projects now have to compete with the profitability of crypto mining. So if (I don't know how or if this is technically solved by Elastic) the use of blockchain can mitigate the vulnerability problem of malicious nodes producing false results in grid systems, this could make it even more difficult. Redundancy would be costly if some amount of power would be needed to form a consensus, so I think other mechanisms are needed. I think that costs will be the main problem of Elastic computing, usually grid projects are used precisely because of their low costs, but when its economic, any computing project will need to compete with crypto mining, this alone is a very significant problem for such projects and any additional costs only make it harder.
Also, arbitrariness enables recursivness, will it be possible to hire elastic network to attack elastic network?
As for the name, I think elastic, elasticity or any variation
https://en.wiktionary.org/wiki/elastic is cool, for the name of the coins or tokens, I'd just stay away from using the word token, as it now means something that serves as a temporary replacement. I personally prefer something that fits well with the name of the system and makes sense, for example elastic/elasticity.
First version of the FAA section (mainly, the description of the FAA)
Sources for the LaTeX document are in the github repository.
I found some grammatical errors:
aims for preventing = aims to prevent
on the safe sides = on the safe side
