ESMA's third-country CCP reporting consultation closes on 12 October
A proposed annual EMIR reporting framework would require clearing members and clients to report activity at recognised third-country CCPs; responses are due 12 October 2026.
Everything we have published, newest first, from every desk.
A proposed annual EMIR reporting framework would require clearing members and clients to report activity at recognised third-country CCPs; responses are due 12 October 2026.
Litecoin Core 0.21.5.8 adds a soft-forking consensus rule at block 3,172,640 and folds in a 0.21.5.7 security fix that was distributed privately to mining pools rather than published.
A crypto filing this week registered zero new shares and was reported by careful outlets as exactly that. The habit that keeps a desk honest is refusing to collapse four distinct events into one word.
The regulator is investigating potential breaches of the 2017 money-laundering regulations by Euro Exchange Securities UK between February 2020 and June 2026 — the firm is already in special administration.
A Polkadot forum post introduces JamScript, a language and SDK meant to let developers build JAM applications without understanding JAM's internals. It is a proposal and a discussion, not a shipped platform.
The change guards an assertion in the silent-payments reference code so it only runs when the optional expected value is present, instead of dereferencing a None.
A draft opcode would create contracts that live only for the duration of a single transaction; the latest update clarifies ephemeral-account semantics and fixes its EIP references.
The validator release adds vote-commission CLI commands and improves send-error stats in votor-transport — the plumbing behind the Alpenglow consensus change now landing in a mainnet-suitable build.
A 21 September post-effective amendment on Form POS AM refreshes disclosures for Bitwise's XRP ETF trust and registers zero new shares — a maintenance filing, not an SEC green light or a launch.
cardano-node 11.1.2 optimises memory in time lock scripts. The release notes keep two known regressions against 11.0.1 in view rather than claiming the problem is closed.