Skip to content

fix(governance): drep_id param is Bech32 only, not hexadecimal - #470

Merged
slowbackspace merged 1 commit into
masterfrom
fix/drep-id-param-description
Sep 15, 2026
Merged

slowbackspace merged 1 commit into
masterfrom
fix/drep-id-param-description

Conversation

@slowbackspace

Copy link
Copy Markdown
Contributor

The drep_id path parameter on all five /governance/dreps/{drep_id}/* endpoints was described as "Bech32 or hexadecimal DRep ID.", but the backend validates it with validateDRepId, which only decodes Bech32 (legacy drep1.../drep_script1... or CIP-129) and returns 400 "Invalid or malformed drep id." for hex input. Updated to "Bech32 DRep ID (legacy or CIP-129)."

The pool endpoints' "Bech32 or hexadecimal pool ID." descriptions are untouched, hex is genuinely accepted there.

🤖 Generated with Claude Code

All /governance/dreps/{drep_id}/* endpoints validate the parameter with
validateDRepId, which decodes Bech32 (legacy drep1/drep_script1 or
CIP-129) and returns 400 for hex input, so the descriptions claiming
hexadecimal is accepted were wrong.
@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openapi Ready Ready Preview Sep 15, 2026 1:21pm UTC

Request Review

@slowbackspace
slowbackspace merged commit 999b79d into master Sep 15, 2026
6 checks passed
@michalrus
michalrus deleted the fix/drep-id-param-description branch September 15, 2026 13:23

@michalrus michalrus left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants