Skip to content

Conversation

@brendanjryan
Copy link
Contributor

@brendanjryan brendanjryan commented Feb 4, 2026

Summary

Documents an important design choice in fee sponsorship: the sender must indicate sponsorship before signing because the signing hash differs based on whether a transaction will be sponsored.

@vercel
Copy link

vercel bot commented Feb 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Feb 4, 2026 4:49pm

Request Review

Adds documentation explaining that when building sponsored transactions,
the sender must indicate sponsorship BEFORE signing because the signing
hash differs:

- Sponsored: fee_token omitted from signing payload, 0x00 marker used
- Non-sponsored: fee_token included in signing payload

This was raised as feedback from an external integration partner who
discovered this behavior during testing.

Changes:
- Added warning callout in Go SDK docs
- Added 'Signing Hash Behavior' section in sponsor-user-fees guide
- Add build step after typecheck in CI to catch build failures before deploy
- Change checkDeadlinks to 'warn' (TIP-1011 has dead link in tempo repo)
@brendanjryan brendanjryan force-pushed the docs/fee-sponsorship-signing-behavior branch from 33bc4b3 to a09d0d1 Compare February 4, 2026 16:47
@brendanjryan brendanjryan merged commit 9a8b746 into main Feb 4, 2026
4 checks passed
@brendanjryan brendanjryan deleted the docs/fee-sponsorship-signing-behavior branch February 4, 2026 16:57
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.

1 participant