fix(release): include ed25519_bip32_wasm.js in the published npm tarball
Signed-off-by: Pat Losoponkul <[email protected]>
Signed-off-by: Pat Losoponkul <[email protected]>
Signed-off-by: Akhil Repala <[email protected]>
feat: use backbone peer as default peer
* mithril-stm from `0.10.32` to `0.10.33`
Change the time for each call so that ghc is forced to run every loop itteration.
Co-Authored-By: Claude Fable 5 <[email protected]>
Keep the mask-interpretation logic out of the Sync service handlers. The `BlockMask` strategy and its path parsing now live in `masking.rs` next to `apply_mask`, with a module doc explaining when each applies: `apply_mask` is a post-hoc JSON projection for low-volume Query responses, `BlockMask` is a source-level projection for the high-volume Sync streams. The handlers only extract the paths and consult the flags while building the version-specific `AnyChainBlock`. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Co-Authored-By: Claude Fable 5 <[email protected]>
When a DecrementTx was applied on-chain before the head was closed (snapshotVersion != openVersion), partialFanout passed fullUTxO to buildAndVerifyAccumulator. But the closed datum's accumulatorCommitment was built from utxoForProof (snapshot UTxO including the decommit set), so the check always failed with StaleChainState, leaving the head stuck. Separate the accumulator proof input from the distribution set by adding a proofUTxO parameter to partialFanout and findFittingFanoutTx. The FanoutTx call site now passes utxoForProof as proofUTxO so it matches what the closed datum was committed to, while fullUTxO (the actual distribution set) is used unchanged for fanout outputs. Signed-off-by: Sasha Bogicevic <[email protected]>