FAQ
What is Signet?
How does Signet differ from traditional rollups?
Signet differs in several key ways:
- It doesn’t use proving systems or state roots, which reduces computational overhead.
- It uses market-based cross-chain transfers instead of complex bridging mechanisms.
- It replaces block auctions and centralized rollup sequencing with a controlled block inclusion mechanism.
- It introduces conditional transactions for secure, atomic cross-chain operations.
How does Signet handle cross-chain transfers?
Signet uses market-based mechanisms and conditional transactions for cross-chain transfers. This allows for secure, instant transfers between Ethereum and Signet without the need for lockup periods.
Is Signet suitable for all use cases?
How does Signet ensure fair block production?
What tokens are supported for bridging?
Signet supports ETH, USDC, USDT, and WBTC for bridging between Ethereum and Signet. Custom assets may be created within Signet but cannot be bridged from Ethereum without coordination with the Signet team.
See Moving Assets to Signet for details.
What is Pecorino?
Pecorino is a private Ethereum testnet for rollup and application experimentation, available to the public for testing and validation. It includes RPC endpoints, faucet, explorer, and transaction cache infrastructure for development.
See Pecorino Quickstart for network configuration and contract addresses.
How does Signet guarantee atomic cross-chain execution?
Signet requires cross-chain transfers to be fully executed in the same block on both chains. If the transfer is not fully executed, the transaction is invalid and has no effect on Signet’s state—as if the transaction never existed.
See Cross-chain Transfers for more details.
Do I need to run my own Ethereum or Signet node?
No. You can use public RPC endpoints. For Pecorino testnet, see the Pecorino Quickstart for endpoints. For block builders, RPC access can be configured via environment variables—running your own nodes is optional infrastructure.
See Environment Variables for builder configuration.