Signatory v1.2.4-beta.2 for Seoulnet bakers; final release at Promotion quorum

Project Updates
1

We recommend Seoulnet bakers upgrade to Signatory v1.2.4-beta.2 to track Seoul-era changes ahead of the Promotion vote.

What’s in this build

  • Versioned signing for era-specific message formats
  • tz4/BLS flows with proof‑of‑possession endpoint
  • Metrics: policy violations, watermark rejections, authentication failures
  • Test stability improvements

Beta components and timeline

  • Nitro Enclave backend, GCP Confidential Space backend, and Firestore watermark storage are beta; targeting v1.3.0 for the general release

Who should upgrade

  • Seoulnet validator/baker participants preparing for Seoul-era operations
  • Anyone validating tz4/BLS workflows or new metrics in testing environments

Final release timing

  • We will publish the final release when the Seoul protocol reaches quorum in the final Promotion stage of governance

Links

2 Likes
2

Hello. I got an error like “attestation_with_dal’ is not allowed” but haven’t found anything in the documentation. I have added attestation_with_dal to signatory.yaml, and it works

.

1 Like
3

Thanks for the note @Nikolay-everstake

I have added a note to the beta release notes as follows;

:warning: DAL Node Users : If you are running a DAL node in your baking setup, you must add attestation_with_dal to the allow: block in your Signatory configuration to participate in DAL attestations and earn additional rewards. See the DAL section in Baking with DAL (Data Availability Layer for configuration details.

4

Thank you, @jevonearth. And one more question:
in config we use:
" allow:
block: # Standard block baking
attestation: # Standard attestations
preattestation: # Pre-attestations
attestation_with_dal: # :sparkles: Required for DAL attestations"
in Signatory logs we can see:
time=“2025-08-28T09:55:04Z” level=info msg=“Signed preattestation successfully” chain_id=NetXnHfVqm9iesp lvl=14648135…
…
time=“2025-08-28T09:55:04Z” level=info msg=“Signed attestation_with_dal successfully” chain_id=NetXnHfVqm9iesp lvl=14648135…
and nothing about Signed attestation without DAL.
Also, in metrics I see:
vault_sign_request_duration_milliseconds_count{address=“tz3gWm2Moxurj6dRD1nhwpyv4tUR4MxcJzC4”,op=“attestation_with_dal”
vault_sign_request_duration_milliseconds_count{address=“tz3gWm2Moxurj6dRD1nhwpyv4tUR4MxcJzC4”,op=“block”
vault_sign_request_duration_milliseconds_count{address=“tz3gWm2Moxurj6dRD1nhwpyv4tUR4MxcJzC4”,op=“preattestation”
but nothing with op=“attestation”.
Is it normal behavior of the Signatory?