Pera Wallet rebuilds on one codebase as its card program resets

2026-08-19

wallet · staking · payments · defi · discovery · web · algorand · updated

Pera Wallet rebuilds on one codebase as its card program resets

The Rebuild That Retired Two Codebases

For most of its life, Pera Wallet built its app twice. Since the wallet's early days — it launched in 2019 as the official Algorand Wallet and was relaunched as Pera in February 2022 — iOS ran on a Swift codebase and Android on Kotlin, so every feature was built, tested and shipped on two separate timelines. On August 11, 2026, the team retired both at once. Version 7.0, per the launch post, 'isn't a patch or a redesign. It's a full rebuild of the app, from the codebase up.' A single React Native codebase — a framework that compiles one app into native iOS and Android binaries — now powers both platforms, the download shrank from 103MB to 67.9MB, and features reach both stores on the same schedule. The consolidation matters beyond download size: for a wallet whose users alone hold the private keys, every future security review now has one implementation to examine instead of two.

The release was not a one-shot. pera-react-native, where all development now lives, shipped v7.0.1, v7.0.2 and v7.0.3 within three days of the announcement and carried commits as recent as August 18, with a 7.1.0 version bump and post-quantum signing fixes landing the following day. The two legacy repositories, pera-ios and pera-android, last saw commits on June 16. The team ran an approval-gated public beta from July at beta.perawallet.app, whose page carried the line 'Powered by Rocca Wallet.'

Algorand's Default Gateway

Pera describes itself as 'the easiest and safest way to store, buy and swap on the Algorand blockchain' — a self-claim worth testing against the record. It is built and maintained by Hipo, the same team behind the Tinyman exchange, and in September 2023 the Algorand Foundation, Borderless Capital, Arrington Capital and DWF Labs invested in 'Algorand's most popular wallet', with the Foundation taking an operational oversight role. The operating company, Pera Wallet LDA, is registered in Lisbon and describes itself as fully remote across eight timezones. The product family spans the iOS and Android apps, the browser wallet at web.perawallet.app, the Pera Explorer block explorer, an [ASA](/glossary/algorand-standard-asset "A built-in mechanism that allows anyone to create and issue new tokens (like stablecoins, utility tokens, or NFTs) directly on Algorand's base layer, ") verification program and a QR-code generator.

Adoption figures put the self-claim in context. Google Play lists 500K+ installs at 4.6 stars across 22.1K reviews, with an update dated August 14, 2026; the App Store shows 7,955 ratings at 4.8 stars. Algorand counted 49.56 million total wallets by January 2026, per the Foundation's Algo Insights report, and the Foundation's 2025 Q4 transparency report called out growth in Pera wallet creation and user retention specifically. It is, in short, the ecosystem's default gateway — which is exactly why the 7.0 rebuild is ecosystem news rather than a routine app update.

Self-Custody Is the Product

The central design decision is that Pera never touches your keys. A wallet holds a public address and a private key, and whoever controls the key controls the assets. Pera's privacy policy states keys are used 'solely for the purpose of signing transactions,' that no personally identifiable information is collected or transmitted, and its terms restrict the service to users 18 and older. The tradeoff is symmetric, and Pera's own terms spell it out: users bear 'sole responsibility for your activities and assume any associated risk of loss.' Lose the 25-word recovery phrase and the funds are gone — no support ticket can restore them. Shared Accounts extend the model to groups: built on Algorand's native [multisig](/glossary/multisig "Short for multi-signature, a security setup where more than one private key is required to approve a transaction. A 3-of-5 multisig means any three of"), where a predefined set of keys must approve before funds move, a 2-of-3 account requires any two designated participants to sign, with pending transactions reviewed and confirmed asynchronously in the wallet's inbox within a 45-minute window — the first time the protocol-level capability reached a consumer-friendly mobile interface, per Genfinity's coverage.

The browser wallet pushes the privacy posture further. Keys are encrypted locally with the [NaCl secretbox algorithm](/glossary/nacl-secretbox-algorithm "A cryptographic method from the NaCl library that encrypts and authenticates data with a symmetric key, used in Pera Web to protect private keys local"), the password never leaves the device, and the page ships with zero analytics or third-party scripts — a deliberate shrinking of the code-injection surface that felled other web wallets (the 2023 compromise of the MyAlgo browser wallet, with reported losses of roughly $9.6M, remains the cautionary tale). The cost is real: no crash reporting or usage telemetry, so edge-case bugs surface through user reports and can take longer to pin down, and Pera Web and Pera Mobile do not sync — moving between them means manual import and export. For larger holdings, all Ledger Nano models can be paired as cold storage, a hardware device that keeps private keys offline. Pera has also added support for post-quantum accounts ahead of the network's roadmap, which introduces multiple concurrent signature schemes in Q3 2026 and targets broad quantum resilience by 2027.

What the Rebuild Ships

The 7.0 feature set clusters around one theme: the failure mode that has cost wallet users across crypto — approving a request without understanding what it does.

7.0 feature	Real-world implication
Account-based home screen with portfolio slider	Holdings at a glance; the chart can be hidden entirely
Balance-impact signing previews	A transaction's effect on the account is shown before approval
Duress mode	A fake PIN opens a decoy account under coercion; shaking the phone closes the app
Native Pera Stake and Pera Fund views	Staking and funding open in-app instead of a webview detour
Global wallet search	One query spans accounts, assets and NFTs — the gallery is searchable by asset ID
3D NFT rendering	NFTs with 3D models display in full dimension
Universal Wallet structure view	The derivation hierarchy behind an account is visible — one 24-word phrase generates up to 50 accounts
Custom network support	Developers can add localnet, betaNet, fNet or other networks in-app
USB Ledger on Android	Hardware wallets connect directly by cable
Consolidated inbox	Notifications, spotlight banners and multisig approvals in one place
iPad optimization	A native tablet layout instead of a stretched phone screen

Beyond the list, 7.0 lets creators of Algorand Standard Assets (tokens issued natively on the chain) sign asset-freeze transactions on demand for assets they issued. The rebuild is also partly built on Rocca, the Foundation's white-label wallet framework — reusable building blocks another team could rebrand into its own product. Pera says 'a meaningful part of this rebuild comes from that foundation,' and Rocca's keystore reached a 1.0 release candidate on August 12; the repo itself still describes the project as a sample onboarding flow with placeholder dashboard UI, so 'built on Rocca' is a direction of travel as much as a finished foundation. One caveat belongs with the momentum: neither the announcement nor the beta posts mention a third-party security audit of the rebuilt app. For a wallet holding real funds in user custody, that is a gap a prospective user should weigh.

Money In: Pera Fund

Pera Fund, launched in January 2026, is the wallet's answer to onboarding friction — the gap between 'download a wallet' and 'hold a balance.' It lets users buy ALGO or USDC directly inside the app, through two very different legs. The fiat leg runs through Meld's [on-ramp](/glossary/on-ramp "A service that lets people convert traditional money (like dollars) into cryptocurrency, often by linking a bank account or card.") API: credit or debit card, or ACH transfer, with identity verification ([KYC](/glossary/kyc "Know Your Customer — a legal requirement for financial services to verify who their customers are, usually by collecting identification documents.")) required and currencies including USD, EUR, GBP, CAD, AUD and BRL depending on region, per Pera's knowledge base. This is the one point where the [non-custodial](/glossary/non-custodial "A system where users retain control of their funds or assets at all times, rather than handing them over to a third party to manage.") posture inverts: a regulated intermediary sits between you and your coins until the purchase lands at your address, and that intermediary can freeze or restrict a transaction.

The crypto leg runs through Exodus's XO Swap: send BTC, ETH, SOL, AVAX, ARB, SUI, ADA, XRP, BNB, HBAR, USDC, USDT or PyUSD to a deposit address on the source network and receive ALGO or USDC on Algorand. No KYC is generally required, but the flow is a bridge in miniature — a third party holds your funds in transit — and Pera's own support documentation warns that sending crypto on the wrong network 'usually results in permanent loss.' Fee delegation in 7.0 softens the entry point: a new user can complete a first transaction even with zero ALGO or USDC.

Money Out: Swap and the Card

On the way out, the in-app swap is powered by Tinyman, the same team's exchange, and the portfolio view is fed by Vestige.fi price data; a March 2025 Genfinity profile of the wallet reported that Pera had eliminated its own swap fee. The most ambitious outbound rail has had a harder year. The Pera Card — a Mastercard-enabled debit card launched May 15, 2025 with Immersve, a Mastercard principal member — let users in the UK, Germany, Italy, Spain and New Zealand spend Algorand USDC anywhere Mastercard is accepted, later expanding to Poland, the Netherlands and Portugal. It was non-custodial by design: the card carried its own wallet address, balances and transactions were visible [on-chain](/glossary/on-chain "Describes transactions that are recorded and permanently stored on a blockchain ledger, making them publicly visible and tamper-resistant."), and funds could be withdrawn back to the wallet at any time without issuer approval. Immersve's CEO Jerome Faury explained the choice of chain plainly: 'We chose Algorand to be the first non-EVM chain supported by Immersve due to Algorand's instant finality, low fees, and robustness.'

Then the partnership ended. Pera's knowledge base announced the Immersve program would close on April 3, 2026: deposits were disabled March 26, cards were deactivated April 3, and users were told to withdraw their USDC during a March 12–April 3 window or have their card account closed out manually. The card page now reads 'Back Soon, Better Than Ever,' with a waitlist for 'the next generation of Pera Card' — more geographies, tighter wallet integration and, per the support article, a new card product 'built closely to the core of Pera.' As of the site's current state, no new provider or launch date is named.

Staking Is Now the Wallet's Core Job

Wallets stopped being storage when Algorand's governance era ended. The commit-and-vote program that rewarded ALGO holders concluded in April 2025 and was replaced by consensus staking rewards introduced with the Algorand 4.0 upgrade — rewards paid by the protocol as each block finalizes, roughly every 2.8 seconds, with no slashing and no lockup. Direct participation requires 30,000 to 70M ALGO, out of reach for most holders, so Algorand's staking page documents four routes, all surfaced inside Pera:

Staking route	Real-world implication
Solo staking	You run the node and earn per block; 30K–70M ALGO required
Delegated staking	A third party runs the node while ALGO stays in your wallet; same 30K minimum
[Liquid staking](/glossary/liquid-staking "A DeFi mechanism where a user locks up a proof-of-stake cryptocurrency (like ALGO) and receives a tradable derivative token (such as xALGO) representi")	Deposit any amount and mint a liquid token (xALGO via Folks Finance, tALGO via Tinyman) that keeps earning while used in DeFi
Staking pools	Combine ALGO via operators like Reti; some pools are [DEX](/glossary/decentralized-exchange "A peer-to-peer marketplace built on Algorand where users can trade ASAs directly from their wallets without relying on a centralized intermediary (lik") liquidity positions that auto-participate in consensus (Pact)

Pera's governance page still lists the Algorand Foundation program, Folks Finance and Messina — the latter an auto-compounding vault — and its support documents are blunt that the old vote-and-earn program is over. The risk note belongs here: staking through Pera means handing ALGO to third-party protocols, and Pera's own staking disclosures frame them that way — the wallet provides access to third-party staking services but does not custody or guarantee the staked assets. A failure in a liquid-staking or vault smart contract is a loss no wallet can recover.

The Developer Side of the Same Release

The rebuild shipped alongside a matching developer update. Pera Connect, the JavaScript SDK web apps use to talk to the wallet over [WalletConnect](/glossary/walletconnect "A protocol that lets a web app connect to a cryptocurrency wallet (such as Pera or Defly on Algorand) by scanning a QR code, so the app can read the w") — the protocol that lets an app connect by scanning a QR code, read the wallet's address and request signed transactions without ever holding the private keys — reached v1.6.0 on July 30 with two new Algorand standards: ARC-27, a connection handshake that lets an app declare which network it needs and check what a wallet supports before connecting, and ARC-60, Sign in with Algorand, which replaces passwords with wallet signatures locked to the requesting app's domain so a phishing site cannot reuse a signature elsewhere. ARC-60 works only on Pera 7.0 and later, tying the SDK's newest feature to the rebuilt app. The npm package recorded 9,902 downloads in the past week and 47,970 in the past month, per npm registry data.

The same company also runs Pera Explorer, whose [ASA](/glossary/asa "Algorand Standard Asset: the layer-1 mechanism on the Algorand blockchain that allows anyone to issue a token such as a stablecoin or NFT, carrying ba")-verification badge program is Pera's own curation — its terms say a badge is not an endorsement — rather than a neutral record of the ledger. The QR-code generator rounds out the tooling, producing codes for sharing an address, receiving ALGO or an ASA, and asset opt-ins, with support for NFDomain names.

Built in the Open, With Strings Attached

Pera publishes 26 public repositories, runs development in the open, and takes feature requests through a Canny board that currently carries 127 requests — Logic Sign Integration and Multichain USDC are among the most-voted. The community is small but real: the Discord server counts 3,739 members with 194 online, and the Telegram channel has 910. The homepage's claim of being 'built in the open, with a transparent and community driven roadmap' is substantively true, but the strings deserve naming: the Foundation that built the Rocca framework Pera now partly runs on also holds an oversight and investment role in the company, so the 'built on Rocca' endorsement carries a family connection — and, as noted above, the 7.0 launch materials disclose no third-party audit.

The honest scorecard for mid-2026 is real momentum with open questions: a single codebase that was actively committed to the day this was written, a funding rail that works, a card program in transition with no named successor, and a security story that rests on open-source review rather than a published audit. For most Algorand users, Pera remains the default choice — and unlike several rival wallets in the ecosystem, the maintenance evidence backs that choice up.

Source

Source: https://perawallet.app/