Skip to content

docs: Clarify attestation_with_dal applies to all key types#673

Open
michaelkernaghan wants to merge 1 commit into
mainfrom
671-dal-doc-clarify-tz1-behavior
Open

docs: Clarify attestation_with_dal applies to all key types#673
michaelkernaghan wants to merge 1 commit into
mainfrom
671-dal-doc-clarify-tz1-behavior

Conversation

@michaelkernaghan
Copy link
Copy Markdown
Contributor

@michaelkernaghan michaelkernaghan commented Oct 9, 2025

Fixes #671

  • Clarify that attestation_with_dal policy is required for ALL key types when DAL node is connected
  • Add detailed explanation of tz1/tz2/tz3 behavior with DAL node
  • Distinguish between attestation encoding vs shard attestation capability
  • Add concrete log examples from Seoulnet testing
  • Update baker command examples for both tz1 and tz4 scenarios
  • Add new 'DAL Behavior by Key Type' section with practical examples

The documentation now accurately reflects that the attestation_with_dal encoding is triggered by DAL node connectivity, not key type. Testing on Seoulnet demonstrated that tz1 keys do sign attestation_with_dal operations when a DAL node is connected, even without shard attestation capability (bitset 0). This prevents operators from mistakenly omitting the attestation_with_dal policy for tz1-only setups.


Note

Cursor Bugbot is generating a summary for commit fbe03e0. Configure here.

Copy link
Copy Markdown
Contributor

@chunkitmax chunkitmax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Fixes #671

- Clarify that attestation_with_dal policy is required for ALL key types when DAL node is connected
- Add detailed explanation of tz1/tz2/tz3 behavior with DAL node
- Distinguish between attestation encoding vs shard attestation capability
- Add concrete log examples from Seoulnet testing
- Update baker command examples for both tz1 and tz4 scenarios
- Add new 'DAL Behavior by Key Type' section with practical examples

The documentation now accurately reflects that the attestation_with_dal
encoding is triggered by DAL node connectivity, not key type. Testing on
Seoulnet demonstrated that tz1 keys do sign attestation_with_dal operations
when a DAL node is connected, even without shard attestation capability
(bitset 0). This prevents operators from mistakenly omitting the
attestation_with_dal policy for tz1-only setups.
@jevonearth jevonearth force-pushed the 671-dal-doc-clarify-tz1-behavior branch from 19fe86b to fbe03e0 Compare March 3, 2026 20:06
@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Mar 3, 2026

Deploying signatory with  Cloudflare Pages  Cloudflare Pages

Latest commit: fbe03e0
Status: ✅  Deploy successful!
Preview URL: https://b84df472.signatory.pages.dev
Branch Preview URL: https://671-dal-doc-clarify-tz1-beha.signatory.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DAL Documentation Unclear About tz1 Key Behavior with attestation_with_dal

2 participants