Proposer: Include some timestamp/expiration data #27

New Issue

Closed

opened 2024-12-19 21:16:26 +00:00 by scjudd · 1 comment

scjudd commented

2024-12-19 21:16:26 +00:00

Member

There's already been a little discussion around this, but for tracking purposes, I'll create an issue.

For the Proposer - Create Transaction Payload docs

How do I know that I've not just been handed a signed transaction request from days/weeks/months ago, asking me to send another million dollars? Should we embed some sort of expiration time in the transaction request? Ideally icepick or whatever downstream tooling would be aware of this and prevent operating on expired, but signed, transaction requests.

There's already been a little discussion around this, but for tracking purposes, I'll create an issue. For the [Proposer - Create Transaction Payload docs](https://git.distrust.co/public/docs/src/commit/57faca72fdb54682ca119f41c3250eee8cf7c795/quorum-key-management/src/generated-documents/level-2/fixed-location/proposer/create-transaction-payload.md#proposer-create-transaction-payload) > How do I know that I've not just been handed a signed transaction request from days/weeks/months ago, asking me to send another million dollars? Should we embed some sort of expiration time in the transaction request? Ideally `icepick` or whatever downstream tooling would be aware of this and prevent operating on expired, but signed, transaction requests.