Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Web Monetization @ Solid

Discussions about Solid + Web Monetization

Linking to a Payment Pointer

You can link from a WebID to a payment pointer using the ilp:InterledgerPaymentPointer class.

You can link from a pod to a payment pointer using a Vanity Payment Pointer.

Requiring Payment for resources

You can require payment for access to a resource using the acl:PayingAgent class.

The WAC spec doesn't prescribe specific http response codes, but a server could inform the client that paying could help to get access by responding with 402 Payment Required and including a Pay http response header, with payment instructions.

A 402 would probably take preference over a 403 response when access is forbidden for the currently authenticated agent, but not for paying agents. But a 402 would probably not take preference over a 401 response.

We identified two approaches for access control: "guest list" and "tickets". In the "guest list" approach, the server looks at some log of payments, and checks whether a payment has been made that would give the current WebID access to the current resource. This is the approach that is now implemented in NSS and tested by the (experimental) monetization tests.

In the "tickest" approach, the client would send an additional http request header containing a verifiable credential, that proves their status of paying agent. This approach is currently blocked on W3C-VC support in WAC.

Projects (formerly

Tani Olhanoski and team, USA

Creating an open source Solid application that will let users easily publish, create, and monetize custom pages showcasing writing, music and video content hosted in their Solid Pod at a domain of their choosing. Existing platforms that allow users to monetize their content require either the skills and capitalization to maintain custom web infrastructure or a willingness to let a third party become a steward of both content and data about content creators. will provide a new option for users who would like to maintain full sovereignty over their content and monetize it without running a web server. Building on top of Solid and Web Monetization means that users will be free to move their content off of itme without interrupting the monetization of their content. In addition to Tani, the team includes Ian Davis and Travis Vachon, and is advised by Dr Dédé Tetsubayashi and her team.

Progress report: and:

Monetizing the user-centric read-write web with Solid

Michiel de Jong, Netherlands

(See WebMonetization Community)

Enabling Web Monetization by default in all open source implementations of the Solid pod server specification. Also, making changes to Darcy Social, a Solid-based social space, so that payments end up at the actual creator of the content that is being viewed, even if it's embedded in a newsfeed.

Progress report:

Web Monetization for Solid based Data Spaces

Ontola & Dexes

(See WebMonetization Community)

Standardizing the agreements for conditional data sharing between data owner and data user to allow Solid Pod owners to monetize their data. Pods re-decentralize the web by giving people a way to store their data, and make it available to others while keeping full data ownership. Interledger offers a perfect solution for micro-payments without the need for complex and centralized payment providers.

Combining ODRL + Interledger.

Grant report:

Reciprocal ecosystem for decentralized health-data

Gijs van den Beucken & Ontola

Researching and building a proof of concept as a first step towards a new financial and data ecosystem combining Solid Webapps, Solid Pods, and Web Monetization. Users will pay webapps to access supportive health webapps and process and store their data on their Solid Pod. Researchers get access to data of the user’s Solid Pod and pay the user for the data, with respect for privacy and consent. This will support health improvements on both a personal and community level, will give people control over their data, and will simultaneously nourish academic research institutes with data from more diverse groups.

Grant report:

Incentivizing Decentralized Application Development within Solid through Web Monetization

KNoWS/IDLab – imec

The Solid decentralization effort decouples data from services, so that users are in full control over their personal data. Since services can not primarily depend on data collection as a primary business model anymore, alternative forms of monetization, such as micropayments via Web Monetization are essential for incentivizing application development.

See for more information.

Monetising Resources on a SoLiD Pod Using Blockchain Transactions (ESWC Demo)

Hendrik Becker, Hung Vu, Anett Katzenbach, Christoph Braun & Tobias Käfer, Institute AIFB, Karlsruhe Institute of Technology (KIT), Germany

Abstract. Our demo showcases a system that allows users to provide access to web resources in exchange for payments via the Ethereum blockchain. The system enables users to create offers for their resources or buy access rights for resources belonging to other users. Access rights can be granted only for a limited amount of time. We built our system as SoLiD Pods and Apps: We developed two server modules for SoLiD Pods that automatically (1) grant access for valid payments via the blockchain and (2) remove expired access rights. On top, we developed a SoLiD App that allows to offer resources, browse and request offered resources, and make payments via the blockchain.

Resource URI
Teaser (1 min)
Demo Website (inkl. 3 min video)


Discussions about Solid + Web Monetization







No releases published


No packages published

Contributors 4