yaci-store omits PlutusV2 cost model from /api/v1/epochs/parameters (yaci-cli 0.12.0-beta5)

[nau]

Summary

On bloxbean/yaci-cli:0.12.0-beta5 the bundled yaci-store's GET /api/v1/epochs/parameters returns cost models only for PlutusV1 (166 entries) and PlutusV3 (251 entries). PlutusV2 is missing entirely, even though the devnet node's Alonzo genesis contains both PlutusV1 and PlutusV2 cost models.

Reproduction

Start a devnet (same command yaci-cardano-test uses):

docker run -d --name yaci-devnet \
  -e yaci_cli_mode=native -e yaci_store_mode=native \
  -e conwayHardForkAtEpoch=1 -e shiftStartTimeBehind=true \
  -e yaci_store_enabled=true \
  --entrypoint /app/yaci-cli -p 8080:8080 \
  bloxbean/yaci-cli:0.12.0-beta5 \
  create-node -o --slot-length 1 --block-time 1 --start

Then:

curl -s localhost:8080/api/v1/epochs/parameters | jq '.cost_models | keys'

returns

["PlutusV1", "PlutusV3"]

while /clusters/nodes/default/node/genesis/alonzo-genesis.json inside the container defines cost models for both PlutusV1 and PlutusV2.

Effect

Any client that builds transactions from these protocol parameters (fee/ExUnits evaluation of PlutusV2 scripts, script integrity hash computation) fails because the PlutusV2 cost model is absent. For comparison, 0.10.0-preview2 returned PlutusV2 as expected.

Environment

• bloxbean/yaci-cli:0.12.0-beta5, arm64, Docker Desktop on macOS

[satran004]

@nau Can you try the same with the Yaci DevKit Docker ZIP version?

https://github.com/bloxbean/yaci-devkit/releases/tag/v0.12.0-beta5 (yaci-devkit-0.12.0-beta5.zip)

In the latest Compose file, you can see the two costmodel specific plutus-costmodels.json files mounted. The cost models from these files are picked up and used in GA during devnet creation, as additional cost-model entries can no longer be specified directly in the existing genesis files with node 11.0.1.

Here is the content of the DevKit Docker Compose file:

services:
  yaci-cli:
    image: bloxbean/yaci-cli:${tag}
    ports:
      - "${HOST_N2N_PORT}:3001"
      - "${HOST_N2C_SOCAT_PORT}:3333"
      - "${HOST_SUBMIT_API_PORT}:8090"
      - "${HOST_STORE_API_PORT}:8080"
      - "${HOST_CLUSTER_API_PORT}:10000"
      - "${HOST_OGMIOS_PORT}:1337"
      - "${HOST_KUPO_PORT}:1442"
      - "${HOST_YANO_HTTP_PORT}:6060"
      - "${HOST_YANO_N2N_PORT}:14447"
    volumes:
      - cluster-data:/clusters
      - ../config/node.properties:/app/config/node.properties
      - ../config/plutus-costmodels-v10.json:/app/config/plutus-costmodels-v10.json
      - ../config/plutus-costmodels-v11.json:/app/config/plutus-costmodels-v11.json
    env_file:
      - ../config/env
      - ../config/node.properties
    entrypoint:
      - sleep
      - infinity

So, we need an equivalent command when using docker run. Thanks for highlighting the issue in yaci-cardano-test. We need a similar fix there as well.

Btw, the following properties are no longer required:

-e conwayHardForkAtEpoch=1 -e shiftStartTimeBehind=true

[nau]

Follow-up: this is also specific to the haskell-only node mode. With nodeMode=companion the Yano bootstrap restores PlutusV2: after startup /api/v1/epochs/parameters reports all three cost models (PlutusV1, PlutusV2 and a full 350-entry PlutusV3), and PlutusV2 script evaluation against the devnet params works again.

So both this and #184 come down to the haskell-only cost-model bootstrap path; companion mode is a working workaround (with the caveats noted in #184 for yaci-cardano-test users).

[satran004]

@nau Currently, the recommended default mode is companion, as users need to wait at least two epochs before testing their first transaction in haskell-only mode. This may not provide a good DX.

I will review the PR and the other issues soon to see if we can find a workaround. But, I think companion mode will also help us in the future by providing the flexibility to perform various types of initial setup for the devnet, which are unfortunately not possible with the production Haskell node.

Thanks for highlighting same issue in yaci-cardano-test , we will look into it next week. Meanwhile, if you want feel free to create a PR for that.