move accounts to main navigation

safe-global · Dec 3, 2024 · fcd5ca3 · fcd5ca3
1 parent b3bad7c
commit fcd5ca3
Show file tree

Hide file tree

Showing 8 changed files with 14 additions and 14 deletions.
diff --git a/pages/safenet/_meta.json b/pages/safenet/_meta.json
@@ -7,6 +7,7 @@
   "introduction": "Why Safenet",
   "chains": "Multi-Chain",
   "architecture": "Architecture",
+  "safenet-account": "Safenet Account",
   "safenet-transaction": "Safenet Transaction",
   "optimistic-validity-proof": "Optimistic Validity Proof",
   "-- details": {

diff --git a/pages/safenet/chains.mdx b/pages/safenet/chains.mdx
@@ -22,7 +22,7 @@ Another name is *source chain*.
 ### Home Chain
 
 Safenet uses Ethereum Mainnet as the home chain for configuration and coordination.
-For example, the configurable set of safety guarantees for a user's [Safenet account](./core-components/safenet-account.mdx) is stored on Ethereum Mainnet.
+For example, the configurable set of safety guarantees for a user's [Safenet account](./safenet-account.mdx) is stored on Ethereum Mainnet.
 
 ## Chains vary per transaction
 

diff --git a/pages/safenet/concepts/attestation.mdx b/pages/safenet/concepts/attestation.mdx
@@ -3,7 +3,7 @@
 The [processor](../core-components/processor.mdx) uses an attestation to prove the validity of a [settlement](../concepts/settlement.mdx).
 It serves as a cryptographic proof that the fulfillment of a Safenet [transaction](../safenet-transaction.mdx) is valid under the specific conditions defined by the user's configured [guarantees](../concepts/guarantee.mdx).
 
-The attestation has to be sent from the spend [chain](../concepts/chain.mdx) to the home chain, where it is validated by the [guarantee engine](../protocol/guarantee-engine.mdx).
+The attestation has to be sent from the spend [chain](../chains.mdx) to the home chain, where it is validated by the [guarantee engine](../protocol/guarantee-engine.mdx).
 It is then sent from the guarantee engine to the [settlement engine](../protocol/settlement-engine.mdx) on the debit chain to finalize the settlement.
 The attestation data is sent through external bridges, which can be costly and slow.
 

diff --git a/pages/safenet/concepts/settlement.mdx b/pages/safenet/concepts/settlement.mdx
@@ -2,7 +2,7 @@ import { Callout, Steps, Tabs } from 'nextra/components'
 
 # Settlement
 
-Settlement is the process by which a [processor](../core-components/processor.mdx) debits funds from a [Safenet account](../core-components/safenet-account.mdx) to repay the [liquidity provider](../core-components/liquidity-provider.mdx) for the short-term loan (pre-funding) used in a [Safenet transaction](../safenet-transaction.mdx).
+Settlement is the process by which a [processor](../core-components/processor.mdx) debits funds from a [Safenet account](../safenet-account.mdx) to repay the [liquidity provider](../core-components/liquidity-provider.mdx) for the short-term loan (pre-funding) used in a [Safenet transaction](../safenet-transaction.mdx).
 
 The [settlement engine](../protocol/settlement-engine.mdx) handles debit requests on the debit [chain](../chains.mdx) by transferring funds from the Safenet Safe to a [beneficiary](../protocol/beneficiary.mdx) designated by the liquidity provider. 
 This occurs after the liquidity provider has fronted funds on the spend chain.

diff --git a/pages/safenet/core-components/_meta.json b/pages/safenet/core-components/_meta.json
@@ -1,6 +1,5 @@
 {
     "processor": "Processor",
     "validator": "Validator",
-    "liquidity-provider": "Liquidity Provider",
-    "safenet-account": "Safenet Account"
+    "liquidity-provider": "Liquidity Provider"
 }
diff --git a/pages/safenet/core-components/end-user.mdx b/pages/safenet/core-components/end-user.mdx
@@ -1,4 +1,4 @@
 # End User
 
-The End User is an individual with one or more [Safenet accounts](safenet-account.mdx), using [Safe\{Wallet\}](https://app.safe.global/welcome) to interact with Safenet.
+The End User is an individual with one or more [Safenet accounts](../safenet-account.mdx), using [Safe\{Wallet\}](https://app.safe.global/welcome) to interact with Safenet.
 
diff --git a/pages/safenet/core-components/safenet-account.mdx b/pages/safenet/core-components/safenet-account.mdx
diff --git a/pages/safenet/safenet-account.mdx b/pages/safenet/safenet-account.mdx
@@ -0,0 +1,8 @@
+# Safenet Account
+
+A Safenet account is a network of [Safe Smart Accounts](../home/what-is-safe.mdx) deployed on multiple [chains](./chains.mdx).
+A Safe Smart Account is connected to a Safenet account by adding the Safenet [Guard](./protocol/guard.mdx) as a co-signer.
+
+Initially, one Safe Smart Account can be added per chain. In later phases of the roadmap, multiple Safe Smart Accounts can be added per chain.
+
+![Safenet-account](../../assets/safenet-account.png)