CIP36 - Catalyst Registration Transaction

[jinglescode]

Describe the feature you'd like

• to create Catalyst registration transaction, https://cips.cardano.org/cip/CIP-36
• also check for native script multisig wallet support

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like

First of, there are two standard currently in use an valid. CIP-15 and CIP-36. CIP-36 is very similar to CIP-15 with the addition or idea that you can delegate and split your vote power. This last part was never adopted and CIP-36 was reverted to work like CIP-15 with a single delegation.

Both use label 61284 and 61285 metadata. 61284 contains the meat of the registration and 61285 the witness that the content of 61284 is correct (signed by staking key for stake pub set in 61284 metadata)

Another big change between CIP-15 and CIP-36 is that CIP-36 define a catalyst voting derivation path to always be able to derive the same voting key while CIP-15 create throwaway keys for every registration.

The private voting key is encrypted by pin code and the result is what is put in the QR code.

This is how stake key (for vote power) is linked to the vote key put in QR code and used for voting. Both of these are included in the 61284 metadata.

to be linked to a single vote key anyway to vote as single entity in Catalyst

m / 1694' / 1815' / account' / chain / address_index

Then when you create the vote registration transaction. You put this vote key in the 61284 metadata in 1 field. Please note that you can only have a single entry here for current Catalyst system. With the weight of 1. Then the rest of the data is taken from the individual wallets that want to give their vote power to the single vote key.

Additional context

No response

Would you be willing to implement it?

• Yes, I will implement it.