xSafe
  • Overview
  • 💻Developers
    • Smart Contracts
      • Create3Factory
  • 🔍References
    • FAQ
    • Deployed Contracts
    • Glossary
    • GitHub
    • User Interface
  • 💬Community
    • Telegram
    • Twitter
Powered by GitBook
On this page
  • The Multi-Chain Deployment Trilemma
  • The Problem with EOA Deployments
  • The Problem with CREATE2 Deployments
  • The Problem with CREATE3
  • The Solution: xSafe

Was this helpful?

Overview

xSafe is the new gold standard for intent-based CREATE3 contract deployments. Deploy your contracts to the same address on many chains.

NextSmart Contracts

Last updated 1 year ago

Was this helpful?

The Multi-Chain Deployment Trilemma

The Problem with EOA Deployments

Traditionally, achieving the same address on many chains requires careful (manual) EOA nonce management. Mess up the nonce once, start all over.

The Problem with CREATE2 Deployments

The Problem with CREATE3

A CREATE3 approach offers an elegant solution, irrespective of contract bytecode, but still requires users to memorize salts.

The Solution: xSafe

  • No need to track nonces.

  • No need to create/store salts.

  • No need for uniform constructor args across chains.

  • No worrying about address front-running on other chains.

The easiest way to deploy your contracts using xSafe is through the user interface.

The CREATE2 opcode can generate identical addresses, but when constructor arguments vary across chains, differing contract bytecode results in distinct addresses. An intent-based solution, , obviates salt storage, but addresses still depend on contract bytecode.

xSafe's contract achieves same-address deployments with:

Under the hood, salts are derived from signatures, thereby allowing to deploy contracts on behalf of principals (signers).

like this
Create3Factory
principal
agents
xSafechainrule_io
xSafe User Interface
Logo