Master into rel latest#9003
Merged
Merged
Conversation
- Adds 76 new tokens for the Robinhood EVM chain, plus their OFC equivalents. - Consolidate all existing hoodeth/thoodeth tokens into dedicated files. Ticket: CECHO-1213
WCN-865 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
WCN-865 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…y-yarn-audit-ci-step-with-retry-logic fix(ci): retry yarn audit on transient network errors (WCN-865)
Pins the retry binary to an exact version and checksum to address supply-chain security concerns in the npm publish pipeline. WCN-865 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…y-yarn-audit-ci-step-with-retry-logic fix(ci): pin EricCrosson/retry to exact version and SHA256 digest
…allets
TSS wallets were missing `buildParams.recipients` after `buildTokenEnablements`
because the TSS branch only called `prebuildTransaction(buildParams)` without
first mapping `enableTokens → recipients`. The non-TSS branch correctly did this
mapping. When `verifyTransaction` runs (`txParams = { ...txPrebuild.buildParams,
...params }`), `txParams.recipients` was undefined, causing `validateRawReceiver`
in near.ts to throw "missing token name in transaction parameters".
Unlike the non-TSS path, `enableTokens` is kept on `buildParams` for TSS since
the server needs it to build the enableToken intent.
Adds a regression test that exercises the real production call path —
using `txPrebuild.buildParams` as `txParams` — which is what the existing
TSS tests failed to do.
TICKET: WP-5782
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…sing-recipients fix(sdk-core): populate recipients in buildTokenEnablements for TSS wallets
Ticket: CECHO-1297 TICKET: CECHO-1297
feat: onboards spaceX token
feat: introduce SUNSETTING coin feature for SEI
Update checksum from 15224553f40d5d16dcc1a696798741227c79670a41f43e522002e634aa1d7c64 to d207746ff0eda67c706df25e88c02520f0cf3172279eb8eec8224fb0d3558911 in both publish.yml and npmjs-release.yml. Ticket: VL-6482 Session-Id: 97fea898-2e16-47ff-b0b5-47798132a382 Task-Id: 3e3641a7-3d6a-483a-9b74-84f4ed665323
ci: fix incorrect pinned SHA for EricCrosson/retry@v1.4.8
feat(sdk-coin-starknet): implement deploy account transaction support
feat(statics): onboard Robinhood EVM tokens
Ticket: CHALO-573
…guard
Two related cleanups enabled by dead-code removal in the parent PR:
1. **Delete fetchInputs.ts** — getTxInputs and getPsbtTxInputs are no
longer called anywhere after the parent PR's dead-code removal.
2. **Remove fee guard from verifyTransaction** — the
`inputAmount - outputAmount < 0` check in
fixedScript/verifyTransaction.ts is unreachable dead code. The PSBT
path calls psbt.parseTransactionWithWalletKeys (wasm), whose Rust
implementation uses checked_sub to compute miner_fee and returns
ParseTransactionError::FeeCalculation ("Fee calculation error: outputs
exceed inputs") if total output value exceeds total input value. This
fires before the TypeScript guard would ever run. A new unit test in
test/unit/transaction/fixedScript/explainPsbt.ts verifies this: it
tampers a PSBT's witnessUtxo.value to make outputs > inputs and
asserts that explainPsbtWasmBigInt throws with that message.
Refs: T1-3279
feat(sdk-core): added canton types in tss prebuild flow
refactor(abstract-utxo): delete fetchInputs and remove redundant fee guard
…tUtxoCoin The only remaining caller was the deleted fetchInputs and the doge override that just delegated to super. Remove the method, drop the doge override, and remove the now-unused createTransactionFromHex stubs from verifyTransaction tests. Refs: T1-3279
BitGoPsbt.fromBytes accepts NetworkName = UtxolibName | CoinName, so the round-trip through utxolib.getNetworkName is unnecessary. Drop the utxolib import from decode.ts. Refs: T1-3279
…h wasm/coinName equivalents - supportsBlockTarget: compare coinName instead of utxolib network objects - isSupportedScriptType: use fixedScriptWallet.supportsScriptType from wasm-utxo - postProcessPrebuild: delete the psbt-lite detection block and the allowNonSegwitSigningWithoutPrevTx flag end-to-end (wasm-utxo signing is permissive by default and never read the flag) Refs: T1-3279
…rmat Replace utxolib.addressFormat.toOutputScriptAndFormat / fromOutputScriptWithFormat with wasm-utxo's address.toOutputScriptWithCoin / fromOutputScriptWithCoin. Detect address format by trying each candidate and checking which round-trips byte-equal. Refs: T1-3279
…branches - isChainCode / scriptTypeForChain -> ChainCode.is / ChainCode.scriptType (wasm-utxo) - hasKeyPathSpendInput: drop unreachable utxolib.bitgo.UtxoPsbt branch and isTransactionWithKeyPathSpendInput call (DecodedTransaction is now BitGoPsbt only) - validAddressTypes: inline the 2-of-3 list instead of utxolib.outputScripts.scriptTypes2Of3 - Drop unused RootWalletKeys / UtxoNetwork type re-exports and the now-empty utxolib bitgo import Three utxolib references remain in abstractUtxoCoin: the ScriptType2Of3 type re-export, the deprecated network getter (still used by tests), and the top-level utxolib import that backs both. Refs: T1-3279
…orkFromCoinName Drop the deprecated coin.network getter from AbstractUtxoCoin and the getNetworkFromCoinName helper from names.ts. Tests that previously called coin.network now call the test-local getNetworkForCoinName(coin.name) from util/utxoCoins. With this, names.ts no longer depends on utxolib. Refs: T1-3279
feat(statics): onboard polygon, avaxc, tempo
chore(bobaeth): updated coin features for wp
feat(sdk-core): disable active operation pre-flight check in DefiVault
feat: exclude singapore trust for ab1
…st-passkey-for-onchain-walletsgeneratewallet fix(sdk-core): persist passkey for onchain generateWallet
chore: Rename ton to gram following the rebrand
alextse-bg
force-pushed
the
master-into-rel-latest
branch
2 times, most recently
from
628b99b to
775df98
Compare
margueriteblair
approved these changes
Jun 11, 2026
alextse-bg
force-pushed
the
master-into-rel-latest
branch
2 times, most recently
from
c997fe8 to
96f4834
Compare
alextse-bg
force-pushed
the
master-into-rel-latest
branch
from
96f4834 to
746e5de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.