corda

It's a follow up question on previously answered legal prose question by Joel.(created separate question on request) @LegalProseReference(uri = "foo.bar.com/my-legal-doc.html") public class MyContract implements Contract { @Override public void verify(LedgerTransaction tx) { // Contract logic. } } As the answer suggests, I got this legal doc my-legal-doc.html. so what happens in case the verify method doesn't throw an exception? and what happens in case verify does throw an exception do I show this legal doc to the user that read this legal doc. That this is why the contract failed? as

To get state I can use Vault, but what about transactions? How I can get them, for example, by txHash? Is it possible to do this by CordaRPCOps, there is internalVerifiedTransactionsSnapshot method, but it is deprecated now. First, note that as of Corda 3, there are no stability guarantees regarding the behaviour of any method to retrieve a transaction or its dependencies. In particular, we cannot guarantee that the set of transactions retrieved will not change across Corda versions. This is because in future versions of Corda, nodes will likely only exchange transaction chains in SGX

Can someone explain what is it legal prose in Corda? I understood that it is a document, which is used to solve conflicts, but i didnt find any information how it looks like. And how is it linked with smart contract? A Contract class can be annotated with the @LegalProseReference annotation. This annotation associates the contract with a document that restates the constraints imposed by verify in legal prose terms. This is not required, but can be useful in contexts where it is expected that legal contracts will take precedence over the software implementations in case of disagreement.

Suppose you're representing cash on the Corda ledger using cash states. How does a network participant exchange their cash states for traditional cash? Firstly, we need to explain how cash states are created on the ledger initially. The mechanism is for an issuing bank to set aside a cash deposit in the traditional banking system, and issue itself cash states of an equal amount and currency on the ledger using a Cash.Issue transaction. The issued cash states can then be transferred between parties on the ledger via Cash.Move transactions. It is not necessary to reflect these movements of on

Currently in v2, if a CorDapp references a module X, which has a transitive dependency to a module Y, such that Y is used by Corda, a potential version conflict can occur if the respective versions of Y for Corda and X differ. An example is the reuse of an existing internal library, containing business and serialisation logic, that depends on Jackson . In this case, the resulting CorDapp packaging and Corda runtime, seem to enforce the version of Y that is relevant for Corda. If the versions of Y differ sufficiently, we can get such scenarios as X breaking because Y doesn’t support certain