Evidence · DiggingBeagle record
Priors ambiguous transaction-receipt spending cap advisory
Maintainer reproductions of cap release after broadcast when a receipt is ambiguous or retry raises an unrelated failure.
- Source role
- primary disclosure
Evidence record
Maintainer reproductions of cap release after broadcast when a receipt is ambiguous or retry raises an unrelated failure.
Claim-level citations (2)
- supportsPriors agent finance caps could be released despite a broadcast transaction: The Priors advisory demonstrates a borrow or bridge spend-cap accounting bypass when a transaction had already been broadcast but a later receipt or RPC retry failure was classified as a pre-send refusal.
GHSA-rh27-m4c4-p2c7: sendBorrow, fundBase, ambiguous receipt and cap-release reproduction
- supportsPriors agent finance caps could be released despite a broadcast transaction: Priors agent finance functions classified several post-broadcast RPC or receipt failures as if the transaction had never been sent. The user needs an agent-controlled borrow or bridge flow subject to a spending cap and an ambiguous remote chain response after broadcast. Releasing the budget too early could permit a second transaction even when the first later settled, defeating the intended cap.
GHSA-rh27-m4c4-p2c7: sendBorrow, fundBase, ambiguous receipt and cap-release reproduction