feat(tangle-cloud): verify pinned blueprint metadata#3158
Merged
Conversation
✅ Deploy Preview for tangle-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-leaderboard ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tangle-dapp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
This PR is the consumer end of the metadata-pinning chain and should merge last. Merge order:
Dependencies: |
This was referenced Apr 23, 2026
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
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.
Summary
metadataHashbefore enabling advanced hosted tier-2 renderingmetadataHashin blueprint create and update flows, GraphQL ingestion, and ABI/client shapesWhy
tnt-corenow pins blueprint metadata onchain andblueprintcan submit the canonical digest at deploy time. The dapp needs to verify the fetched payload against that hash and fall back to the protocol-controlled host when verification fails.Notes
metadataUriValidation
NX_DAEMON=false yarn nx run tangle-cloud:typecheckNX_DAEMON=false yarn nx test tangle-cloudNX_DAEMON=false yarn nx run tangle-cloud:build