Merge branch 'main' into factory-pattern

Author: td202

source/mainnet/net/guides/dapp-examples.rst

@@ -61,6 +61,22 @@ Starting a new project on the Concordium blockchain? Have a look at the `dApp st
 
     `Back end and front end code <https://github.com/Concordium/concordium-dapp-examples/tree/main/sponsoredTransactions>`__
 
+.. dropdown:: CIS2 Sponsored Transactions
+
+    `Demo front end <https://cis2-sponsored.testnet.concordium.com/>`__ where you can try the functionality on Concordium's testnet
+
+    :ref:`Tutorial about the sponsored Transactions dApp<sponsoredTransactions>`
+
+    `Smart contract <https://github.com/Concordium/concordium-rust-smart-contracts/tree/main/examples/cis2-multi>`__
+
+    `Back end and front end code <https://github.com/Concordium/concordium-dapp-examples/tree/main/sponsoredTransactionsAuction>`__
+
+.. dropdown:: Track and Trace
+
+    `Smart contract <https://github.com/Concordium/concordium-dapp-examples/tree/main/trackAndTrace/smart-contract>`__
+
+    `Front end and back end code <https://github.com/Concordium/concordium-dapp-examples/tree/main/trackAndTrace>`__
+
 .. dropdown:: Voting
 
     `Demo front end <https://voting.testnet.concordium.com>`__ where you can try the functionality on Concordium's testnet
@@ -77,6 +93,12 @@ Starting a new project on the Concordium blockchain? Have a look at the `dApp st
 
     `Front end code <https://github.com/Concordium/concordium-dapp-examples/tree/main/signMessage>`__
 
+.. dropdown:: EuroE age verification
+
+    `Demo front end <https://euroe-demo.testnet.concordium.com/>`__ where you can try the functionality on Concordium's testnet
+
+    `Front end code <https://github.com/Concordium/concordium-dapp-examples/tree/main/euroe-demo>`__
+
 .. dropdown:: Smart contract deploy and initialize tool
 
     `Demo front end <https://sctools.mainnet.concordium.software/>`__ where you can deploy and initlize a smart contract on testnet or mainnet

source/mainnet/net/guides/developer-page.rst

@@ -57,7 +57,9 @@ All of our repositories are on `GitHub <https://github.com/Concordium>`__.
 
     For information about how to create proofs to verify identity for dApps and services see :ref:`Create proofs<create-proofs>`.
 
-    If you want to familiarize yourself with how proofs work and can be constructed, you can use the `Concordium Proof Explorer <https://web3id-proof-explorer.testnet.concordium.com/>`__ to create proofs and send them to a |bw| to see how they interact with account credentials and verifiable credentials. The Concordium Proof Explorer works on Testnet. You can use the `Web3Id Issuer Front End <https://web3id-issuer-frontend.testnet.concordium.com/>`__ to create verifiable credential to test with the proof explorer.
+    If you want to familiarize yourself with how proofs work and can be constructed as well as test them, you can use the `Concordium Proof Explorer <https://web3id-proof-explorer.testnet.concordium.com/>`__ to create proofs and send them to a |bw| to see how they interact with account credentials and verifiable credentials. The Concordium Proof Explorer works on Testnet. You can use the `Web3Id Issuer Front End <https://web3id-issuer-frontend.testnet.concordium.com/>`__ to create verifiable credential to test with the proof explorer.
+
+    If you decide that you want to become an issuer of verifiable credentials, see :ref:`Web3 ID issuers<web3id-issuer>` to learn more and access the production ready tools to become an issuer.
 
 .. dropdown:: dApps
 

source/mainnet/net/release-notes/release-notes-lp.rst

@@ -167,12 +167,16 @@ Wallets
 |bw|
 -------------------------
 
-    February 13, 2024
+    March 6, 2024
 
-    Version 1.4.1 fixes an issue with backward compatibility for gRPC and an identity issue.
+    In version 1.4.2 the token transfer estimate now takes the transfer amount into account and the wallet no longer blocks creating the last possible account for an identity.
 
     .. dropdown:: Previous releases
 
+        .. dropdown:: |bw| 1.4.1 - February 13, 2024
+
+            Version 1.4.1 fixes an issue with backward compatibility for gRPC and an identity issue.
+
         .. dropdown:: |bw| 1.4.0 - February 5, 2024
 
             Verison 1.4.0 adds support for recovery to be aborted when an identity takes a long time to recover. It also fixes an issue where the wrong list of identity providers was sometimes used when recovering from the wallet settings menu.

source/mainnet/net/web3-id/issuer.rst

@@ -17,12 +17,12 @@ How to become an issuer
 An issuer needs to have the following components.
 
 1. Some way of identifying users to whom the credentials will be issued, e.g., an existing database of users.
-2. JSON schemas and metadata for credentials. These are used by the wallet to display and style the credential. This might be a logo, a background color, how the attributes will appear in the credential (e.g., date format, title), and so on. The `Concordium Web3 ID Issuer Front End <https://web3id-issuer-onboarding.mainnet.concordium.software/>`__ helps with setting up your metadata.
+2. JSON schemas and metadata for credentials. These are used by the wallet to display and style the credential. This might be a logo, a background color, how the attributes will appear in the credential (e.g., date format, title), and so on. The `Concordium Web3 ID Issuer Front End <https://web3id-issuer-onboarding.mainnet.concordium.software/>`__ helps with setting up your metadata which you then should upload to a public URL. The Concordium Web3 Issuer Front End works on both mainnet and testnet.
 3. A smart contract where credential lifetime is managed, together with its metadata such as expiry time. The `Concordium Web3 ID Issuer Front End <https://web3id-issuer-onboarding.mainnet.concordium.software/>`__ helps with setting up your credential registry contract.
 4. A dApp where the user will request credentials with the help of the wallet.
 5. A back end which will issue credentials, which involves registering the credential in the smart contract, and returning it to the holder's wallet.
 
-To make it easier to become an issuer, you can use the `Concordium Web3 ID Issuer Front End <https://web3id-issuer-onboarding.mainnet.concordium.software/>`__. This tool walks you through steps two and three when becoming an issuer.
+To make it easier to become an issuer, you can use the `Concordium Web3 ID Issuer Front End <https://web3id-issuer-onboarding.mainnet.concordium.software/>`__. This tool walks you through steps two and three when becoming an issuer. The Concordium Web3 Issuer Front End works on both mainnet and testnet.
 
 Concordium Issuer tool
 ----------------------

source/mainnet/smart-contracts/tutorials/counter/counter-contract.rst

@@ -23,9 +23,9 @@ Once you have set up the tools needed you are ready to create your smart contrac
 
 .. code-block:: console
 
-    cargo concordium init
+    $cargo concordium init
 
-Select the ``Default`` option from the menu.
+Select the ``default`` option from the menu.
 
 .. image:: images/select-default.png
     :width: 100%
@@ -165,7 +165,7 @@ Create a ``dist`` folder to keep the schema output file and Wasm compiled contra
 
 .. code-block:: console
 
-    cargo concordium build --out dist/module.wasm.v1 --schema-out dist/schema.bin
+    $cargo concordium build --out dist/module.wasm.v1 --schema-out dist/schema.bin
 
 .. image:: images/build.png
     :width: 100%
@@ -174,7 +174,7 @@ Deploy it with the command below.
 
 .. code-block:: console
 
-    concordium-client module deploy dist/module.wasm.v1 --sender <YOUR-ACCOUNT> --name counter --grpc-port 20001
+    $concordium-client module deploy dist/module.wasm.v1 --sender <YOUR-ACCOUNT> --name counter --grpc-port 20001
 
 .. image:: images/deploy.png
     :width: 100%
@@ -183,7 +183,7 @@ Initialize it to create your contract instance, so you are ready to invoke the f
 
 .. code-block:: console
 
-    concordium-client contract init <YOUR-MODULE-HASH> --sender <YOUR-ADDRESS> --energy 30000 --contract counter --grpc-port 20001
+    $concordium-client contract init <YOUR-MODULE-HASH> --sender <YOUR-ADDRESS> --energy 30000 --contract counter --grpc-port 20001
 
 .. image:: images/initialize.png
     :width: 100%
@@ -198,7 +198,7 @@ First, check the initial state of the contract.
 
 .. code-block:: console
 
-    concordium-client contract invoke <YOUR-CONTRACT-INSTANCE> --entrypoint view --schema dist/schema.bin --grpc-port 20001
+    $concordium-client contract invoke <YOUR-CONTRACT-INSTANCE> --entrypoint view --schema dist/schema.bin --grpc-port 20001
 
 Since you just initialized the contract it is 0.
 
@@ -212,7 +212,7 @@ Create a JSON file that holds your operator that will be given as input to the f
 
 .. code-block:: console
 
-    concordium-client contract update <YOUR-CONTRACT-INSTANCE> --entrypoint increment --parameter-json <PATH-TO-JSON> --schema dist/smart-contract-multi/schema.bin --sender <YOUR-ADDRESS> --energy 6000 --grpc-port 20001
+    $concordium-client contract update <YOUR-CONTRACT-INSTANCE> --entrypoint increment --parameter-json <PATH-TO-JSON> --schema dist/smart-contract-multi/schema.bin --sender <YOUR-ADDRESS> --energy 6000 --grpc-port 20001
 
 Start by testing with your conditions. First, try another account other than the owner of the contract since you want that only the owner can call this function.