Ivan ꙮ retweeted
Introducing tiny.london
A massive isometric pixel map of London, based on amazing NYC demo by @_coenen from 9 months ago
My agent created the dataset, finetuned qwen image LoRA adapter, did a multiday inference run and built an efficient tile viewer!
I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents.
I didn't write a single line of code.
Ivan ꙮ retweeted
WE DID IT! We reverse-engineered BlueWallet with AI and made it open source. Introducing BlueWalletFOSS 🚀
Ivan ꙮ retweeted
I was able to decompile and analyse 494 wallets on the AppStore.
I found 45 apps that raised red flags for me during my research.
I looked specifically for 2 things: private keys exfiltration and weak entropy.
Ivan ꙮ retweeted
There are 648 apps on Apple Appstore that larp as non-custodial cryptocurrency wallets.
My clanker is busy now downloading all of them.
Then I will decompile all of them to see which ones have broken/backdoored entropy or private keys exfil.
Should be fun.
Ivan ꙮ retweeted
I have just decompiled IPA app binary from Apple Appstore of a fresh new bitcoin wallet. It has obfuscated seed exfiltration to 3rd party server.
Literally a few lines difference from the published Github source.
Ivan ꙮ retweeted
Breaking down the claims of Wavelength, an Ark implementation by Lightning Labs:
Wavelength embeds an Ark wallet in your app. Funds become operator-coordinated VTXOs, while “Lightning payments” are swaps between those VTXOs and Lightning through LL’s infrastructure.
The misleading claims:
1. “No trusted third parties”
Users depend on the operator for transactions, refreshes, recovery and normal exits. System is entirely trusted for users that can't afford blockspace incidentally. Swap-based payments require 3rd party cooperation.
2. “Exit anytime”
Only with an unexpired VTXO, recovery data, sufficient fees and available blockspace. Exits shrink as usage increases (does not scale).
3. “True sovereignty”
VTXOs expire, after which the operator can sweep the funds. Dependent and trusted.
4. “Instant settlement”
Payments create off-chain Ark claims. Swaps can remain pending, fail or require refunds. ALL layers are made of unconfirmed txns. Settlement is fundamentally determined by people, app state, not guarantee-able.
5. “On-chain guarantees”
A VTXO is a conditional path to an on-chain claim, not settlement. Conditional. Not guaranteed.
6. “No liquidity required”
Liquidity was moved to Lightning Labs, not eliminated. This affects economics and incentives differently than LN.
7. “Scale without compromise”
Ark compresses cooperation but creates no additional exit capacity, while introducing trust, credit, and complexity as compromises.
8. “Open infrastructure”
The Ark operator is replaceable, but the swap server is not publicly runnable. The complete product remains LL-dependent and mainnet is allowlisted.
9. "Wavelength"
It's Ark. An invention not made by LL, but by Burak; and a torch carried by Arkade and Bark. The launch info makes it appear as something LL invented, with only one slight mention of being "ark-like" buried in the middle of the blog post.
Thanks for reading.
Ivan ꙮ retweeted
Introducing BLUEBERRY, a new project I'm working on, privacy focused neutrino-based wallet:
* does not need server infra - syncs blocks via bitcoin p2p network (compact block filters!)
* blocks download is spread among peers to prevent clustering
* encrypted connections only (bip324/v2 protocol)
* tx broadcast via Tor only
* cli, but has UI
* works great on tiny vps (1cpu/1Gb)
I will be demoing it and talking about privacy & bitcoin p2p on @mempool dev day (Apr-21) luma.com/antidote-k30j (hosted by @AntidoteBTC @orangesurfbtc)
For years, the main blocker to adding BlueWallet to bitcoin.org was our camera library’s dependency on Google ML Kit for qrcode decoding.
We’ve finally removed that dependency by porting a pure JavaScript library by @paulmillr to Kotlin.
Building a mobile Bitcoin wallet? Give it a try:
github.com/limpbrains/qr
github.com/BlueWallet/react-…
BlueWallet is now listed on bitcoin.org providing a better alternative to its visitors.
Thank you everyone for the support, feedback and reviews efforts to get listed!
bitcoin.org/en/wallets/mobil…
Ivan ꙮ retweeted
BlueWallet is now listed on bitcoin.org providing a better alternative to its visitors.
Thank you everyone for the support, feedback and reviews efforts to get listed!
bitcoin.org/en/wallets/mobil…
Ivan ꙮ retweeted
bitcoin.org deploy is broken, Coldcards are still recommended.
the team is looking into it.
Just remembered I bought a Coinkite wallet back in 2020. It never arrived because the FSB (former KGB) wanted paperwork for this “special encryption device.”
Thanks, KGB.
Your bitcoin wallet is only as secure as the secret behind it.
That secret starts with entropy: random information used to create your seed words.
Weak or predictable entropy can create predictable wallets.
That is why wallet developers must take seed generation seriously.
In BlueWallet, you can add your own entropy with coin flips or dice rolls.
This was one of my first major contributions to the project, and recent events show why this option matters.
A lot of you are asking.
How BlueWallet handles wallet entropy 👇
Wallets created in BlueWallet use your device’s cryptographically secure system random number generator. The industry standard approach for generating keys.
Want extra peace of mind? You can also add your own entropy using dice rolls or coin flips (Add wallet → Provide entropy). BlueWallet lets users add entropy via dice or coin flips, and if insufficient manual entropy is provided, it fills the remainder from the system RNG.
We regularly review this code, including with the latest AI-assisted tooling, and continuously test it as part of our development process. We ask you to do the same if you have the knowledge to do so.
Every build also runs runtime self-tests that generate large numbers of seeds and check for unexpected collisions. While no single test can prove an RNG is perfect, these checks are designed to catch obvious regressions before they ever reach users (this is important, your wallet should have this!).
You can even run the self-test yourself:
Settings → About → Self Test
Relevant ways to add security layers:
bluewallet.io/docs/manual-en…
bluewallet.io/docs/import-pa…
bluewallet.io/multisig-walle…
Security is hard, bitcoin will humble you. Please verify!
Ivan ꙮ retweeted
We're finally ready to talk about Flipper One — a project we've been grinding on for years and have rebuilt from scratch several times. Read blog post >>
blog.flipper.net/flipper-one…
Ivan ꙮ retweeted
It's 2026, and it's easier than ever to add Lightning to your app:
* @moneydevkit (LDK on the server; auto-liquidity; 2% fee)
* phoenixd by @acinq_co (server; auto-liquidity; 1% fee)
* @spark (L2 with gateway to LN; free to receive, 0.25% to send; works great on frontend)
* arkade by @arklabshq (L2 with gateway to LN through @Boltzhq; 0.1%-0.5% fee; works great on frontend)
* @breez_tech SDK (L2 with gateway to LN; 0.1% to send, 0.25% fee to receive; works ok on frontend)
Honorary mention: Blockstream Greenlight, cross-compiled LND & all LDK diy repacks.
Share it with your fellow developers!
Ivan ꙮ retweeted
If you like what we build, consider leaving a review on the appstores or a donation to support our work.
donate.bluewallet.io
Ivan ꙮ retweeted
Bitkit 2.0 is now live
blog.bitkit.to/bitkit-2-0-a-…
Released a pure Kotlin QR library - no ML Kit, no closed source deps. Ported from @paulmillr's JS lib (thanks Paul! 🙏)
Should help @bluewalletio and other Bitcoin wallets get back on F-Droid.
Took a couple days poking with Claude. 98%+ accuracy, optimized for camera frames.
github.com/limpbrains/qr
github.com/limpbrains/react-…















