Cover image for Announcing the Grant For The Web Hackathon on DEV
The DEV Team

Announcing the Grant For The Web Hackathon on DEV

ben profile image Ben Halpern ・6 min read

We are so excited to announce the Grant For The Web x DEV Community hackathon.

Grant for the Web is a collaboration between Mozilla, Creative Commons, and Coil. They are working towards a healthier internet, using open standards to give people more independence and control over how they distribute and monetize content. It’s a future where creators and their publishers can leverage open standards and protocols like Web Monetization instead of relying on invasive ads, paywalls, and the abuse of personal data.

We are deeply aligned with Grant For The Web’s mission, and are very excited to support their open Call For Proposals. They are funding projects that contribute to an ecosystem of content, users, tools, and infrastructure over the next 5 years. The grants will range from $5,000 to $100,000 USD!

In order to help drive exploration and experimentation around Web Monetization and possible grant proposals, we’re excited to host a Community Hackathon right here on DEV. We hope that you’ll participate in the DEV contest, and then consider expanding your submission into a full-on Grant for the Web proposal via the Grant for the Web CFP.

Read on for more details about the contest, categories, prizes, and key dates.

What is Web Monetization?

For many of you, this might be your first exposure to Web Monetization. Web Monetization provides content creators with an alternative solution to get paid for the content they share on the Web. When a user visits a monetized Web page, their browser (if it supports Web Monetization) may send micropayments to it. The Web page can detect these micropayments and give the user a better experience, for example by removing advertisements or by unlocking additional content. All this is made possible thanks to a new Web API developed at W3C, the Web Monetization API. This API is intended to be implemented natively in browsers but is already available today via a Web extension for popular desktop browsers and Puma Browser on mobile.

In order to add Web Monetization to your project, you’ll need to:

  • Set up a “wallet” for receiving payments
  • Get your wallet’s “payment pointer”
  • Add a special tag to your page with your payment pointer
    <title>Web Monetized Site</title>
    <meta name="monetization" content="$wallet.example.com/sloan">

From that point on, you can use the JavaScript API to react to the small payments from users who have a Web Monetization provider, like Coil. You might choose to reward these monetized browsers by removing ads, unlocking exclusive content, or enabling special features. We’ve outlined a few example projects a little bit lower down in this announcement post.

Here are a few options for wallets that can receive payments. The first Web Monetization provider for sending payments is Coil but others will likely crop up as the ecosystem grows.


Now that we’ve gone through the basics of Web Monetization, let’s get to the fun part: the DEV Community hackathon. For this contest, we are looking for projects in these three categories:

  • Foundational Technology: projects that innovate around the technology itself: i.e.building plugins, documentation, APIs, and templates for monetizing the web, etc.
  • Creative Catalyst: projects that use existing Web Monetization technology to explore the creation, distribution, and discoverability of content online.
  • Exciting Experiments: an innovative or unexpected web monetized app that doesn’t necessarily fit any of the above categories, but is a clear winner nonetheless.

The Foundational Technology and Creative Catalyst categories mirror Grant for the Web’s call for proposals, should you wish to consider expanding your Hackathon submission into a full-on application.


3 Grand Prize Winners (one in each category):

  • $2,000 USD gift card or equivalent 💸
  • $300 USD credit to the DEV Shop 🎁
  • DEV “Grant For The Web Hackathon” winner badge 🏆

Runner-up Prizes (10 total):

  • $400 USD gift card or equivalent 💸
  • $150 USD credit to the DEV Shop 🎁
  • DEV “Grant For The Web Hackathon” runner-up badge 👏

Participants (with valid projects):

  • $50 USD credit to the DEV Shop 🎁
  • DEV “Grant For The Web Hackathon” participation badge 💪

How To Participate

In order to submit a valid project, please follow the submission process and rules closely.

How To Submit

  • Document your project journey along the way with the #gftwhackathon tag.
  • Submit your project as a DEV post by filling out this template
  • Please be sure to include the code repository in the post with embedded live demos, screenshots, and/or code snippets.

Additional Rules

  • Your project must be started and completed between May 6 - June 5.
  • Your code must be licensed with a permissive license (i.e. MIT, Apache-2).
  • You may work in a team but only one person should submit the project. Only one prize will be awarded to each team
  • You must be 13 years of age or older to participate in the DEV Hackathon. To submit to the Grant for the Web CFP, your team lead must be at least 18 years old (though younger people are allowed to participate as part of the team).

Coil Trial

Coil is generously offering a free trial to Grant for the Web Hackathon participants. More information in this post:

Example Projects

Need some inspiration on what sorts of projects to build? There are several examples you may want to check out in the WebMonetization.org Docs. You’ll find examples related to:

There are some additional examples on Coil’s Glitch page.

Community Support

We’ve set up a GftW Hackathon Discussion / Help Thread where you can discuss ideas, find collaborators, and receive support from experts in Web Monetization. Team members from Grant for the Web and Coil will be spending time on DEV and answering questions in this thread.

We’ll also be setting up a dedicated DEV Connect group channel for more synchronous help. To join this group, just leave a comment in the discussion / help thread. This will be a great place to spend time with the team from Grant for the Web + Coil, and to engage with you fellow community participants.

Call For Proposals

In addition to the hackathon hosted right here on DEV, Grant For The Web is welcoming submissions to their call for proposals. They are looking to fund individuals, projects, and global communities that contribute to a privacy-centric, open, and accessible Web Monetization ecosystem with grants ranging from $5,000 to $100,000 USD.

The $100 Million, five-year fund will prioritize innovative ideas that incorporate or build upon the Web Monetization standard and protocols. Funds will support projects, content, experimentation, and learning around natively integrating monetization into the web using open protocols and standards.

Our hackathon categories are intentionally similar to the call for proposal tracks in order to make your life easier. We strongly encourage you to submit to both the hackathon and the call for proposals if you’d like to take your project a step further!

Important Dates 🗓

  • May 7: Hackathon Begins!
  • June 5 June 14: Hackathon Submission Due at 11:59pm PST.
  • June 10 June 18: Hackathon Winners Announced
  • June 12 June 22: Grant for the Web Call For Proposals Due

DEV Is Participating Too

During the hackathon, the DEV team will be taking on a Web Monetization project of our own. We’ll start by adding a Payment Pointer right here on the open-source platform! Once we get a deeper sense of how the technology works, and feel confident that we’ve implemented everything correctly, we’ll enable Web Monetization for everyone in the community. This means that every DEV member will be able to add a payment pointer to their profile and published posts!

We’re so excited to be supporting Grant for the Web as they push the internet towards more fair and open standards. We hope you have fun, learn some new things, and build something you’re proud of. We can’t wait to see what you come up with!

Happy Coding!

Posted on May 7 by:

ben profile

Ben Halpern


A Canadian software developer who thinks he’s funny. He/Him.

The DEV Team

The team behind this very platform. 😄


markdown guide

Hello DEV community,

my name is Ali and I'm a member of the team here at Coil working on Web Monetization. If you have any questions about Grant for the Web, Web Monetization, or Coil please let me know.

I'm pretty new to Coil (3 whole weeks!) so I'll be likely be learning some things right along with you. That said, I'll be coordinating with plenty of folks from the Coil team to ensure we're supporting the community with technical guidance as people start on their projects.

DEV is a wonderful and supportive community, and I know I can count on your patience as much as I'm anticipating your creativity. All of us at Grant for the Web & Coil are excited to see the amazing projects you are going to create!


Are JS libraries that facilitate the use of Web Monetization part of the Foundational Technology category?


Yes, a JS libraries would count as foundational technology.

Is there any special Coil's redeem code for developers that join this hackathon?

We will be providing codes for trial memberships to people/teams who submit a project.
Information is here: dev.to/devteam/free-coil-trial-for...


Hello Ali.
Coil seems a really nice idea and as an author on Dev.to, looking forward for deep integration between the two platforms.

Not sure if it´s the best place to ask this, but a suggestion for improving the onboarding process in Coil Platform is to improve the "Select Payout option" page.

I know very few about Bitcoins and Blockchain and on that page I am requested to select a payment method. I have no idea what xrp, Gatehub, Stronghold or Payment pointers are. Any user like me can feel a little bit "intimidated" with that page.

I would choose Gatehub, just because it supports payouts in EUR and SEPA transfers but not sure if there are better options.

It would be nice to have some kind of introductory guide on the topic and provide a link that page.


Hi Bruno,
Thank you for the feedback! We are currently working on improvements to our documentation and guides, so, yes, this is relevant and appreciated information.


Hi Ali
Are there any special Coil's redeem code for developers that join this hackathon?


We will be providing codes for trial memberships to people/teams who submit a project.
Information is here: dev.to/devteam/free-coil-trial-for...


I have a doubt. When is the last date for the submission for this hackathon?


The submission deadline has been extended to June 14.

Grant for the Web's Call for Proposals (CFP) has been extended until June 22, but the DEV.to hackathon ends on June 14.


I am new here. Didn't get it at all. If this is a hackathon then we suppose to build stuff right? Please enlighten me..


Yes, we are looking for people to build projects that utilize and/or promote the Web Monetization API in the hackathon.

Broadly, projects can include things like building new plugins or interfaces, or writing documentation and templates. It also includes projects that focus on enabling the creation, distribution, and discoverability of web monetized content.

Hope this helps!


I'm so excited about this collab! Immediately thought of you all when I met Coil in Amsterdam! I think adding web monetization to DEV is the perfect fit and incentive for authors!


Yeah we agree. We hope this could empower folks to make the most of the traffic they're generating in one small way with a lot of transparency.


Hi Ali, funny how all the parts connected on this thread!


We are so excited to be working with Grant For The Web on this Hackathon, especially just a few short days after we wrapped up the Twilio Hackathon (awarding those prizes today!!). We’re really hoping to bring these fun events to the community regularly, giving people the opportunity to build with new technologies and earn great prizes.

One of the best parts about this particular Hackathon is that the DEV team gets to build right alongside everyone as we implement our own payment pointer -- can't wait to discover our learnings together :)



I'm Dees. A South African, based out in London. I've spent many a year championing the open web and standards, most notably from my time at Mozilla, the makers of Firefox. I joined Mozilla Labs in 2010 at the time of Firefox 3.8! Prior to that I've had check-ins at various dot-coms. And was even part of the very early CSS movement, taking eBay from a table-based front end.

Most recently, I co-created Grant for the Web. And I'm super thrilled to see this collaboration go live. It started as an 'all the things' conversations with Ali Spittel, @aspittel at ViewSource in Amsterdam late last year — led to coffee in NYC with PB&J. Which led to impressive virtual only co-ordination as we all entered lockdown to make this a reality within a few weeks.

The Grant for the Web team and our founding collaborators Mozilla, Creative Commons and Coil are excited to see the DEV community's creativeness with the emerging Web Monetization web standard and Interledger protocol within W3C, one which at it's core brings the creator back to the forefront and fairly rewards them for their work and effort.

We can't wait to see what this amazing community comes up with.


Hello! I'm brand new to Web Monetization, I've heard the term floating around. Can you help paint a better picture with a bullet point list of things that people might build for this hackathon, or for the grant application?


Check out some samples within the Web Mometization documentation

Also perhaps wander across to the Grant for the Web Community Forum. There are loads of ideas being thrown about there by many others.

And lastly to highlight @ben main post above some starter ideas and demos listed under the Example Projects header.

Happy building!

Interesting! I checked out those examples, but one thing I don't see is payment amounts. The examples only show placing or removing the <meta> tag in certain ways, and showing monetization states based on events. How do payment amounts come into play?

EDIT: Ah, ok, I see the explainer shows an event.detail.amount property.

I take this to mean that a website could show a message like "pay such and such amount and receive such and such stuff", then the user can take that action, and eventually the website would see event.detail.amount.

How would something like selling individual products work? Would we need to dynamically switch out the meta tag (or go to an entirely separate page with its own meta tag) depending on which product the user will be paying for?

I'm taking the below directly from @sharafian — and it's likely best that he expand...

Web Monetization doesn't allow for the requesting of specific amounts. Discrete or 'retail' payments like that are better served by a traditional checkout flow or the Web Payments API.

Interesting. So how do you know if it is worth disabling ads for someone if your business relies on ads, for example? What if they donate only 1 cent. Maybe that won't outweigh the benefit of keeping the ads. There must be a way to track amounts. and therefore, a way to list those amounts somewhere on the website for users to set as their goal, which would equate to requesting specific amounts but in a different way.

There are some interesting privacy related challenges here. Unless users/members explicitly opt-in of course. @sharafian likely has thoughts and ideas here.

On the member side, @wobsoriano has been working on a separate extension (they opt-in by explicitly installing something) for members showing them their spend. It's a work-in-progress for the hackathon and he is writing about it.


Hello DEV community, my name is Chris Lawrence. I am on the Grant for the Web program team. We are excited to be partnering with Dev on this Hackathon.

Myself and others on our team are here to answer any questions you have about the program, provide feedback on ideas, or discuss the broad themes of Grant for the Web.

We are giddy with curiosity about the tinkering, prototypes, and new ideas this community is going to come up with and we hope when you’re through, you consider applying to Grant for the Web. Let's roll!


Hi Chris! Sent you a message.


Oh man, I've never done a hackathon before, but absolutely putting some time aside for this!


Daaaaamn this is one of the coolest APIs I've heard of. I definitely want to do something with this, there's soooo much potential. Now I just need to think of an idea!


Hyped as hell too! Got an idea to bounce off. The API coupled with documentation.
Let me know if you'd be interested


Happy to hear your ideas - you can email me directly if you like.


As we work out the ways that web monetization will exist in our ecosystem for the benefit of individual authors and the free and open web in general, we'll definitely have an eye on contest submissions for interesting ideas and approaches we can adopt. I'm really excited to see what folks come up with.


This is truly an incredible step toward the future of content monetization. Kudos to Coil for investing in this technology and being the first provider out there 🦄🦄

Regarding the Hackathon I have some question:

  • Is it allowed to participate with multiple projects? in multiple categories?
  • Could anyone clarify more this category "Creative Catalyst"?
  • A platform that helps creators to manage their monetization or get monetized in which category it will be part of?

You can do more than one project but only win 1 prize.

Creative Catalyst projects, generally, would focus on ways to create, distribute, and discover web monetized content. So, for example, you could build things that enable publishing or that help users find monetized content.

A platform to help creators manage monetization or set up monetization seems like it would fit best into Foundational Technology. However, we want you to build cool projects, so don't worry too much about categorizing them, if it's a grey area we'll sort it out.


Thanks for the reply Ali 🦄 It's an interesting technology hence there's a flood of ideas to explore. Good luck for everyone.


Ooh, another hackathon! Coil sounds super interesting and I'm keen to give it a try on my own personal website.


Happy to assist with lightweight technical instructions if experimenting on your personal url, Emma. Feel free to email .


I just have the 100 year old idea. Framework ! :D Like, enable by default for users to input their wallets into system. Then all payments made by looking at post of specific users could contain additional tag where website could split payments in two parts, one for the website, another for the user that wrote the content. Like YouTube, they could use this to avoid having ads on video but still pay the content creator also. They could allow users to input start and end times for ads which are part of the video, and if micro payment is made player skips ads automatically :D

Just brainstorming in comment section. I might make stupid video website which can solely rely on these things just for fun. But I doubt it so if anyone likes the idea he can make a go at it.

Oh yeah maybe something like a "nice" stackoverflow where you can ask "stupid" questions without getting shamed, but if you get a lot of + points you get micro payments, goes both for answers and questions. Viewers could be "charged" by quality of content they're looking at, so if they want "best" answer they might need to allow payment to go through.


Ideas are great. The whackier the better. While they may not all work or be viable ultimately it's the creative experiments are going to help move the web standard forward and more so catalyse the content ecosystem. Go wild...


I might just for fon xD. I may be underestimating some of my ideas just because I don't see some actual value in it for myself but it might be fun to learn a new technology. Although I dislike frontend mainly because of design, it could be family time well spent, wife using being social media marketer with great knowledge in video and image editing could make some templates. Like instead of board games people could start doing this during lockdowns XD


This makes me so happy! Thanks DEV for again giving us something to keep busy with and working towards through these times! It really makes the days go by faster and in the best way possible - by learning!😊❤️


Amazing initiative, definitely plan on submitting a project :)


Cool that DEV is doing these Hackathons!
Is Grant For The Web a similar concept as BAT (Brave Attention Tokens)? Never heard of it before, but sounds interesting.


Grant for the Web is a $100M fund to boost open, fair, and inclusive standards and innovation in Web Monetization.

Web Monetization enables secure, streaming payments to creators & publishers. The API is proposed as a W3C standard based on Interledger, an open protocol suite for sending payments across different ledgers and is not tied to a single company, blockchain, or currency.

Web Monetization is similar in concept to Brave Rewards. Brave Rewards is built on the Basic Attention Token (BAT), an Ethereum based token which was created alongside its home platform, the Brave Browser (the wallet can be funded with a currency or by earning tokens with ad views).


We're thrilled about the opportunity to collaborate with Grant for the Web. They will be funding projects that help the internet become more open, independent, and fair. The long-term promise of Web Monetization may help us all move away from a system that is currently based on invasive advertising.

The DEV Hackathon is an opportunity to experiment with Web Monetization and to create projects that innovate on the technology itself, or to put forth some creative and experimental applications. There's plenty of great prizes on the line, and we can't wait to see what the community comes up with.

We're also hopeful that some participants will expand their DEV Hackathon project into a full-blown submission to the Grant for the Web CFP. That's an opportunity to earn a seriously impactful grant to continue working on your idea well after this DEV contest ends.

Have fun!


I'd love to know more about the server-side of things regarding Web Monetization, currently the site says "Examples on how to verify Web Monetization from the server side will come soon."

I have an idea for something though it requires effectively running a custom payment pointer - at a quick glance, I can't see much detail about that on the Web Monetization site. Also, does that (an idea built on a custom payment pointer) actually fit into the hackathon categories?


You're correct that server-side verification requires a custom payment pointer right now; it can be quite complex and requires peering into the Interledger network which can be hard for an individual. wouldn't recommend it as a hackathon project as peering into the Interledger network requires setting up business relationships with other Interledger network participants.

As a more developer-friendly alternative, we've been developing STREAM receipts.

STREAM receipts are signed messages that say how much a user has paid to your payment pointer. They can be verified server-side without requiring you to run your own payment pointer and without requiring you to peer your server to the Interledger network.

So far we've implemented STREAM receipts in the STREAM libraries, and the next step is for wallet providers to pull in that new version of the library and expose the receipts functionality.

I'd expect it should be available on at least one wallet provider within a couple of weeks to a month and available on all wallet providers within a month or two.


Thanks for replying! Basically I was thinking of some form of middle-man for the monetization system where a user (who makes the content) can manage it without knowledge of coding.

For example, if they wanted to do profit sharing off a particular page, just knowing the page URL and who they wanted to split it between would be enough. Similarly, if they wanted to donate a particular % to charity or something, they can automagically do that with some changes in an admin system.

While there are JS examples on the Web Monetization site that do a revenue sharing example, to me this is something that makes more sense as a server-side system and I figured "incepting" the actual money through its own custom payment pointer to do the processing on makes the most sense for a real implementation.

Gotcha, that's a cool idea! Implementing a revenue share like that is easier than writing a payment pointer which verifies payments, because it doesn't require you to hook into the Interledger network yourself.

If you want to do revenue sharing server-side you can run a server that redirects to different payment pointers, just like this example on webmonetization.org. The website that wants to use your revsharing service would embed a URL from the revshare service instead of their own payment pointer. Then the user can adjust the revenue sharing parameters on your service without having to update their page every time.


Hi @thepracticaldev team!
The rules don't mention if minors can participate in this DEV hackathon.
I am asking this because I am 17 years old. Am I eligible for participation?

Thank you.


Hi @vladodev thanks for the question, we'll clarify in the original post as well.

You must be 13+ to participate in the DEV Hackathon. For the Grant for the Web CFP, the team lead who submits the project must be at least 18 (but you can still participate as part of a team).


Hi Peter! I am very pleased to hear this.
I am aware that Grant requires a person to be 18 or older.

Thank you Peter and the rest of the @thepracticaldev for allowing us to show our skills :)


I am participating, just took a web page that i coded some years before. I explained which functionality only works if the browser supports Web Monetization. But I don´t include code of Web Monetization, do you thing that it will be a problem?


Let me make sure i understand your question...

You have taken an existing web page & added information about Web Monetization to it, but have not monetized the page (by adding the meta tag).


I have not added Web Monetization to it, because I don't have a payment pointer. I will use something as example of payment pointer later.


Careful! These examples hide content on the client side. A clever user could pretend to be web monetized by using the developer console. Examples on how to verify Web Monetization from the server side will come soon.

How soon? :P


it's been specified in Interledger RFC 39 and included in protocol stream 2.5.0. But it's up to wallets to implement this. Currently we are working on getting wallet adoption which hopefully won't take more than a month or two.


After reading about Web Monetization I honestly have to express my, very likely unpopular, opinion.

This is horrible. Honestly. This is 'loot boxes' mechanics brought from the worst of games and buffed to absolute. Not only services will rely on microtransactions that are harder to resist for certain people - they will become a stream, money will flow from you without any sane control of your budget.

Do I have to point out that even now many services make all and every attempt to keep you on their page? Well with WM in play - this will only get worse.

Should I mention governmental 'parent control' problem? The moment this thing becomes popular governments of many countries will start to implement all kinds of regulations that will result in more borders, control etc as a result making the internet less free and open. Net neutrality? Forget it.

This is terrible idea that does not really solve any problem at all.


Thanks for taking time to relay your thoughts and opinions, Artem. They are all welcome.

We are very early in this journey — and a number of folks from various organizations are involved in the discussion which includes challenging decisions and making this better and better, like any good standards process.

Perhaps you could add your voice to the various discussions starting with the WICG thread.

UPDATE: Also, @adrianhopebailie can likely point to other places for discussion.


Would anyone like to collaborate? We have two team members 😭


Hey Bernard! I'm looking for a team :) can join yours? ping me! souzabibiana@hotmail.com


I've sent you a collaborator invite via GitHub.


Are there any special Coil's redeem code for developers that join this hackathon?


We will be providing codes for trial memberships to people who submit a project. Full details coming soon!


Interledger, the protocol, is agnostic to transfer of value whether fiat or cryptocurrency. End user wallets allow the content creator to decide in what they would like to be remunerated in. Today a few wallets are available as options to creators. More wallets are coming increasing the payment options available.


Thanks for the clarification. Hopefully some BTC wallets get in there soon.

With more usage of the standard and protocol — that is indeed the aim.

UPDATE: @wagslane

Uphold has just become the latest Interledger (ILP) enabled wallet. This introduces a whole number of Payout and Withdrawal currencies.

More information can be located within the Web Monetization documentation.


hello all i didn't so much after reading this
but I get few things we have to create app related to blocking ads or things like buy me coffee
if anyone can elaborate me this hackathon concept that will be helpful thank you


Thank you Ben for sharing this with us, I think I will give this a try even though I have never participate in hackathon before


The only 2 hackathons I ever did, were both won with monetization/valuestream projects.

I don't have much time, though. If anyone wants off-the-wall-dude-are-you-****ing-with-us-again ideas, though, I'm open for business monetizeness.


If anyone wants to come along and support, chat, and or laugh at my attempts to code node.js then I'll be live streaming the coding of my hackathon entry at 2pm BST today: dev.to/hammertoe/live-coding-my-de...


Hello! I'm a little bit confused about the Web Monetization API.

When do you pay? How do you add funds?

It's only session based from what I read, does that means that every time I hit reload on a website with monetization I'm paying them more money?

Can I decide which websites I pay or the default configuration is just "pay everyone some money"?

I'm trying to understand how people wouldn't abuse this system if it automatically pays the website with the meta tag.


Hi Jayver,

The Web Monetization API pays based on time using 'streaming payments'. Rather than sending one large payment when you load the page, Web Monetization works through many tiny micropayments, sent each second that you spend on a web monetized page.

The default configuration is to pay everyone some money, but the amounts are small and based on time so a site can't just siphon off all your funds. The rate that Coil pays, for example, is $0.00001 per second. If a tab is not visible then it won't be paid, to prevent payment from occurring while the user's attention is not on the page.


if anyone is looking to join a team, ping me here! We have a team of 3 as of now with a couple of ideas to work with.