Overview
0xSlots is a property primitive for scarce onchain assets, based on a Harberger-tax-style model.
It introduces slots: onchain positions that are always priced and always contestable.
Each holder sets their own price and pays an ongoing fee based on that self-assessed value. But that price is not just informational, it is a standing sell offer. Anyone can buy the slot at that declared price, at any time.
- Set the price too high, and the ongoing cost becomes expensive.
- Set it too low, and someone takes it.
- Set it fairly, and you keep control.
This creates continuous pressure toward fair pricing and productive ownership. Passive property becomes costly to hold, while valuable positions tend to flow toward the people who value them most.
Revenue can be directed to a creator, community, protocol, or public good, turning scarce digital property into an ongoing source of aligned revenue instead of idle control.
How it works

Think of it like Splits but for collective ownership.
Slots
Slots are smart contracts that are single use & immutable by default.
- They fund one recipient
- Use a single currency
- At a tax percentage (optionally mutable)
- Implement a single module (optionally mutable)
If you want a different configuration, just deploy another.
Slots hold a minimum deposit of currency (defined at launch by the user, protocol minimum: 1 day) that is the source of tax collections (which can be triggered by anyone). At creation you can also define a bounty % of the tax being collected to incentivize liquidations.
Modules
Modules are what can bring extra value to a slot.
They're smart contracts that implement custom logic and are triggered by slot events (ownership transfer, price update, release).
They can also require a cut of the tax revenue a slot generates through feePercentage() & feeRecipient().
Conclusion: Slots as Fertile Ground
A slot starts empty. It's a position — nothing more.
What makes it valuable is what the developpers do with it. Modules attached to a slot define the rights it grants: ad space, access, governance weight, revenue share, anything. The slot is the plot; the module is the crop.
Each slot becomes a small, bounded space of productive ownership. Not a walled garden you lock people out of — a public garden you tend. The market decides if you're tending it well enough to keep it.
This is the primitive. What grows on it is up to you.
Quick Links
- Getting Started — Install the SDK and create your first slot
- Protocol — Architecture, tax system, roles, and modules
- SDK Reference —
SlotsClientAPI - React Hooks — wagmi hooks for React apps
- Contracts — Addresses and ABIs
- Subgraph — GraphQL queries