New Crowdin updates

locales/de/Basics/README.md

@@ -0,0 +1,3 @@
+## Loading, Compiling, Deploying
+
+This beginner level tutorial introduces Remix's interface and concepts used in Ethereum.

locales/de/Basics/config.yml

@@ -0,0 +1,26 @@
+---
+id: basics
+name: Basics of Remix
+summary: A typical workflow in Remix
+level: 1
+tags:
+  - Remix
+steps:
+  - 
+    name: Intro to the Interface
+    path: interface_introduction
+  - 
+    name: Intro to Workspaces
+    path: workspaces
+  - 
+    name: Loading & Compiling
+    path: load_and_compile
+  - 
+    name: Deploying to the Remix VM
+    path: deploy_to_the_remixvm
+  - 
+    name: Interacting with Functions
+    path: interacting
+  - 
+    name: Deploying to Public Networks
+    path: deploy_injected

locales/de/Basics/deploy_injected/README.md

@@ -0,0 +1,21 @@
+1. If you don't have a browser wallet like **MetaMask** download and install one now.
+
+2. Click the MetaMask icon in your browser. Sign in and choose the Ephemery test network. You might need to update your wallet's settings so that you can see **test networks**.  Alternatively, you can go to Remix's Deploy & Run transation module and in the ENVIRONMENT section select Ephemery.
+
+3. Getting test ETH for public test networks is often annoying.  Ephemery is a public network that is refreshed monthly, so getting test ETH should be painless.  Here is a link to some <a href="https://github.com/ephemery-testnet/ephemery-resources?tab=readme-ov-file#faucets" target="_blank">Ephemery faucets</a>.
+
+![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/deploy_injected/images/testnet.png)
+
+Sepolia is another popular testnet that is not refreshed, so deployments will persist, but Sepolia faucets are more difficult to use.
+
+In your browser wallet make sure that you have NOT selected mainnet or any network that will cost real ETH. In the Deploy & Run module, below the Environment select box, you'll see a badge with the network's ID and for popular chains, its name.  In the case below its Sepolia.
+
+![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/deploy_injected/images/sepolia.png)
+
+5. Make sure you see the 2_Owner.sol as a choice in the **CONTRACT** select box, then click the **Deploy** button.
+
+If the **CONTRACT** select box is empty, you'll need to compile 2_Owner again by making 2_Owner.sol the active file in the **editor** and then go to the **Solidity Compiler** to compile it.
+
+6. After you hit the `Deploy` button, you'll see the browser wallet popup asking you to pay for the transactions.  If you have the appropriate kind of ETH for this chain, approve this transaction.  Check the printout in the terminal.  Once the block is validated, the **deployed instance** will appear at the bottom of Deploy & Run
+
+And with that you have finished this tutorial.  You now have experience with opening, compiling, deploying and interacting with Smart Contracts in Remix IDE.

locales/de/Basics/deploy_to_the_remixvm/README.md

@@ -0,0 +1,15 @@
+In the previous chapter, we compiled a contract  - which is to say the Solidity code has been transformed into little chunks of Ethereum Virtual Machine (EVM) bytecode.
+
+Now we will put that code on a test blockchain.
+
+1. Click the Deploy and Run icon ![deploy & run icon](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/deploy_to_the_remixvm/images/run.png "deploy & run icon").
+
+2. Select one of the **Remix VM**s from the **Environment** pulldown.
+
+3. Click the Deploy button (or the transact button in the expanded view).
+
+4. You have deployed your compiled contract to the Remix VM - a simulated blockchain that is running inside of your browser window.  The Remix VM is simple, fast test chain.  It is not that realistic because you don't need to approve each transaction.
+
+5. Check the terminal to see detail of this deployment transaction.
+
+You can also use Remix to deploy to other public EVM chains. To do this, you'll need to connect to a different **Environment** - like Injected Provider.  The Injected Provider connects Remix to browser wallet (like MetaMask or similar).  We'll try deploying to a public network at the end of this tutorial. But before we get there, we'll cover how to interact with a deployed contract's functions.

locales/de/Basics/interacting/README.md

@@ -0,0 +1,19 @@
+## Accessing functions in a deployed contract
+
+1. When a contract has been successfully deployed, it will appear at the bottom of the Deploy and Run plugin. Open up the contract by clicking the caret - so the caret points down.
+   ![deploy contract](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interacting/images/instance.png "deployed contract")
+
+2. There are 2 functions in this contract.  To input the parameters individually, clicking the caret to the right of changeOwner (outlined in red below). In the expanded view, each parameter has its own input box.
+
+![deploy contract](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interacting/images/deployed_open2.png "deployed contract")
+
+If this contract had imported other contracts, then the functions of the imported contracts would also be visible here.  At some point, try playing with An ERC20 contract to see all its many functions.
+
+3. Functions with blue buttons are either  **pure** or **view** functions.  This means that they are just reading a property or are returning a value.  In other words, they aren't saving anything - so they are FREE (they don’t cost gas).  Functions with other colors - usually orange (depending on the Remix theme) cost gas because they are saving information.  They are creating a **transaction**.
+
+4. 2_Owner.sol does not have a **payable** function.  If it did, the button's color would be red.  Payable functions allow you to send Ether to the function.  To send ETH with a payable function, you put the amount you want to send in the **value** field towards the top of the Deploy & Run module.
+
+5. In the Remix VM, you don't need to approve a transaction.  When using a more realistic test environment or when using the mainnet - you will need to approve the transactions for them to go through. Approving a transaction costs gas.
+
+6. Choosing a public network is not done in Remix but in your Browser Wallet.  There is a plug icon to the right of the Environment title that links to chainlist.org where you can get the specs of the chain you want to interact with.
+   ![chainlist](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interacting/images/chainlist.png "chainlist")

locales/de/Basics/interface_introduction/README.md

@@ -0,0 +1,15 @@
+## Remix is composed of four panels.
+
+![Remix layout](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/a-layout1c.png "Remix layout")
+
+- Most plugins appear in the **Side Panel**.
+- Editing code happens in tabs in the **Main Panel**.
+- The results of transactions and other actions are visible in the **Terminal**.
+- Switching between plugins happens in the **Icons Panel**.
+- To make a panel larger, drag its border.
+
+Try clicking the **Solidity Compiler** icon ![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/solidity-icon.png) in the **Icons Panel**. Then click the **Deploy & Run** icon ![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/deploy-run.png).  Then come back to **LearnEth** by clicking this icon ![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/learneth.png).
+
+In the **Main Panel** of Remix, make sure you see the **Home** tab.  The **Home** tab has lots of useful links. To navigate there, either click the **Home** tab in the **Main Panel** or click the Remix icon ![Remix icon](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/remix-logo.png "Remix icon") on the top of the icon panel.
+
+- See all the plugins in the **Plugin Manager**.  Click this icon ![plugin manager](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/plugin1.png "Plugin Manager icon") in the lower left corner Remix.

locales/de/Basics/load_and_compile/README.md

@@ -0,0 +1,20 @@
+Let's load a file from the File Explorer into the Editor.
+
+1. In the icon panel, click ![file explorer icon](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/load_and_compile/images/files1.png "file explorer icon") , the File Explorer's icon.
+
+2. Make sure you are in the **default_workspace**.
+
+![default workspace](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/load_and_compile/images/default_workspace_open.png)
+
+3. Open the contracts folder and click on **2_Owner.sol** in the contracts folder. Click it. The file will appear in a tab in the main panel.
+
+4. In the icon panel, click the **Solidity Compiler** ![solidity compiler icon](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/load_and_compile/images/solidity1.png "solidity compiler icon"). The Solidity compiler should now be in the side panel.
+
+5. Click the compile button.
+   ![compile 2\_owner](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/load_and_compile/images/compile2owner.png "compile 2_Owner")
+
+6. Compiling can also be triggered by hitting **CTRL + S**.
+
+The spinner will turn while the file is compiling.
+
+**Note:** The spinner also turns when the compiler itself is loading.  To choose a **different version of Solidity**, go to the select box at the top of the plugin.

locales/de/Basics/workspaces/README.md

@@ -0,0 +1,23 @@
+## Workspaces help organize your separate projects.
+
+If this is your first time to Remix, a Workspace named **default_workspace** is loaded in the File Explorer.
+
+![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/default_workspace.png)
+
+The **default_workspace** has three Solidity (.sol) files in the contracts folder. Remix has a number of other templates. When you load a template, it goes into a Workspace. To go between Workspaces, use the select box at the top of the File Explorer.
+
+![](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/interface_introduction/images/select-box.png)
+
+But Workspaces are not only for templates. When cloning a repo into Remix, the files will be put into a Workspace.
+
+Let's create a new Workspace
+
+1. At the top of the File Explorer, click the hamburger icon (the 3 horizontal lines). Read through the commands and tools in this menu.
+
+2. Select **+ Create** (the first choice).
+
+3. In the modal the comes up, choose one of the templates.
+
+![hamburger](https://raw.githubusercontent.com/ethereum/remix-workshops/master/Basics/workspaces/images/popup.png)
+
+Notice that in this popup menu, you can clone a repo. Managing a Git repo happens in the DGit plugin. You can also create Github actions with the three workflow choices in the popup menu.

locales/de/CircomHashChecker/README.md

@@ -0,0 +1,14 @@
+Hash Checker Tutorial
+
+This tutorial guides you through creating and understanding a Hash Checker circuit using Remix-IDE. You'll learn how to generate the circuit using a template, explore the code, perform a trusted setup, generate proofs, and verify them. This tutorial is suitable for beginners familiar with Circom and Zero-Knowledge Proofs.
+
+Prerequisites
+
+```
+Basic understanding of Zero-Knowledge Proofs and Circom.
+Familiarity with Remix-IDE.
+```
+
+Estimated Time
+
+Approximately 1-2 hours.

locales/de/CircomHashChecker/config.yml

@@ -0,0 +1,35 @@
+id: circom-hash-checker
+name: Hash Checker Tutorial
+summary: A tutorial on creating and understanding a Hash Checker circuit using Remix-IDE templates, including trusted setup and proof generation.
+level: 1
+tags:
+  - Circom
+  - Remix-IDE
+steps:
+  - 
+    name: Introduction to the Hash Checker Circuit
+    path: step-1
+  - 
+    name: Generating the Hash Checker Template in Remix-IDE
+    path: step-2
+  - 
+    name: Exploring calculate_hash.circom
+    path: step-3
+  - 
+    name: Compiling the Circuit
+    path: step-4
+  - 
+    name: Performing a Trusted Setup
+    path: step-5
+  - 
+    name: Compute Witness
+    path: step-6
+  - 
+    name: Generate Proof
+    path: step-7
+  - 
+    name: Exploring the Trusted Setup Script (Optional)
+    path: step-8
+  - 
+    name: Exploring the Proof Generation Script (Optional)
+    path: step-9

locales/de/CircomHashChecker/step-1/README.md

@@ -0,0 +1,8 @@
+In this tutorial, we'll explore the **Hash Checker** circuit, a zero-knowledge proof (ZKP) application using Circom and Remix-IDE. The Hash Checker circuit allows you to prove knowledge of certain inputs that hash to a given value without revealing the inputs themselves.
+
+### What You'll Learn
+
+- How to generate a Hash Checker circuit using Remix-IDE's workspace templates.
+- Understanding the Circom code for hashing and checking hashes.
+- Performing a trusted setup using Groth16.
+- Generating zero-knowledge proofs.

locales/de/CircomHashChecker/step-2/README.md

@@ -0,0 +1,37 @@
+Follow these steps to create the Hash Checker workspace in Remix-IDE.
+
+### Step 1: Access the Workspace Templates
+
+1. In the **File Explorer** sidebar, click on the **hamburger menu icon** (three horizontal lines).
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/hamburger_menu.png" alt="hamburger-menu" width=300 height=60>
+
+2. Select **"Create Using Template"** from the dropdown.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/create_using_template.png" alt="create-using-template" width=275 height=400>
+
+### Step 2: Find the Hash Checker Template
+
+1. In the main panel, scroll down to the **"Circom ZKP"** section.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/circom_zkp_section.png" alt="create-zkp-section" width=450 height=150>
+
+2. Locate the **"Hash Checker"** item.
+
+### Step 3: Create the Workspace
+
+1. Click on the **"Create"** button on the Hash Checker item.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/create_hash_checker.png" alt="create-hash-checker" width=220 height=140>
+
+2. In the modal pop-up, provide a **workspace name** (e.g., `hash-checker-workspace`).
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/workspace_name_modal.png" alt="workspace-name-modal" width=400 height=225>
+
+3. Click **"OK"** to create the template.
+
+### Result
+
+- The workspace is created with the necessary files and directories.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-2/images/workspace_files.png" alt="workspace-name-modal" width=350 height=425>

locales/de/CircomHashChecker/step-3/README.md

@@ -0,0 +1,32 @@
+## Exploring `calculate_hash.circom`
+
+Navigate to the `circuits` directory and open `calculate_hash.circom`. This file contains the Circom code for the Hash Checker circuit.
+
+### Code Breakdown
+
+#### Pragma and Includes:
+
+- `pragma circom 2.0.0;` specifies the Circom version.
+- `include "circomlib/circuits/poseidon.circom";` fetch and includes the Poseidon hash function from [CircomLib](https://github.com/iden3/circomlib).
+
+#### `CalculateHash` Template:
+
+- Defines inputs `value1`, `value2`, `value3`, `value4`.
+- Uses the `Poseidon` hash function to compute a hash of these values.\
+- Outputs `out`, which is the hash.
+
+#### `HashChecker` Template:
+
+- Inputs are the same values plus a `hash`.
+- Instantiates `CalculateHash` as `calculateSecret`.
+- Computes `calculatedHash`.
+- Uses `assert(hash == calculatedHash);` to ensure the provided hash matches the calculated hash.
+
+#### Main Component:
+
+- `component main {public [hash]} = HashChecker();`
+- Specifies that `hash` is a `public` input, while the values are `private`.
+
+### Purpose
+
+The circuit allows someone to prove they know `value1`, `value2`, `value3`, and `value4` that hash to a specific `hash` without revealing the values themselves.

locales/de/CircomHashChecker/step-4/README.md

@@ -0,0 +1,32 @@
+## Compiling the Circuit
+
+### Selecting the Compiler Version
+
+1. Go to the **Circuit Compiler** plugin in the sidebar.
+2. Choose the desired **Compiler Version** from the dropdown menu. For this tutorial, select the latest stable version.
+
+<img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-4/images/select_compiler_version.png" alt="select-compiler-version" width=250 height=100>
+
+### Configuring Compilation Options
+
+- **Auto Compile:** You can enable this option to automatically compile your circuit whenever you save changes.
+- **Hide Warnings:** Enable this to suppress compiler warnings if any.
+- **Advanced Configuration:**
+  - Click to expand.
+  - Select the **Prime Field**. For most cases, `BN128` is sufficient.
+
+<img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-4/images/advanced_configuration.png" alt="advanced-configuration" width=300 height=100>
+
+### Compiling the Circuit
+
+1. Click on the **Compile** button.
+2. Wait for the compilation to complete. A success badge will appear if compilation is successful.
+
+<img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-4/images/compilation_success.png" alt="compilation-success" width=300 height=675>
+
+### Understanding the Compilation Output
+
+- After successful compilation, the **Setup and Exports** section becomes visible.
+- You can proceed to the next step to perform a trusted setup.
+
+In the next step, we'll perform a trusted setup using the compiled circuit.

locales/de/CircomHashChecker/step-5/README.md

@@ -0,0 +1,25 @@
+## Performing a Trusted Setup
+
+1. **Access the Setup and Exports Section**:
+
+- After successful compilation, the **Setup and Exports** section becomes available in the plugin.
+
+2. **Select Proving Scheme**:
+
+- Choose **Groth16** from the **Proving Scheme** dropdown.
+
+3. **Select Power of Tau File**:
+
+- Choose the appropriate **Power of Tau** file from the dropdown. If unsure, use the default option.
+
+4. **Export Verification Key and Contract** (optional):
+
+- Enable **Export Verification Key** to save the verification key to the File Explorer.
+- Enable **Export Verifier Contract** to save the Solidity contract for on-chain verification.
+
+<img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-5/images/trusted_setup.png" alt="trusted-setup" width=330 height=350>
+
+5. **Run the Trusted Setup**:
+
+- Click on the **Run Setup** button.
+- Wait for the process to complete. This may take some time depending on the circuit complexity.

locales/de/CircomHashChecker/step-6/README.md

@@ -0,0 +1,28 @@
+## Compute Witness
+
+1. **Access the Compute Witness Section**:
+   - After the trusted setup, the **Compute Witness** section becomes available.
+
+2. **Input Values**:
+   - You'll see input fields for `value1`, `value2`, `value3`, `value4`, and `hash`.
+   - Enter values for each input. For example:
+     - `value1`: `1234`
+     - `value2`: `2`
+     - `value3`: `3`
+     - `value4`: `4`
+
+3. **Calculate the Hash**:
+
+   - Compute the Poseidon hash of the four values using an external tool or library compatible with the Poseidon hash function.
+   - For the values above, here is the computed Poseidon hash `16382790289988537028417564277589554649233048801038362947503054340165041751802`.
+   - Enter the calculated `hash` value in the `hash` input field.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-6/images/compute_witness.png" alt="compute-witness" width=250 height=400>
+
+4. **Compute the Witness**:
+
+   - Click on the **Compute Witness** button.
+   - Wait for the process to complete. A success badge will appear if the witness is computed successfully.
+   - If successful, you'll see `calculate_hash.wtn` created in the `.bin` directory in the file explorer.
+
+   <img src="https://raw.githubusercontent.com/ethereum/remix-workshops/master/CircomHashChecker/step-6/images/witness_computed.png" alt="witness-computed" width=300 height=100>