Leap Wallet: Sunset Notice
After careful consideration, we've made the decision to sunset Leap Wallet and its associated products.
The products will be sunset on 28th May, 2026, and all users should complete their migration before then.
We started Leap in 2022 to redefine what wallet experiences in crypto mean. Over time, that journey expanded across multiple ecosystems and 100+ chains. Through every phase, the team approached the work with conviction, care, and a deep sense of responsibility to the users and communities we served.
This decision was not made lightly. We continue to believe in the long-term future of crypto and the interchain ecosystem, and we remain supporters of the builders still in the arena.
What's being sunset
The following products will be sunset after 28th May, 2026:
• Leap Wallet (Extension, iOS, Android)
• Compass Wallet (Extension, iOS, Android)
• Leap WebApp
• Swapfast
• Leap Cosmos Hub Validator
• Leap Cosmos Snaps
Until that date, all wallet products listed above will retain their existing core functionality. You will still be able to view balances, send tokens, manage staking positions, and export your recovery phrase and private keys. All other products listed above will likewise retain their existing functionality until 28th May, 2026.
What users need to do
If you are using one of Leap’s wallet products, we recommend migrating your wallets to another wallet like Keplr, MetaMask, Phantom, or Rabby.
Because Leap is a non-custodial wallet, your assets live on the blockchain, not in our apps. As long as you have your recovery phrase, you can continue to access your assets through another compatible wallet by importing that recovery phrase. Your addresses and balances will carry over automatically.
If you have ATOM delegated to Leap’s Cosmos Hub validator, please redelegate to another validator to continue earning staking rewards. We encourage doing this as early as possible to account for network unbonding periods.
Detailed migration guide and FAQs can be found on the website - https://t.co/kVQa7HM32y
What to expect next
After 28th May, 2026, all Leap products will be sunset and will no longer function, including applications already installed in your browser or on your mobile device.
Even if you do not migrate from Leap to another wallet before that date, you can still recover access to your assets by importing your recovery phrase into another supported wallet
Migration support will be available through our official support channels until 28th May, 2026 at [email protected]
Thank You
Thank you to all our users, for letting us serve you through so many market cycles.
Thank you to our amazing partners, for helping us build experiences & worlds we never thought possible.
Thank you for Leaping with us.
🐸 💚
Leadership across companies expects AI to magically cut time-to-ship in half.
Yes, AI can help engineers code faster. But coding was never the bottleneck.
The real drag is non-tech stuff - planning, periodic status updates, cross-team coordination, unclear requirements, stakeholder alignment, reviews, approvals, handoffs, deployment cycles, and on-call rotations.
Cumulatively, that's ~80% of the work.
Optimizing the remaining ~20% cannot produce a 50% reduction.
If leaders really want to see gains, they should focus less on coding velocity and more on eliminating process friction.
As maintainer of React Native CLI I learned about this vulnerability today, and actually the issue only existed in two versions of CLI (v19, v18), so React Native v0.80 and v0.81.
‼️ Starting from CLI v9 (~3 years ago), so from React Native v0.70 URL validation was included to prevent using different protocol than http/https, so users between v0.70 and v0.80 (majority of CLI users) are not affected. [0]
The check was removed during a refactor which we didn't spot when reviewing the PR.
We released v20.0.2 in September with the fix for the vulnerability. I've just cherry-picked and released 2 patch versions for other affected
➡️v19.1.2 for RN v0.81
➡️v18.0.1 for RN v0.80
Please use relevant CLI version for each React Native major version. Updating to latest 20.x version is not supported when your project is using older React Native, it might work but wasn't tested and is not recommended. Learn more here: [1].
[0] → https://t.co/H5sH6CxYkj
[1] → https://t.co/M2BmbItkY8
Implementing clean onboarding flow in React Native is harder than it should be.
So, we made react-native-onboarding! 🎉
✅ get started with default styles
✅ use smooth animations powered by react-native-reanimated
✅ replace any panel, step, or button with your own components
…and more! Check out our article for details👇
https://t.co/ieNBB0CGka
wait this video is insane lmao?
didn't know half of this shit
i) zooko wrote the first BTC blog and was cited by Satoshi?
ii) was working on the idea before Bitcoin (??)
iii) him, satoshi, and hal were all trying to work on privacy??
wtf
today, Solana changes forever
we've solved the biggest data/RPC problem that exists
solana historical/archival data — has now been redesigned
quick context:
today when you query historical data (getBlock/getTransaction/getSignaturesForAddress), it hits Google BigTable
this is i) slow, ii) expensive, iii) inflexible for queries
e.g., you physically can not get the first tx for a Solana address without looping back endlessly from the latest tx
for busy addresses, this can take thousands of RPC calls — extremely slow, expensive, and annoying
also, imagine you wanted to get the most recent 100 txs for an address, how do you do it?
you first hit getSignaturesForAddress to get all the tx signatures and then call getTransaction on each tx to get its details — this can take 1,001 RPC calls in the worst case
not anymore
we have built a new distributed archival storage system that is 1,000x faster, more flexible, and more scalable
the best part? we're introducing a new API method:
getTransactionsForAddress
with this method, you can now:
i) combine getSignaturesForAddress and getTransaction calls into just 1 call instead of 1,000
ii) you can search in reverse order without needing to traverse
iii) you can search historical transactions by time and slot ranges (e.g. get me all the txns from January 5th, 2025 until February 5th, 2025)
what's more:
- getBlock calls are now 10x faster
- getTransaction calls are now 10x faster
- getSignaturesForAddress calls are now 10x faster
10x lower latency, 100x fewer RPC calls, and 1000x less code
enjoy!
docs below