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

Was this helpful?

Edit on GitHub
  1. Native Token Transfers
  2. Configuration

Access Control

Owner and Pauser Roles

Pausing the NTT manager contract will disallow initiating new token transfer. While the contract is paused, in-flight transfers can still be redeemed (subject to rate limits, if configured).

NTT can be paused on a particular chain by updating the paused parameter on the deployment to true via the NTT CLI, and then performing ntt push to sync the local configuration with the on-chain deployment.

  • Owner: Full control over NTT contracts, can perform administrative functions. Has the ability to un-pause contracts if they have been paused.

  • Pauser: Can pause NTT contracts to halt token transfers temporarily. This is crucial for responding quickly to potential risks without a prolonged governance process. Cannot un-pause contracts.

Note that while the Pauser has the ability to pause contracts, the ability to un-pause contracts is callable only by the Owner.

The contract can be paused via the contract Owner or the Pauser address. Since the contract Owner address is typically a multi-sig or a more complex DAO governance contract, and pausing the contract only affects the liveness of token transfers, protocols can choose set the Pauser address to be a different address. This can help ensure that protocols are able to respond very quickly to potential risks without going through a drawn-out process.

Consider separating Owner and Pauser roles for your multichain deployment. Owner and Pauser roles are defined directly on the NttManager.

Last updated 10 months ago

Was this helpful?