Revenue splits that actually pay themselves.
Stop wiring Stripe to a spreadsheet and chasing collaborators. Deploy a contract once, give people the address, and every payment that lands gets routed to the right wallets automatically. The chain itself is the bookkeeper.
The problem with how this works today.
Royalty distribution today: someone manually exports a CSV, runs a payroll spreadsheet, wires N transfers, eats the FX spread. Repeat every month.
Platforms (App Store, Spotify, Steam, OnlyFans) take 15-30% before you see a dollar. The collaborator split happens AFTER the platform cut, on whatever cadence the platform decides.
When the music label, the producer, the editor, and the distributor each take their cut, half the trust in the workflow is the lawyer reviewing the contract. The other half is whoever cuts the checks.
Off-chain "splitter" tools (0xSplits, Splice, Songcamp) need a keeper bot to fire the payouts. Chainlink Automation, Gelato — extra surface, extra cost, single point of failure.
How Asentum changes it.
Three primitives that make this category cheaper, faster, and impossible to censor.
Native scheduled execution
Every block, the chain itself walks due jobs and fires them. No external bot. No off-chain orchestrator. Built into the consensus loop. Your splitter contract gets executed on the schedule the contract itself defines.
Stablecoin-shaped value
ASE is an ARC-20 token at the protocol level. Receive payment, distribute by percent, settle in seconds. Composable with any wallet, indexer, or third-party tool that speaks the standard.
Write the rules in JavaScript
No Solidity tax. Your splitter contract is a small JS module any developer on your team can read, audit, and modify. Custom split rules — cliffs, vesting, geo-routing — are 10 lines of code.
What the code looks like.
Plain JavaScript. No new language, no new mental model.
// Deploy a revenue splitter contract.
// Every ASE that lands here is auto-routed by percent.
// Cron fires the distribution every block — no off-chain keeper.
contract RevenueSplit {
recipients = [
{ addr: '0xd1e4…', pct: 40 }, // director
{ addr: '0xb03c…', pct: 30 }, // producer
{ addr: '0x86d0…', pct: 20 }, // editor
{ addr: '0x049b…', pct: 10 }, // distributor
];
// Called by the chain's cron registry every block.
// Distributes the contract's balance per the splits above.
distribute() {
for (const r of this.recipients) {
const cut = (this.balance * r.pct) / 100;
transfer(r.addr, cut);
}
}
}
What you can actually build.
Concrete scenarios builders are already shipping on this primitive.
Music labels splitting streaming royalties between artist, producer, label, songwriter — no quarterly statements, every play, every second.
Indie game studios with a revenue agreement: 40% lead dev, 25% artist, 25% composer, 10% publisher. Every Steam payout splits automatically.
A podcast network with 20 shows, each with 2-3 hosts on different splits. One subscription product, hundreds of correct payments.
A creator collective on Substack-equivalent paid newsletters — 70% to the author of the post, 20% to the editor, 10% to the platform.
OnlyFans-style platforms running creator + agency + manager + platform splits without manual reconciliation.
NFT collectibles with persistent secondary-market royalties — every resale auto-splits to the original artist, the collector who consigned it, and the platform.