This repository has been archived by the owner on Dec 2, 2024. It is now read-only.
SCP-3130: Tx constraint to specify stake stake key hash with payment #181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modified the tx creation constraints (
plutus-ledger-constraints
repo) to allow to specify the stake public key hash of a transaction output address.This isn't strictly necessary, since you can make payments using only the payment key. However, it is useful when you want to derive a specific Cardano address (bech32 format) which needs the payment key + stake key.
While doing that, I also took the time to add a additionnal newtype wrappers to
PubKeyHash
such asPaymentPubKeyHash
,PaymentPubKey
,StakePubKeyHash
andStakePubKey
in order to clearly understand to whichPubKeyHash
we are refering to. This implied a lot of code change. These datatypes where defined inLedger.Address
.Related to that, I changed the name of
WalletEffect.ownPubKeyHash
toWalletEffect.ownPaymentPubKeyHash
. Maybe it also makes sense to also add the effectWalletEffect.ownStakePubKeyHash
, but this should be in a separate PR.Pre-submit checklist: