A consumer app that already has users holds the scarcest asset in a DePIN launch, and the job is to turn some of those users into active wallet holders without breaking the product or its store listing. In the case this guide is built on, an app with 200M downloads and 3M monthly active users reached roughly 0.5M monthly active wallets, about ten per cent of all active wallets on its host chain. The order of decisions is what got it there.
Who decides this
The CEO owns this decision, because it changes the product, the legal entity map and the brand at the same time. The CEO is accountable for three outcomes: the app’s existing users are not harmed, the token has a job inside the product, and the first year of distribution is planned before launch rather than bought after it.
Delegate the workstreams, not the decision. Product, legal, tokenomics and marketing each have a lead, but only the CEO can trade one against another. In the case below, the work ran end to end, from entity setup and crypto integration through to launch and distribution.
What should the token reward, and who earns it?
Reward a contribution the network can verify, made by users who already use the app; do not reward installs, referrals or social posts. A DePIN token earns its place when it pays for something the network needs, such as coverage, data, bandwidth or compute, and the app is the tool people use to supply it.
That design choice is also a distribution constraint. Apple’s App Review Guidelines (opens in new tab) say crypto apps may not hand out currency for tasks such as downloading other apps, getting others to download, or posting to social networks. A reward loop built on referrals is therefore a store-listing risk as well as a quality problem.
The regulatory picture is moving, but it rests on facts, not labels. In September 2025 the SEC’s Division of Corporation Finance told DoubleZero (opens in new tab) it would not recommend enforcement if certain programmatic transfers of 2Z, as described in the request, went unregistered. The staff stressed that the position rests on the representations in the request, that different facts could change it, and that it states no legal conclusion.
What we would do: write down what the token pays for in one sentence, then ask counsel whether the reward mechanics match that sentence. If they do not, change the mechanics before launch, not after.
Where should the wallet live?
Put the wallet where the user already is, inside the app, unless store rules or licensing make that impossible in a given market; every extra step to an outside wallet loses users you have already paid to acquire. The trade-off is that an in-app wallet brings the app’s store listing into scope.
Apple’s guidelines set the boundaries for an iOS app. Wallet apps must come from developers enrolled as an organisation. Apps may facilitate crypto transactions only on an approved exchange, and only where the app holds the licences to do so. On NFTs, an app may show users their own tokens, but owning an NFT may not unlock features inside the app.
The three common designs differ on friction, store exposure and what you can honestly report.
| Wallet design | User friction | Store and licensing exposure | What you can report |
|---|---|---|---|
| Embedded wallet inside the app | Lowest; sign-up flows straight into the wallet | Highest; wallet and transaction features sit inside the listed app | Wallets created and monthly active wallets, tied to app accounts |
| Connected external wallet | Highest; users install and fund a second app | Lower for the app; the wallet provider carries more of it | Connected wallets only, which excludes users who never connect |
| Off-chain balance, claimable later | Low at first; friction moves to the claim step | Depends on what the balance can be used for and where | Balances, not holders, until users claim |
Our view: for an app with millions of monthly users, the embedded wallet is usually right, provided the feature set is cut to what the store rules and the company’s licences allow in each market. The off-chain balance looks safer but defers the hard question to the claim day, when attention is highest.
Which chain, and which launch venue?
Choose the chain where your users would be a large share of the active base, because that makes you a partner the chain and its leading venues want to work with. A consumer app is a distribution asset for an ecosystem, and the terms you get reflect that.
The case fits that pattern. Alongside reaching about ten per cent of all active wallets on its host chain, the result included a Launchpad partnership with the chain’s leading DEX. That is a different negotiating position from a new team asking for a listing.
The trade-off is concentration. Being a large share of a small chain makes you important to it and dependent on it. Being a rounding error on a large chain gives you liquidity and tooling but little leverage. Decide which risk the company would rather carry, and write it into the plan.
What entity issues the token, and when?
Set up the issuing entity and its disclosures before the token design is final, because the entity decides which rules apply and in which markets the reward can be offered. Structuring itself sits with counsel; the strategic decision is sequencing.
The EU shows why the details matter. Under MiCA (opens in new tab), several white-paper obligations do not apply to offers made to fewer than 150 persons per member state, or worth no more than EUR 1,000,000 over 12 months. Article 4 also lifts the offer rules for tokens given away free and for tokens created automatically as a reward for maintaining the ledger or validating transactions. An offer does not count as free if recipients must provide personal data in exchange.
Whether a reward for supplying a physical network service counts as a reward for maintaining the ledger is an open question for counsel, and this guide does not answer it. Do not assume the exemption covers a DePIN reward. Put the question to the legal opinion and record the answer.
How should the launch fit the app’s release cycle?
Ship the wallet and the reward mechanics in an app release before the token goes live, so users meet the product before they meet the price. A DePIN launch that arrives as one big-bang update asks millions of users to learn a wallet, a reward and a market on the same day.
We would stage it in three steps. First, a release that creates wallets quietly and records contributions without a tradable token. Second, a claim window for an engaged cohort, with support staff and incident plans ready. Third, the public launch, once the claim flow has run at scale and the store review has passed.
The trade-off is speed. Staging adds weeks, and the market may move in that time. But a failed claim day at consumer scale produces support tickets, store reviews and press coverage that outlast any token cycle. For an app whose core business is not crypto, protecting the existing product is worth the delay.
Assign one owner for the release plan who sits across product and the token workstream. Where those teams report to different executives, the launch date becomes the place where their plans collide.
How will you know it is working?
Measure monthly active wallets against monthly active users, not downloads; downloads describe the app’s past, while wallet activity tells you whether the network has users. The case reports all three: 200M downloads, 3M MAU and about 0.5M monthly active wallets.
The metric that matters is a share: how many real users also act on-chain each month. Track it from the first release, using the same definitions of “active” for the app and the wallet.
Set the targets before launch. Decide what share of monthly users should hold an active wallet at three, six and twelve months, and what the company will change if the share stalls. A DePIN launch without that target tends to be judged on the token price, which the company does not control.
What goes wrong: distribution left to chance
The failure for a consumer app is assuming the install base is the distribution plan. The app has millions of users, so the team expects holders to follow. The token launches, a banner goes up, and a small share of users click through.
The gap gets filled with incentives. Campaigns pay for wallet creation, quests and referrals, some of which the store rules forbid. Wallets appear while the budget runs and go quiet when it stops. The headline number is wallets created; the number that matters, monthly active wallets, barely moves.
The warning signs show up in the plan, not on launch day: no target for active wallets as a share of users, a reward tied to tasks rather than network contribution, and no named owner for the in-app wallet experience. Fix those three before anything else.
How Alcyone approaches it
Alcyone treats a consumer app’s DePIN launch as one programme, run by one team across its service areas. In the DePIN engagement, its partners ran a full incubation end to end, from entity setup and crypto integration through tokenomics, launch and distribution through TrustSwap’s platforms. The situation, the work and the result are set out in Alcyone’s published advisory engagements (opens in new tab). There is no obligation to use TrustSwap products.