Welcome to the Building on Bitcoin Hackathon!
A virtual hackathon where you'll build your very own smart contracts using Clarity. The hack will let you experiment and familiarize yourself with Clarity’s developer environment.
Clarity is a programming language for writing smart contracts on the Stacks 2.0 blockchain. It supports programmatic control over digital assets. It provides native functions that make it easy for developers to create complex smart contracts while protecting users at every step. Clarity provides precise tools for enabling on-chain logic while reducing unintentional errors.
Join us for office hours sessions on February 28th and March 2nd at 11:00am EST for one hour each with the Whitelabel team. They will hold sessions to answer any questions you have for the hackathon in the Stacks Discord Clarity Universe #office-hours channel: https://discord.gg/QHrYFqmAGC
Included is a list of categories of contract types you might want to build, however this is an open-ended contest and you're free to run with your own ideas! Your submission must include at least one Clarity smart contract. The project should be open source and posted on GitHub.
|Simple exchange||Contracts call another Contract||Delegated Voting|
|DAOs||Fundraising||Smart contract IOT - devices|
|Supply chain||Simple Marketplace||Legal Agreements|
|Deeds||Basic Provenance||Payment Splitting|
Remember the core benefits of blockchain technology: transparency, immutability, and security.
- What day-to-day apps do you use that could benefit from being architected this way?
- While learning Clarity and exploring the Stacks ecosystem, were there any utilities or smart contracts you felt were missing that you could create?
- Are there any existing financial systems or ownership models that could be recreated trustlessly?
- What do you want to see exist that doesn't?
When thinking of your submission, remember that it's more important to have something with a smaller scope that is complete, functional, and secure, rather than a larger idea that is incomplete or of lower quality. You can always take your submission idea and expand on it after the hackathon. Your submission will be judged on a combination of factors including uniqueness, code quality, execution, and documentation. Try to create something that is a basic version of a contract that could later be expanded to build a real tool or product.
Check out this fantastic list of helpful tools and resources that will give you a headstart with Clarity: https://clarity-lang.org/universe#resources
- You must build and submit a new contract to be eligible.
- You must provide your Stacks wallet address with your project submission.
- You must scope your submission to reflect a fully functioning MVP, even if it is a part of a larger project.
- It will be at the discretion of Stacks Foundation if it is suspected someone is trying to game the system by trying to make slight changes to existing contracts for the reward.
- Participants must be at least eighteen years old and may participate individually or form teams.
- The Hackathon is open to U.S. legal residents and residents of any other jurisdiction where the Hackathon is not prohibited or restricted by law. The Hackathon is not open to residents of Brazil, Quebec, Cuba, Iran, North Korea, Russia, Sudan, Syria, or and any jurisdiction where the Hackathon would be restricted or prohibited by law. Participants, including individual participants and members of a team, must be at least 18 years of age (or the local age of majority where they live, if older) at the time of registration.
$1,750 in prizes
Prizes paid in cryptocurrency
First Place Prize is $1,000 for best overall contract paid in STX.
Second Place Prize is $500 for best overall contract paid in STX.
Second Place Prize is $250 for best overall contract paid in STX.
Submitting to this hackathon could earn you:
Stacks Ventures Accelerator
is the code well-structured?
does the project work well?
has it been done before? How unique is the project?
is the contract properly tested? Have relevant test cases been covered with unit tests?
does the project have a readme? Is the code commented?