SORA Announcements 天
Open in Telegram
📢This channel provides information about latest releases and news for the SORA decentralized economic system.
Show more1 922
Subscribers
-324 hours
-77 days
-1130 days
Data loading in progress...
Similar Channels
Tags Cloud
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
September '26
September '26
+10
in 0 channels
August '26
+69
in 0 channels
Get PRO
July '26
+70
in 1 channels
Get PRO
June '26
+34
in 0 channels
Get PRO
May '26
+16
in 0 channels
Get PRO
April '26
+17
in 0 channels
Get PRO
March '26
+34
in 0 channels
Get PRO
February '26
+56
in 0 channels
Get PRO
January '26
+46
in 0 channels
Get PRO
December '25
+69
in 0 channels
Get PRO
November '25
+162
in 0 channels
Get PRO
October '25
+98
in 0 channels
Get PRO
September '25
+55
in 0 channels
Get PRO
August '25
+51
in 0 channels
Get PRO
July '25
+29
in 0 channels
Get PRO
June '25
+19
in 0 channels
Get PRO
May '25
+40
in 0 channels
Get PRO
April '25
+60
in 0 channels
Get PRO
March '25
+27
in 0 channels
Get PRO
February '25
+49
in 1 channels
Get PRO
January '25
+82
in 0 channels
Get PRO
December '24
+89
in 2 channels
Get PRO
November '24
+45
in 3 channels
Get PRO
October '24
+52
in 2 channels
Get PRO
September '24
+54
in 3 channels
Get PRO
August '24
+46
in 2 channels
Get PRO
July '24
+44
in 2 channels
Get PRO
June '24
+76
in 1 channels
Get PRO
May '24
+123
in 1 channels
Get PRO
April '24
+58
in 2 channels
Get PRO
March '24
+76
in 1 channels
Get PRO
February '24
+72
in 1 channels
Get PRO
January '24
+49
in 0 channels
Get PRO
December '23
+56
in 0 channels
Get PRO
November '23
+58
in 1 channels
Get PRO
October '23
+60
in 1 channels
Get PRO
September '23
+45
in 0 channels
Get PRO
August '23
+65
in 0 channels
Get PRO
July '23
+40
in 0 channels
Get PRO
June '23
+30
in 0 channels
Get PRO
May '23
+33
in 0 channels
Get PRO
April '23
+24
in 0 channels
Get PRO
March '23
+38
in 0 channels
Get PRO
February '23
+25
in 0 channels
Get PRO
January '23
+37
in 0 channels
Get PRO
December '22
+24
in 0 channels
Get PRO
November '22
+29
in 0 channels
Get PRO
October '22
+31
in 0 channels
Get PRO
September '22
+26
in 0 channels
Get PRO
August '22
+24
in 0 channels
Get PRO
July '22
+38
in 0 channels
Get PRO
June '22
+20
in 0 channels
Get PRO
May '22
+22
in 0 channels
Get PRO
April '22
+21
in 0 channels
Get PRO
March '22
+21
in 0 channels
Get PRO
February '22
+7
in 0 channels
Get PRO
January '22
+31
in 0 channels
Get PRO
December '21
+45
in 0 channels
Get PRO
November '21
+31
in 0 channels
Get PRO
October '21
+28
in 0 channels
Get PRO
September '21
+25
in 0 channels
Get PRO
August '21
+56
in 0 channels
Get PRO
July '21
+13
in 0 channels
Get PRO
June '21
+56
in 0 channels
Get PRO
May '21
+115
in 0 channels
Get PRO
April '21
+736
in 0 channels
Get PRO
March '21
+277
in 0 channels
Get PRO
February '21
+300
in 0 channels
Get PRO
January '21
+1 071
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 08 September | 0 | |||
| 07 September | +3 | |||
| 06 September | +1 | |||
| 05 September | 0 | |||
| 04 September | +1 | |||
| 03 September | +2 | |||
| 02 September | +2 | |||
| 01 September | +1 |
Channel Posts
| 2 | https://x.com/hl_iroha/status/2091352583499817382 | 409 |
| 3 | Why this matters: deterministic ledger code can still be compromised through a poisoned build dependency. The source, dependency lockfile and resulting build all need to remain part of the security boundary.
📌 OVERALL
The main achievement this week was not a single headline feature. It was a broad reduction in the number of places where ambiguous state could survive:
• Old consensus work cannot silently control a newer round.
• Restarting cannot erase permanent exchange budgets.
• Recreating an asset cannot revive an obsolete permission.
• Interrupted offline payments can recover from durable evidence.
• Proof components cannot be mixed across different contexts.
• A candidate build cannot be promoted using mismatched validators or configuration.
The direction is clear: important state transitions should be deterministic, authenticated, reproducible and recoverable. When the required evidence is missing, the system should stop safely rather than guess.
This is meaningful progress toward Iroha 3 and SORA Nexus release readiness.
🔗 https://github.com/hyperledger-iroha/iroha/tree/optimizations | 393 |
| 4 | 🧠 6. MORE DETERMINISTIC SMART-CONTRACT EXECUTION
The Iroha Virtual Machine, or IVM, is the execution environment for Iroha smart contracts.
This week’s hardening work included:
• Loading a new program now resets the complete execution profile so state from a previous program cannot leak into the next one.
• Arithmetic and register behaviour was made consistent across different build configurations.
• Undefined, malformed or noncanonical instructions are rejected earlier.
• Memory-commitment edge cases were repaired.
• Proof transcripts and verifier-key handling were strengthened.
• Smart-contract, data-space and asset models were updated together with their SDK representations.
Why this matters: every validator must obtain exactly the same result from the same contract. Behaviour must not depend on which compiler mode was used, which program ran previously or how malformed input happened to reach the virtual machine.
🚪 7. SAFER APIS, ROUTING AND APPLICATION INTEGRATION
Torii is Iroha’s API gateway. Wallets, exchanges, explorers and institutional applications use it to submit transactions, query the ledger and subscribe to events.
Work this week improved:
• Query error handling.
• Account-alias registration and resolution.
• Routing between lanes and data spaces.
• JavaScript, Kotlin, Java, Python and Swift SDK compatibility.
• Configuration and parameter handling.
• Iroha Connect integration and developer tooling.
• Governance telemetry, including network-governance membership status and exact membership counts.
Why this matters: core ledger correctness is not enough if different SDKs construct different transactions or if applications receive ambiguous results from the API. The client-facing surface must be deterministic as well.
🛡 8. A CONTROLLED RELEASE AND ROLLOUT PROCESS
This week, the rollout controls gained:
• Cryptographic qualification records for the exact four-validator set.
• Binding between the candidate build, runtime configuration, genesis state and validator identities.
• One-use promotion identifiers that cannot be silently reused.
• Signed activation and finality receipts.
• A separately authorized canary transaction performed after activation.
• Challenge-based evidence showing that all four qualified validators responded after the canary.
• Protection against replacing files or substituting a configuration after qualification.
• Explicit reconciliation states when the system cannot determine whether publication completed successfully.
No live publication, activation, canary transaction or production rollout was performed.
Why this matters: a release process should not rely on someone saying, “This appears to be the same build we tested.” The deployed candidate must be cryptographically connected to the exact software, configuration, validator identities and authorization that passed qualification.
🔎 9. DEPENDENCY AND SUPPLY-CHAIN SECURITY
The team also responded to a reported Rust package supply-chain incident:
• The repository was checked for the named malicious arrayref releases and related packages.
• The legitimate version in use was exact-pinned.
• No named malicious release was found in the active dependency tree.
• Several other vulnerable or obsolete dependencies were updated or removed.
• A fresh Rust security audit reported no actionable vulnerability in the active dependency tree. | 251 |
| 5 | • Usage budgets and rate limits are now stored durably and survive restarts.
• Removing expired replay records no longer erases permanent accounting information.
• Reusing an old sub-transaction number is rejected even after temporary records have been pruned.
• Re-registering an asset with the same visible identifier cannot revive permissions created for an earlier version of that asset.
• Transaction-local changes remain isolated until the whole operation is accepted.
• Validators can load only the exact budget information touched by a transaction instead of copying the entire world state.
Why this matters: an attacker must not be able to reset a spending limit by restarting a node, waiting for a temporary record to expire or recreating an asset with the same name. Cross-data-space exchanges need the same durable protections as ordinary ledger balances.
📴 4. OFFLINE CASH AND MOBILE WALLET RELIABILITY
Offline cash allows two devices to transfer value while one or both devices are disconnected from the network. The resulting payment can later be synchronized, redeemed and settled against the ledger.
This week’s progress included:
• Kotlin support for offline redemption requests, settlement state and cryptographic redemption proofs.
• Shared test fixtures to verify that different SDKs encode and interpret the same proof identically.
• Rust-backed proof generation exposed through the common mobile bridge.
• Faster proof generation for native and mobile SDKs.
• Stronger send, receive, acknowledge and cancellation state transitions.
• Durable payment outboxes and hardware-backed journals so an interrupted application does not forget whether a payment was sent.
• A fix for an escrow edge case where the payer’s own account was involved.
• An Android networking improvement that lets wallet developers provide a correctly configured thread pool, preventing strict Android socket checks from terminating the application.
• Continued alignment between the Kotlin, Java, JavaScript, Python and Swift SDKs.
Why this matters: an offline payment must not disappear, execute twice or become spendable again merely because a phone lost power between two steps. The wallet must be able to resume from durable evidence rather than guessing what happened.
🔐 5. PRIVATE COMPUTATION AND CRYPTOGRAPHIC PROOFS
MKHE means multi-key homomorphic encryption.
Ordinary encryption protects data while it is stored or transmitted, but the data normally has to be decrypted before it can be processed. Homomorphic encryption is designed to allow certain calculations to be performed directly on encrypted values.
The “multi-key” part means that values encrypted by different participants can contribute to the same protected calculation without every participant first sharing one common secret key.
This week’s MKHE and related proof-system work focused on making the implementation verifiable rather than simply declaring it ready:
• Proof inputs, parameters and resource limits are represented as canonical records instead of informal readiness flags.
• Every stage is bound to one cryptographic transcript, preventing pieces from different proofs or execution contexts from being mixed together.
• The verifier checks committed data, query openings, intermediate proof stages and final consistency conditions rather than trusting values supplied by the proof producer.
• Verification and proving keys can be installed only in a canonical, bounded and non-replaceable form.
• Partial verification does not produce a production-authorizing receipt.
• Sensitive temporary values and randomness are erased after use, including during errors. | 143 |
| 6 |  🛠 Hyperledger IROHA 3 / SORA NEXUS DEVELOPMENT UPDATE
15–22 August 2026
This week’s work focused primarily on reliability, recovery, privacy and safe deployment.
Rather than adding one large user-facing feature, the team strengthened the foundations that allow Iroha 3 to continue operating correctly when validators restart, messages arrive late, storage must be recovered, offline payments are interrupted or a new software build is prepared for deployment.
Here is what changed and why it matters.
⚙️ 1. SAFER CONSENSUS AND VALIDATOR RECOVERY
Sumeragi is Iroha’s consensus protocol: the process through which validators agree on the next block and make it final.
This week, the team strengthened how Sumeragi handles difficult network conditions:
• Messages belonging to an old consensus round are prevented from interfering with newer work.
• Validators recovering after a restart can obtain a missing block body and verify it before continuing.
• Pending blocks now retain clearer information about how far they have progressed toward finality.
• Timeout behaviour was bounded so repeated failures cannot create uncontrolled delays.
• Four-validator tests covered restarts, late joins, disconnected peers, delayed messages, abandoned proposals and recovery by a new validator leader.
Why this matters: a distributed ledger must do more than work under ideal conditions. When machines restart or networks become unreliable, validators must either reach the same correct result or stop safely. They must never finalize conflicting histories because an old message arrived at the wrong time.
💾 2. MORE RELIABLE STORAGE, SNAPSHOTS AND RESTARTS
Kura is Iroha’s durable ledger storage. It preserves blocks and the information required to reconstruct network state after a restart.
Work this week improved the consistency of Kura, snapshots and the Taira deployment environment:
• Snapshot information now survives a restart without changing the network’s topology.
• Lane identities and storage geometry are reconstructed consistently.
• Compatibility was added for an earlier Taira ledger layout without changing the rules used by new networks.
• Auxiliary storage reads were isolated so unrelated writes cannot alter the result being recovered.
• A disposable four-validator Taira development network can now be started, checked and removed through one workflow. It verifies node health, submits a real transaction and confirms that all validators reach the same block height.
In Iroha 3, lanes are parallel processing channels for different categories of activity. Preserving their identities across restarts is essential because transactions, policies and private data spaces may depend on a particular lane.
Why this matters: restarting a validator should reproduce exactly the same ledger and lane structure that existed before the restart. Recovery must not silently reinterpret historical state using newer software rules.
🔄 3. SAFER EXCHANGES BETWEEN DATA SPACES
AXT means Asset Exchange Toolkit.
SORA Nexus can contain multiple data spaces: separately governed execution environments with their own assets, applications, permissions and privacy rules, while still belonging to one shared ledger.
AXT coordinates exchanges between those data spaces. For example, one asset could be transferred in one data space while another asset is transferred in a different data space. The exchange is intended to be atomic: either every authorized part succeeds, or the entire exchange fails.
This week’s work strengthened the security state surrounding AXT: | 170 |
| 7 |  No text... | 263 |
| 8 |  Bitcoin Is Not the Savior
https://x.com/M4K070/status/2089703601858068597 | 585 |
| 9 | https://x.com/M4K070/status/2089342935246766249 | 569 |
| 10 | https://x.com/FearlessWallet/status/2088795670195163534 | 399 |
| 11 | https://x.com/sora_xor/status/2088634347494732280 | 542 |
| 12 |  📣 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. ❤️ | 649 |
| 13 | https://x.com/hl_iroha/status/2088620128296673646 | 415 |
| 14 |  📣 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 | 340 |
| 15 | Shift_credit_from_extraction_to_production.m4a | 489 |
| 16 |  Credit Should Build, Not Extract
https://x.com/M4K070/status/2088431367524860105 | 517 |
| 17 | https://x.com/sora_xor/status/2083481520170577928 | 941 |
| 18 | You can use https://bafybeib37grzb5cddrcwubvjl2xxm5pu5e4grp6ibk4sy7r55keyxqvpca.ipfs.dweb.link/#/swap to access Polkaswap | 713 |
| 19 |  sora.org was updated with new info | 953 |
| 20 | https://polkamarkt.com/#markets/32 | 1 007 |
