Introducing OnchainSuite

For a long time, one thing about web3 never sat right with us. You can see everything your users do. Every deposit, every swap, every stake and unstake, every position opened at 2 am, all of it public and permanent and sitting right there on-chain.

And then, at the exact moment it matters, you can do nothing about it. The wallet that just pulled its liquidity is a string of characters, not someone you can reach. So you watch, and you wait, and more often than not you watch them go.

That gap is the reason OnchainSuite exists.

OnchainSuite is the communication and retention layer for web3. Put plainly, it lets a protocol respond to what a wallet actually does. A user acts on-chain, OnchainSuite notices, works out who to reach and how, and sends something that fits the moment.

It is the same loop every other industry has taken for granted for decades: a customer does something, you notice, you respond, finally built for web3.

The first decision we made shapes everything else: the wallet is the identity, not the email. For years, the unwritten rule in web3 marketing was that a user only counted once you had matched their wallet to an email address, which meant most of your users never counted at all.

We flipped that. A wallet is a real, reachable user from the first block, and email becomes one channel among several, attached to the wallet when it exists and simply absent when it does not. You stop waiting to collect emails before you can do anything at all.

That opens up the thing we care about most, which is reaching people where they already are. The channel we lead with is in-app push, for a simple reason. It needs nothing but the wallet address that is already in your dApp session, so it reaches every connected wallet, with no email, no domain warm-up, and no waiting.

Your team drops in a small SDK, and when a wallet does something worth responding to, OnchainSuite pushes a message that shows up right there in the app. Email is there too, live through a privacy bridge for wallets that have linked an address, and Telegram, Farcaster and X are on the way.

The idea is that one trigger fans out to whichever channels a given wallet can actually be reached on. You define the behavior once, and we handle where it lands. We also did not want to hand you a blank canvas and wish you luck. Most people do not want to design a churn flow from nothing; they want a good one they can adjust.

So OnchainSuite ships with a library of pre-built automations for the situations every protocol runs into: welcoming a first deposit, winning back a wallet that has gone quiet for thirty, sixty or ninety days, catching a staker the moment their unbonding cooldown ends so you can nudge a restake instead of a walk, reminding holders who have not voted yet when a proposal is short of quorum and running out of time.

Each one arrives already wired with a trigger, a sensible default segment, and copy you can edit. The starter plays work from day one on any protocol with the basic primitive, a deposit, a stake, a wallet. The more involved ones wait until you have the data or the structure to justify them. You fork one, tweak it, and you are live.

We rebuilt the first ten minutes completely, because that is where most tools lose you. You connect your contracts, we index the last ninety days of activity in the background, and before you have built a single campaign you see one specific, useful thing about your own users.

Something like: 142 dormant LPs from the last month, median lifetime deposit around $4,200, and 38 of them also active on Aave. One real insight, no setup, in about the time it takes to make coffee. It all runs on normalized on-chain data, so a deposit reads as a deposit whether it happened on Uniswap, Aerodrome or Jupiter, across Ethereum, Solana, Base and Polygon.

We also thought about the newest protocols, the ones that have not been around long enough to have much history yet, since those are often the teams most willing to try something new. If you are a few weeks old with a hundred wallets, a report about your past does not tell you much. So for those teams, the first insight looks ahead instead of behind.

Rather than summarizing what already happened, it points to what is about to happen: which of your early wallets are coming up on the age where users like them tend to go quiet, and which play to set up now so you catch them before they drift. Even on day one, that gives you something you can actually act on.

A word on privacy, because it is built into the foundation rather than bolted on afterwards. Wallet addresses are already public, so building on them changes nothing there. But the moment a regulated channel is involved - an email, an X handle, anything that counts as personal information - that link is bridged with zero-knowledge proofs.

We can confirm that a wallet belongs to a given contact without holding their personal data in a way that exposes it. It is opt-in for the user, and it is compliant by the way the system is built rather than by a policy we ask you to trust.

Now the honest part. Retention will not save every user, and OnchainSuite will not pretend otherwise. Some capital only ever chases the highest yield, and no message, however well-timed, will talk it out of leaving. Incentives still have their place too, for the users who genuinely respond to nothing but a number.

What we are after is the large group in the middle, the people who would have stayed for a reason and a nudge at the right moment, the ones you have been quietly losing because you had no way to say a word to them. And we are early.

OnchainSuite is in early access; we are building it in the open, and the protocols joining now are shaping what it becomes. Underneath all of it is one simple loop we think web3 has been missing.

Notice what a user does, work out who they are and what they need, reach them on a channel that actually lands, and measure whether it worked. Detect, segment, message, improve.

That loop is the whole reason Web2 companies can hold onto their customers, and it is the thing Web3 never had the plumbing to run. We built the plumbing so that when your users act on-chain, you can act back.

If you are a protocol tired of watching good users leave with no way to reach them, we would love to have you in early access. Come build the loop with us!