docs(blueprints): add product blueprint guide#148
Merged
Conversation
…iceManager (v0.13.0) - ITangleSlashing: align with the actual SlashingLib events. SlashProposed is 8 fields, SlashExecuted is 4. Add SlashDisputed, SlashCancelled, SlashConfigUpdated event sections. proposeSlash takes uint16 slashBps (was uint256 amount). disputeSlash is external payable. setSlashConfig is the 6-arg form. Add getSlashConfig view. - IMBSMRegistry.pinBlueprint: add a paragraph documenting the deprecation grace-window rejection (revisions in the grace window are refused so pinning cannot defeat the deprecation flow). - IBlueprintServiceManager: document forceRemoveAllowsBelowMin (default false; custom BSMs not inheriting BlueprintServiceManagerBase MUST implement) and getNonPaymentTerminationPolicy (added in v0.11.1, never documented). Mirrored to generated/ copies; tnt-core sync check still passes.
QuoteDetails and JobQuoteDetails now carry address requester as the FIRST field of the EIP-712 typed data. The contract enforces requester == msg.sender and rejects wildcard requester == address(0). - pricing-and-payments: reorder field lists (requester first), add a copyable Solidity struct literal and JSON typed-data example, and a Quote-binding key-property bullet covering both QuoteDetails and JobQuoteDetails (with the new typehash strings). - pricing-engine: add Security Notes bullet on requester binding and a Best Practices entry on always populating requester. - operators/pricing/overview: RFQ section gains a requester-binding callout for operator quote-server implementations. - execution-confidentiality: append a customer-request bullet noting that confidential quotes are bound to a specific consumer via requester so they cannot be lifted from the mempool.
… self-dispute (v0.13.0) - slashing: proposeSlash and disputeSlash now nonReentrant. proposeSlash rejects bytes32(0) evidence. executeSlash for a Disputed proposal uses disputeDeadline + TIMESTAMP_BUFFER (15s symmetric with the Pending branch). SLASH_ADMIN_ROLE that is also the proposer of a slash cannot self-dispute their own proposal. - service-lifecycle: new "Exit Gates (v0.13.0)" section covering the Active-status gate on every operator-exit entrypoint, nonReentrant on terminateService, approveService rejecting past-grace requests, and rejection of duplicate operators. force-remove paragraph now mentions the forceRemoveAllowsBelowMin opt-in. - auth-surface: append "(admin cannot self-dispute their own proposal)" to the disputeSlash row. Mark terminateService and forceRemoveOperator as nonReentrant. Note that pinBlueprint reverts inside the deprecation grace window. - network/metrics-and-scoring: list the full slashing event names (Proposed, Disputed, Executed, Cancelled, ConfigUpdated) so indexers know to subscribe to all five.
…slasher rotation infrastructure/protocol-deployment runbook now reminds operators that bootstrap setMessenger / setSlasher (current = address(0)) takes effect immediately on L2SlashingReceiver, but subsequent rotations are timelocked: queue the new address with setMessenger / setSlasher, then call activateMessenger() / activateSlasher() after SENDER_ACTIVATION_DELAY (2 days) elapses. Document the queue/activate pair as two transactions in the runbook so operators know to schedule the activation tx before the delay window closes. (The L2SlashingReceiver auth-surface table was already updated in the previous commit on this branch.)
New /release-notes/0.13.0 page documenting the v0.12.0/v0.13.0 BREAKING changes (EIP-712 quote requester binding, ITangleSlashing event reshape, Types.ServiceRequest.activated reorder, forceRemoveAllowsBelowMin BSM hook), the round-2 hardening fixes (slashing nonReentrant + admin self-dispute, service lifecycle gates, MBSM grace-window pinning, L2 slashing receiver timelock + CEI revert, beacon SSZ canonical endianness, TNTLockFactory beneficiary gate), and a migration checklist for operator quote servers, indexers, custom BSMs, MBSM operators, L2 receiver operators, beacon proof builders, and SLASH_ADMIN holders. Cites tnt-core PRs #124 and #125 and links the bindings CHANGELOG. Adds top-level "Release Notes" entry to pages/_meta.ts so the section is discoverable from the global navigation.
✅ Deploy Preview for tangle-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
tangletools
approved these changes
Jun 14, 2026
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — 6c9d32a3
Blanket team auto-approval is enabled for this reviewer service.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-06-14T21:36:18Z
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
2 participants
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
Validation