Video Walkthrough: Building a Tooth Fairy smart contract with EtherScripter

mode80

http://www.youtube.com/embed/6Wkx60XgMIs?rel=0

ethergrok

!

ethergrok

Thanks for the YouTube demo and your thoughts to advance the Tooth Fairy from a magical existence to something of greater real world functionality. To see you demo and present in "split-screen" mode really drives home the functionality and value of working in split-screen to learn the LLL coding convention for Ethereum contracts.

The potential logic flow of the Tooth Fairy that was most intriguing to me was the "Tooth Fairy Council", where some group of individuals could verify "Proof of Tooth" by sending a transaction to the contract and having that stored in the contract. So we see multisig transaction and multiple entities funding that multisig account.

So if several departments in a DAO are required to send funds to some contract, to provide the payment for the contract, then they are building a multisig transaction and at the same time each department enjoys further autonomy and control over their eventual approval of the contract payment, because they must provide the payment portion their department is responsible for in order to have say in the dispersal of the funds. And all departments providing payment, or entities providing payment for the contract payout, they are then protected until all of the obligates are present and accounted for.

Crowdfunding applications, charity applications, claims adjustment, etc ... it's all there in the Ether.

To have a say in the potential release of funds, one must invest first, so one has a "share or vote" in the council, the concern.

So TFC members would then have "voted" to verify "Proof of Tooth" by sending their donation, or their part of the total reward. When enough accounts, some threshold of accounts had then voted by donating to the contract, that group of donations would then be payed out to the child providing "Proof of Tooth".

In Ethereum Client POC 4, we do not have the integrated browser that can host and run the javascript binding code to call to the Ethereum client. With POC 5, and the ability to query the contract and manipulate the contract through an HTML interface, (the embedded browser), we see the potential for contracts is magnitudes of complexity greater. We see the potential for persistent contract storage, (Dennis' Lotto), and logic to trigger further execution of the contract that is dependent on continued interaction with the contract, error checking, and the ability to provide for some "proofs", even the query of the bitcoin blockchain as some proof in order to continue or complete execution of some Ethereum contract.

Good show, the exit plan for the Tooth Fairy is a success, acquired by a large insurance company for many millions of dollars, :-)