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. Smart Contracts

Leverage Compass Library for contracts

Compass library is a special type of contract provided by Satschain on Satschain network, it allows users to convert their BTC addresses to EVM compatible hexadecimal addresses.

Smart contract programmers on Satschain are advised to use this contract to convert BTC addresses to EVM addresses, rather than rolling out their own versions.

This library enables address conversions at runtime, over other several solutions that we pondered over which allowed only compile-time static conversions.

PreviousBuild a ContractNextWhat type of contracts can be supported?

Last updated 11 months ago

📝