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. Developer Guide

Fetching current state via JSON RPC integration

PreviousHow to interact with Smart Contract?NextHow to integrate compass library in solidity code

Last updated 10 months ago

After you have deployed your contract, you will need to query the current state of your deployed contract to update your DApp. For this use case you can use the JSON RPC apis exposed by Sats Intel.

This JSON-RPC endpoint resembles the JSON RPC apis exposed by Ethereum nodes like Besu. To avail this functionality for your DApp, you will need access keys, connect with our team at , to get your access keys.

📚
query@satschian.xyz