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

Leveraging OP_RETURN

Inscriptions use OP_RETURN opcode to inscribe data onto the Bitcoin blockchain. This is how Satschain inscribes immutable Satschain transactions (which are EVM like) directly onto the Bitcoin, and thus borrowing Bitcoin’s Data Availability and Security.

The Satschain indexers detect transactions with valid execution instructions within the OP_RETURN field. These transactions undergo validation to ensure adherence to predetermined criteria before being processed in an EVM-compliant execution environment.

PreviousSats InfrastructureNextSats Intel

Last updated 11 months ago

πŸ› οΈ