BIFROST Network
  • Introduction
  • Bifrost Network Architecture
    • Consensus
    • Cross-Chain Communication Protocol (CCCP)
    • Oracle Service
  • Running a Node
    • Basic-Node Requirements
    • Full-Node Requirements
    • Validator Account Management
    • Guide for Operators
      • Setting up an Endpoint Node
        • Using Docker
        • Using Systemd
      • Setting up a Validator Node
        • Using Docker
        • Using Systemd
      • Setting up a Relayer
        • bifrost-relayer.rs
        • bifrost-relayer.py (Deprecated)
      • Chain Data Snapshots
      • Trouble Shooting
        • Testnet Chain Sync Issue
    • System Monitoring
      • Prometheus and Grafana
      • Sentry
  • Nominators
  • Developer Documentations
    • Ethereum API
      • Ethereum Precompiled Contracts
      • Libraries
      • Developer Environments
    • Bifrost Precompiled Contracts
      • Staking
      • Governance
      • RelayManager
    • Pallet Interfaces
      • BfcStaking
      • BfcUtility
      • BfcOffences
      • RelayManager
    • Client API
      • JSON-RPC API
        • author
        • chain
        • childstate
        • debug
        • eth
        • grandpa
        • net
        • offchain
        • payment
        • rpc
        • state
        • system
        • trace
        • txpool
        • web3
      • Explorer API
      • Runtime API
    • Cross-Chain Transaction and Oracle API
      • Price Oracle Contract API
      • Socket Contract API
    • Testnet Faucet
  • Governance
  • Security
  • Tokens & Assets
    • Unified Token
    • Inflation Model
  • Add Network
    • Pockie
    • MetaMask
  • Bridge
    • Bridge Guide
      • Depositing to the Bifrost Network
      • Withdrawing to another network
    • Glossary
  • Staking
    • Staking Guide
      • Stake BFC
      • Unstake BFC
    • Glossary
      • All Validators
      • My Staking Status
  • Language
    • 바이프로스트 네트워크 가이드
Powered by GitBook
On this page
  • traceBlockByHash(id: BlockHash, params?: TraceParams): Vec<TransactionTrace>
  • traceBlockByNumber(id: BlockNumber, params?: TraceParams): Vec<TransactionTrace>
  • traceTransaction(transaction_hash: hash, params?: TraceParams): TransactionTrace
  1. Developer Documentations
  2. Client API
  3. JSON-RPC API

debug

traceBlockByHash(id: BlockHash, params?: TraceParams): Vec<TransactionTrace>

  • jsonrpc: debug_traceBlockByHash

  • summary: traceBlockByHash accepts a block hash and will replay the block that is already present in the database. For the second parameter, see theTraceParams reference.

traceBlockByNumber(id: BlockNumber, params?: TraceParams): Vec<TransactionTrace>

  • jsonrpc: debug_traceBlockByNumber

  • summary: traceBlockByNumber accepts a block number and will replay the block that is already present in the database. For the second parameter, see theTraceParams reference.

traceTransaction(transaction_hash: hash, params?: TraceParams): TransactionTrace

  • jsonrpc: debug_traceTransaction

  • summary: The traceTransactiondebugging method will attempt to run the transaction in the exact same manner as it was executed on the network. It will replay any transaction that may have been executed prior to the current one before it finally attempts to execute the transaction that corresponds to the given hash. For the second parameter, see the TraceParams reference.

PreviouschildstateNexteth

Last updated 2 years ago