[dan437]

Explanation

Add an optional trust callback to TransactionController. Trusted transactions continue to re-simulate on the current block, while untrusted transactions keep the future-block timestamp used to detect time-dependent behavior.

The callback defaults to untrusted, so existing consumers keep their current behavior until they explicitly provide trust data.

References

• Related to CONF-2074

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Changes re-simulation timing for security-sensitive paths; incorrect trust classification could skip future-block checks on malicious or mismatched txs.

Overview
Adds an optional isTransactionTrusted callback on TransactionControllerOptions so hosts can mark transactions that only touch trusted contracts. On re-simulation, shouldResimulate still runs for security alerts and value/native-balance mismatches, but future-block blockTime (used to surface time-dependent behavior) is applied only when the transaction is not trusted.

The callback defaults to always untrusted (false), so existing integrations keep today’s future-block re-simulation until they wire trust explicitly. Changelog and tests cover the new option and trusted vs untrusted blockTime behavior.

^{Reviewed by Cursor Bugbot for commit 8761887. Bugbot is set up for automated code reviews on this repo. Configure here.}