Most on-going service arrangements are "unidirectional" "two-party": someone provides a service, someone consumes the service, and the consumer pays the provider.

Subbit.xyz is an L2 that models this. Just this.

Because Subbit.xyz is focused, it is featherweight 🪶. There's no skimping on security: The Subbit.xyz smart contract keeps both parties safe from foul play.

Bob runs an API service. Alice wants to use it. Alice opens an subbit account by locking ada up at the subbit smart contract. Bob spots the new account on chain. Now when Alice uses the API, Bob knows the request is coming from Alice, and that Alice is a paying customer.

Alice doesn't pay immediately. The transaction fees would be too high, and too much latency for a usable service. Instead he hands Bob verifiable IOUs. When Bob needs to pay his server bills, he sumbits the latest IOU to the L1 and claims what he's owed. In fact, Bob can settle many accounts in a single transaction.

When Alice decides she no longer wants to use Bob's service, she closes her account. Bob sees this, and makes his last claim. Alice can then retrieve the rest of her funds.

It is a lot of effort and expense to make applications that are decentralised and permissionless. We do it because we think its important - a little power in many hands is better than a lot of power in only a few.

Blockchains/ L1s provide robust infrastructure on which to base dapps, but they rarely provide a great context for executing all aspects of an application. For example, transactions on a distributed ledger are relatively slow and expensive.

Instead dapps can be designed so that some kernel of integrity runs on an L1, while the rest of the application functionality happens "off-chain". This kernel of integrity is the logic that keeps dapp users safe from one another. Designing applications in such a way can be a complicated exercise, and componded by additional implications such as "what happens if there's a rollback on the L1".

Taking an off-the-shelf L2 with a design tailored to the use-case can greatly simplify the process. Subbit.xyz is designed for subscribtions services. Using Subbit.xyz is highly efficient way to turn a service into dapp that is financially sustainable.

It's a great idea! Where do I start?

If you think that Subbit.xyz is a good fit for your project, then please reach out via a github issue.

To get an idea of the feature set, check out our demo. It's just a slide show but you can get the gist.

We are pumped that Subbit.xyz's Project Catalyst F13 bid was successful. Thanks to all those who have supported the project to date. As a result, work on Subbit.xyz has begun in earnest.

Updates are periodically posted on the blog pages [TODO].

Subbit.xyz is developed Kompact.io.