Confusing message with aiken blueprint apply

[Quantumplation]

What Git revision are you using?

aiken v1.1.13+900bf91

What operating system are you using, and which version?

• Linux / Ubuntu
• Linux / Other
• macOS
• Windows

Describe what the problem is?

I'm trying to update the build.sh script from the SundaeSwap v3 contracts repo, and it seems the format for blueprint apply has changed.

In particular, the following command, which previously worked:

aiken blueprint apply -v settings.spend $PROTOCOL_BOOT_UTXO

Now produces the following output:

    Analyzing blueprint
      Parsing inputs
     Applying d8799fd8799f5820382b27b28c70343161f9abebdab78264
              e0fd7271baf3bb88ca04b52e5f0067efff01ff
  × I didn't find any validator matching your criteria.
  help: Here's a list of all validators I've found in your project. Please double-check this list against the options that you've
        provided:

        → documentation.documentation.spend
        → documentation.documentation.else
        → oracle.oracle.spend
        → oracle.oracle.mint
        → oracle.oracle.else
        → order.order.spend
        → order.order.else
        → pool.manage.else
        → pool.pool.spend
        → pool.pool.mint
        → pool.pool.else
        → pool_stake.pool_stake.else
        → settings.settings.spend
        → settings.settings.mint
        → settings.settings.else
        → stake.stake.else

      Summary 1 error, 0 warnings

This seems to be misleading, because if I pick the correct validator from that list and run:

aiken blueprint apply -v settings.settings.spend $PROTOCOL_BOOT_UTXO

I get the same error.

It seems like I get a different error if I use settings instead of settings.settings.spend, but the error message here also confuses me; did the OutputReference type change?

    Analyzing blueprint
      Parsing inputs
     Applying d8799fd8799f5820382b27b28c70343161f9abebdab78264
              e0fd7271baf3bb88ca04b52e5f0067efff01ff
        Error aiken::blueprint::apply::mismatch

  × I caught a parameter application that seems off.
  help: When applying parameters to a validator, I control that the shape of the parameter you give me matches what is specified
        in the blueprint. Unfortunately, it didn't match in this case.

        I am looking at the following value:

        121([_ h'38 2b 27 b2 8c 70 34 31 61 f9 ab eb da b7 82 64 e0 fd 72 71 ba f3 bb 88 ca 04 b5 2e 5f 00 67 ef'])

        but failed to match it against the specified schema:

        {
          "dataType": "bytes"
        }


        NOTE: this may only represent part of a bigger whole as I am validating the parameter incrementally.

So I'm not sure how to construct the appropriate script hash at this point.

What should be the expected behavior?

The error message should list the validators in the format that it expects to receive them on the command line.

Also, the second error message could probably be more helpful, but I'm not sure exactly how (since I don't understand the problem yet).

[Quantumplation]

The protocol boot UTxO value it's passing is:

d8799fd8799f5820382b27b28c70343161f9abebdab78264e0fd7271baf3bb88ca04b52e5f0067efff01ff

[Quantumplation]

I was able to get it working with

aiken blueprint apply -v settings "d8799f5820382b27b28c70343161f9abebdab78264e0fd7271baf3bb88ca04b52e5f0067ef01ff"

So it does appear that the format of OutputReference changed;

However, this led to another issue, which I've documented in #1128

[KtorZ]

Fixed in #1129.