LogoLogo
  • Introduction
  • Quick Start
    • Developing Cross Chain Dapps
      • Standard Relayer
      • Specialized Relayer
    • Tutorials
      • Hello Wormhole
        • Hello Wormhole Explained
        • Beyond Hello Wormhole
      • Hello Token
      • CCTP
        • USDC Transfers With Connect SDK
      • Simple Relayer
        • Advanced Relayer Example
    • Demos
    • Wormhole Connect: Bridging Made Easy
  • Explore Wormhole
    • Architecture
    • Security
    • Core Contracts
    • Guardians
    • VAAs
    • Relayers
    • Spy
    • Gateway
      • Onboarding
  • Reference
    • Constants Reference
    • Development Environment
      • Tilt
      • Tooling
    • Blockchain Platforms
      • Algorand
      • Aptos
      • CosmWasm
      • EVM
        • Relayer
      • Near
      • Solana
      • Sui
    • API Docs
      • Wormholescan API
    • SDK Docs
      • Legacy SDK
    • CLI Docs
    • Glossary
  • Wormhole Connect
    • Overview
    • Routes
    • Features
    • Configuration
  • Native Token Transfers
    • Overview
      • System Components
      • Deployment Models
    • Deployment
      • Installation
      • Deploy to EVM
      • Deploy to Solana
      • Post Deployment
    • Configuration
      • Rate Limiting
      • Access Control
    • Security
    • Custom Transceivers
    • Architecture
      • EVM Message Lifecycle
      • Solana Message Lifecycle
  • Queries
    • Overview
    • Getting Started
    • FAQs
  • MultiGov
    • Overview
    • Getting Started
    • Deployment
      • Configuration
    • Upgrading
    • Architecture
    • Guides
    • FAQs
  • External Links
    • Explorer
    • Ecosystem
    • Guardian Dashboard
    • Portal Bridge Docs
    • Discord
    • Twitter
    • Github
Powered by GitBook
On this page
  • Tooling Installation
  • Development Stages
  • Initial Development
  • Integration
  • Prepare for Deployment
  • Validator Setup
  • Tilt
  • Deploying to public networks
  • Testnet
  • Mainnet

Was this helpful?

Edit on GitHub
  1. Reference

Development Environment

Last updated 1 year ago

Was this helpful?

Developers building for smart contract integration will want to get a development environment setup to allow testing the full integration, possibly including VAA generation and relaying.

Tooling Installation

The should be installed regardless of environments chosen.

Each environment has its own set of recommended tools. To begin working with a specific environment, see the recommended tools on its

Development Stages

Different approaches to development and testing are recommended at different stages of application development.

Initial Development

During initial development of an on-chain application, the best option is to use the native tools available in the environment.

For the specific native tools recommended, see the page for the you're interested in.

For any methods the program that require some message be sent or received, it's recommended to set up some Mock Guardian or Emitter to provide signed VAAs.

A Mock utility is available and an example of its use can be found in the

This approach allows for more rapid prototyping and iteration without waiting for, or debugging issues related to, Wormhole.

Integration

For integration to Wormhole and with multiple chains, the simplest option is to use the chains' testnets.

In choosing which chains to use for integration testing, consider which chains in a given environment provide easy access to testnet tokens and where block times are fast.

The variation in host environments causing unique issues and the computational intensity of multiple simultaneous local validators can make it difficult or time consuming to setup. Prefer testnets for the simplest integration testing.

Prepare for Deployment

Once you've finished initial development of the application and performed integration testing, you may want to set up some CI test environment.

Validator Setup

If you'd like to set up a local validator environment, follow the setup guide for Tilt.

Tilt

A full-fledged Kubernetes deployment of every chain connected to Wormhole, along with a Guardian node. Usually takes 30 min to spin up fully, but comes with all chains running out of the box.

Deploying to public networks

Testnet

When doing integration testing on testnets, keep in mind that there is a single Guardian node watching for transactions on various test networks. Because testnet only has a single Guardian, there's a small chance that your VAAs will not be processed. This rate is not indicative of performance on mainnet, where there are 19 Guardians watching for transactions.

Mainnet

Find links for testnet faucets in the

A developer may prefer standing up a set of local validators instead of using the testnet. For this option, is available to run local instances of all the chains Wormhole supports.

For that, the best option is likely to be since it allows you to spin up any of the chains supported by Wormhole in a consistent environment.

The testnet contract addresses are available on the page for the each .

The testnet Guardian RPC configuration is available on the .

The mainnet contract addresses are available on the page for each .

The mainnet Guardian RPC configuration is available on the .

Worm CLI Tool
environment page
Environment
here
Wormhole Scaffolding repo
blockchain details section
Full setup guide for Tilt
environment
environment
Tilt
Tilt
SDK page
SDK page