Please describe your proposed solution
Subbit.xyz : Cardano's featherweight L2
+ Security guarantees of the L1
+ Instant settlement
+ Absolutely tiny footprint
The user journey goes like:
- Alice runs a service and wants it to be financially sustainable
- Bob wants to use Alice's service
- Alice sees Bob's account on-chain, and is happy to serve Bob
- All the while Bob is supplying Alice IOUs, Alice serves his request, all is well
- When Alice needs to pay her server bills, she submits the latest set of IOUs (from Bob, Charlie, …) to the L1
- When Bob wants, he can close the account
- After the final claim or some pre-agreed time frame, Bob can withdraw the remaining funds
Components:
+ Smart contract
+ Tx-builders
+ Spec, SDK, & How-To docs on wrapping any existing service in subbit
+ Demo application
+ Hosted instance of demo
"… But why not hydra?!" we hear some of you ask.
Subbit is premised on the observation that most on-going service engagements are unidirectional two-party : someone provides a service, and someone consumes the service. And normally the consumer pays for it.
Subbit is an L2 that models this. Just this.
Because subbit is focused, it's featherweight. No need for persistent network connection. No mutli-sig. No need to port a plutus VM to a new device. A subbit account costs bytes of storage to the consumer and the provider. If the device can sign and send a message, it can run subbit.
Your arduino can run subbit. Your minimal spec cloud VM can run 100,000s of channels subbit. Reasoning about subbit is simple because subbit is simple.
Subbit is not a hydra replacement. They are both L2s, and that is the end of their similarities.