Skip to content

Conversation

@csoreff
Copy link

@csoreff csoreff commented Nov 12, 2025

Since the Seoul protocol, reveal operations on Tezos require the presence of a boolean for whether or not the proof field is present. This is required when manually forging bytes:

https://octez.tezos.com/docs/shell/p2p_api.html#reveal-tag-107

If support for BLS/tz4 is added later, this can be updated to include the proof field when the address is a tz4 address.

… boolean for whether or not the proof field is present. This is required when manually forging bytes. Added.
Copy link
Collaborator

@satoshiotomakan satoshiotomakan left a comment

Choose a reason for hiding this comment

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

LGTM, thank you for the fix @csoreff

@satoshiotomakan satoshiotomakan mentioned this pull request Nov 12, 2025
6 tasks
gupnik
gupnik previously approved these changes Nov 12, 2025
Copy link
Collaborator

@gupnik gupnik left a comment

Choose a reason for hiding this comment

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

Looks good, thanks!

@csoreff csoreff dismissed stale reviews from gupnik and satoshiotomakan via eb176af November 12, 2025 09:40
@csoreff
Copy link
Author

csoreff commented Nov 12, 2025

Sorry, missed TezosTests.swift, updated

@satoshiotomakan
Copy link
Collaborator

Hi @csoreff, would you be able to fix the other tests please? Otherwise, we can fix them ourselves shortly

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.

3 participants