Shielded balances are only the beginning. STRK20 opens a wider design space for payments, payroll, trading, governance, games, treasury tools, and future app flows on Starknet.
It does this by making shielding a normal crypto action, and shielding is what closes the leak. Public chains do not only expose balances. They expose relationships, timing, strategy, participation, and intent. Often the real leak is not the asset itself but the story around it, and shielding is what keeps that story private.
It does this by making shielding a normal crypto action. That matters because public chains do not only expose balances. They expose relationships, timing, strategy, participation, and intent. Often the leak is not the asset itself, but the story around the asset.
So the real builder question is what becomes possible when privacy creates a hidden interval inside an ordinary workflow. A team can run payroll without publishing salaries. A donor can back a cause without making that support a permanent identity marker. A trader can act before the market reads the position. A game can keep the answer hidden until the round is over.
Any supported ERC-20 asset can be shielded, used in private flows, and unshielded as the same asset. That keeps privacy usable where crypto already happens, instead of pushing users into a separate stack or a destination they have to go out of their way to reach.
Why Starknet? Because it gives builders more room to build, and privacy is part of that. Starknet settles with STARK proofs, and zero-knowledge privacy is built from those same proofs, so shielding is the network doing what it already does rather than an expensive layer bolted on. Account abstraction folds it into normal wallet actions. The result is the part that matters: private flows that work where crypto already happens.
What can you build when privacy is a property of the workflows people already use? Below are 11 examples: 7 products you can explore today, and 4 emerging areas where privacy could open up the design space.
Products you can build today
1. Private Transfers And Payment Links
The Problem
The simplest crypto action is still too revealing.
Send someone money on a public chain and the payment can expose the sender, receiver, amount, timing, and surrounding wallet history. For a basic transaction, that is a lot of extra context.
What To Build
Private payment links, invoices, and peer-to-peer transfers that feel like normal wallet actions.
A user should be able to send a private payment without understanding the privacy protocol underneath it. Before private DeFi or private games, there is the basic need to pay someone without publishing the relationship.
Why STRK20 Matters
STRK20 enables supported assets to move through private transfer flows without forcing users into separate privacy assets or specialist workflows.
The point is not to create a new private-money silo. It is to make privacy a normal action for the assets people already use.
2. Private Payroll And Contractor Payouts
The Problem
Payroll is an easy place to see the problem.
On a public chain, compensation can become exactly that: public. Every recipient, amount, and payment rhythm is visible by default. That may be tolerable for a bounty campaign, but it is much harder for a company, DAO, or contributor network that wants to pay people without turning compensation into a public record.
What To Build
A payroll product that lets teams send assets privately while still supporting accounting, reporting, and selective disclosure where required.
The thing to build is the payout workflow, not the private balance itself. The team wants to pay people without publishing the org chart.
Why STRK20 Matters
STRK20 gives builders a way to make private payouts feel like a normal asset flow.
For organizations, the value is not secrecy. It is controlled visibility: confidential from public view, but still able to support the operational needs that real teams have.
3. Private Claims, Grants, And Donations
The Problem
Public support has an awkward onchain problem.
This is true for public goods, ecosystem grants, airdrops, charitable campaigns, and sensitive support. The total can matter. The recipient can matter. The fact that support exists can matter. Making every claimant, donor, amount, and timestamp public changes the social meaning of the act.
What To Build
A claims-and-donations platform that shows aggregate participation while giving individual users more control over what they reveal. A user could prove eligibility, claim support, or back a cause without turning that action into a permanent public identity marker.
Why STRK20 Matters
STRK20 makes it possible to design participation flows where exposure is not the price of entry.
The product does not need to market itself as a privacy app. It can simply be a better claims, grants, or donations product because it gives users more control over visibility.
4. Trade Obfuscation Tools
Markets change when everyone can see the trade before the trade is over. Active traders, and DeFi participants often have a concrete reason to hide what they are doing. They may not want copy-traders following them, competitors reading their position, or social observers calling them out before an outcome settles.
The product is not simply a hidden trade. It is a market action with less strategy leakage. A user could take a position without immediately tying it to a public wallet, a visible pattern, or a reputation they do not want dragged into the trade. The more ambitious version starts to look like private market structure, where order flow, position-taking, and intent do not become public signals before execution completes.
STRK20 creates a private interval inside normal asset movement. The trade still happens through existing market structure, but the public does not get the same clean read on the actor behind it. The real product is the ability to act before the market reads you.
5. Private Swap And Portfolio-Rebalancing Interfaces
Swaps do not only move assets. they reveal decisions. When a user exits one position, rotates into another, or rebalances a portfolio, the public chain turns that move into a signal. Observers can infer what the wallet believes, what it is accumulating, what it is leaving, and how it manages risk.
A STRK20-powered interface could make rebalancing feel like a normal wallet action while reducing what observers can connect back to the user. A concrete version is a rebalance button inside a wallet or portfolio app. The user picks a target allocation, the app routes the trade, and STRK20 keeps the wallet behind the move harder to read. Rebalancing feels like a normal wallet action while observers lose the thread back to the user.
This does not make every part of the swap private. Public liquidity and public protocol state still exist. The win is narrower and more practical: reducing what the public can infer about who is changing strategy.
6. Institutional Treasury Tooling
The Problem
A company’s treasury is not a content feed.
Vendor payments, rebalancing, settlement operations, stablecoin movement, and counterparty relationships can all reveal sensitive business information. Onchain transparency can make normal operations legible to competitors, suppliers, employees, and observers.
What To Build
An operating layer for treasury movement.
Institutions could manage assets with more confidentiality while keeping defined disclosure paths for audit, reporting, or compliance. A first version might look like a treasury dashboard that lets an organization pay vendors, rebalance stablecoins, and preserve an audit trail without making each movement publicly legible.
Why STRK20 Matters
STRK20 fits the actual institutional requirement: confidentiality from the public, accountability to the right parties. Most organizations do not want absolute secrecy. They want to choose what is visible, when, and to whom.
7. Private Lending And Yield Adapters
DeFi positions are strategies, not just balances. A lending position can reveal collateral, timing, risk appetite, leverage, and liquidation exposure. A yield route reveals how a user thinks about risk and opportunity. On a public chain, those signals are easy to inspect and easy to copy.
One buildable object is an adapter that routes private assets into a lending, borrowing, or yield protocol, then returns new private state after the action. A user might deposit into a vault, borrow against collateral, or move into a yield route without making the whole path easy to tie back to their public wallet.
As with swaps, the protocol state can stay public while the actor does not. The win is in obscuring who is moving through the system, and how.
The Emerging Design Space
8. Private Governance For Decentralized Systems
Decentralized systems want public legitimacy. They do not always need public voting dossiers.
Governance often asks people to make choices that attach to their wallet, reputation, employer, community role, or political alignment. When every vote and delegation is permanently public, participation changes. Some people posture, some people abstain, and some people follow the room.
The interesting version preserves public outcomes while reducing public pressure on participants. A voter could prove eligibility and cast privately. The system could publish the result without turning every wallet into a permanent political dossier.
A practical version might start with private delegation, shielded votes for sensitive proposals, or claim-style eligibility proofs for participation. The governance result remains public, but the participation trail is not automatically turned into a social graph.
Governance gets healthier when people can say what they actually think without turning every choice into a permanent public label.
9. Sealed Bids And Private Auctions
Some markets only work if information arrives late.
If every bid is public immediately, the auction changes. Bidders can shadow each other, sellers can infer too much, and competitors can use the process as a signal instead of a market.
Here the mechanism is timing. Bidders commit funds or place bids privately first, then reveal or settle later. A simple product could accept private commitments during the bidding window, reveal the winning result, and settle after the auction closes.
Privacy here is not about hiding forever. It is about making the reveal happen at the right time.
10. Games With Hidden State
A fog of war does not work if every move is public. Secret roles do not work if every role is visible. Strategy games lose depth when inventories, resources, alliances, and plans are exposed by default.
The mechanic is hidden state where token-linked actions could happen privately. Inventories and bids could stay concealed, resources could remain unknown, roles could reveal later, and rewards would not need to point immediately back to a public wallet.
A first product does not need to be a full game engine. It could be a simple onchain game where players commit moves privately, reveal outcomes at the end of a round, and earn rewards without immediately exposing the whole strategy trail.
Some games need hidden information. If the chain reveals every move, role, resource, or outcome, the design space collapses.
11. Private AI Agent Payments
Agent wallets and autonomous payment flows are already starting to appear. The privacy side is the part that still needs to be built.
An agent might pay for APIs, data, compute, subscriptions, other agents, or onchain services. If every payment is public, the wallet can reveal what the agent is doing, which tools it uses, how often it acts, and what the operator may be trying to build.
A private agent-payment product would let software spend without turning every payment into a public workflow map. The operator could still keep records, limits, and permissions, but outside observers would not automatically see every supplier, task, and pattern.
A first version might look like a policy-controlled wallet for an agent. The agent can spend within approved rules, and STRK20 helps keep the payment trail from becoming a public map of the operator’s workflow.
As agents begin to transact more often, the question is what should be visible to the public and what should remain between the agent, its operator, and the services it uses.
The Bigger Point
The best STRK20 apps may not look like privacy apps. They may look like payment links, payroll tools, claim flows, donation platforms, trading interfaces, treasury products, governance systems, auctions, games, or agent wallets. Privacy is not the category. It is the property that makes those categories work better onchain.
That is the promise worth building toward. Not a new token category, not a separate app silo, but practical privacy inside the products people already want to use.
If you are exploring what privacy could unlock for you, STRK20 is a good place to start. Learn more about building private flows on Starknet.
