ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-02-20 09:26:41 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Clearer caveat about using observable states.

Browse Source
This commit is contained in:
Joel Dudley 2018-04-03 09:11:35 +01:00 committed by GitHub
parent 0d1d7daedc
commit 4106e9837d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/source/tutorial-observer-nodes.rst
View File

@ -38,11 +38,11 @@ reports from their database and observe new transactions coming in via RPC.
Caveats
-------
* Nodes which act as both observers and direct participants in the ledger are not supported at this time. In
particular, coin selection may return states which you do not have the private keys to be able to sign for. Future
versions of Corda may address this issue, but for now, if you wish to both participate in the ledger and also observe
transactions that you can't sign for you will need to run two nodes and have two separate identities
* By default, vault queries do not differentiate between states you recorded as a participant/owner, and states you
recorded as an observer. You will have to write custom vault queries that only return states for which you are a
participant/owner. See https://docs.corda.net/api-vault-query.html#example-usage for information on how to do this.
This also means that ``Cash.generateSpend`` should not be used when recording ``Cash.State`` states as an observer
* Nodes only record each transaction once. If a node has already recorded a transaction in non-observer mode, it cannot
later re-record the same transaction as an observer. This issue is tracked here:
https://r3-cev.atlassian.net/browse/CORDA-883
https://r3-cev.atlassian.net/browse/CORDA-883