Why is timestamp part of every transaction input in hyperledger composer?

Question

How can I prevent users from submitting a timestamp with their transaction? When I create a transaction, the timestamp field is added to the transaction and can be inputted by the user. While the timestamp on the transaction is populated if the client does not send it, the user can send in their own timestamp to back-date a transaction.

Answer 1

I think you would have to enforce this in the client tier (prior to submitting the transaction using the Node.js or REST API).

This is an interesting requirement however. Can you elaborate more on the use case and what you are worried about?