Allow extended payment keys to be specified as a Plutus required signer.

[Jimbo4350]

No description provided.

[catch-21]

Tested on testnet. Confirmed that it is possible to build with --required-signer using extended and normal signing keys before submitting (checked positive and negative cases).

Used this policy to test with (confirmed that key hash redeemer is required in transaction)

mkPolicy :: PubKeyHash -> ScriptContext -> Bool
mkPolicy pkh ctx = traceIfFalse "not signed by redeemer pubkeyhash" checkWitness
  where
    info :: TxInfo
    info  = scriptContextTxInfo ctx

    checkWitness :: Bool
    checkWitness  = txSignedBy info pkh

[JaredCorduan]

Looks good to me!

[nhenin]

Hi @Jimbo4350, my team and I discovered this restriction while trying to implement the vesting contract (from plutus-use-cases) via cardano-cli....as a quick hack I have made the following modifications : https://github.com/smart-chain-fr/cardano-node/pull/1/commits/3fd17aa7b285492b3f270c78f7b5a19174295d02 .I have seen you are casting into Hash PaymentKey instead of Hash PaymentExtendedKey with castVerificationKey , aren't they any consequences from doing it ?

[Jimbo4350]

bors r+

[Jimbo4350]

Hi @Jimbo4350, my team and I discovered this restriction while trying to implement the vesting contract (from plutus-use-cases) via cardano-cli....as a quick hack I have made the following modifications : smart-chain-fr@3fd17aa .I have seen you are casting into Hash PaymentKey instead of Hash PaymentExtendedKey with castVerificationKey , aren't they any consequences from doing it ?

There are no consequences from doing this as the public keys corresponding to PaymentKeys and PaymentExtendedKeys are the same

[iohk-bors]

Build succeeded:

• ci/hydra-build:required
• buildkite/cardano-node