EL Russo

RedWallet update for iPhone + Android 🔴 An independent XBT community wallet built on BlueWallet. Credit to the BlueWallet team for the foundation. Thank you to every tester, reviewer, contributor and bug reporter! Major upgrades: • Native SegWit (BIP84) and Taproot (BIP86): creation, recovery, receive/change addresses and key-path spending. • XBT Unified Sighash (0x21) signing. • Watch-only public-account import and cold signing through signed PSBTs with a compatible XBT signer. • RBF fee bumps and single-parent CPFP. • QR receive/send, your own Fulcrum server, and XBT pricing with source/time labels. Recent fixes: • “Batch limit exceeded” recovery using smaller individual requests on the same server. • History decoding handles outputs without addresses, correctly identifies P2WSH, and avoids nonexistent coinbase-parent lookups. • History covers discovered receive AND change addresses, including activity outside RedWallet. • Recovery/persistence, fee-review and transaction-status improvements. Security upgrades: • Authenticated TLS with certificate/hostname checks. • Stronger scrypt + AES-256-GCM password storage and randomized encrypted caches. • Authentication for seed/private-key export and clipboard safeguards. • Raw transaction/prevout verification, wallet-owned change checks and conservative coinbase-maturity filtering. • Returned PSBT signatures checked against the current request; altered outputs and incompatible BTC signatures rejected. • High-fee warnings, protected signing/upload, full production source-tree matching and verified package hashes. 767 unit tests passed, plus native suites on both platforms. Still beta: no Lightning, multisig or full SPV. Physical Android/cold-signer compatibility needs more testing. Taproot is key-path only. iOS: testflight.apple.com/join/Uu… Android: zapstore.dev/apps/com.romanm… Source, APKs & contributions: github.com/romanmodin/RedWal…

RedWallet’s updated iPhone beta is ready! 🟥📱 Based on BlueWallet, built for Bitcoin using BLAKE2b (XBT). Features: • Create and restore Native SegWit wallets • Full SIGHASH_UNIFIED signing for supported XBT transactions • Send/receive, QR scanning and address copying • Balance and transaction history through Fulcrum • Configure your own Fulcrum server • Manual or NeoxEX XBT pricing • Review destination, amount and fee before sending • Wallets and settings persist across restarts • Conservative 6,480-confirmation safeguard for mining rewards Security update: All seven PR suggestions and the private security findings were addressed. Stronger transaction safeguards, protected release signing, affected credentials rotated, and PR #1 merged. iPhone checks passed: recovery, restart persistence, receive/copy, QR scanning, saved settings, send review/cancellation and invalid-address rejection. Live sending/confirmation remains to be tested. Thanks to Kyle for the careful security review and Luke for the corrections and clarification: XBT/BLAKE2b is Bitcoin, and supported transactions use the full unified sighash. Only a few TestFlight spots are available—Devs DM or email me for the installation link. Public App Store release is planned as soon as Apple approves the submission. Android test build passed; a public phone APK is not yet released. Still beta. Hardware signing, Taproot, Lightning and multisig are outside this release.

RedWallet for Android is here 🟥 Our first beta release, updated with the latest connection and security fixes. Bitcoin (XBT) for people who want a mobile wallet without learning Linux or using a command line. Features: • Self-custody: create or restore BIP39 Native SegWit wallets • Send/receive, QR scanning, balances, wallet history and fee-bump tools • Your own Fulcrum server, with authenticated TLS and explicit private-certificate trust • Unified (0x21) signing; watch-only accounts and PSBT signing with compatible XBT cold wallets • USDC value estimates, using a manual price or NeoxEX • Password encryption, decoy wallets and fee/recipient confirmations Recent fixes improve certificate/hostname validation and slow connections, verify transaction inputs and change before signing, validate returned cold-wallet signatures, strengthen encrypted storage/cache handling, and protect secret exports and clipboard contents. I don’t own an Android phone, so I haven’t personally tested this build. It passed automated and Android emulator checks, but it’s an early beta. Start with an empty disposable wallet, keep an offline backup, and don’t downgrade after upgrading encrypted storage. Cold-wallet device compatibility still needs testing. Still pending: Taproot and multisig support, independent chain verification (SPV), and more testing on real phones and cold wallets. Developers: please test, review the source, verify the behavior and submit bugs, critiques or PRs. Thoughtful criticism helps improve it. Android 7+ APK, checksums and build receipt: github.com/romanmodin/RedWal… Source/issues: github.com/romanmodin/RedWal… iPhone testing continues separately through TestFlight. Thank you to the BlueWallet team for the foundation, and to Kyle, Luke, Boozy and everyone who tested, reviewed or reported issues. Screenshots: Android emulator, empty demo wallet; manual demo quote, not a market price.

🟥 RedWallet Web — a SUPER EARLY XBT wallet preview is now available to try. Don’t have an iPhone or Android device handy? You can test it from your desktop browser. No app installation required. What’s available now: • Create or recover a local encrypted wallet • Native SegWit receiving addresses • Account recovery scanning, balances and transaction history • Saved scan progress, so interrupted recovery can resume • Send XBT with local signing and SIGHASH_UNIFIED replay protection • Built-in network connection, with options to configure your own • Configurable XBT pricing • Wallet management, including removing test/demo wallets The web interface is hosted on ICP. Keys and recovery words stay in your browser; signing happens locally. This is an early preview—not a finished 1.0 release. Expect bugs, rough edges and missing features. Native SegWit account 0 is supported; Taproot and broader account support are still future work. Background scanning while keys are locked and mining-reward maturity support are being worked on. Those updates are NOT live yet. I’m looking for early testers and practical ideas: What feels confusing? What’s missing? What would make this easier for someone who simply wants to use XBT without learning Linux or the command line? Please start with a test wallet and avoid meaningful funds at this stage. Try it here: redwallet-7m3.caffeine.xyz Bug reports, screenshots and constructive feedback are welcome. Help shape what comes next.

🔴 RedWallet XBT for iPhone — “world’s first”? You tell me 😂 RedWallet is running on my iPhone through TestFlight. I’ve successfully received XBT AND sent it back out, with receipt verified in an external wallet! Looking for developers willing to test and review the code. Reply here or DM me FIRST. Only 20 external testing spots are available. I’ll post the TestFlight link once we have interested testers and Apple approves the external beta. Features implemented: • Noncustodial software wallets: your keys stay on your device. • BIP39 seed creation/import and BIP84 native SegWit receive/change addresses. • XBT sending/receiving, QR receive codes and address scanning. • Balances, transaction history, fee estimates and XBT/sats amounts. • XBT Unified Sighash signing, with replay-separation tests against Bitcoin Core. • Your own compatible XBT Electrum/Fulcrum server, verified against the XBT fork checkpoint; no automatic BTC fallback. • Coinbase-maturity filtering to avoid selecting immature mining rewards. • Manual price entry or on-demand NeoxEX XBT/USDC refresh, with source/time labels. • Inherited wallet encryption and light/dark themes. • New red palette and optional RedWallet development donations alongside BlueWallet’s original donation section. Huge credit to the BlueWallet team! This is an open-source fork built on their work and adapted for XBT. Latest code: github.com/romanmodin/RedWal… XBT signing/core review PR (newer release changes are on the branch above): github.com/romanmodin/RedWal… EARLY BETA, not an audited release. My receive/send test worked, but recovery and broader device testing remain—use tiny test amounts. This release is XBT-only: no Taproot, Lightning, multisig, watch-only imports or hardware signing yet. Devs: especially interested in reviews of signing, chain separation, recovery and transaction handling. Who’s in?

What is happening at Grover Heights Elementary in Lucia Mar Unified in Grover Beach, SLO? Grover Heights is already struggling academically. In 2024–25, only 43.2% of tested students met/exceeded the ELA standard and 31.9% met/exceeded math—both below Lucia Mar Unified (55.2% ELA / 38.6% math) and below California overall (48.8% / 37.3%). (SchoolDigger) Enrollment has also fallen: 301 → 290 → 282 students, with CDE reporting 282 students for 2025–26. (California Department of Education) The school’s own 2026–27 performance plan identifies ELA and Math as Orange, with math 43.7 points below standard. Most concerning given the proposed restructuring, its internal data showed only 16% of first graders meeting the cited iReady math benchmark versus 25% districtwide. The school’s plan acknowledges that declining enrollment is affecting staffing and anticipates four or more combination classes. Its public explanation is that combination classes will create more “balanced classes,” increase teacher collaboration and ultimately improve achievement. That raises a serious concern: Are already-struggling first graders being asked to absorb the educational cost of solving an enrollment/staffing problem? Combining first graders with TK students means educating children at very different developmental and curricular stages. The school says this will improve achievement, but parents deserve to see the evidence supporting that conclusion—especially when first grade is already one of the weakest-performing groups. I have found no evidence that Grover Heights is deliberately trying to lower scores to obtain additional funding, and that should not be stated as fact. But it is reasonable to ask whether this restructuring could further depress performance while simultaneously balancing staffing—and whether poorer results could subsequently qualify the school for additional intervention resources. Before implementing this plan, Lucia Mar Unified and Grover Heights should explain exactly how TK/1 combination classes will improve first-grade outcomes, how much dedicated first-grade instructional/intervention time students will receive, and what objective measurements will determine whether the experiment is working.