Kleros Ipfs Upload
Upload one Kleros-ecosystem file per paid request to IPFS through the Kleros x402...
Install
npx skills add internet-court/internet-court-skill --skill kleros-ipfs-upload -g -a claude-code -y- Repository
- internet-court/internet-court-skill7k
- Category
- Testing
- Updated
- 9d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Upload one Kleros-ecosystem file per paid request to IPFS through the Kleros x402 gateway for $0.01 USDC on Base mainnet. Use for dispute evidence, MetaEvidence JSON, court/dispute/arbitrator policies, Curate item metadata, juror justifications, or any artifact a Kleros contract or subgraph will reference by CID. Trigger when the request mentions Kleros, court, arbitrator, dispute, juror, Curate, Proof of Humanity, evidence, meta-evidence, justification, explicitly names this gateway or skill, or asks to test or validate it. Do NOT use for generic IPFS/CID requests without Kleros context; recommend a general-purpose pinning service. Each request accepts exactly one file: different bytes require separate paid uploads, while identical bytes should reuse one CID.
Kleros IPFS Upload (x402)
Upload Kleros-ecosystem files to IPFS via https://kleros-ipfs-gateway.fly.dev/upload-to-ipfs, an x402-protected gateway that charges $0.01 USDC per upload on Base mainnet. The returned IPFS CID is content-addressable and dereferenceable through any IPFS gateway, and indexed by Kleros's Graph Node for subgraph discoverability.
The gateway is a thin reverse-proxy in front of a Filebase-backed pinning service operated by Kleros. Every upload is pinned to Filebase indefinitely as long as Kleros runs the gateway, a reasonable assumption for artifacts the Kleros ecosystem itself depends on (the team has a strong incentive to keep this live), but not a substitute for a general-purpose pinning provider if the content is unrelated to Kleros.
When to use this skill
Trigger this skill when the user is uploading Kleros-ecosystem content:
- Dispute evidence attachments, screenshots, documents, contracts, transcripts.
- Meta-evidence JSON, the policy/spec referenced by a court or arbitrator smart contract at dispute creation.
- Court / dispute / arbitrator policies, JSON describing rules, fees, juror counts, appeal mechanics.
- Kleros Curate item metadata, JSON for items submitted to a Curate list (e.g. tokens, badges).
- Juror / arbitrator justifications, rulings, dissents, deliberation rationale.
- Any artifact whose CID will end up in a Kleros smart contract event, transaction, or subgraph.
- The user explicitly names this gateway (
kleros-ipfs-gateway.fly.devetc.) or this skill. - The user is asking the agent to test, validate, or sanity-check this gateway or this skill itself (e.g. "smoke-test the Kleros IPFS gateway" / "verify pay-and-upload works"). A deliberate end-to-end test is a legitimate trigger even if no Kleros artifact is being uploaded for real use.
