migrate #2287, up heapMem

this branch is ready to merge

Author: JFWooten4

.gitignore

@@ -31,6 +31,7 @@ yarn-error.log*
 
 # Environment variables
 .env
+**/cookies.txt
 
 stellar-cli-repo
 

docs/build/apps/x402.mdx

@@ -20,17 +20,35 @@ To support x402 on Stellar, a wallet must support [auth-entry signing](../guides
 - Hana
 - HOT
 - Klever
-- One Key
+- OneKey
 
 :::note
 
 Freighter Mobile does not currently support x402; use the Freighter browser extension. Mobile support is planned for a future release.
 
 :::
 
-## x402 Facilitator from OpenZeppelin
+## x402 Facilitator
 
-The [OpenZeppelin Relayer x402 Plugin for x402](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator) implements the x402 facilitator API so you can serve x402 payments directly from a Relayer instance. It works with the Coinbase x402 ecosystem (e.g., @x402/express) and exposes the expected `/verify`, `/settle`, and `/supported` endpoints under the Relayer plugin router.
+The [OpenZeppelin Relayer x402 Plugin for x402](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator) implements the x402 Facilitator API so you can serve x402 payments directly from a Relayer instance. The x402 Facilitator leverages the OpenZeppelin Relayer Framework. It works with the [Coinbase x402](https://github.com/coinbase/x402) ecosystem and exposes the expected `/verify`, `/settle`, and `/supported` endpoints under the Relayer plugin router.
+
+### How to Use
+
+The x402 facilitator Service is now live on Testnet and Mainnet. Under the hood, the plugin leverages OpenZeppelin Channels to submit transactions onchain via a managed Relayer and Facilitator setup.
+
+#### Testnet
+
+To use the facilitator on testnet, you will need:
+
+- An API Key (Relayer Service). Generate your testnet API key here: https://channels.openzeppelin.com/testnet/gen
+- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402/testnet`
+
+#### Mainnet
+
+To use the Facilitator on mainnet, you will need:
+
+- An API Key (Relayer Service). Generate your mainnet API key here: https://channels.openzeppelin.com/gen
+- Facilitator URL. Use the following facilitator endpoint in your configuration: `https://channels.openzeppelin.com/x402`
 
 :::note
 
@@ -43,7 +61,18 @@ This version supports x402 v2 specification. For x402 v1 support, please use a p
 - **x402 Starter Template** — A starter template for building payment-enabled applications with x402. Simplified scaffolding demonstrating x402 payment protocol integration with browser wallet support; use it as a foundation for micropayment-enabled services, SaaS applications, or any project that needs frictionless web payments. [View on GitHub](https://github.com/ElliotFriend/x402/tree/stellar-browser-wallet-example/examples/typescript/fullstack/browser-wallet-example)
 - **Economic Load Balancer** — An intelligent multi-chain payment router that automatically selects the most cost-efficient network for high-frequency AI agent micropayments. [View on GitHub](https://github.com/marcelosalloum/x402/tree/x402-hackathon)
 
+## Additional Documentation
+
+- [OpenZeppelin x402 Facilitator Plugin Source Code](https://github.com/OpenZeppelin/relayer-plugin-x402-facilitator)
+- [OpenZeppelin x402 Facilitator Docs](https://docs.openzeppelin.com/relayer/1.4.x/guides/stellar-x402-facilitator-guide)
+- [OpenZeppelin Stellar Relayer SDK](https://github.com/OpenZeppelin/openzeppelin-relayer-sdk)
+- [OpenZeppelin Stellar Relayer Docs](https://docs.openzeppelin.com/relayer/1.4.x)
+- [OpenZeppelin Smart Account](https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account)
+
 ## Learn more
 
+- [x402 Demo](https://x402-stellar-491bf9f7e30b.herokuapp.com/) - A demo site to a x402 transaction on Testnet
 - [x402 protocol (Coinbase Developer Platform)](https://docs.cdp.coinbase.com/x402) — Official x402 protocol overview and spec
+- [x402 protocol specification](https://www.x402.org/) — x402 Specification and Whitepaper
+- [Coinbase x402 GitHub](https://github.com/coinbase/x402) — Official x402 Protocol GitHub Repo
 - [Signing Soroban invocations](../guides/transactions/signing-soroban-invocations.mdx) — Auth-entry signing and transaction signing on Stellar

docs/build/guides/archival/README.mdx

@@ -1,7 +1,6 @@
 ---
 title: State Archival
 hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
 sidebar_position: 77
 ---
 

docs/build/guides/archival/_category_.json

@@ -75,7 +75,7 @@ fn create_env() -> Env {
 }
 ```
 
-You could also use the current [network settings](../../../networks/resource-limits-fees.mdx#resource-fees) when setting up the tests, but keep in mind that these are subject to change, and the contract should be able to work with any values of these settings.
+You could also use the current [network settings](https://lab.stellar.org/network-limits) when setting up the tests, but keep in mind that these are subject to change, and the contract should be able to work with any values of these settings.
 
 Now we run a test scenario that verifies the TTL extension logic (see [`test_extend_ttl_behavior`](https://github.com/stellar/soroban-examples/blob/v23.0.0/ttl/src/test.rs#L38) test for the full scenario). First, we setup the data and ensure that the initial TTL values correspond to the network settings we've defined above:
 

docs/build/guides/archival/test-ttl-extension.mdx

@@ -1,7 +1,6 @@
 ---
 title: Contract Authorization
 hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
 sidebar_position: 1
 ---
 

docs/build/guides/auth/README.mdx

@@ -1,7 +1,6 @@
 ---
 title: Stellar Basics
 hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
 sidebar_position: 80
 ---
 

docs/build/guides/auth/_category_.json

@@ -1,7 +1,6 @@
 ---
 title: Contract Accounts
 hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
 sidebar_position: 5
 description: Build, evaluate, and extend contract accounts on Stellar.
 ---