From 7a0a7f1bd3c0eff9f3b7536e0e7734f70f313f4d Mon Sep 17 00:00:00 2001 From: iPLAY888 <133153661+letmehateu@users.noreply.github.com> Date: Mon, 25 Aug 2025 14:46:56 +0300 Subject: [PATCH 1/3] Update ens-names.md fixed dead links --- docs/learn/architecture/ens-names.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/learn/architecture/ens-names.md b/docs/learn/architecture/ens-names.md index 37f8e55a..4a3bd93b 100644 --- a/docs/learn/architecture/ens-names.md +++ b/docs/learn/architecture/ens-names.md @@ -7,7 +7,7 @@ Farcaster uses ENS names as human readable identifiers for accounts. Two kinds o ENS names can only be used on Farcaster if they are <= 16 characters and contain only lowercase letters, numbers, and hyphens. -![Usernames](/assets/usernames.png) +![Usernames](../../assets/usernames.png) ## Onchain ENS Names @@ -40,7 +40,7 @@ Decisions are made by the Farcaster team and often require human judgment. Users Fnames are issued as offchain names under the subdomain `fcast.id`. -Bob can register the offchain ENS name `bob.fcast.id` and use it on any Farcaster app with the shorthand `@bob`. The name can be registered by making a signed request to the Fname Registry server. See the [FName API reference](/reference/fname/api) for more details on how to query and create Fnames. +Bob can register the offchain ENS name `bob.fcast.id` and use it on any Farcaster app with the shorthand `@bob`. The name can be registered by making a signed request to the Fname Registry server. See the [FName API reference](../../reference/fname/api.md) for more details on how to query and create Fnames. To learn more about how Fnames work, see [ENSIP-16](https://docs.ens.domains/ens-improvement-proposals/ensip-16-offchain-metadata) and [ERC-3668](https://eips.ethereum.org/EIPS/eip-3668). From 8e6a0927285aaad2e6257314f40fe1679694d4c1 Mon Sep 17 00:00:00 2001 From: iPLAY888 <133153661+letmehateu@users.noreply.github.com> Date: Mon, 25 Aug 2025 14:48:52 +0300 Subject: [PATCH 2/3] Update contracts.md fixed broken link --- docs/learn/architecture/contracts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/architecture/contracts.md b/docs/learn/architecture/contracts.md index 7d21a64d..4d407a28 100644 --- a/docs/learn/architecture/contracts.md +++ b/docs/learn/architecture/contracts.md @@ -12,7 +12,7 @@ There are three main contracts deployed on OP Mainnet:
-![Registry Contracts](/assets/registry-contracts.png) +![Registry Contracts](../../assets/registry-contracts.png) The contracts are deployed at the following addresses: From 563c628af661c8125d1ec7a605a0f283019127f4 Mon Sep 17 00:00:00 2001 From: iPLAY888 <133153661+letmehateu@users.noreply.github.com> Date: Mon, 25 Aug 2025 14:49:51 +0300 Subject: [PATCH 3/3] Update overview.md fixed broken link --- docs/learn/architecture/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/architecture/overview.md b/docs/learn/architecture/overview.md index e6968921..418d38b1 100644 --- a/docs/learn/architecture/overview.md +++ b/docs/learn/architecture/overview.md @@ -2,7 +2,7 @@ Farcaster has a hybrid architecture that stores identity onchain and data offchain. -![Architecture](/assets/architecture.png) +![Architecture](../../assets/architecture.png) ## Onchain