SORA Announcements 天

https://x.com/M4K070/status/2089342935246766249

https://x.com/FearlessWallet/status/2088795670195163534

https://x.com/sora_xor/status/2088634347494732280

📣 SORA Wallet Development Updates: June 1 to August 15, 2026 Hey SORA community 👋 Over the past ten weeks, we’ve been modernizing the Android and iOS wallets while strengthening the Polkaswap indexer that powers wallet history, market data, and upcoming experiences. 📱 Android and iOS • Improved production stability around account switching and removal, QR payment requests, transaction history, fee estimation, and network connectivity. • Built a safer wallet-upgrade system designed to preserve existing accounts, addresses, selected wallets, and encrypted credentials. If retained data cannot be verified, the app enters recovery instead of silently replacing it. • Strengthened SORA2 transactions with network and runtime verification, better pending-transaction tracking, and restart recovery. An uncertain transaction is never automatically sent twice. • Added the foundations for a SORA Nexus multi-network portfolio covering SORA2 and Minamoto, with Taira Testnet controlled separately. This includes balances, receiving, sending, pending transfers, and finalized history. • Built native Polkamarkt experiences for Android and iOS: browse and filter markets, view probability and price history, track positions and activity, request quotes, buy or sell outcomes, and claim eligible payouts. ⚙️ Polkaswap Indexer • Expanded the GraphQL API with Polkamarkt markets, snapshots, account positions, trades, and mobile-ready transaction history. • Added an optional RocksDB storage engine with indexed queries plus migration, verification, backup, restore, checkpoint, and maintenance tooling. • Improved indexing and query performance, historical-data recovery, finalized-block tracking, pagination, and resource limits. • Added stronger production health checks, CI, deployment verification, worker protection, database-role separation, and documented rollback procedures. • Introduced independent capability switches for SORA Nexus, SORA Nexus sends, Polkamarkt, Polkamarkt transactions, and Taira visibility, allowing each feature to be rolled out safely. 🛡 Release safety We also added pinned and verified dependencies, extensive retained-wallet migration tests, production signing checks, internal TestFlight support, candidate-bound canaries, and staged rollout controls. Status as of August 15: the core implementation is well advanced, but these new features are not publicly live yet. Current polishing work includes clearer fee errors, safer send completion handling, QR-flow improvements, and additional history and pagination checks. Thank you for your patience and continued support. We’ll share rollout details once the exact store candidates have completed qualification. ❤️

https://x.com/hl_iroha/status/2088620128296673646

📣 Hyperledger Iroha 3 — Development Update 📅 11 July–15 August 2026 The past five weeks focused on first-release hardening: making core paths deterministic, recoverable and fail-closed. ⚙️ Consensus, data availability & storage Sumeragi advanced in the production flow. DA is now explicitly Merkle-based and resource-bounded. Live and restart-recovered work share a lifecycle-owned path, from proposals and voting through body recovery, commit, Kura persistence and the next height. Four-validator testing exposed and drove fixes for real liveness, late-body, stale-certificate, queue-ordering and WAL-recovery faults. Its release inventory now covers 856 tests across 40 modules; the final formal and fault/soak wave remains open. 🧠 Smart contracts & IVM Kotodama V1 was tightened around exact numerical types, deterministic gas, prepared contract metadata and shared multi-file builds. Contract calls now bind the expected code hash, deployment uses bounded resumable uploads, and governed heap/output limits apply across contract, trigger and executor paths. The IVM gas schedule is bound into the consensus handshake so different hardware still produces identical results. 🔐 Data, security & APIs Norito gained depth-safe JSON, safer compressed/sequential decoding and early rejection of malformed or oversized input. Signed queries and app authentication now bind the genesis-derived network, route, timestamp, nonce and request, with replay protection and one-shot submission. Torii and MCP were hardened so inner operations keep their own authentication and resource limits. Universal accounts also advanced through versioned aliases, cross-dataspace routing and holding limits. 🛡️ Privacy & ZK Kagemusha and the wider proof pipeline advanced with stronger artifact provenance, circuit-resource guards and SDK parity. Unsound generic confidential entry points were removed instead of kept as compatibility paths. Offline-cash readiness remains deliberately off until authenticated artifacts, independent review, benchmarks and physical-device evidence are complete. 📱 SDKs & mobile Shared fixtures now check identical canonical transaction bytes and hashes across the major SDKs. A standout is transport-neutral offline exchange over QR, Google Nearby and NFC, with bounded parsers, replay protection, durable acknowledgements and cross-platform fixtures. Fee sponsorship, signed-query, finality, Musubi registry and SoraFS orderbook tooling also gained typed flows across Rust, JavaScript, Python, C#, Swift, Kotlin and Java. 🌐 SoraFS, Nexus & network operations SoraFS pinning, provider, retrievability, reputation, moderation, transparency and orderbook paths gained stronger authentication, accounting and restart safety. The CLI also gained Soracloud starters for web, API and privacy-aware services. Taira’s profile was corrected to seven logical lanes over five physical dataspaces, with deterministic signed Kagami bundles and stronger restart/rollout gates; Minamoto’s topology model was corrected too. Read-only Taira diagnostics helped isolate serious finality stalls and drive source fixes, but no live cutover or soak is being claimed yet. 🧹 Developer experience The 97-crate workspace now has clearer feature ownership, focused CI, generated-file/source-size guards and smaller modules. Long-form public documentation moved to iroha-docs, leaving the main repository focused on source-coupled specs and validation. Next: freeze and sign the candidate; finish the formal-proof wave; run full locked workspace tests, strict Clippy and wire goldens; complete multi-validator fault/soak and mobile-device testing; regenerate source-bound OpenAPI/SDK artifacts; and validate the live Taira rollout. Bottom line: Iroha 3 is materially closer to its first release, more deterministic, more recoverable and harder to misuse, but the remaining release gates stay explicit. #Hyperledger #Iroha #Blockchain #OpenSource

Credit Should Build, Not Extract https://x.com/M4K070/status/2088431367524860105

https://x.com/sora_xor/status/2083481520170577928

You can use https://bafybeib37grzb5cddrcwubvjl2xxm5pu5e4grp6ibk4sy7r55keyxqvpca.ipfs.dweb.link/#/swap to access Polkaswap

sora.org was updated with new info

New market on Polkamarkt.com https://polkamarkt.com/#markets/32

4/20 - 7/10 Hyperledger Iroha Dev Update https://x.com/hl_iroha/status/2075661668865171835

https://x.com/sora_xor/status/2073842534351258090

FIRST TON TESTNET SCCP TEST with SORA Nexus TAIRA TESTNET https://youtu.be/c7BIArkPsuY

https://x.com/sora_xor/status/2072327584587940132

https://youtu.be/PNqwj7PSujE?si=wcp5V6rDgodsbaZj

https://x.com/sora_xor/status/2071967553422045512

No One Cares about AI Safety https://x.com/M4K070/status/2070958670104666583

No One Cares about AI Safety https://x.com/M4K070/status/2070958670104666583