Sismo Docs
  • Welcome to Sismo
    • What is Sismo?
  • Build with Sismo Connect
    • Overview
    • Installation
    • Sismo Connect Cheatsheet
    • Tutorials
      • Get Your appId - Create a Sismo Connect App
      • Onchain Tutorial (1/2): Code Your Airdrop Contract With Privately-Aggregated Data
      • Onchain Tutorial (2/2): Deploy Your Airdrop Contract
    • Technical Documentation
      • Sismo Connect Configuration
      • Auths
      • Claims
      • Signature
      • Packages
        • Sismo Connect Client: Request
        • Sismo Connect React: Request
        • Sismo Connect Server: Verify Offchain
        • Sismo Connect Solidity Library: Verify Onchain
    • FAQ
  • Data Groups
    • Overview
    • Tutorials
      • Factory Guide: Create a Data Group in 5 Minutes
      • Sismo Hub Guide: Create Data Groups Programmatically
      • Sismo Hub Guide: Add a Data Provider to the Sismo Factory
    • Sismo Hub
      • Sismo Hub Repository
        • Group Generators
        • Data Providers
        • Data Operators
        • Command Line Interface
      • Accounts Registry Tree
  • Data Vault
    • Overview
    • Vault Identifiers
    • Proving Schemes
      • Hydra-S1
      • Hydra-S2
    • Commitment Mapper
  • Resources
    • Deployed Contract Addresses
    • Sismo API
      • API Links
      • Query From a Client
      • Group
        • Get groups
        • Get group snapshots
      • Common Parameters
      • Advanced Filtering
      • Transaction
  • Links
    • Sismo Landing Page
    • Sismo Factory
    • Sismo App Store
    • Sismo Builder Resources
    • GitHub
    • Discord
    • Twitter
    • Blog
Powered by GitBook
On this page
  1. Build with Sismo Connect

FAQ

Frequently asked questions.

PreviousSismo Connect Solidity Library: Verify OnchainNextOverview

Last updated 1 year ago

What to do if I am stuck with pending transactions on a fork network?

You can end up in this situation if you are following the or the onchain boilerplate. If it is the case, you are unable to make any transaction work on your local chain, and you surely view this type of message on your MetaMask:

To get rid of this issue, you will need to go to "Settings > Advanced > Clear activity tab data" while connected to the fork chain (so anvil node is still running).

You can then stop your anvil local node and the frontend of your application before relaunching the anvil node with yarn chain and then your frontend with yarn dev. If you are still stuck with this restart, come ask your questions in our in the #dev-support channel or in our .

onchain tutorial
Discord
Dev Telegram