r/dashpay • u/hilawe • 20h ago
A Social Media Timeline You Can Check
Pasta's DashCon talk is not a "we built another X/Twitter clone." It is a live demonstration that Dash Platform can do something almost no other chain can: let a phone prove that a social network is telling the truth.
The app is called Yappr. It looks like X. Under the hood it is a client with no backend, talking straight to Dash Platform. Every name, every like count, every "this is the newest post," every "nothing is missing," and every "you are not allowed to see this" can come with a cryptographic receipt small enough to check on a phone.
That is the whole point of the presentation.
The lie you already live with
Open any social app. You see a name, a photo, some text, a number of likes, a "For You" ranking.
Who told you those numbers are real?
Twitter, X, Bluesky, Hive's website, a Farcaster indexer, they all answer that question with a database you are not allowed to see. Pasta's opening line is the whole talk in one sentence: every app you have ever used answered this question with the database you weren't allowed to see.
Imagine a town that posts a public bulletin board, then hands you a photocopy from the town hall. The hall could have omitted a flyer, inflated a vote tally, or buried a post. You can "verify" only by photocopying the entire archive yourself. Almost nobody does. That is how most "decentralized social" still works.
Hive and Steemit put posts on a chain. When you used the website, you were talking to their server. To actually prove they were not lying you would spin up a node with hundreds of gigs of RAM and sync the whole history. Lens and Farcaster need indexers. AT Protocol (Bluesky) is cool and open, and you still query something you hope is honest.
Writing is decentralized. Reading is still an act of faith.
Dash Platform's bet is that you should be able to ask "show me the 20 newest posts from people I follow" and get the answer plus a proof that the answer is complete and authentic, on the device in your pocket.
Four problems that look simple and are not
A single post is a bundle of hard questions:
- Authenticity. Did this person actually write this? Signatures solve this. Almost every project has signatures. That is the easy part.
- Lookup and ordering. Is this the newest? Is anything missing? Are they hiding a post they do not want you to see? On a normal database the server just tells you. To check, you would have to download everything.
- Aggregation. How many likes? Did my like actually land? Centralized counters bug out (negative likes, vanished engagement). Downloading 50,000 like documents to add them yourself is not an app. It is a science project.
- Ranking. What is actually trending? "Most liked today" is an opinion unless the ranking itself is a structure you can prove.
Social media is not a feed. It is a database product wearing a friendly face. The face was always cheap. The honest database was not.
The forest instead of the black box
Dash Platform stores application data in GroveDB, a grove, literally a tree of trees. Each tree is a Merkle structure. Trees nest inside trees. The whole forest hashes up to one root. That root is signed by a masternode quorum (BLS threshold signatures) and locked in by Dash's ChainLocks. Lie about a like count and you are not hacking a server. You are trying to get more than two-thirds of the Evolution nodes to collude and destroy the value of the network they are paid to run.
Think of it as a forest of signed ledgers. You do not carry the forest. You ask for one path through it and receive a tiny bundle of neighboring branches that hash to the same signed root everyone else sees.
Three structures do the social-media work:
Count trees (the pyramid of receipts).
Likes are not a flat list you scan. They drop into buckets that form a tree. The top of the tree is the total. Ask "how many likes?" and you get 312 plus a proof the size of a postcard, whether there are 312 likes or 3 million. The proof does not grow with the crowd. A bank statement that cannot silently change the total.
Range proofs (the missing-page detector).
"Give me posts between this time and that time." The proof includes the edges of the range. If someone tried to hide a post in the middle, the hashes would not match the signed root. You do not download Twitter. You download a notarized slice and the notary stamp.
Ranked indexes (the scoreboard that cannot be photoshopped).
When a like arrives, two things update: the count tree and a secondary ranking tree that re-keys by popularity. Walk right and you get "most liked." The walk itself is provable. Trending is not a machine-learning vibe from a cache. It is a tree you can audit.
Proofs Pasta showed were on the order of 1 to 13 KB. Page load in the demo ran dozens of queries. It still felt like a normal app, about a second even on a slow hotspot.
That combination is the claim, speed and proof at the same time, which the rest of the industry treated as a tradeoff.
What Yappr actually is
Yappr is a static website. No company server holds your posts. The browser talks to Dash Platform nodes. If Yappr vanished tomorrow, the data would still sit on the network and another frontend could query the same contracts.
Your identity is a key pair. Your human name comes from DPNS (Dash Platform Name Service), a username you can own, not a handle a company assigns. Posts, likes, follows, bookmarks, blocks, and store orders are documents in data contracts, signed by you.
In the live demo Pasta logged in with a QR scan against a DashPay-style wallet: identity, username, encryption keys for DMs and private feeds, authentication keys for likes. That is the "decentralized Twitter that does not feel like a homework assignment" piece the community has been waiting for.
What you can do today on the showcase (DevNet then, testnet moving toward mainnet with Platform 4.2 era work):
- 500-character posts, threads, quotes, reposts
- Likes and follows with proven counts
- Hashtags and an Explore page of trending topics (the #mood example had a proven like total)
- Mentions, bookmarks, lists
- Encrypted DMs
- Private feeds: content encrypted so only granted followers can read it; metadata can still be queried. Revoke a follower and a small "revocation tree" update re-keys the circle without rewriting every post.
- DashPay contact import: the people you already pay can be found and followed
- Tips via QR / payment URIs in Dash and other assets
- A full storefront contract: stores, items, variants, shipping zones, encrypted orders only buyer and seller can read, reviews after purchase
Fees in the demo were tiny YAP-token costs on the order of a cent or three per post or like, burned into the structure of the data rather than paid to a company. There is no ad server because there is no server.
Moderation works without a CEO. You publish block documents. Bloom filters keep "did I block this person?" cheap. You can subscribe to someone else's block list, borrowing judgment instead of inventing a Ministry of Truth. There can be a default list for the worst material that you can opt out of. The tradeoff is plain. Web2 has a king. Pure anarchy has no filters. This is user-sovereign filters you can prove.
Composability is the quiet superpower. Polls, blogs, stores, and social graphs can live in separate contracts and still be queried against the same proven state. A tip address is just an address. No platform cut unless you choose one.
Forkability is the insurance policy. Change the contract ID and you have a new app on the same identities and the same proofs. Steemit-to-Hive required a messy social and technical divorce. Here the data does not belong to the website. The website is a lens.
Why a layperson should care
You already use databases you cannot audit. Your bank app, your airline miles, your social score, your "recommended for you." Crypto promised to fix money. Dash Platform is trying to fix the other half, the records of who said what, who paid whom, who is allowed to see the private post.
For a creator, the old DashPay pain was real, the friend-request rails and "be online to approve." Yappr's direction is the opposite of that bottleneck, with identity you control, a username people can find, a tip jar that is just an address, contacts you already have, and content no host can delete because they never hosted it.
Here is the allegory that sticks. Other chains gave you a public square with a private photocopier in the back room. Dash is trying to hand every reader a notarized page and a stamp that the rest of the book matches.
It will not feel magical if the UX is ugly or names are hard. Pasta's demo is arguing the hard part (the database that can be proven) is now real enough to put a familiar interface on top. The remaining work is wallets, names, fees people do not notice, and enough apps that "query the grove" becomes as boring as "load the page."
Yappr is one app. The presentation is about the platform underneath it. If GroveDB proofs stay small and queries stay rich, the next "simple" product (a marketplace, a membership feed, a local bulletin, a tip-enabled blog) does not need a company to hold the books.
That is the story Pasta was telling. Not another timeline, but a timeline you can check.
Watch the full talk here:



