refactor(docs): rename

nikerzetic-aflabs · nikerzetic-aflabs · commit 6591206d92fe · 2026-05-20T11:30:31.000+02:00
diff --git a/docs/smart-accounts/3-full-custom-instruction.mdx b/docs/smart-accounts/3-full-custom-instruction.mdx
@@ -1,9 +1,9 @@
 ---
 sidebar_position: 1
-slug: custom-instruction
-title: Custom Instruction
+slug: full-custom-instruction
+title: Full Custom Instruction
 authors: [nikerzetic]
-description: Performing custom function calls in the Flare Smart Accounts.
+description: Performing custom function calls in the Flare Smart Accounts by carrying the full PackedUserOperation in the XRPL memo (0xFF).
 tags: [intermediate, ethereum, flare-smart-accounts]
 keywords:
   [
@@ -19,17 +19,32 @@ keywords:
 import ThemedImage from "@theme/ThemedImage";
 import useBaseUrl from "@docusaurus/useBaseUrl";
 
-Flare Smart Accounts let an XRPL user execute arbitrary contract calls on Flare trough the [`Payment`](https://xrpl.org/docs/references/protocol/transactions/types/payment) transaction on the XRPL blockchain.
+Flare Smart Accounts let an XRPL user execute arbitrary contract calls on Flare through an XRPL [`Payment`](https://xrpl.org/docs/references/protocol/transactions/types/payment) transaction.
 Each personal account exposes an [EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) style `executeUserOp` entry point that the [`MasterAccountController`](/smart-accounts/reference/IMasterAccountController) invokes when it processes a custom instruction memo.
 
-Custom instructions carry the full call payload in the XRPL **memo** field.
-The user signs a `PackedUserOperation`, ships it on XRPL, and the smart account replays it on the Flare blockchain.
+The **full** custom instruction (memo opcode `0xFF`) carries the entire ABI-encoded `PackedUserOperation` in the XRPL memo immediately after a 10-byte header.
+The user signs an XRPL `Payment`, ships the payload on XRPL, and the smart account replays the user operation on Flare with no further off-chain data.
+For the alternative that ships only a 32-byte hash of the user operation and lets an executor deliver the bytes on Flare, see the [Hash Custom Instruction](/smart-accounts/hash-custom-instruction); the [comparison guide](/smart-accounts/custom-instruction-comparison) covers when to pick which.
 
 :::warning No destination tags
 XRPL transactions targeting smart accounts must not use a destination tag.
 A destination tag forces [FAssets direct minting](/fassets/direct-minting) to credit the tag-holder, which would let an unrelated party front-run the user operation.
 :::
 
+## Memo layout
+
+The XRPL memo carries a 10-byte instruction header followed by the ABI-encoded `PackedUserOperation`:
+
+| Bytes | Field            | Meaning                                                                  |
+| ----- | ---------------- | ------------------------------------------------------------------------ |
+| `0`   | `instructionId`  | `0xFF` — full custom instruction                                         |
+| `1`   | `walletId`       | One-byte wallet identifier assigned by Flare; `0` if not registered      |
+| `2-9` | `executorFeeUBA` | Executor fee in the FAsset's smallest unit, big-endian `uint64`          |
+| `10+` | `userOpData`     | `abi.encode(PackedUserOperation)` — the call payload the facet decodes   |
+
+The total memo length is `10 + len(abi.encode(userOp))` bytes.
+The XRPL caps each memo at roughly `1024` bytes, so large or repetitive call batches may need to be split across multiple XRPL payments.
+
 ## User operation payload
 
 The custom instruction payload has two layers: the outer EIP-4337 [`PackedUserOperation`](https://eips.ethereum.org/EIPS/eip-4337#useroperation) carried in the XRPL memo, and the inner [`executeUserOp(Call[])`](/smart-accounts/reference/IPersonalAccount#executeuserop) that the personal account runs once the controller dispatches it.
diff --git a/docs/smart-accounts/6-reference.mdx b/docs/smart-accounts/6-reference.mdx
diff --git a/docs/smart-accounts/guides/typescript-viem/02-full-custom-instruction.mdx b/docs/smart-accounts/guides/typescript-viem/02-full-custom-instruction.mdx
@@ -1,9 +1,9 @@
 ---
 sidebar_position: 2
-slug: custom-instruction-ts
-title: Custom Instruction
+slug: full-custom-instruction-ts
+title: Full Custom Instruction
 authors: [nikerzetic]
-description: Sending custom smart account instructions using Viem.
+description: Sending the full PackedUserOperation in an XRPL memo with Viem (0xFF flow).
 tags: [quickstart, ethereum, flare-smart-accounts]
 keywords:
   [
@@ -20,8 +20,10 @@ unlisted: false
 import CodeBlock from "@theme/CodeBlock";
 import CustomInstructionsScript from "!!raw-loader!/examples/developer-hub-javascript/smart-accounts/custom-instructions.ts";
 
-The [Custom Instruction overview](/smart-accounts/custom-instruction) explains how Flare smart accounts replay an [EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) `PackedUserOperation` carried in an XRPL `Payment` memo.
-This guide walks through a TypeScript script that builds the user operation with Viem library, sends a payment transaction with the user operation on XRPL, and waits for the [`UserOperationExecuted`](/smart-accounts/reference/IMasterAccountController#useroperationexecuted) event on Flare.
+The [Full Custom Instruction overview](/smart-accounts/full-custom-instruction) explains how Flare smart accounts replay an [EIP-4337](https://eips.ethereum.org/EIPS/eip-4337) `PackedUserOperation` carried in full in an XRPL `Payment` memo (opcode `0xFF`).
+This guide walks through a TypeScript script that builds the user operation with the Viem library, sends a payment transaction with the user operation on XRPL, and waits for the [`UserOperationExecuted`](/smart-accounts/reference/IMasterAccountController#useroperationexecuted) event on Flare.
+
+If your batch overflows the XRPL memo cap, or you want to keep call payloads off the public XRPL ledger, see the [Hash Custom Instruction guide](/smart-accounts/guides/typescript-viem/hash-custom-instruction-ts) for the 0xFE variant that ships only `keccak256(userOp)` in the memo.
 
 The script executes three calls on three example smart contracts on the Flare blockchain.
 Because the XRPL memo field is capped at roughly `1024` bytes, the calls are split into two user operations sent in sequence.
@@ -477,6 +479,8 @@ Memo-only amount (XRP, fees only): 0.0011
 To continue your Flare Smart Accounts development journey, you can:
 
 - Get the smart account state using the [State Lookup guide](/smart-accounts/guides/typescript-viem/state-lookup-ts).
-- Explore the [Custom Instruction](/smart-accounts/custom-instruction) overview.
+- Explore the [Full Custom Instruction overview](/smart-accounts/full-custom-instruction).
+- Compare the full and hash variants in the [Custom Instruction Comparison](/smart-accounts/custom-instruction-comparison).
+- Try the hash variant with the [Hash Custom Instruction guide](/smart-accounts/guides/typescript-viem/hash-custom-instruction-ts).
 - Dig into the `IMasterAccountController` [reference](/smart-accounts/reference/IMasterAccountController).
   :::
diff --git a/docs/smart-accounts/guides/typescript-viem/04-cross-chain-mint.mdx b/docs/smart-accounts/guides/typescript-viem/04-cross-chain-mint.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 4
 slug: cross-chain-mint-ts
 title: Cross-Chain Mint
 authors: [nikerzetic]
diff --git a/docs/smart-accounts/guides/typescript-viem/05-cross-chain-redeem.mdx b/docs/smart-accounts/guides/typescript-viem/05-cross-chain-redeem.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 slug: cross-chain-redeem-ts
 title: Cross-Chain Redeem
 authors: [nikerzetic]
diff --git a/docs/smart-accounts/guides/typescript-viem/06-cross-chain-redeem-to-tag.mdx b/docs/smart-accounts/guides/typescript-viem/06-cross-chain-redeem-to-tag.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 slug: cross-chain-redeem-to-tag-ts
 title: Cross-Chain Redeem to Tag
 authors: [nikerzetic]
