com.r3corda.node.services.transactions / NotaryService / processRequest

# processRequest

`fun processRequest(txBits: SerializedBytes<WireTransaction>, reqIdentity: Party): Result`

Checks that the timestamp command is valid (if present) and commits the input state, or returns a conflict if any of the input states have been previously committed

Note that the transaction is not checked for contract-validity, as that would require fully resolving it into a TransactionForVerification, for which the caller would have to reveal the whole transaction history chain. As a result, the Notary will commit invalid transactions as well, but as it also records the identity of the caller, it is possible to raise a dispute and verify the validity of the transaction and subsequently undo the commit of the input states (the exact mechanism still needs to be worked out)

TODO: the notary service should only be able to see timestamp commands and inputs