ETHWaterloo Hackathon was Awesome
ETHWaterloo is the world’s largest Ethereum hackathon of 2017, where over 300 developers of all.
What you will learn
- Where ethwaterloo hackathon was awesome fits into an Ethereum application.
- Which assumptions should be tested before a mainnet deployment.
- What to read next when this concept is working.
ETHWaterloo is the world’s largest Ethereum hackathon of 2017, where over 300 developers of all backgrounds worked on projects using Ethereum that can have an impact on the world. Teams to make something great in only 36 hours by providing an abundance of hacking resources like mentors, sponsors, and software.
If you did not made it to the event you can still enjoy it thanks to the streamed video. The keynote includes some awesome speaks from the organizer and main actors of the blockchain ecosystem about what to look in the future such as the relationship between blockchains and mechanism design.
The same engineering term can describe different protocol rules. Use the protocol-level Bitcoin versus Ethereum guide.
And Vitalik Butterin explaining what are the strenghts and visions about blockchains and privacy through cryptography explaining things like Plasma, Ring Signatures and Zk-SNARKS.
During the event, another talk was held about how decentralized technologies will Impact our society with the talks from Joseph Lubin (Consensys), Vitalik Buterin (Ethereum) and more:
Before treating every on-chain object as the same kind of asset, review the differences between network coins and application tokens.
Finally, You can find all the submissions of ETHWaterloo on DevPost here.
This hackathon is a nice proof of the blockchain and Ethereum technologies getting more and more popular among institutions, companies and developers.
When the example needs market context, use the ETH/USD price page with historical Ethereum data; it is informational data, not an executable quote.
Turn the example into production evidence
A working demo is the beginning of verification, not the end. Add tests for failure paths, inspect every permission, and record the chain, contract address, compiler, and dependency versions used for the deployment.
Check behavior
Test expected inputs, boundary values, reverts, events, and calls made to other contracts.
Check operations
Plan key storage, monitoring, pause or upgrade authority, and a response if an assumption stops being true.