diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md index cd802dbed1..761ec63330 100644 --- a/CONTRIBUTORS.md +++ b/CONTRIBUTORS.md @@ -150,6 +150,7 @@ see changes to this list. * Milen Dobrinov (Industria) * Mohamed Amine LEGHERABA * Mustafa Ozturk (Natixis) +* Manish Kumar (ChainThat) * Nick Skinner (Northern Trust) * Nigel King (R3) * Nitesh Solanki (Persistent Systems Limited) diff --git a/docs/source/tutorial-contract.rst b/docs/source/tutorial-contract.rst index 3b75d2c181..d43d31b39e 100644 --- a/docs/source/tutorial-contract.rst +++ b/docs/source/tutorial-contract.rst @@ -346,7 +346,7 @@ the owner. To calculate how much cash is moving, we use the ``sumCashBy`` utility function. Again, this is an extension function, so in Kotlin code it appears as if it was a method on the ``List`` type even though JDK provides no such -method. In Java we see its true nature: it is actually a static method named ``CashKt.sumCashBy``. This method simply +method. In Java we see its true nature: it is actually a static method named ``StateSumming.sumCashBy``. This method simply returns an ``Amount`` object containing the sum of all the cash states in the transaction outputs that are owned by that given public key, or throws an exception if there were no such states *or* if there were different currencies represented in the outputs! So we can see that this contract imposes a limitation on the structure of a redemption