🐛 CIP-129 Script-based DRep IDs are using the wrong Bech32 prefix

[Ryun1]

Area

Delegation Pillar

Domain

gov.tools

Which wallet were you using?

No response

Context

• The conversion to CIP129 IDs for script-based DReps uses the drep_script prefix instead of the drep prefix

• This means script-based DReps are being shown with the wrong CIP-129 DRep ID

• See example implementation for converting between DRep ID standards and I have it hosted here

• Example script-based DRep

  • CIP-105 ID: drep_script1g2d3y3skgr806wj2ryhhc5ca3akx6vmppde87jq7kgknj5wf0ec
  • incorrect CIP-129 ID shown by GovTool: drep_script1ydpfkyjxzeqvalf6fgvj7lznrk8kcmfnvy9hyl6gr6ez6wgeq8q7q
  • correct CIP-129 ID: drep1ydpfkyjxzeqvalf6fgvj7lznrk8kcmfnvy9hyl6gr6ez6wgsjaelx

• I believe this maybe affecting why the show details button is not shown for this DRep, but this may be a separate issue

• and also the metadata isnt loaded for this DRep, but this may be a separate issue (I suspect this is related though)

Steps to reproduce

• Go to https://gov.tools/drep_directory/drep1ydpfkyjxzeqvalf6fgvj7lznrk8kcmfnvy9hyl6gr6ez6wgsjaelx
  • Im not sure the relationship between the ID shown in the URL and on the profile
• This brings up a page showing DRep IDs which don't match the URL
• Compare against; https://tempo.vote/drep-profile?dRepId=drep1ydpfkyjxzeqvalf6fgvj7lznrk8kcmfnvy9hyl6gr6ez6wgsjaelx

Actual behavior

• Incorrect DRep ID is shown

Expected behavior

• Correct DRep ID is shown