Skip to content

[BUG] - required signer should take a very instead of skey #6301

@disassembler

Description

@disassembler

Internal/External
Internal if an IOHK staff member.
External otherwise.

Area
Governance Related to CIP1694 implementation
Token Locking Related to Token Locking.
Native Tokens Related to Native Tokens.
Plutus Related to Plutus Scripts.
Other Any other topic (Delegation, Ranking, ...).

Summary
A clear and specific description of what the bug is.
It's very dangerous have an skey available when building transactions. I'd suggest you make it only accept a vkey
Steps to reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

System info (please complete the following information):

  • OS Name: [e.g. Ubuntu]
  • OS Version [e.g. 20.04]
  • Node version (output of cardano-node --version)
  • CLI version (output of cardano-cli --version)

If the git revision is reported to be 0000000000000000000000000000000000000000, please use cabal build instead of cabal install to build the binaries because cabal install does not record the git revision in the binaries.

Screenshots and attachments

  • If applicable, add screenshots, config files and/or logs to help explain the problem.

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions