updated links for samples-kotlin (#110)

ILoomans · web-flow · commit d97a04f62cd3 · 2025-03-18T15:22:27.000Z
diff --git a/Accounts/tictacthor/README.md b/Accounts/tictacthor/README.md
@@ -1,5 +1,5 @@
 # Tic Tac Thor
-This CorDapp recreates the game of Tic Tac Toe via Corda. It primarilly demonstrates how you can have [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) transactions between cross-node accounts.
+This CorDapp recreates the game of Tic Tac Toe via Corda. It primarilly demonstrates how you can have [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) transactions between cross-node accounts.
 <p align="center">
   <img src="https://upload.wikimedia.org/wikipedia/commons/thumb/3/32/Tic_tac_toe.svg/1024px-Tic_tac_toe.svg.png" alt="Corda" width="200">
 </p>
diff --git a/Advanced/auction-cordapp/README.md b/Advanced/auction-cordapp/README.md
@@ -1,7 +1,7 @@
 # Auction CorDapp
 
 This CorDapp serves as a demo of building an auction application on Corda. It leverages
-different features of Corda like [SchedulableState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces), [StatePointer](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#state-pointers) and [OwnableState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#ownablestate). It also demonstrates
+different features of Corda like [SchedulableState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces), [StatePointer](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#state-pointers) and [OwnableState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#ownablestate). It also demonstrates
 how to perform a DvP (Delivery vs Payment) transaction on Corda.
 
 It has a full-functional client included and an angular UI to interact with the nodes.
@@ -48,7 +48,7 @@ internally triggers two flows:
     flow can also be triggered to  exit an auction which did not receive any bid till its deadline.
 
 ## Pre-requisites:
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Running the nodes:
 Open a terminal and go to the project root directory and type: (to deploy the nodes using bootstrapper)
diff --git a/Advanced/duediligence-cordapp/README.md b/Advanced/duediligence-cordapp/README.md
@@ -13,7 +13,7 @@ Note: another key feature of this app is whitelisting trusted auditors. It is do
 
 
 ## Pre-Requisites
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Running the nodes
 
diff --git a/Advanced/negotiation-cordapp/README.md b/Advanced/negotiation-cordapp/README.md
@@ -29,7 +29,7 @@ In the `AcceptanceFlow.java`, we receive the modified ProposalState and it's con
 ## Usage
 
 ### Pre-Requisites
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 
diff --git a/Advanced/obligation-cordapp/README.md b/Advanced/obligation-cordapp/README.md
@@ -18,7 +18,7 @@ Finally, once we have the ability to transfer assets, we just need to settle up.
 
 
 ## Pre-Requisites
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Usage
 
diff --git a/Advanced/secretsanta-cordapp/README.md b/Advanced/secretsanta-cordapp/README.md
@@ -21,7 +21,7 @@ There's essentially five processes you'll need to be aware of.
 
 #### Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Running these services
diff --git a/Advanced/snakesandladders-cordapp/README.md b/Advanced/snakesandladders-cordapp/README.md
@@ -17,7 +17,7 @@ Each player can create an account to participate. Players can either be on the s
 Oracle node is used to obtain the player dice rolls.
 
 ## Pre-Requisites
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ## Running the nodes
diff --git a/Advanced/superyacht-cordapp/README.md b/Advanced/superyacht-cordapp/README.md
@@ -11,7 +11,7 @@ There are 4 main parties in this example:
 
 
 ## State
-* `YachtState`: This is an [OwnableState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#ownablestate) and a [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) that represents a Yacht that can be issued by the Yacht Issuer to the Yacht Owner (Party A).
+* `YachtState`: This is an [OwnableState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#ownablestate) and a [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) that represents a Yacht that can be issued by the Yacht Issuer to the Yacht Owner (Party A).
 
 ## Contract
 * `YachtContract`: This is used to govern the evolution of a `YachtState`. This file includes validation rules governing the `Create` and `Purchase` command for YachtState
@@ -23,7 +23,7 @@ There are 4 main parties in this example:
 
 ## Pre-Requisites
 
-[Please ensure that your device is set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Please ensure that your device is set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ## Running the nodes
diff --git a/Advanced/syndicated-lending/README.md b/Advanced/syndicated-lending/README.md
@@ -12,7 +12,7 @@ and agreeing on loan terms.
 
 # Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 # Usage
 
diff --git a/Basic/cordapp-example/README.md b/Basic/cordapp-example/README.md
@@ -5,7 +5,7 @@ This cordapp-example application allows a party (lender) to issue an IOU to anot
 
 ## States
 
-* `IOUState`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) and a [QueryableState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces) that represents an IOU that can be issued by one party (lender) to another party (borrower).
+* `IOUState`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) and a [QueryableState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces) that represents an IOU that can be issued by one party (lender) to another party (borrower).
 
 ## Contracts
 
@@ -16,7 +16,7 @@ This cordapp-example application allows a party (lender) to issue an IOU to anot
 * `ExampleFlow`: This flow is used to create an `IOUState`. It takes 2 arguments as the parameters: the `iouValue` (Int) and the `otherParty` (Party).
 
 ## Pre-requisites:
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Running the nodes:
 1. Open a terminal and go to the project root directory and type: (to deploy the nodes using bootstrapper)
diff --git a/Basic/flow-database-access/README.md b/Basic/flow-database-access/README.md
@@ -1,5 +1,5 @@
 # Flow Database Access CorDapp
-This CorDapp provides a simple example of how the node database can be accessed in flows using a [JDBC Connection](https://docs.r3.com/en/platform/corda/4.9/community/api-persistence.html#jdbc-session). In this case, the flows
+This CorDapp provides a simple example of how the node database can be accessed in flows using a [JDBC Connection](https://docs.r3.com/en/platform/corda/4.12/community/api-persistence.html#jdbc-session). In this case, the flows
 maintain a table of cryptocurrency values in the node's database.
 
 
@@ -18,7 +18,7 @@ Be aware that support of database accesses in flows is currently limited:
 
 ## Pre-Requisites
 
-For development environment setup, please refer to: [Setup Guide](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html).
+For development environment setup, please refer to: [Setup Guide](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html).
 
 
 ## Running the nodes
diff --git a/Basic/opentelemetry-cordapp-example/README.md b/Basic/opentelemetry-cordapp-example/README.md
@@ -41,7 +41,7 @@ This opentelemetry-cordapp-example application allows a party (lender) to issue
 
 ## States
 
-* `IOUState`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) and a [QueryableState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces) that represents an IOU that can be issued by one party (lender) to another party (borrower).
+* `IOUState`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) and a [QueryableState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#the-queryablestate-and-schedulablestate-interfaces) that represents an IOU that can be issued by one party (lender) to another party (borrower).
 
 ## Contracts
 
@@ -52,7 +52,7 @@ This opentelemetry-cordapp-example application allows a party (lender) to issue
 * `ExampleFlow`: This flow is used to create an `IOUState`. It takes 2 arguments as the parameters: the `iouValue` (Int) and the `otherParty` (Party).
 
 ## Pre-requisites:
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Running the nodes:
 1. Open a terminal and go to the project root directory and type: (to deploy the nodes using bootstrapper)
diff --git a/Basic/ping-pong/README.md b/Basic/ping-pong/README.md
@@ -2,7 +2,7 @@
 
 This CorDapp allows a node to ping any other node on the network that also has this CorDapp installed.
 
-It demonstrates how to use Corda for messaging and passing data using a flow that initiates a [communication session](https://docs.r3.com/en/platform/corda/4.9/community/api-flows.html#create-communication-sessions-with-initiateflow) without saving any states or using any contracts.
+It demonstrates how to use Corda for messaging and passing data using a flow that initiates a [communication session](https://docs.r3.com/en/platform/corda/4.12/community/api-flows.html#create-communication-sessions-with-initiateflow) without saving any states or using any contracts.
 
 
 ### Concepts
diff --git a/Basic/tutorial-applestamp/README.md b/Basic/tutorial-applestamp/README.md
@@ -5,7 +5,7 @@ Example use of an apple stamp: "One stamp can be exchanged for a basket of Honey
 
 
 ## States
-* `AppleStamp`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) that represents an Apple Stamp that can be issued by one party (issuer) to another party (holder).
+* `AppleStamp`: This is a [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) that represents an Apple Stamp that can be issued by one party (issuer) to another party (holder).
 * `BasketOfApples`: This state represents a specific basket of apples (description of the brand/type, farm, owner, and weight). To change ownership of this basket of apples, the `changeOwner` function can be used.
 
 ## Contracts
@@ -20,7 +20,7 @@ Example use of an apple stamp: "One stamp can be exchanged for a basket of Honey
 
 ## Pre-Requisites
 
-For development environment setup, please refer to: [Setup Guide](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html).
+For development environment setup, please refer to: [Setup Guide](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html).
 
 
 ## Running the nodes
diff --git a/Basic/tutorial-networkbootstrapper/README.md b/Basic/tutorial-networkbootstrapper/README.md
@@ -7,7 +7,7 @@ Due to the size cap of the github uploaded file, you will need to manually downl
 ## Deploy a local Corda Network via the bootstrapper 
 With the Corda Network Bootstrapper downloaded to this directory, you can simply call: (with the version name of the bootstrapper that you downloaded)
 ```
-java -jar corda-tools-network-bootstrapper-4.9.jar
+java -jar corda-tools-network-bootstrapper-4.12.jar
 ```
 This command will gennerate the node folders that correspondes with each node config file. You should expect some folder structure like this: 
 ```
@@ -47,7 +47,7 @@ rpcSettings {
 ```
 After change the p2pAddress, you can now perform the bootstrapping with 
 ```
-java -jar corda-tools-network-bootstrapper-4.9.jar
+java -jar corda-tools-network-bootstrapper-4.12.jar
 ```
 Next, we need to drop the node folder to the remote VMs. I simply use the `scp` command. For example: 
 ```
diff --git a/Features/attachment-blacklist/README.md b/Features/attachment-blacklist/README.md
@@ -27,7 +27,7 @@ check that the parties to the `AgreementState` are not blacklisted. There aren't
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Deploy and run the node
diff --git a/Features/attachment-sendfile/README.md b/Features/attachment-sendfile/README.md
@@ -43,7 +43,7 @@ The flow logic is the following:
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ### Deploy and run the node
 ```
diff --git a/Features/confidentialIdentity-whistleblower/README.md b/Features/confidentialIdentity-whistleblower/README.md
@@ -1,6 +1,6 @@
 # Whistleblower -- Confidential Identity 
 
-This CorDapp is a simple showcase of [confidential identities](https://docs.r3.com/en/platform/corda/4.9/community/api-identity.html#confidential-identities) (i.e. anonymous public keys).
+This CorDapp is a simple showcase of [confidential identities](https://docs.r3.com/en/platform/corda/4.12/community/api-identity.html#confidential-identities) (i.e. anonymous public keys).
 
 ## Concepts
 
@@ -15,7 +15,7 @@ automatically by the `SwapIdentitiesFlow`.
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Deploy and run the node
diff --git a/Features/contractsdk-recordplayers/README.md b/Features/contractsdk-recordplayers/README.md
@@ -8,7 +8,7 @@ If you're familiar with record players you probably know how difficult it is to
 
 This cordapp simulates how you could model the process of a limited edition record player (the cordagraf) that is manufactured and issued to specific dealers, and those dealers are the only entities that can service those record players after the fact and report stats back to the manufacturer about how the players are being used.
 
-A Record Player is issued as a [LinearState](https://docs.r3.com/en/platform/corda/4.9/community/api-states.html#linearstate) and is updated by dealers, that act functionally as the only entity that can update the `RecordPlayerState`.
+A Record Player is issued as a [LinearState](https://docs.r3.com/en/platform/corda/4.12/community/api-states.html#linearstate) and is updated by dealers, that act functionally as the only entity that can update the `RecordPlayerState`.
 
 
 ### Using the Contract SDK
diff --git a/Features/cordaService-autopayroll/README.md b/Features/cordaService-autopayroll/README.md
@@ -21,7 +21,7 @@ There are two states `PaymentRequestState` and `MoneyState`, and two flows `Requ
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ### Deploy and run the nodes
 ```
diff --git a/Features/customlogging-yocordapp/README.md b/Features/customlogging-yocordapp/README.md
@@ -73,7 +73,7 @@ You can end up getting log feeds in json that look something like this:
 ### Pre-Requisites
 
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Running the CorDapp
diff --git a/Features/encumbrance-avatar/README.md b/Features/encumbrance-avatar/README.md
@@ -4,7 +4,7 @@
 
 # Corda encumbrance sample
 
-Corda supports the idea of "Linked States", using the [TransactionState.encumbrance](https://docs.r3.com/en/platform/corda/4.9/community/key-concepts-contracts.html#encumbrances) property. When building a transaction, a state `x` can
+Corda supports the idea of "Linked States", using the [TransactionState.encumbrance](https://docs.r3.com/en/platform/corda/4.12/community/key-concepts-contracts.html#encumbrances) property. When building a transaction, a state `x` can
 point to other state `y` by specifying the index of `y`'s state in the transaction output index.
 
 In this situation `x` is linked to `y`, i.e. `x` is dependent on `y`. `x` cannot be consumed unless you consume `y`.
@@ -58,7 +58,7 @@ otherwise one can spend the "encumbrance" (Expiry) state, which would freeze the
 That's why we also make Expiry dependent on Avatar. (See how we have added encumbrance index's to the output states in
 both the flows.)
 
-Read more about Encumbrances [here](https://docs.r3.com/en/platform/corda/4.9/community/key-concepts-contracts.html#encumbrances).
+Read more about Encumbrances [here](https://docs.r3.com/en/platform/corda/4.12/community/key-concepts-contracts.html#encumbrances).
 
 ## Reminder
 
diff --git a/Features/notarychange-iou/README.md b/Features/notarychange-iou/README.md
@@ -5,7 +5,7 @@ using one of the Corda library flow called `NotaryChangeFlow`.
 
 ## Concepts
 
-[Notary](https://docs.r3.com/en/platform/corda/4.9/community/key-concepts-notaries.html) is a critical component of a Corda network. It helps prevent double-spending 
+[Notary](https://docs.r3.com/en/platform/corda/4.12/community/key-concepts-notaries.html) is a critical component of a Corda network. It helps prevent double-spending 
 attempts in a Corda network. Thus, all states issued in Corda are tied to a Notary. 
 Any transaction involving the update of a state must be notarised by the Notary 
 that the state is tied to. Since other notaries wouldn't have seen any previous 
@@ -26,7 +26,7 @@ issue an IOU at a particular Notary and try to settle the IOU using a different
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ### Running the CorDapp
 
diff --git a/Features/observableStates-tradereporting/README.md b/Features/observableStates-tradereporting/README.md
@@ -26,7 +26,7 @@ In this CorDapp, the seller runs the `TradeAndReport` flow to create a new `High
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Running the CorDapp
diff --git a/Features/oracle-primenumber/README.md b/Features/oracle-primenumber/README.md
@@ -27,7 +27,7 @@ This repo is split into three CorDapps:
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ### Running the CorDapp
 
diff --git a/Features/postgres-cordapp/README.md b/Features/postgres-cordapp/README.md
@@ -5,7 +5,7 @@ The CorDapp being used is another copy of the yo CorDapp, as the majority of the
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ## Usage
 
diff --git a/Features/referenceStates-sanctionsBody/README.md b/Features/referenceStates-sanctionsBody/README.md
@@ -7,7 +7,7 @@ This CorDapp allows two nodes to enter into an IOU agreement, but enforces that
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 
 ### Running the CorDapp
diff --git a/Features/schedulableState-heartbeat/README.md b/Features/schedulableState-heartbeat/README.md
@@ -1,5 +1,5 @@
 # Heartbeat -- Schedulablestate
-This CorDapp is a simple showcase of [flow watch](https://docs.r3.com/en/platform/corda/4.9/community/shell.html#command-2) (i.e. activities started by a node at a specific time without
+This CorDapp is a simple showcase of [flow watch](https://docs.r3.com/en/platform/corda/4.12/community/shell.html#command-2) (i.e. activities started by a node at a specific time without
 direct input from the node owner).
 
 
@@ -21,7 +21,7 @@ In this way, calling the `StartHeartbeatFlow` creates an endless chain of `Heart
 
 ## Pre-Requisites
 
-[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.9/community/getting-set-up.html)
+[Set up for CorDapp development](https://docs.r3.com/en/platform/corda/4.12/community/getting-set-up.html)
 
 ### Running the CorDapp
 
diff --git a/Features/state-reissuance/README.md b/Features/state-reissuance/README.md
diff --git a/Tokens/bikemarket/README.md b/Tokens/bikemarket/README.md
diff --git a/Tokens/dollartohousetoken/README.md b/Tokens/dollartohousetoken/README.md
diff --git a/Tokens/fungiblehousetoken/README.md b/Tokens/fungiblehousetoken/README.md
diff --git a/Tokens/stockpaydividend/README.md b/Tokens/stockpaydividend/README.md
diff --git a/Tokens/tokentofriend/README.md b/Tokens/tokentofriend/README.md
