[sdk-generation-automation]

Changelog

2026-11-10

Added

Add TON per-wallet fee breakdown (Early Access)

Products: Transactions

Scope: API + SDKs

• What's new
  Transaction responses now report what a TON transfer cost each of your wallets, with per-role sender and recipient amounts plus a detailed nanoTON fee breakdown for TON and Jetton transfers.

• Impact
  Customers can see the exact TON cost and credited amount for each of their wallets in a transfer; existing integrations are unaffected because all fields are optional additions.

Affected endpoints:

1. Get a specific transaction by external transaction ID
2. Get a specific transaction by Fireblocks transaction ID
3. Get transaction history

Add trading pairs discovery endpoint

Products: Trading

Scope: API + SDKs

• What's new
  Adds an endpoint that lists supported base/quote trading pairs per provider, with filters for asset, chain, transfer rail, side, trade class, provider, and account.

• Impact
  Customers can discover which pairs, rails, and amount limits are tradable before requesting rates or quotes.

Affected endpoints:

1. Get trading pairs

Changed

UTXO Management is now generally available

Products: Off exchanges, Transactions

Scope: API + SDKs

• What's new
  UTXO Management has graduated from beta to general availability, and the beta notices have been removed from its endpoints and parameters.

• Impact
  Documentation only - beta notices removed from the referenced schemas; requests and SDK methods are unchanged, no call changes are required.

Affected endpoints:

1. Create a new transaction
2. Estimate transaction fee
3. Add Collateral
4. Remove Collateral

UTXO Management is now generally available

Products: Vaults

Scope: API + SDKs

• What's new
  UTXO Management has graduated from beta to general availability, and the beta notices have been removed from its endpoints and parameters.

• Impact
  Documentation only - beta notices removed from the referenced parameters; requests and SDK methods are unchanged, no call changes are required.

Affected endpoints:

1. Get max spendable amount in a transaction

UTXO Management is now generally available

Products: UTXO Management

Scope: API + SDKs

• What's new
  UTXO Management has graduated from beta to general availability, and the beta notices have been removed from its endpoints and parameters.

• Impact
  SDK users will find UTXO Management grouped under a new name without the beta suffix, so existing SDK calls to this group will need to be updated.

Affected endpoints:

1. Get UTXO selection config
2. Upsert UTXO selection config
3. Attach or detach labels to/from UTXOs
4. Get vault and asset UTXO selection config
5. Upsert vault and asset UTXO selection config
6. List unspent outputs (UTXOs)

---

[github-actions]

Thanks for bringing this request to our attention. We'll review and provide updates soon. (Note that this SDK code is auto generated)

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Recently published: npm follow-redirects published 2 weeks ago Location: Package overview From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block

View full report

[semgrep-code-fireblocks]

Semgrep found 6 block-public-registry-refs-in-package-lock findings:

• package-lock.json
  • L1298 - Triage
  • L1335 - Triage
  • L1438 - Triage
  • L1719 - Triage
  • L1929 - Triage
  • L3375 - Triage

🟠 High severity issue identified in your code:

package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/node-releases/-/node-releases-2.0.59.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run npm install and commit the regenerated lockfile.