docs: add Builder Code attribution troubleshooting - #1815
Open
sanjeebdas1979 wants to merge 1 commit into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed? Why?
Notes to reviewers
How has it been tested?
What changed? Why?
Added a troubleshooting section to the Builder Codes for App Developers documentation.
The new section helps developers diagnose cases where an onchain transaction succeeds but does not appear in Builder Code analytics. It explains how to verify the ERC-8021 attribution suffix in transaction calldata and clarifies that a transaction without the suffix cannot be attributed to the developer's Builder Code.
This should make Builder Code integration issues easier to debug, especially when developers are testing transactions outside the Base App.
Notes to reviewers
This is a documentation-only change. No application or protocol code is modified.
How has it been tested?
Reviewed the MDX formatting and verified that the new section follows the existing Builder Codes documentation structure and terminology.