public class NonValidatingNotaryFlow
extends Service
Service.TransactionParts
Constructor and Description |
---|
NonValidatingNotaryFlow(Party otherSide,
TimestampChecker timestampChecker,
UniquenessProvider uniquenessProvider) |
Modifier and Type | Method and Description |
---|---|
Service.TransactionParts |
receiveAndVerifyTx()
The received 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).
|
call, getOtherSide, getTimestampChecker, getUniquenessProvider, receiveAndVerifyTx
call, getCounterpartyMarker, getLogger, getProgressTracker, getRunId, getServiceHub, getStateMachine, receive, send, sendAndReceive, setStateMachine, subFlow, subFlow, track, waitForLedgerCommit
public NonValidatingNotaryFlow(Party otherSide, TimestampChecker timestampChecker, UniquenessProvider uniquenessProvider)
public Service.TransactionParts receiveAndVerifyTx()
The received 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).