agoric-chain-snapshot

Inject bundles into captured mainnet swing-store snapshots to reproduce Agoric contract-upgrade failures.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill agoric-chain-snapshot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agoric-chain-snapshot
Source: https://github.com/kriscendobot/garden/tree/main/skills/agoric-chain-snapshot
Command: npx skills add https://github.com/kriscendobot/garden --skill agoric-chain-snapshot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, lz4, tar, sqlite3, rsync, wget, node, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the difficulty of debugging contract-upgrade failures by enabling the reproduction of issues against actual mainnet swing-store state, rather than relying on synthetic or stale environments.

Core Features & Use Cases

  • Mainnet Snapshot Acquisition: Fetches and prepares real Agoric mainnet swing-store snapshots for offline analysis.
  • Faithful Reproduction: Provides drivers to inject bundles and trigger contract-control upgrades, allowing developers to verify fixes against the exact state that caused a failure.
  • Use Case: When a contract upgrade fails due to resource constraints like XS value-stack overflows, use this Skill to import the failing bundle into a captured mainnet snapshot and validate that a code patch resolves the issue.

Quick Start

Use the agoric-chain-snapshot skill to fetch the latest Polkachu snapshot and run the reproduction driver against the captured swing-store.

Frequently Asked Questions about agoric-chain-snapshot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce an Agoric contract-upgrade failure against real mainnet swing-store state?

To reproduce Agoric contract-upgrade failures, fetch a mainnet swing-store snapshot, inject your code bundles into the captured state, and run the reproduction driver to trigger the exact failure conditions offline.

How do I debug XS value-stack overflows in an Agoric xs-worker?

Debugging XS value-stack overflows in an xs-worker requires importing the failing contract bundles into a local swing-store snapshot, allowing you to validate engine-level fixes against the actual chain state that caused the overflow.

What dependencies do I need to run an offline Agoric swing-store snapshot validation?

Offline Agoric swing-store snapshot validation requires local installations of curl, lz4, tar, sqlite3, rsync, wget, and node-based inquisitor tools to acquire, decompress, and query the captured chain state.

Can I validate Agoric contract code patches against captured mainnet state instead of synthetic environments?

Yes, you can validate Agoric contract patches against captured mainnet state by acquiring a real swing-store snapshot, injecting the updated bundles, and triggering the contract-control upgrade path offline to confirm the fix.

Why does my Agoric contract upgrade fail with resource constraints on mainnet but not in local testing?

Agoric contract upgrades fail on mainnet due to real resource constraints like XS value-stack overflows that synthetic local environments cannot replicate, making captured swing-store snapshots necessary for faithful reproduction.

What is the best way to fetch a Polkachu snapshot for Agoric chain-state debugging?

The best way to fetch a Polkachu snapshot for Agoric chain-state debugging is using automated acquisition scripts that download and prepare the compressed swing-store data for immediate offline analysis.