mirror of
https://github.com/corda/corda.git
synced 2024-12-28 08:48:57 +00:00
36 lines
1.9 KiB
ReStructuredText
36 lines
1.9 KiB
ReStructuredText
|
.. highlight:: kotlin
|
||
|
|
.. raw:: html
|
||
|
|
|
||
|
|
<script type="text/javascript" src="_static/jquery.js"></script>
|
||
|
|
<script type="text/javascript" src="_static/codesets.js"></script>
|
||
|
|
|
||
|
|
Observer nodes
|
||
|
|
==============
|
||
|
|
|
||
|
|
Posting transactions to an observer node is a common requirement in finance, where regulators often want
|
||
|
|
to receive comprehensive reporting on all actions taken. By running their own node, regulators can receive a stream
|
||
|
|
of digitally signed, de-duplicated reports useful for later processing.
|
||
|
|
|
||
|
|
Adding support for observer nodes to your application is easy. The IRS (interest rate swap) demo shows to do it.
|
||
|
|
|
||
|
|
Just define a new flow that wraps the SendTransactionFlow/ReceiveTransactionFlow, as follows:
|
||
|
|
|
||
|
|
.. container:: codeset
|
||
|
|
|
||
|
|
.. literalinclude:: ../../samples/irs-demo/cordapp/src/main/kotlin/net/corda/irs/flows/AutoOfferFlow.kt
|
||
|
|
:language: kotlin
|
||
|
|
:start-after: DOCSTART 1
|
||
|
|
:end-before: DOCEND 1
|
||
|
|
|
||
|
|
In this example, the ``AutoOfferFlow`` is the business logic, and we define two very short and simple flows to send
|
||
|
|
the transaction to the regulator. There are two important aspects to note here:
|
||
|
|
|
||
|
|
1. The ``ReportToRegulatorFlow`` is marked as an ``@InitiatingFlow`` because it will start a new conversation, context
|
||
|
|
free, with the regulator.
|
||
|
|
2. The ``ReceiveRegulatoryReportFlow`` uses ``ReceiveTransactionFlow`` in a special way - it tells it to send the
|
||
|
|
transaction to the vault for processing, including all states even if not involving our public keys. This is required
|
||
|
|
because otherwise the vault will ignore states that don't list any of the node's public keys, but in this case,
|
||
|
|
we do want to passively observe states we can't change. So overriding this behaviour is required.
|
||
|
|
|
||
|
|
If the states define a relational mapping (see :doc:`api-persistence`) then the regulator will be able to query the
|
||
|
|
reports from their database and observe new transactions coming in via RPC.
|