https://media3.giphy.com/media/gvoias0j99ako/giphy.gif

Very interesting read!

Hi. I am a regular Joe, and I don't understand most of what is in this post. I have gathered that EOS is a competitor to Ethereum and that your goal is to make it more effective in terms of transactions per sec. I have never participated in an ICO, but I did sign up for the mailing list, hoping to participate in this one. If you read this comment and you are tech savvy, could you please try to explain what EOS is capable of in layman terms? And how it works? This would be greatly appreciated.

> When writing an application you start by asking yourself what actions are taken by the actors (aka accounts)... After you have defined these things you specify the logic that transforms database state based upon an incoming action. 

So this looks similar to redux in the react world with actions that triggers reducers to perform some changes on state.  Is this accurate?

Indeed.. very detail. Thanks. I ve been looking information like this..

l like   
how can  l  join this?  ico  or pos?

i like your post

Great to see example of practical use cases! Hope there will be more of these... :)

>Every account (aka application) has its own private database

Where these db is stored?

Great article for newbies. I would like to see real world use case scenarios with more complex data structures and scope management. 
Thanks,

What I like about this code, is that it looks like a "template" that is easily modified by amateur coders.

Many people started learning programming languages by taking existing code that someone else wrote... making a few changes, and personalizing it to do what they wanted instead.

Instead of API's which explain commands, and you have to write your own code to talk to the API...

Having modular code that already does basic tasks, and inviting anyone to plug and play with this code, changing only certain parameters makes it even easier to onboard a lot of people.

Remember the original LOGO programming language?

It was so easy to use.  Kids were drawing boxes and lines on the screen with real basic commands.  It gave you a sense of empowerment and encouraged you to learn more.

If we do away with API's, and instead give pre-made, basic scripts that already do basic functions, this will help make widespread adoption easier.

Think of basic perl cgi scripts for websites. Once you looked at how some worked, you could modify the source code and build your own version. The key was finding existing scripts written by someone else and making your own tweaks, modifications, and edits.

I have a lot to read then :) This seems like just a flake of everything possible

More awesomeness. Shared with @Steemtrail.

Great to see your recent work on the language.  Very clean.  You said it would change so here goes..

It would be very cool to get rid of this: `Balance.save(to)` and this `Balance.save(from)`.  The contract would need to be transactional to some extent so a failed assertion or error would roll all the changes.

This is motivating me to add your text format in a struct serialization parser.   Using text in addition to json is a very easy enhancement.

Very cool. I was searching for more info on EOS and here it is. Crypto-currencies are evolving before our very eyes.

im hyped on this project ;)

Sweeeeeeet! Please keep writing like this!!!

Excellent. Definitely looking forward for the testnet

This sounds really interesting. I almost want to think up some real world problems just to see if I could build their solutions within EOS. :)

Will there be a testnet for people who want to play around with this?

> Once a block is deemed irreversible validate and precondition never have to execute again whereas apply must be executed to generate the deterministic state every time the blockchain is synchronized.

I really like that. Seems like an efficient way to go if much of the code to validate things has already been run before it was applied and won't need to be run again.

We need to off block chain contacts too, like Aeternity is implementing. Private contacts that only ever need to touch the chain if there is a dispute

Excellent newbie guide to smart contracts on the "Blockchain with a Heart" known as EOS!  Thanks for the prompt updates guys!  We are all so excited for launch.  We'll put those Eth heads to shame.  I have always wanted to create my own token and I have so many cool ideas I want to implement for my products like a rewards system.  Also I thought of an idea to put QR codes on cigarette butts and fast food bags so that if they are properly disposed of the consumer or recycler can receive a reward!  A cryptographic solution to real world problems!  All things will be possible with the EOS graphene chain, low cost compared to Ethereum I'm sure!

Was that graph made with yEd Graph Editor?

Good lucky with this project !
This may help you :
https://steemit.com/eos/@patelincho/dpos-consensus-algorithm-white-paper-of-eos-translated-into-bulgarian-dpos-algoritm-za-konsensus-byala-kniga-na-eos-prevedena-na

Messages, will be checked / earmarked as 'processed' by the chain software? In the end one of the validators is processing the message and executes the code right to store it in the db. What happens if a physical server in the middle of the execution quits because of power failure?

Will messages get a lifetime? Doubles(p)ent messages :) will there be unexecuted messages floating around on chain? Are you the messenger? 

Lastly, are you know working on hypothetical apps and building the source afterwards or is the source, specifically for the eos part, already ready? 

See you in nyc!

What database are you referring to in the "Structure of an Application" section. Is it levelDB ? If levelDB how are you achieving the concept of indices in the NoSQL database, and are you achieving the O(logN) efficiency ? Can you please explain ?

I am flabbergasted by the fact that you can include a fully functional private database in each contract. It means that you could write accounting and business solutions in a revolutionary new way (no more double entry archaic methods). For the first time, as a former business application developer, I can relate to the blockchain technology and figure how massively disruptive it will be. Is this feature exclusive to EOS Blockchain (contract private database)?

Hello @eosio .. what a great week for y'all, and ... for us all as well!  This post has been featured in the latest issue of <a href="https://steemit.com/steem/@steemint/steemint-004-the-steem-intelligence-journal-special-eos-edition">STEEMINT - The STEEM Intelligence Journal .... the Special EOS Edition!</a>