From 184bd6db4fd5c19542eef39664a352be5068d7c9 Mon Sep 17 00:00:00 2001 From: "dev-portal-updater[bot]" <149019135+dev-portal-updater[bot]@users.noreply.github.com> Date: Fri, 5 Sep 2025 09:00:54 +0000 Subject: [PATCH] feat: update `bitgo-api-docs` This commit updates the BitGo API. --- api.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/api.yaml b/api.yaml index e6fceee..50c490b 100644 --- a/api.yaml +++ b/api.yaml @@ -26151,9 +26151,7 @@ paths: description: (ETH only) Specify forwarder version to use in address creation. To reduce the cost of creating ETH forwarders, BitGo uses a set of forwarder contracts that deploy as a simple proxy to a single implementation (https://eips.ethereum.org/EIPS/eip-1167). Additionally, forwarders deploy using opcode, CREATE2, enabling them to deploy only when needed (https://eips.ethereum.org/EIPS/eip-1014). These forwarders otherwise operate identically to prior ETH forwarders. Use this flag to specify the forwarder contract version when deploying a forwarder contract. Use 0 for the older forwarder (https://github.com/BitGo/eth-multisig-v2). Use 1 for the new fee-improved forwarder (https://github.com/BitGo/eth-multisig-v4). Use 2 for NFT-supported forwarders and version 2 wallets. Use 3 for MPC wallets. Use 4 for forwarders with the same functionality as v2 but with some changes. v4 is applicable for Arbitrum, Optimism, ZkSync, and other EVM-compatible chains that we will onboard in the future. Use 5 for new MPC based wallets with wallet-version 6 minimum: 0 maximum: 5 - referenceAddress: - type: string - referenceCoin: + evmKeyRingReferenceAddress: type: string onToken: type: string @@ -44300,7 +44298,7 @@ components: type: string salt: type: string - referenceWalletId: + evmKeyRingReferenceWalletId: type: string required: - pendingChainInitialization