From d8cba2b77cdf50e2d1c486e2890cfc272e723fe8 Mon Sep 17 00:00:00 2001 From: Pedro Novais <1478752+jpnovais@users.noreply.github.com> Date: Mon, 16 Sep 2024 14:40:00 +0100 Subject: [PATCH 1/4] gradle: update project name to Linea --- settings.gradle | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/settings.gradle b/settings.gradle index e11180525..185e18734 100644 --- a/settings.gradle +++ b/settings.gradle @@ -1,4 +1,4 @@ -rootProject.name = 'zkevm' +rootProject.name = 'linea' include 'jvm-libs:errors' include 'jvm-libs:http-rest' @@ -6,12 +6,12 @@ include 'jvm-libs:kotlin-extensions' include 'jvm-libs:logging' include 'jvm-libs:testing-teku-helper' include 'jvm-libs:web3j-extensions' -include('jvm-libs:blob-compressor') -include('jvm-libs:blob-shnarf-calculator') -include('jvm-libs:future-extensions') -include('jvm-libs:json-rpc') -include('jvm-libs:traces') -include('jvm-libs:vertx-helper') +include 'jvm-libs:blob-compressor' +include 'jvm-libs:blob-shnarf-calculator' +include 'jvm-libs:future-extensions' +include 'jvm-libs:json-rpc' +include 'jvm-libs:traces' +include 'jvm-libs:vertx-helper' include 'jvm-libs:core:domain-models' include 'jvm-libs:core:metrics' include 'jvm-libs:core:long-running-service' @@ -19,15 +19,15 @@ include 'jvm-libs:linea-contracts:l1-rollup' include 'jvm-libs:linea-contracts:l2-message-service' include 'jvm-libs:metrics:micrometer' include 'jvm-libs:teku-execution-client' -include('coordinator:app') -include('coordinator:core') -include('coordinator:utilities') +include 'coordinator:app' +include 'coordinator:core' +include 'coordinator:utilities' include 'coordinator:clients:prover-client:file-based-client' include 'coordinator:clients:prover-client:serialization' -include('coordinator:clients:type2-state-manager-client') -include('coordinator:clients:traces-generator-api-client') -include('coordinator:clients:shomei-client') -include('coordinator:clients:smart-contract-client') +include 'coordinator:clients:type2-state-manager-client' +include 'coordinator:clients:traces-generator-api-client' +include 'coordinator:clients:shomei-client' +include 'coordinator:clients:smart-contract-client' include 'coordinator:clients:web3signer-client' include 'coordinator:ethereum:common' include 'coordinator:ethereum:models-helper' @@ -46,8 +46,8 @@ include 'coordinator:ethereum:gas-pricing:static-cap' include 'coordinator:ethereum:gas-pricing:dynamic-cap' include 'finalized-tag-updater' include 'testing-tools' -include('testing-tools:app') -include('traces-api-facade:app') -include('traces-api-facade:core') -include('traces-api-facade:conflation') +include 'testing-tools:app' +include 'traces-api-facade:app' +include 'traces-api-facade:core' +include 'traces-api-facade:conflation' include 'transaction-decoder-tool' From e3a2a42a21fe6fb3a810ae76e570411988059ca0 Mon Sep 17 00:00:00 2001 From: Victorien Gauch <85494462+VGau@users.noreply.github.com> Date: Mon, 16 Sep 2024 16:36:24 +0200 Subject: [PATCH 2/4] feat(3102): add FAQ page (#19) * feat: add FAQ page * fix: update faq content and rephrase some faq titles * fix: add spacing between paragraph * fix: remove padding for list in collapse component --- bridge-ui/src/app/faq/page.tsx | 214 ++++++++++++++++++ bridge-ui/src/components/Collapse.tsx | 13 ++ .../components/layouts/header/HeaderLogo.tsx | 2 + bridge-ui/src/utils/constants.ts | 12 +- 4 files changed, 235 insertions(+), 6 deletions(-) create mode 100644 bridge-ui/src/app/faq/page.tsx create mode 100644 bridge-ui/src/components/Collapse.tsx diff --git a/bridge-ui/src/app/faq/page.tsx b/bridge-ui/src/app/faq/page.tsx new file mode 100644 index 000000000..8cfa5dab2 --- /dev/null +++ b/bridge-ui/src/app/faq/page.tsx @@ -0,0 +1,214 @@ +import Link from "next/link"; +import { Collapse } from "@/components/Collapse"; + +export default function FaqPage() { + return ( +
By default, your bridged funds are sent to the same address they were originally sent from.
++ Yes — find the 'To different address' button beneath the field that displays the amount of ETH or + tokens you will receive on the target chain. You can then enter the address you want the funds to be bridged + to. Only send funds to addresses on Ethereum Mainnet or Linea Mainnet. You may lose funds otherwise, and + they will be irretrievable (see this{" "} + + MetaMask Support article + {" "} + for an explanation). This means you cannot bridge to Bitcoin or Solana, for example, using the Linea Bridge. +
++ If you chose manual claiming, you need to return to the Linea Bridge and make an additional transaction. It + typically takes around 20 minutes (two Ethereum epochs) before you can claim a deposit; withdrawals from + Linea can take much longer, and vary in duration. +
++ To claim, head to the 'Transactions' tab and locate the bridge transaction you want to claim; it + should be marked as 'Ready to claim'. Click on it, and then on the 'Claim' button to + initiate the transaction. +
++ Linea does not charge fees for using the bridge. However, you will need to pay gas fees for transactions. + Gas fees vary according to network activity, so we cannot accurately predict how much you'll pay. The + bulk of the cost will be for interacting with Ethereum Mainnet; Linea's gas fees are considerably + cheaper. +
++ If you use manual claiming, you pay gas fees for the bridge transaction and then gas fees for the claim + transaction. +
++ For automatic claiming, you pay gas fees for your initial bridge transaction and then a fee to cover the gas + costs of the postman executing the claim on your behalf. +
++ The Linea Bridge is designed to transact between layer 1 (Ethereum Mainnet) and layer 2 (Linea Mainnet), + rather than for bridging to any other chains. +
++ If you want to bridge to other EVM-compatible networks, consider using the{" "} + + MetaMask Portfolio bridge + + . +
++ The tokens available to select on the Linea Bridge are sourced from a curated list defined{" "} + + here + {" "} + and maintained by the Linea team. This practice ensures users always bridge to the correct token—rather than + variants, preventing{" "} + + liquidity fragmentation + {" "} + and mitigates the risk of funds loss. +
++ First, check whether your funds are ready to claim. To see claimable funds, go to the “Transactions” tab of + the Linea Bridge app. +
++ If claiming isn't the issue, head to Lineascan and see if the transaction is pending, and in the queue: +
++ If the transaction is still pending, just wait for it to be confirmed, and your funds will be available to + claim or will be in your wallet (depending on the claiming method you chose). If the transaction is missing, + or it has been confirmed and you still don&pos;t see your tokens, contact support by clicking the button in + the bottom-left of the Linea Bridge app, or head to the{" "} + + Linea help center + + . +
+This depends on the direction of your bridge:
++ Yes, although it's not a method we recommend for beginners.{" "} + + View the guide on the MetaMask Help Center + + . +
++ Note that this only speeds up your submission of the bridge transaction. It does not actually speed up the + bridging process itself that you initiate with this transaction — you cannot speed up the 8-32 hour waiting + time for a withdrawal. +
+Click the “Contact support” button in the bottom-left corner of the Linea Bridge app.
+Alternatively, head to the Linea Help Center and click the “Contact” button on the homepage.
++ You can also get advice and support on our moderated{" "} + + Discord + + . +
+