Skip to content
Back to skills

Cardano Protocol Params

ASecurity

Fetch protocol parameters, understand fee inputs, and keep pparams aligned with the target era/network.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 27, 2026
tools

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill cardano-protocol-params --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cardano Protocol Params?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cardano Protocol Params
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-cardano-protocol-params/badge)](https://www.skillsdirectory.com/skills/david-li0406-cardano-protocol-params)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cardano-protocol-params
description: "Fetch protocol parameters, understand fee inputs, and keep pparams aligned with the target era/network."
---

# cardano-protocol-params

## When to use
- Use when you need to fetch `pparams.json`, compute min-UTxO/fees, or debug fee/script budgeting issues.

## Operating rules (must follow)
- Confirm the user's network (mainnet vs preprod/preview) and **magic** before generating commands.
- Print commands in **copy/paste blocks**. Keep secrets out of logs.
- For any `cardano-cli` command: verify syntax with `cardano-cli --help` (and era help) and adjust if needed.
- Use fresh protocol parameters from the target network when calculating fees or script execution units.

## Workflow
1) Fetch fresh params with `cardano-cli query protocol-parameters` for the target network.

2) Validate params fields used by your workflow:
   - min fee coefficients, coins per UTxO byte, execution unit prices, ref-script pricing, etc.

3) For script txs:
   - ensure you use params consistent with the era (Conway) and script version (V2/V3).

4) Capture params alongside tx artifacts for reproducibility.


## Safety / key handling
- Never assume params from mainnet apply to testnets.
- Always keep the pparams file that was used to build a tx (it matters for audit/debug).


## References used by this skill
- `shared/PRINCIPLES.md` (repo)

Files in this skill

  • SKILL.md1.3 KB
  • reference/pparams.md454 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…