Use case · Social

The social graph belongs to the user.

Every profile is a wallet. Every post is a signed transaction. Every follow, every like, every comment lives on-chain. The platform doesn't own the audience; the user does. We ship a working showcase at social.asentum.com — a Twitter-shaped app where deleting your account doesn't delete your data.

social.asentum.com · live feed
@neurenburg
· 2m
0x1b94…7af3
just deployed a revenue-split contract for our music collective. royalties auto-split to 4 people every payout. wild that this is one contract on-chain.
12 likes · 3 comments
@hilsboro
· 11m
0x46d3…863b
spun up an AI agent that wakes itself every hour, fetches papers, summarizes, posts here. it lives on-chain. my laptop is off rn lol.
47 likes · 12 comments
@asia
· 34m
0x9b77…b439
subscribed to a newsletter that takes 5 ASE/month via on-chain recurring billing. signed once. that's it. that's the post.
83 likes · 21 comments

The problem with how this works today.

01

Twitter, Instagram, TikTok all own the social graph. If they suspend you, your audience goes with the account. There is no "export to another platform."

02

Lens, Farcaster, and other on-chain social attempts work, but they live on chains where every interaction is expensive. A like-on-Ethereum is absurd; even a like-on-L2 is friction.

03

Moderation is binary: either centrally controlled (the platform decides) or completely absent (4chan). Nothing in between, even though "in between" is what every healthy community actually wants.

04

Creators have no portable revenue layer. Subscriptions, tips, merch — every category lives in a different walled garden with a different rev-share.

How Asentum changes it.

Three primitives that make this category cheaper, faster, and impossible to censor.

JS-NATIVE

A social contract you can read

Profile, Posts, Follow, Gallery, Votes, Comments — five small JS contracts, fully on-chain, easy to fork. The shape of the network is in code, not in a platform's closed source.

FAST + CHEAP

Likes that cost a fraction of a cent

5-second blocks, sub-penny gas. Every like, every comment, every follow is a signed transaction — and still inexpensive enough to use it like Twitter.

PAY SDK

Native revenue, not "creator monetization"

Tipping, subscriptions, paid posts, revenue-splits-with-collaborators are all just contract calls. The same Pay SDK powers them. No platform middle-cut.

What the code looks like.

Plain JavaScript. No new language, no new mental model.

// A post, fully on-chain.

contract Posts {
  post(body, mediaCid) {
    const id = blake3(msg.sender + body + chain.blockNumber);
    storage.set('post:' + id, {
      author:    msg.sender,
      body,
      mediaCid,
      createdAt: chain.timestamp,
    });
    emit('PostCreated', { id, author: msg.sender });
    return id;
  }
}

What you can actually build.

Concrete scenarios builders are already shipping on this primitive.

01Build

A creator who got banned from Twitter can stand up the same audience on social.asentum.com — the followers list is on-chain and portable.

02Build

A subscription-gated post: 5 ASE to unlock. The contract verifies the payment, the front-end reveals the content. No Patreon middle-tax.

03Build

A community moderation game: post moderation decisions to a Votes contract; collective consensus from token-weighted votes resolves edge cases.

04Build

A "tip jar" contract on every profile that auto-splits incoming tips between the creator and a contributor pool (their editor, their researcher, their friends).

05Build

An invite-only group where membership is gated by holding a specific NFT. The Posts contract checks ownership, the social-app UI hides the feed for non-holders.

06Build

Cross-app reputation: every action on every Asentum-native social app counts toward the same on-chain identity. Your reputation isn't locked to a single product.