@ocap/client 1.25.3 → 1.25.5

package/docs/how-to-guides-delegate-permissions.md

@@ -0,0 +1,167 @@
+# Delegate Permissions
+
+Delegating permissions is a powerful feature that allows one account (the delegator) to authorize another account (the delegatee) to send specific types of transactions on its behalf. This is particularly useful for applications that need to perform actions for a user without having direct access to the user's primary private key. For example, you could delegate permission to an application-specific key to transfer certain assets or interact with a smart contract, enhancing security by limiting the scope of the key's authority.
+
+This guide will walk you through granting, using, and revoking delegations.
+
+## Granting Delegation
+
+To authorize another account, you use the `delegate` method. You must specify who you are delegating to and which specific transaction types they are allowed to send. Each permission can also have limits, such as which tokens or assets can be involved.
+
+### Parameters
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The wallet object of the delegator (the account granting permissions).</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The wallet object of the delegatee (the account receiving permissions).</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<object>" data-required="true">
+    <x-field-desc markdown>An array of permission objects to grant. Each object defines a specific authorization.</x-field-desc>
+    <x-field data-name="typeUrl" data-type="string" data-required="true">
+      <x-field-desc markdown>The type URL of the transaction being permitted (e.g., `fg:t:transfer_v2`).</x-field-desc>
+    </x-field>
+    <x-field data-name="limit" data-type="object" data-required="false">
+      <x-field-desc markdown>Optional limits on the permission, such as restricting it to specific tokens or assets.</x-field-desc>
+      <x-field data-name="tokens" data-type="Array<string>" data-required="false" data-desc="An array of token addresses that this permission applies to."></x-field>
+      <x-field data-name="assets" data-type="Array<string>" data-required="false" data-desc="An array of asset addresses that this permission applies to."></x-field>
+    </x-field>
+  </x-field>
+</x-field-group>
+
+### Returns
+
+<x-field data-name="result" data-type="Promise<[string, string]>" data-desc="A promise that resolves to an array containing the transaction hash and the newly created delegate address."></x-field>
+
+### Example
+
+Here’s how to delegate the `transfer` permission from one account to another.
+
+```javascript Granting transfer permission icon=logos:javascript
+import Client from '@ocap/client';
+import { fromRandom } from '@ocap/wallet';
+import { typeUrls } from '@ocap/proto';
+
+const client = new Client('https://beta.abtnetwork.io/api');
+
+// The account granting permission
+const delegatorWallet = fromRandom();
+
+// The account receiving permission
+const delegateeWallet = fromRandom();
+
+async function grantPermission() {
+  try {
+    // First, ensure the delegator account has funds.
+    // In a real application, you would transfer funds to delegatorWallet.address
+    // from a faucet or another account.
+    console.log(`Delegator address: ${delegatorWallet.address}`);
+    console.log(`Delegatee address: ${delegateeWallet.address}`);
+    console.log('Please fund the delegator account before proceeding.');
+
+    const privileges = [
+      {
+        typeUrl: typeUrls.TransferV2Tx,
+        // No limits specified, allowing transfer of any token/asset
+        limit: { tokens: [], assets: [] },
+      },
+    ];
+
+    const [hash, delegateAddress] = await client.delegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: privileges,
+    });
+
+    console.log('Delegation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log('Delegate Address:', delegateAddress);
+  } catch (error) {
+    console.error('Error delegating permissions:', error);
+  }
+}
+
+grantPermission();
+```
+
+## Sending a Transaction as a Delegatee
+
+Once delegated, the delegatee wallet can send the authorized transaction by specifying the `delegator`'s address in the transaction parameters. The transaction is signed by the delegatee, but executed on behalf of the delegator, and the transaction fees are paid from the delegator's account.
+
+### Example
+
+```javascript Sending a transfer as a delegatee icon=logos:javascript
+// Assuming the grantPermission() function from the previous example was successful
+
+// The recipient of the transfer
+const recipientWallet = fromRandom();
+
+async function sendDelegatedTransaction() {
+  try {
+    const hash = await client.transfer({
+      to: recipientWallet.address,
+      token: 1, // Transfer 1 of the chain's native token
+      wallet: delegateeWallet, // Signed by the delegatee
+      delegator: delegatorWallet.address, // Executed on behalf of the delegator
+    });
+
+    console.log('Delegated transfer successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error sending delegated transaction:', error);
+  }
+}
+
+// Make sure to call this after the delegation is confirmed on-chain.
+// sendDelegatedTransaction();
+```
+
+## Revoking Delegation
+
+The delegator can revoke any granted permissions at any time using the `revokeDelegate` method. You need to specify which transaction types to revoke for a given delegatee.
+
+### Parameters
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The wallet object of the delegator who originally granted the permissions.</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The wallet object of the delegatee whose permissions are being revoked.</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<string>" data-required="true">
+    <x-field-desc markdown>An array of transaction `typeUrl` strings to revoke.</x-field-desc>
+  </x-field>
+</x-field-group>
+
+### Returns
+
+<x-field data-name="hash" data-type="Promise<string>" data-desc="A promise that resolves to the transaction hash for the revocation."></x-field>
+
+### Example
+
+```javascript Revoking transfer permission icon=logos:javascript
+// Assuming the same delegatorWallet and delegateeWallet from previous examples
+
+async function revokePermission() {
+  try {
+    const hash = await client.revokeDelegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: [typeUrls.TransferV2Tx], // The list of permissions to revoke
+    });
+
+    console.log('Revocation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error revoking delegation:', error);
+  }
+}
+
+// revokePermission();
+```
+
+After this transaction is confirmed, the `delegateeWallet` will no longer be able to send `transfer` transactions on behalf of the `delegatorWallet`.

package/docs/how-to-guides-delegate-permissions.zh-TW.md

@@ -0,0 +1,167 @@
+# 委派權限
+
+委派權限是一項強大的功能，它允許一個帳戶（委派人）授權另一個帳戶（受派人）代表其發送特定類型的交易。這對於需要為使用者執行操作但又不想直接存取使用者主私鑰的應用程式特別有用。例如，您可以將權限委派給特定於應用程式的金鑰，以轉移某些資產或與智慧合約互動，透過限制金鑰的權限範圍來增強安全性。
+
+本指南將引導您完成授予、使用和撤銷委派的過程。
+
+## 授予委派
+
+要授權另一個帳戶，您可以使用 `delegate` 方法。您必須指定要委派給誰以及他們被允許發送哪些特定的交易類型。每項權限還可以有其限制，例如可以涉及哪些代幣或資產。
+
+### 參數
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>委派人（授予權限的帳戶）的錢包物件。</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>受派人（接收權限的帳戶）的錢包物件。</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<object>" data-required="true">
+    <x-field-desc markdown>要授予的權限物件陣列。每個物件定義一個特定的授權。</x-field-desc>
+    <x-field data-name="typeUrl" data-type="string" data-required="true">
+      <x-field-desc markdown>被允許的交易的類型 URL（例如 `fg:t:transfer_v2`）。</x-field-desc>
+    </x-field>
+    <x-field data-name="limit" data-type="object" data-required="false">
+      <x-field-desc markdown>對權限的可選限制，例如將其限制為特定的代幣或資產。</x-field-desc>
+      <x-field data-name="tokens" data-type="Array<string>" data-required="false" data-desc="此權限適用的代幣地址陣列。"></x-field>
+      <x-field data-name="assets" data-type="Array<string>" data-required="false" data-desc="此權限適用的資產地址陣列。"></x-field>
+    </x-field>
+  </x-field>
+</x-field-group>
+
+### 返回值
+
+<x-field data-name="result" data-type="Promise<[string, string]>" data-desc="一個解析為包含交易雜湊和新建立的委派地址的陣列的 Promise。"></x-field>
+
+### 範例
+
+以下是如何將 `transfer` 權限從一個帳戶委派給另一個帳戶的方法。
+
+```javascript Granting transfer permission icon=logos:javascript
+import Client from '@ocap/client';
+import { fromRandom } from '@ocap/wallet';
+import { typeUrls } from '@ocap/proto';
+
+const client = new Client('https://beta.abtnetwork.io/api');
+
+// 授予權限的帳戶
+const delegatorWallet = fromRandom();
+
+// 接收權限的帳戶
+const delegateeWallet = fromRandom();
+
+async function grantPermission() {
+  try {
+    // 首先，確保委派人帳戶有資金。
+    // 在實際應用中，您需要將資金從水龍頭或其他帳戶轉入 delegatorWallet.address
+    // from a faucet or another account.
+    console.log(`Delegator address: ${delegatorWallet.address}`);
+    console.log(`Delegatee address: ${delegateeWallet.address}`);
+    console.log('Please fund the delegator account before proceeding.');
+
+    const privileges = [
+      {
+        typeUrl: typeUrls.TransferV2Tx,
+        // 未指定限制，允許轉移任何代幣/資產
+        limit: { tokens: [], assets: [] },
+      },
+    ];
+
+    const [hash, delegateAddress] = await client.delegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: privileges,
+    });
+
+    console.log('Delegation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log('Delegate Address:', delegateAddress);
+  } catch (error) {
+    console.error('Error delegating permissions:', error);
+  }
+}
+
+grantPermission();
+```
+
+## 作為受派人發送交易
+
+一旦被委派，受派人錢包可以通過在交易參數中指定 `delegator` 的地址來發送已授權的交易。該交易由受派人簽名，但代表委派人執行，交易費用從委派人的帳戶中支付。
+
+### 範例
+
+```javascript Sending a transfer as a delegatee icon=logos:javascript
+// 假設前一個範例中的 grantPermission() 函數已成功執行
+
+// 轉帳的接收者
+const recipientWallet = fromRandom();
+
+async function sendDelegatedTransaction() {
+  try {
+    const hash = await client.transfer({
+      to: recipientWallet.address,
+      token: 1, // 轉移 1 單位的鏈原生代幣
+      wallet: delegateeWallet, // 由受派人簽名
+      delegator: delegatorWallet.address, // 代表委派人執行
+    });
+
+    console.log('Delegated transfer successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error sending delegated transaction:', error);
+  }
+}
+
+// 確保在鏈上確認委派後再調用此函數。
+// sendDelegatedTransaction();
+```
+
+## 撤銷委派
+
+委派人可以隨時使用 `revokeDelegate` 方法撤銷任何已授予的權限。您需要為指定的受派人指定要撤銷哪些交易類型。
+
+### 參數
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>最初授予權限的委派人的錢包物件。</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>其權限正在被撤銷的受派人的錢包物件。</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<string>" data-required="true">
+    <x-field-desc markdown>要撤銷的交易 `typeUrl` 字串陣列。</x-field-desc>
+  </x-field>
+</x-field-group>
+
+### 返回值
+
+<x-field data-name="hash" data-type="Promise<string>" data-desc="一個解析為撤銷交易雜湊的 Promise。"></x-field>
+
+### 範例
+
+```javascript Revoking transfer permission icon=logos:javascript
+// 假設使用與前述範例相同的 delegatorWallet 和 delegateeWallet
+
+async function revokePermission() {
+  try {
+    const hash = await client.revokeDelegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: [typeUrls.TransferV2Tx], // 要撤銷的權限列表
+    });
+
+    console.log('Revocation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error revoking delegation:', error);
+  }
+}
+
+// revokePermission();
+```
+
+此交易確認後，`delegateeWallet` 將無法再代表 `delegatorWallet` 發送 `transfer` 交易。

package/docs/how-to-guides-delegate-permissions.zh.md

@@ -0,0 +1,166 @@
+# 委托权限
+
+委托权限是一项强大的功能，它允许一个账户（委托人）授权另一个账户（被委托人）代表其发送特定类型的交易。这对于需要为用户执行操作但又不想直接访问用户主私钥的应用程序尤其有用。例如，您可以将权限委托给特定于应用程序的密钥，以转移某些资产或与智能合约交互，通过限制该密钥的权限范围来增强安全性。
+
+本指南将引导您完成授予、使用和撤销委托权限的过程。
+
+## 授予委托
+
+要授权另一个账户，您可以使用 `delegate` 方法。您必须指定要委托给谁以及他们被允许发送哪些特定的交易类型。每个权限还可以有限制，例如可以涉及哪些代币或资产。
+
+### 参数
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>委托人（授予权限的账户）的钱包对象。</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>被委托人（接收权限的账户）的钱包对象。</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<object>" data-required="true">
+    <x-field-desc markdown>要授予的权限对象数组。每个对象定义一个特定的授权。</x-field-desc>
+    <x-field data-name="typeUrl" data-type="string" data-required="true">
+      <x-field-desc markdown>被许可的交易的类型 URL（例如，`fg:t:transfer_v2`）。</x-field-desc>
+    </x-field>
+    <x-field data-name="limit" data-type="object" data-required="false">
+      <x-field-desc markdown>对权限的可选限制，例如限制于特定的代币或资产。</x-field-desc>
+      <x-field data-name="tokens" data-type="Array<string>" data-required="false" data-desc="此权限适用的代币地址数组。"></x-field>
+      <x-field data-name="assets" data-type="Array<string>" data-required="false" data-desc="此权限适用的资产地址数组。"></x-field>
+    </x-field>
+  </x-field>
+</x-field-group>
+
+### 返回值
+
+<x-field data-name="result" data-type="Promise<[string, string]>" data-desc="一个 Promise，它解析为一个包含交易哈希和新创建的委托地址的数组。"></x-field>
+
+### 示例
+
+以下是如何将 `transfer` 权限从一个账户委托给另一个账户。
+
+```javascript Granting transfer permission icon=logos:javascript
+import Client from '@ocap/client';
+import { fromRandom } from '@ocap/wallet';
+import { typeUrls } from '@ocap/proto';
+
+const client = new Client('https://beta.abtnetwork.io/api');
+
+// 授予权限的账户
+const delegatorWallet = fromRandom();
+
+// 接收权限的账户
+const delegateeWallet = fromRandom();
+
+async function grantPermission() {
+  try {
+    // 首先，确保委托人账户有资金。
+    // 在实际应用中，您需要从水龙头或其他账户向 delegatorWallet.address 转账。
+    console.log(`Delegator address: ${delegatorWallet.address}`);
+    console.log(`Delegatee address: ${delegateeWallet.address}`);
+    console.log('Please fund the delegator account before proceeding.');
+
+    const privileges = [
+      {
+        typeUrl: typeUrls.TransferV2Tx,
+        // 未指定限制，允许转移任何代币/资产
+        limit: { tokens: [], assets: [] },
+      },
+    ];
+
+    const [hash, delegateAddress] = await client.delegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: privileges,
+    });
+
+    console.log('Delegation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log('Delegate Address:', delegateAddress);
+  } catch (error) {
+    console.error('Error delegating permissions:', error);
+  }
+}
+
+grantPermission();
+```
+
+## 作为被委托人发送交易
+
+一旦被委托，被委托人钱包可以通过在交易参数中指定 `delegator` 的地址来发送已授权的交易。该交易由被委托人签名，但代表委托人执行，并且交易费用从委托人的账户中支付。
+
+### 示例
+
+```javascript Sending a transfer as a delegatee icon=logos:javascript
+// 假设前一个示例中的 grantPermission() 函数已成功执行
+
+// 转账的接收方
+const recipientWallet = fromRandom();
+
+async function sendDelegatedTransaction() {
+  try {
+    const hash = await client.transfer({
+      to: recipientWallet.address,
+      token: 1, // 转移 1 个链的原生代币
+      wallet: delegateeWallet, // 由被委托人签名
+      delegator: delegatorWallet.address, // 代表委托人执行
+    });
+
+    console.log('Delegated transfer successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error sending delegated transaction:', error);
+  }
+}
+
+// 确保在链上确认委托后再调用此函数。
+// sendDelegatedTransaction();
+```
+
+## 撤销委托
+
+委托人可以随时使用 `revokeDelegate` 方法撤销任何已授予的权限。您需要为给定的被委托人指定要撤销的交易类型。
+
+### 参数
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>最初授予权限的委托人的钱包对象。</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>其权限被撤销的被委托人的钱包对象。</x-field-desc>
+  </x-field>
+  <x-field data-name="privileges" data-type="Array<string>" data-required="true">
+    <x-field-desc markdown>要撤销的交易 `typeUrl` 字符串数组。</x-field-desc>
+  </x-field>
+</x-field-group>
+
+### 返回值
+
+<x-field data-name="hash" data-type="Promise<string>" data-desc="一个 Promise，它解析为撤销操作的交易哈希。"></x-field>
+
+### 示例
+
+```javascript Revoking transfer permission icon=logos:javascript
+// 假设使用与前面示例相同的 delegatorWallet 和 delegateeWallet
+
+async function revokePermission() {
+  try {
+    const hash = await client.revokeDelegate({
+      from: delegatorWallet,
+      to: delegateeWallet,
+      privileges: [typeUrls.TransferV2Tx], // 要撤销的权限列表
+    });
+
+    console.log('Revocation successful!');
+    console.log('Transaction Hash:', hash);
+    console.log(`Check transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+  } catch (error) {
+    console.error('Error revoking delegation:', error);
+  }
+}
+
+// revokePermission();
+```
+
+此交易确认后，`delegateeWallet` 将无法再代表 `delegatorWallet` 发送 `transfer` 交易。

package/docs/how-to-guides-manage-accounts.ja.md

@@ -0,0 +1,73 @@
+# アカウントの管理
+
+OCAP を利用したブロックチェーンでは、アカウントは基本的にアドレスに関連付けられた状態であり、暗号鍵のペア（公開鍵と秘密鍵）によって制御されます。理解すべき重要な概念は、アカウントが暗黙的に作成されるということです。アカウントは、トークンや資産の転送など、最初の受信トランザクションを受け取るとすぐに、チェーン上で公式に存在します。明示的な `createAccount` トランザクションはありません。
+
+このガイドでは、重要なアカウント管理操作である、アカウントを新しい鍵セットに移行する方法に焦点を当てます。これは、アドレス、残高、または資産を変更することなく、アカウントの所有権を変更できる重要なセキュリティ機能です。
+
+## アカウントを新しい鍵に移行する
+
+`migrateAccount` 関数を使用すると、既存のアカウントアドレスを新しい公開鍵に関連付けることができます。これは、次のような複数のシナリオで役立ちます。
+
+- **鍵の侵害**：秘密鍵が漏洩した疑いがある場合、アカウントを新しい安全な鍵ペアに移行して、不正アクセスを防ぐことができます。
+- **セキュリティのアップグレード**：古いタイプの鍵から、より新しく安全な鍵に移行したい場合があります。
+
+この操作により、ブロックチェーン上の履歴と状態を保持しながら、アカウントの制御を効果的に移転できます。
+
+### パラメーター
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>移行される現在のアカウントを表すウォレットオブジェクト。このウォレットは、所有権を証明するためにトランザクションに署名する必要があります。</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>制御が移転される新しいウォレットオブジェクト。このウォレットの公開鍵が、アカウントアドレスの新しい権限になります。</x-field-desc>
+  </x-field>
+</x-field-group>
+
+### 戻り値
+
+`migrateAccount` メソッドは、トランザクションハッシュを文字列として解決する Promise を返します。
+
+### 例
+
+古いウォレットから新しいウォレットにアカウントを移行する方法を次に示します。
+
+```javascript Migrating an Account icon=logos:javascript
+import Client from '@ocap/client';
+import { fromRandom } from '@ocap/wallet';
+
+const client = new Client('https://beta.abtnetwork.io/api');
+
+// oldWallet がアカウントの現在承認されているウォレットであると仮定します
+const oldWallet = fromRandom(); 
+
+// 新しい鍵セットで新しいウォレットを作成します
+const newWallet = fromRandom();
+
+async function migrate() {
+  try {
+    // 移行する前に、通常は oldWallet のアドレスに資金を供給します。
+    // この例では、トランザクション手数料を支払うのに十分な資金があると仮定します。
+    // テストトークンは https://faucet.abtnetwork.io/ から入手できます
+    console.log(`アカウントを ${oldWallet.address} から ${newWallet.address} に関連付けられた新しい鍵に移行しています`);
+
+    const hash = await client.migrateAccount({
+      from: oldWallet,
+      to: newWallet,
+    });
+
+    console.log('アカウント移行トランザクションは正常に送信されました！');
+    console.log('トランザクションハッシュ:', hash);
+    console.log(`トランザクションを表示: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+
+  } catch (err) {
+    console.error('アカウント移行エラー:', err);
+  }
+}
+
+migrate();
+```
+
+---
+
+鍵を移行してアカウントを保護する方法がわかったので、プライマリキーを共有せずに他のアカウントに限定的な権限を付与する方法を学びたいと思うかもしれません。詳細については、[権限の委任](./how-to-guides-delegate-permissions.md) ガイドを参照してください。

package/docs/how-to-guides-manage-accounts.md

@@ -0,0 +1,73 @@
+# Manage Accounts
+
+On an OCAP-powered blockchain, an account is fundamentally a state associated with an address, controlled by a pair of cryptographic keys (a public key and a private key). A key concept to understand is that accounts are created implicitly. An account officially exists on-chain as soon as it receives its first incoming transaction, such as a token or asset transfer. There is no explicit `createAccount` transaction.
+
+This guide focuses on a critical account management operation: migrating an account to a new set of keys. This is an essential security feature that allows you to change the ownership of an account without altering its address, balance, or assets.
+
+## Migrate an Account to New Keys
+
+The `migrateAccount` function allows you to associate an existing account address with a new public key. This is useful in several scenarios, such as:
+
+- **Key Compromise**: If you suspect your private key has been exposed, you can migrate the account to a new, secure key pair to prevent unauthorized access.
+- **Upgrading Security**: You might want to migrate from an older key type to a newer, more secure one.
+
+This operation effectively transfers control of the account while preserving its history and state on the blockchain.
+
+### Parameters
+
+<x-field-group>
+  <x-field data-name="from" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The wallet object representing the current account that is being migrated. This wallet must sign the transaction to prove ownership.</x-field-desc>
+  </x-field>
+  <x-field data-name="to" data-type="WalletObject" data-required="true">
+    <x-field-desc markdown>The new wallet object to which control will be transferred. The public key from this wallet will become the new authority for the account address.</x-field-desc>
+  </x-field>
+</x-field-group>
+
+### Returns
+
+The `migrateAccount` method returns a Promise that resolves to the transaction hash as a string.
+
+### Example
+
+Here's how to migrate an account from an old wallet to a new one.
+
+```javascript Migrating an Account icon=logos:javascript
+import Client from '@ocap/client';
+import { fromRandom } from '@ocap/wallet';
+
+const client = new Client('https://beta.abtnetwork.io/api');
+
+// Assume oldWallet is the currently authorized wallet for the account
+const oldWallet = fromRandom(); 
+
+// Create a new wallet with a new set of keys
+const newWallet = fromRandom();
+
+async function migrate() {
+  try {
+    // Before migrating, you would typically fund the oldWallet's address.
+    // For this example, we'll assume it has enough funds to pay for the transaction fee.
+    // You can get test tokens from https://faucet.abtnetwork.io/
+    console.log(`Migrating account from ${oldWallet.address} to new keys associated with ${newWallet.address}`);
+
+    const hash = await client.migrateAccount({
+      from: oldWallet,
+      to: newWallet,
+    });
+
+    console.log('Account migration transaction sent successfully!');
+    console.log('Transaction Hash:', hash);
+    console.log(`View transaction at: https://beta.abtnetwork.io/explorer/txs/${hash}`);
+
+  } catch (err) {
+    console.error('Error migrating account:', err);
+  }
+}
+
+migrate();
+```
+
+---
+
+Now that you know how to secure your account by migrating keys, you might want to learn how to grant limited permissions to other accounts without sharing your primary keys. See the [Delegate Permissions](./how-to-guides-delegate-permissions.md) guide for more details.