Base-Solana Bridge Executor Route

v2.0 Migration Guide (from 1.x)

Breaking change: Auto-registration on import has been removed. Consumers must now call register() explicitly before using any route factories.

Before (1.x)

import { baseBridgeRoute } from "@wormhole-labs/base-bridge-executor-route";
// Protocols auto-registered on import
const route = baseBridgeRoute(config);

After (2.x)

import {
  register,
  baseBridgeRoute,
} from "@wormhole-labs/base-bridge-executor-route";
register(); // call once, at app startup
const route = baseBridgeRoute(config);

register() is idempotent. For tree-shake-friendly bundling, platform-specific registers are available at /evm and /svm subpaths.

Transfer Example

This project implements a Wormhole SDK route for Base-Solana bridge transfers with executor service integration.

Prerequisites

First, install dependencies and build the project:

npm ci && npm run build

Configure Environment Variables

Set your private keys as environment variables:

export EVM_PRIVATE_KEY=<your_evm_private_key>
export SVM_PRIVATE_KEY=<your_svm_private_key>
export EXECUTOR_API_URL=<your_executor_api_url>

⚠️ Note:

• All relevant contract addresses and constants are defined in src/consts.

⚠ This software is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Or plainly spoken - this is a very complex piece of software which targets a bleeding-edge, experimental smart contract runtime. Mistakes happen, and no matter how hard you try and whether you pay someone to audit it, it may eat your tokens, set your printer on fire or startle your cat. Cryptocurrencies are a high-risk investment, no matter how fancy.