[USERSNAP] We registered our drep unsing mesh multisig and everything worked flawless. https://cardanoscan.io/drep/drep1ydwtnlvdd8atlj5c5ylgw4kg5e640vyt8resattrjmwufyg4qclf7 However we are not listed on gov tools which is raver disappointing. Could this...

[kickloop]

Taken at: https://gov.tools/drep_directory
Fields:

• Add a comment: We registered our drep unsing mesh multisig and everything worked flawless.

https://cardanoscan.io/drep/drep1ydwtnlvdd8atlj5c5ylgw4kg5e640vyt8resattrjmwufyg4qclf7

However we are not listed on gov tools which is raver disappointing.

Could this be a bug in the update mechanism of the drep directory or does gov tools exclusivly list dreps which have been registered with the in house tool.

Best Regards
Quirin Schlegel

Browser: Chrome 131 (macOS Catalina)
Screen size: 2560x1080
Open #178 in Usersnap

Powered by Usersnap.

[Ryun1]

Issues/ confusion over DRep ID standard
This DRep can be seen via CIP105 ID: https://gov.tools/drep_directory/drep_script1tjulmrtfl2lu4x9p86r4dj9xw4tmpzec7v826cukmhzfzxns7fy

[MSzalowski]

However, the generated CIP-129 identifiers are different in GovTool than in Cardanoscan

We might have some issue with CIP-129 for script based DReps

[Ryun1]

Here is an script example, of how it can be done

CIP-105 Hex: 5cb9fd8d69fabfca98a13e8756c8a67557b08b38f30ead6396ddc491
(CIP-105 Bech32:drep_script1tjulmrtfl2lu4x9p86r4dj9xw4tmpzec7v826cukmhzfzxns7fy)

To convert to from CIP-105 hex to CIP-129 hex we add two bytes to the front of ID.
For script DReps we add 23 and for normal key-based DReps we add 22 (in hex).

CIP-129 Hex: 235cb9fd8d69fabfca98a13e8756c8a67557b08b38f30ead6396ddc491
(CIP-129 Bech32: drep1ydwtnlvdd8atlj5c5ylgw4kg5e640vyt8resattrjmwufyg4qclf7)