Withdrawals abroad will wait for a purpose-and-counterparty questionnaire, and incoming deposits from nonresidents can be held or returned. The data goes to the central bank monthly.
The permissionless 0x02 route, now on the Hoodi testnet with mainnet expected in Q4, compares with a 2.4 ETH bond on the existing route. Fees catch up only once a key holds enough stake.
Victims of the April exploit hold one DFX per dollar lost; the pool paid about 0.0104 USDT per token at launch. Redeeming burns the token and gives up a share of future deposits.
A new tfVaultDonate flag on VaultDeposit adds assets that raise every share's value. Only the owner may donate, and only into a vault with shares outstanding. It is gated by LendingProtocolV1_2.
Parity's repository, where Polkadot SDK networks registered address prefixes, stopped accepting changes. MADAR Network forked it on 4 October and offers to hand it over to an official successor.
The 2 October order clears the exchange rule, not the registration: trading dates for the proposed BITH and ETHK are unconfirmed. The products are commodity trusts, not 1940 Act funds.
Three changes this week deal with what happens after something goes wrong, from a hack to a defaulted loan to a signature that pays the wrong address. Each puts the cost somewhere different.
Such a signature commits to no output at all, so the destination could be swapped. The PSBT path still signed it; the check now sits in shared signing code. Not yet in a release.
The workflow takes an ISO 20022 corporate action message, builds one register from four ledgers, screens wallets and pays in stablecoins or tokenised deposits. It is a challenge entry, not a live service.
Three unrelated changes this week deal with the same question: which secrets a wallet must hold, who can restore them, and what exactly gets signed.
Today Bitcoin Core's wallet cannot accept a miniscript preimage except through PSBT fields set by another tool. A new syntax, sha256(preimage(HEX)), would let the wallet store it and sign.
