Satz
  • 👋Welcome
  • 🤝Introduction
    • What is SatsChain?
    • How is SatsChain different from L2s?
    • What is the security paradigm for SatsChain?
  • 📇Use Cases
    • Cerebrum (Retail use cases)
    • Institutional use cases
    • Anchoring L2s on BTC
  • 🖥️For Developers
  • 📝Smart Contracts
    • What is smart contract?
    • Build a Contract
    • Leverage Compass Library for contracts
    • What type of contracts can be supported?
  • 🔐Contract Deployment
    • Deploy smart contract on SatsChain
  • ⛓️Core Principles
    • What are Inscriptions?
    • Taproot/native-segwit user addresses
    • What is EVM?
    • What is Solidity?
    • How BTC connects with EVM?
  • 🛠️Sats Infrastructure
    • Leveraging OP_RETURN
    • Sats Intel
    • Sats Nuclei
    • Sats Reverse Processor (SRP)
    • Sats connector
    • Compass (EVM <> BTC)
      • Compass Solidity Library
      • Compass Logic
      • Rainbow table
  • ⚙️Configurations
    • Testnet
    • Mainnet
  • 📚Developer Guide
    • Deploy contract
    • Anchoring of L2s
    • How to interact with Smart Contract?
    • Fetching current state via JSON RPC integration
    • How to integrate compass library in solidity code
  • Website
  • WhitePaper
  • Twitter
Powered by GitBook
On this page
  1. Sats Infrastructure
  2. Compass (EVM <> BTC)

Compass Logic

The Compass module handles the core operations of converting addresses between BTC and EVM formats. This conversion is essential because the Sats Nuclei (the EVM engine) operates solely with EVM addresses, while users interact exclusively with BTC addresses.

The Compass module ensures that requests from users, which involve BTC addresses, are converted to EVM addresses for processing by the EVM engine. Conversely, responses from the EVM engine are converted back into BTC addresses, as users are uninterested in the internal EVM addresses.

PreviousCompass Solidity LibraryNextRainbow table

Last updated 11 months ago

🛠️