Code

Foreign chain probe: fold in the whitelist verifier and judge chain health

Fold the whitelist verifier into the foreign chain probe

Rerun the foreign chain probe when the whitelist changes

Split the foreign chain probe into modules

Revisit foreign chain config registration to base it on diagnostics

node: asset consumption delete is not fsynced, so a VM crash can resurrect a used triple

docs: clarify upgrade order and node/contract compatibility in RELEASES.md

[SPICE data distribution] C2d — the fallback push as recipient re-evaluation

Catch-up drops a fork block that commits just after its parent is marked done, and the node stalls on that branch

PendingBlocksPool::take_block leaks a block hash per block on chunk producers

Chunk witnesses are dropped with no retry after a skipped height (PV87+) and in two orphan-pool races

Child flat-storage registration race during a shard split makes a node reject every later block

A restart during a shard split can strand the node or let GC delete the new shards' state

[TYPE IT] Collapse the key-event forwarding layers in the contract state

bug: foreign chain registrar must ensure the contract accepted the new registry

Dry run of external calls

1Click swap stuck in PROCESSING for 20+ days(no refund) - WBTC on Ethereum, partner: THORSwap

[SPICE data distribution] C2c — one signing-key rule for a block not stored yet

refactor(contract): simplify the node types and their tests

Limits on external calls

TEE localnet: fixes for running several CVMs on one host

[TYPE IT] Store the interface Config in the contract instead of a copy

Remove the unused block entropy from node requests

Upgrade dstack to 0.6

A view call right after a transaction returns `null`; document which finality to request (and a helper to read after write)

After `Promise::and(...).then(callback)`, the callback cannot tell which joined promise failed; a failed transfer leg leaves funds stranded

Structured contract errors (code + message) instead of parsing `Smart contract panicked: …` out of a string

`store::` collections write lazily: document `flush()` before `env::storage_usage()`, or provide a `measure_storage` helper (and a storage estimator for caller-funded deposits)

Publish the tee-verifier wasm and its hash in each release

Document when operators should call verify_tee and clean_invalid_attestations