Protocol
Smart Contract Verification on RamaScan
Understand why source verification matters, what compiler settings must match and how proxy contracts should be verified.
In this guide
Practical outcomes
- Prepare standard JSON input
- Verify implementation and proxy
- Publish transparent source
How this works in practice
Understand why source verification matters, what compiler settings must match and how proxy contracts should be verified.
A Ramestta protocol flow should be explained as a sequence: a wallet or application submits an EVM transaction, Bor executes it, the validator and Heimdall layers coordinate network state, and checkpoints provide a verifiable path toward Polygon and Ethereum-aligned settlement.
Implementation sequence
Turn the topic into a controlled implementation rather than a one-off transaction. Each step below should leave evidence a teammate, user or auditor can independently review.
- 01. Prepare standard JSON input. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 02. Verify implementation and proxy. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
- 03. Publish transparent source. Define the expected result, capture the relevant onchain or operational evidence, and stop for review if the result differs from the plan.
Evidence to retain
Useful evidence includes the transaction hash, block number, validator or checkpoint status, and the corresponding RamaScan record. Do not treat a UI success state as the only confirmation for a high-value action.
Control point
Fast execution feedback and deeper settlement are different confirmation stages. Product teams should state which stage their users are seeing and choose confirmation rules appropriate to the value at risk.
Related guides
What Is a Layer-3 Blockchain?
A practical introduction to Layer-3 execution networks and why application-grade performance needs a layer focused on user experience, predictable costs and high-volume activity.
Ethereum, Polygon and Ramestta: The Three-Layer Stack
See how Ethereum settlement, Polygon checkpoint infrastructure and Ramestta execution work together in the network design.
Layer-3 vs Layer-2: What Changes for Applications?
Compare Layer-2 and Layer-3 tradeoffs for latency, fee predictability, throughput and application-specific user experience.