Join us for a weekend of hacking, hustling, and deep-diving into the blockchain industry's most cutting edge DLT developer tools.
Today's most exciting use cases for blockchain technology extend far beyond payments and digital currency. New protocols that offer much more robust programming capabilities than bitcoin have ushered in the era of the "smart contract," and expectations are sky-high for what that could mean in industries ranging from capital markets trading, digital rights management, new peer-to-peer insurance models, and the internet of things.
The Building Blocks Hackathon at Consensus convenes many of the world's top blockchain developers vying to build the next killer smart contract app. Participants can build on top of any blockchain protocol: bitcoin, ethereum, any hyperledger project or otherwise. And through various sponsor challenges, they're encouraged to leverage the software and support made available by our world-class mentors in order to deliver these solutions.
Join us for a weekend of hacking, hustling, and deep-diving into the blockchain industry's most cutting-edge developer tools.
You can walk away with new contacts, prizes of up to $30,000 plus other sponsor goodies, in-kind awards, and coverage for your new creation on CoinDesk.
Please apply here: forms.gle/FRvN87RSXhzsVDJG9
Schedule (subject to change)
Saturday, May 11
9:00 AM : Registration and Power Breakfast
9:30 AM : Welcome, Sponsor prizes, Ideas & Team formation
10:30 AM : Coding starts
1:00 PM : Lunch
4:00 PM : Rehearsal signups (required to present)
6:00 PM-8:30 PM : Dinner and Coding Continues
Sunday, May 12
8:30 AM : Breakfast
8:30 AM : Rehearsals (required to present)
12:00 PM : Lunch
1:00 PM : Coding ends / Submissions due on Devpost
2:00 PM : Demos begin / Demos only / No slide decks
3:45 PM : Judges weigh in
4:30 - 5:00 PM : Winners announced / Prizes awarded
More details on how to use DevPost:
- Have EVERY person on your team go to the link above and click Register for this hackathon. (You all must create Devpost accounts.)
- One person from each team will Enter a Submission (which is a button you'll see after you Register). Where it asks you to add your teammates' email addresses, make sure to use the same ones they used to create their Devpost accounts.
- Submit early and include as much information as you can, so you won't be rushed toward the end. And remember, you can keep updating your project until the deadline.
$40,603 in prizes
CoinDesk Grand Prize - $15,000
Winning team will also have the opportunity to present their hack on the main stage at Consensus Monday, May 13.
The Blockchain Ecosystem has advanced considerably from the primitive beginnings of permissionless protocols of Bitcoin in 2009 and Ethereum in 2015. Over the past five years enterprises have created permissioned protocols, platforms and apps. Many Central Banks, the IMF, the BIS are researching digital and cryptocurrencies. The decentralized technology stacks are evolving to include distributed p2p storage, compute power, etc. New forms of block validation and network consensus are evolving - perhaps most notably PoS. Hardware devices including wallets and Trusted Execution Environments continue to grow. New cryptographic primitives are advancing along the lines of Taproot and Schnorr signatures which may lead to a whole new level of Bitcoin smart contracts. Tangential technologies are converging with blockchain and DLTs including machine learning, various forms of artificial intelligence, connected devices, virtual/artificial reality and quantum computing.
Your challenge is to build in the context of these various trends - ideally illuminating one or more of them.
You may hack an app/dApp, platform, or protocol. The goal is to show working code - not to share an idea or vision. Your demo should clearly explain what you built during the hackathon, not what you built before, or what you could build later. Good Luck!
CoinDesk 2nd Place Prize - $10,000
CoinDesk 3rd Place Prize - $5,000
Quorum: High Performance $2,000
Best use of Quorum’s fast transactions and throughput
Quorum: Privacy $2,000
Best use of Quorum’s privacy features
Quorum: Private/Public $2,000
Best use of tools and APIs from public Ethereum on Quorum (e.g. MetaMask, Truffle, 0x, Dharma Protocol, etc.)
Quorum: Best Use of Quorum on Azure $1,000 (4)
Top teams building with Quorum on Azure (between 1 to 4 teams)
IBM - Design Thinking
Nintendo Switch to each team that demonstrates the best application of IBM Design Thinking to their hack in any category.
Microsoft Azure Blockchain Service
2 xBox's for the winning team.
Core should be to use show the use of our new Azure Blockchain Service.
Bonus points for showcasing multiple members using this service (true consortium workflow)
Bonus points for building the Dapp using this service to use our logic, flow or power apps.
The application to be built by hackers is open ended (besides this criteria)
BigApps Blockchain challenge is to create a blockchain application, platform or protocol with the potential to improve the efficiency, security, and transparency of the NYC public sector.
Prize is entry to BigApps incubation Program this Summer and automatic qualification to pitch at BigApps Demo Day this September 2019.
Participant: Individuals 18 or over in age.
Team size is up to 5 members.
Prize money winners will likely be required to show government issued IDs to Sponsors; and additionally may require Tax form completion.
The objective is to create a new working prototype of an app, a DApp, a protocol, a platform etc. Your project may include hardware.
It is recommended to have a full description of your project, and any slides on DevPost. However judges may not have time to review your DevPost submission.
How to enter
Senior Software Development Engineer / Microsoft
Head of Engineering / J.P. Morgan
Program Manager / NYC BigApps Blockchain
Blockchain Solutions Architect & Developer / IBM
Founder / Tierion
Use of DLT Tech
Use of Blockchain / distributed ledger technology. Bonus points for use of other Web 3.0 technologies: AI/ML, AR/VR, Quantum, IoT, etc.
Implementation & tech quality
Did the team create code that worked?
Problem being solved
Is it important? Would it have a big impact?
Did you clearly present what you built?