We've heard you - all the complaints about low-quality online hackathons, weird judging systems, constrictive prizing systems, etc. - the list goes on. That's why at DVHacks III, even though we're going online, we hope to address your concerns and run a hackathon truly catering to the makers.


DVHacks operates off of a slightly different prizing system. Instead of assigning "N" amount of an item for each placing, we've instituted a new system called the prize pool.

As opposed to traditional systems, we've bought a plethora of different prizes in varying amounts. You'll find that some items are restricted to smaller counts than you're used to, but this was done on purpose - to account for both demand and relative cost.

If you win an award (any award!), each person on your team is entitled to pick 1 item from the pool - regardless of the cost. If it's still available, you're welcome to claim it. This way, you don't need to aim for a specific place or cater your project to a certain audience - we want to see just how good of a maker you are, not how good you are at marketing. Make the best project you can, and you'll get your pick out of our selection of goodies.

Wait - what are the prizes? Without further ado, here is the pool in all its glory.

Disclaimer: The prizes aren't listed in any specific order. Furthermore, as the event nears, we may substitute items based on availability/budget.

  • 2x Sennheiser HD560S Headphones
  • 4x Airpods Pro
  • 2x Switch Lite
  • 4x Wacom Wireless Drawing Tablet + Clip Studio Paint Pro License
  • 2x Ultimate Ears Boom 3 Wireless Speaker
  • 2x Ducky One 2 RGB TKL Keyboard (your choice of keyswitch)
  • 2x HHKB Classic Keyboard(your choice of color)
  • 2x Creality Ender 3 Pro 3D Printer
  • 4x Raspberry Pi Package (Canakit 8GB Pro Variant, starter pack of parts)
  • 2x Official Arduino Starter Kit
  • 6x "Participant's Choice" of:

    • 7 months Discord Nitro
    • $75 gift card of your choice (amount is flexible based on circumstances)

And to sweeten the deal, anyone that places in the top 3 will walk out with a cash prize along with their pick from the pool - amounts are detailed on the front page. This means that we've put up roughly $6000 worth of prizing up for grabs from our end - one of the highest prizing brackets offered in an online hackathon recently.

On the off chance that you don't want to pick anything from the pool when it's your turn, we offer a backup - a $60 gift card at a service of your choice. We've intentionally reduced the value of the backup so that it truly is a backup - only indulge in this option if you truly don't want anything else in the pool.

But in what order do winners pick prizes? We've tried to make this process as merit-based as possible, which is why we've created a "hierarchy" of awards to determine what order prizes are chosen in.

1-3: General Winners (1st, 2nd, 3rd Place)

4-6: Technical Winners - order will be determined based on rubric scores. In the event of a tie, a coin will be flipped.

  • Best Mobile Application
  • Best Web Application
  • Best Hardware Hack

7: Best Social Good Hack

8: Best Beginner Hack - eligibility will be determined at the judges' discretion.

As you can see, there's pretty much no benefit from catering your project to a certain platform or cause - in fact it might actually work against you! So put all your qualms aside, and just make the best project you can.

Judging Regulations

We've noticed that the number of people that cheat or "bend the rules" at hackathons has been significantly higher at online hackathons - and that number rises progressively. As such, we've tried to implement some measures that we hope will deter cheating and allow us all to have a more enjoyable and fair competition. With this much on the line, we're sure that you feel the same.


In order to ensure that your project was actually constructed during the time frame of the hackathon itself, we require periodic GitHub commits. The recommended interval is 1 hour in between commits - as long as we can see that you were genuinely making progress during the event (developing code, improving on your code, debugging, etc.), we will assume that you followed the Code of Conduct.

If you are making a hardware project, we humbly request that you take pictures while you're making it, and include it in the GitHub repo! That way we can see that you developed your hardware within the timeframe, and you'll have some memories to look back on :) In the event that you can't submit pictures of your hardware, it's fine - we'll be more scrutinous of your code though.

As it is with most of our rules, we're willing to make exceptions if the situation calls for it. In the event that you have an unusually long gap in between your commits, contact an organizer ASAP and explain your situation, and we'll determine whether or not your situation merits an exception. But we cannot stress this enough - unless excused, any submissions without proper GitHub commit histories will be disqualified during the judging period.

So In Conclusion...

That's pretty much everything you need to know about our quirks. We've tried to do as much as we can to make DVHacks the most seamless, accommodating online hackathon it can be.

If you have any further inquiries, please email the information account. Happy hacking!