From f39f199ac507da29e396461553432cc98e9ea93b Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Tue, 31 Mar 2026 08:02:06 -0700 Subject: [PATCH 1/6] add cw state tooltips --- docs/cloud-wallet/tooltips.md | 132 ++++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) diff --git a/docs/cloud-wallet/tooltips.md b/docs/cloud-wallet/tooltips.md index ac2a702a97..eb9279bd6c 100644 --- a/docs/cloud-wallet/tooltips.md +++ b/docs/cloud-wallet/tooltips.md @@ -240,3 +240,135 @@ Token issuers can send messages with a variety of different topics. You can subs - /company/general - /company/airdrops - /company/meetups/miami + +## Transaction states + +These labels describe the lifecycle of a transaction in your vault. For more on clawbacks and pending activity, see [Clawback](#clawback) and the [FAQ](/cloud-wallet/faq/). + +### Transaction UNSIGNED + +The transaction is a draft and coins are still in your vault but are locked in reserve for the transaction. **Action:** Sign the transaction and it will be submitted to the mempool or delete the transaction to unlock the coins for use in another transaction. + +### Transaction SIGNED + +Transaction is ready for submission to the mempool. **Action:** The transaction will be automatically submitted to the blockchain; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Transaction MEMPOOL + +The transaction has been submitted to the blockchain and the associated coins have left your available balance but are not yet confirmed. **Action:** Wait for the network to include the transaction in a block; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Transaction PENDING + +The transaction is being prepared or is waiting on another step (for example vault coordination or signer availability) before it can be submitted or advance to the mempool. It is not yet fully signed or broadcast. **Action:** Complete any prompts or signing steps in the Cloud Wallet; if the status does not change for an extended time, refresh the app or contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Transaction SETTLED + +Transaction has completed and coins have successfully transferred to the destination. **Action:** None. Transaction is complete. + +### Transaction RE_ORG + +This transaction was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party of the transaction and ensure they resync their wallet as needed; you will likely need to recreate and submit this transaction from the initiating wallet. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Transaction INVALID + +The transaction failed (likely due to low fees or a conflict) and coins have not been transferred. **Action:** Re-create the transaction with corrected details. + +## Offer states + +These labels describe the lifecycle of an offer. For context on vault-based offers, see [Known issues](/cloud-wallet/known-issues/). + +### Offer OPEN + +The offer is active and available for others to accept (others will need a copy of the offer file to accept it). Coins are reserved in your vault and may have been moved to an offer reservation address controlled by your vault (based on whether you enabled the auto-split feature when creating the offer). **Action:** Wait for a counterparty to accept or cancel the offer if you no longer wish to trade. + +### Offer MEMPOOL + +An acceptance of the offer has been broadcast to the network. The associated coins have left your available balance but are not yet confirmed. **Action:** Wait for the transaction to be included in a block; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Offer SETTLED + +The trade is successful and the exchange of coins is final. **Action:** None. The offer is complete. + +### Offer RE_ORG + +This offer was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party and ensure they resync their wallet as needed; you may need to recreate or resubmit this offer. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +### Offer EXPIRED + +The time limit for this offer has passed and coins are no longer reserved. **Action:** Create a new offer if you still wish to trade. + +### Offer INVALID + +The offer can no longer be fulfilled (e.g., coins were spent elsewhere or fees were too low). **Action:** Remove the offer and create a new one with available funds. + +### Offer PENDING + +The offer is being prepared, validated, or updated; reserved coins may still be settling into the correct shape for the offer. **Action:** Wait for the status to advance to Open or another terminal state; if it stays pending for an extended time, try refreshing or contact our support team with the in-app form or in [discord](https://discord.gg/chia). + +## Vault recovery states + +These are workflow states during a vault [recovery](#recovery). See [Instant Recovery](#instant-recovery) and [Timelocked Recovery](#timelocked-recovery) for types of recovery. + +### Recovery IDLE + +No recovery is in progress, or the last recovery-related transaction has settled and the vault is no longer in an active recovery workflow. **Action:** None unless you intend to start or continue a recovery. + +### Recovery AWAITING_REVIEW + +A recovery request has been submitted and is waiting for review by a [recovery provider](#recovery-provider), when one is configured. **Action:** Wait for the provider; follow any email or in-app instructions. If nothing changes for an unusually long time, contact the recovery provider or support with the in-app form or in [discord](https://discord.gg/chia). + +### Recovery PENDING + +The recovery request is waiting for your signature (after provider approval, if applicable, or when using a direct recovery path). **Action:** Open the signing flow and complete the required signatures. + +### Recovery SIGNED + +The recovery transaction has been signed on your side but has not yet been submitted to the blockchain. **Action:** Wait for submission; if it remains here, retry or check connectivity, or contact support with the in-app form or in [discord](https://discord.gg/chia). + +### Recovery SUBMITTED + +The recovery transaction has been submitted to the blockchain and is awaiting confirmation or further processing. **Action:** Wait for block inclusion; see [Transaction MEMPOOL](#transaction-mempool) if you need general context on mempool behavior. + +### Recovery TIMELOCK + +The recovery has been processed by blockchain sync: your vault is in the recovery timelock period described under [Recovery timer](#recovery-timer) and [Recovery clawback](#recovery-clawback). **Action:** Monitor the timer; you can cancel the recovery with the spend key during this window if appropriate, or wait until the timelock completes. + +### Recovery TIMELOCK_COMPLETE + +The recovery timelock has completed according to chain state. You may [claw back](#clawback) the recovery attempt or finish the recovery, depending on your situation. **Action:** Follow the Cloud Wallet prompts to either complete recovery or cancel it. + +### Recovery FINISH_SIGNED + +The transaction to finish recovery has been signed but not yet submitted. **Action:** Wait for broadcast or complete any remaining submit step. + +### Recovery FINISH_SUBMITTED + +The finish-recovery transaction has been submitted to the blockchain. **Action:** Wait for confirmation before assuming recovery is complete. + +### Recovery CLAWBACK_SIGNED + +The transaction to claw back the recovery attempt has been signed but not yet submitted. **Action:** Wait for broadcast or complete any remaining submit step. + +### Recovery CLAWBACK_SUBMITTED + +The clawback transaction has been submitted to the blockchain. **Action:** Wait for confirmation and verify vault status in the vault. + +## Wallet state + +These labels describe high-level vault status. They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. + +### Wallet READY + +The wallet is available for transfers and normal operations. + +### Wallet VAULT_PENDING_CREATE + +The vault singleton has been minted and is in the mempool; the vault is not fully ready until creation confirms. + +### Wallet VAULT_RECOVERY_TIMELOCK + +The vault is in a recovery flow and the recovery timelock is active. You may be able to claw back the recovery or, after the timelock has passed, complete recovery; see **Recovery TIMELOCK** under [Vault recovery states](#vault-recovery-states). + +### Wallet VAULT_RECOVERY_TIMELOCK_COMPLETE + +The vault’s recovery timelock has completed on chain. You can claw back the recovery attempt or finish recovery. **Action:** Follow in-app steps; see **Recovery TIMELOCK_COMPLETE** under [Vault recovery states](#vault-recovery-states). From 710a4b9537c255cc3638a81e3c2c27b7d85aed68 Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Wed, 6 May 2026 10:29:24 -0600 Subject: [PATCH 2/6] docs(cloud-wallet): refine CW tooltip copy per doc review - UNSIGNED: split draft/reserve explanation and action bullets - SIGNED/MEMPOOL: mempool-first wording; 45m guidance vs busy mempool - Offer SETTLED: past tense trade outcome - Wallet state: vault-consistent wording under READY Co-authored-by: Cursor --- docs/cloud-wallet/tooltips.md | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/docs/cloud-wallet/tooltips.md b/docs/cloud-wallet/tooltips.md index eb9279bd6c..847cfe5317 100644 --- a/docs/cloud-wallet/tooltips.md +++ b/docs/cloud-wallet/tooltips.md @@ -247,15 +247,24 @@ These labels describe the lifecycle of a transaction in your vault. For more on ### Transaction UNSIGNED -The transaction is a draft and coins are still in your vault but are locked in reserve for the transaction. **Action:** Sign the transaction and it will be submitted to the mempool or delete the transaction to unlock the coins for use in another transaction. +The transaction is a draft. Your coins are still in your vault, but they are locked in reserve for the transaction. + +**Action:** Do one of the following: + +- Sign the transaction, after which it will automatically be submitted to the mempool. +- Delete the transaction, which will unlock the coins for future use. ### Transaction SIGNED -Transaction is ready for submission to the mempool. **Action:** The transaction will be automatically submitted to the blockchain; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +The transaction has been submitted to the mempool and is waiting for inclusion in a block; it is not confirmed on-chain yet. If the mempool is busy and the fee is not large enough, it is not unusual to wait up to 45 minutes in this state. + +**Action:** Wait for confirmation; if the transaction remains in this state for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Transaction MEMPOOL -The transaction has been submitted to the blockchain and the associated coins have left your available balance but are not yet confirmed. **Action:** Wait for the network to include the transaction in a block; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +The transaction has been submitted to the mempool. The associated coins have left your available balance but the transaction is not yet confirmed in a block. If the mempool is busy and the fee is not large enough, waits of up to about 45 minutes are common. + +**Action:** Wait for the network to include the transaction in a block; if the transaction remains in this state for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Transaction PENDING @@ -283,11 +292,11 @@ The offer is active and available for others to accept (others will need a copy ### Offer MEMPOOL -An acceptance of the offer has been broadcast to the network. The associated coins have left your available balance but are not yet confirmed. **Action:** Wait for the transaction to be included in a block; if the transaction remains in this state for more than 10 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +An acceptance of the offer has been broadcast to the network. The associated coins have left your available balance but are not yet confirmed. **Action:** Wait for the transaction to be included in a block; if the transaction remains in this state for more than 45 minutes please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Offer SETTLED -The trade is successful and the exchange of coins is final. **Action:** None. The offer is complete. +The trade was successful and the exchange of coins is final. **Action:** None. The offer is complete. ### Offer RE_ORG @@ -355,11 +364,11 @@ The clawback transaction has been submitted to the blockchain. **Action:** Wait ## Wallet state -These labels describe high-level vault status. They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. +These labels describe high-level vault status in the Cloud Wallet UI. They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. Descriptions below refer to your **vault** consistently. ### Wallet READY -The wallet is available for transfers and normal operations. +The vault is ready for transfers and normal operations. ### Wallet VAULT_PENDING_CREATE From ed38b599d12dc66e1ff7d2d7565361579e9fd191 Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Wed, 6 May 2026 11:32:56 -0600 Subject: [PATCH 3/6] docs(cloud-wallet): distinguish SIGNED vs MEMPOOL; vault terminology SIGNED = signed, mempool submission pending; MEMPOOL = broadcast accepted. Vault vs wallet: vault for custody; Chia Cloud Wallet for product; Vault state headings. RE_ORG: initiating/resync vault wording. Co-authored-by: Cursor --- docs/cloud-wallet/tooltips.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/docs/cloud-wallet/tooltips.md b/docs/cloud-wallet/tooltips.md index 847cfe5317..a859811d6f 100644 --- a/docs/cloud-wallet/tooltips.md +++ b/docs/cloud-wallet/tooltips.md @@ -256,13 +256,15 @@ The transaction is a draft. Your coins are still in your vault, but they are loc ### Transaction SIGNED -The transaction has been submitted to the mempool and is waiting for inclusion in a block; it is not confirmed on-chain yet. If the mempool is busy and the fee is not large enough, it is not unusual to wait up to 45 minutes in this state. +The transaction is **fully signed** on your side; it has **not** necessarily been **accepted into the mempool** yet. The Chia Cloud Wallet will typically submit it automatically—once broadcast is accepted, the status moves to **Transaction MEMPOOL**. -**Action:** Wait for confirmation; if the transaction remains in this state for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +If the mempool is busy or the fee is too low, it can take noticeable time before submission succeeds—waits of up to about 45 minutes **before** the status advances beyond **Transaction SIGNED** are not unusual. + +**Action:** Wait for the status to advance (usually to **Transaction MEMPOOL**); if the transaction **remains only** in **Transaction SIGNED** for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Transaction MEMPOOL -The transaction has been submitted to the mempool. The associated coins have left your available balance but the transaction is not yet confirmed in a block. If the mempool is busy and the fee is not large enough, waits of up to about 45 minutes are common. +The transaction **has been submitted to the mempool** (broadcast accepted). The associated coins have left your available balance, but the transaction is not yet confirmed in a block. If the mempool is busy and the fee is not large enough, waits of up to about 45 minutes **for block inclusion** are common. **Action:** Wait for the network to include the transaction in a block; if the transaction remains in this state for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). @@ -276,7 +278,7 @@ Transaction has completed and coins have successfully transferred to the destina ### Transaction RE_ORG -This transaction was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party of the transaction and ensure they resync their wallet as needed; you will likely need to recreate and submit this transaction from the initiating wallet. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +This transaction was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party of the transaction and ensure they resync their vault as needed; you will likely need to recreate and submit this transaction from the initiating vault. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Transaction INVALID @@ -300,7 +302,7 @@ The trade was successful and the exchange of coins is final. **Action:** None. T ### Offer RE_ORG -This offer was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party and ensure they resync their wallet as needed; you may need to recreate or resubmit this offer. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +This offer was part of a blockchain re-org and coins have not been transferred. **Action:** Confirm the coin status with the other party and ensure they resync their vault as needed; you may need to recreate or resubmit this offer. If questions arise please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Offer EXPIRED @@ -362,22 +364,22 @@ The transaction to claw back the recovery attempt has been signed but not yet su The clawback transaction has been submitted to the blockchain. **Action:** Wait for confirmation and verify vault status in the vault. -## Wallet state +## Vault state -These labels describe high-level vault status in the Cloud Wallet UI. They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. Descriptions below refer to your **vault** consistently. +These labels match high-level status shown in the Chia Cloud Wallet UI (heading names follow the in-app strings where noted). They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. Unless referring to the **Chia Cloud Wallet** product by name, descriptions use **vault** for your custody. -### Wallet READY +### Vault READY The vault is ready for transfers and normal operations. -### Wallet VAULT_PENDING_CREATE +### Vault VAULT_PENDING_CREATE The vault singleton has been minted and is in the mempool; the vault is not fully ready until creation confirms. -### Wallet VAULT_RECOVERY_TIMELOCK +### Vault VAULT_RECOVERY_TIMELOCK The vault is in a recovery flow and the recovery timelock is active. You may be able to claw back the recovery or, after the timelock has passed, complete recovery; see **Recovery TIMELOCK** under [Vault recovery states](#vault-recovery-states). -### Wallet VAULT_RECOVERY_TIMELOCK_COMPLETE +### Vault VAULT_RECOVERY_TIMELOCK_COMPLETE The vault’s recovery timelock has completed on chain. You can claw back the recovery attempt or finish recovery. **Action:** Follow in-app steps; see **Recovery TIMELOCK_COMPLETE** under [Vault recovery states](#vault-recovery-states). From a255cf566697092fd703f2bb2df16f2865668cf2 Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Wed, 6 May 2026 11:34:34 -0600 Subject: [PATCH 4/6] docs(cloud-wallet): remove heavy bold from SIGNED/MEMPOOL and vault state Co-authored-by: Cursor --- docs/cloud-wallet/tooltips.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/cloud-wallet/tooltips.md b/docs/cloud-wallet/tooltips.md index a859811d6f..8c554e73cc 100644 --- a/docs/cloud-wallet/tooltips.md +++ b/docs/cloud-wallet/tooltips.md @@ -256,15 +256,15 @@ The transaction is a draft. Your coins are still in your vault, but they are loc ### Transaction SIGNED -The transaction is **fully signed** on your side; it has **not** necessarily been **accepted into the mempool** yet. The Chia Cloud Wallet will typically submit it automatically—once broadcast is accepted, the status moves to **Transaction MEMPOOL**. +The transaction is fully signed on your side and has not necessarily been accepted into the mempool yet. The Chia Cloud Wallet will typically submit it automatically; once broadcast is accepted, the status moves to Transaction MEMPOOL. -If the mempool is busy or the fee is too low, it can take noticeable time before submission succeeds—waits of up to about 45 minutes **before** the status advances beyond **Transaction SIGNED** are not unusual. +If the mempool is busy or the fee is too low, it can take noticeable time before submission succeeds—waits of up to about 45 minutes before the status advances beyond Transaction SIGNED are not unusual. -**Action:** Wait for the status to advance (usually to **Transaction MEMPOOL**); if the transaction **remains only** in **Transaction SIGNED** for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). +**Action:** Wait for the status to advance (usually to Transaction MEMPOOL); if the transaction stays in Transaction SIGNED for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). ### Transaction MEMPOOL -The transaction **has been submitted to the mempool** (broadcast accepted). The associated coins have left your available balance, but the transaction is not yet confirmed in a block. If the mempool is busy and the fee is not large enough, waits of up to about 45 minutes **for block inclusion** are common. +The transaction has been submitted to the mempool (broadcast accepted). The associated coins have left your available balance, but the transaction is not yet confirmed in a block. If the mempool is busy and the fee is not large enough, waits of up to about 45 minutes for block inclusion are common. **Action:** Wait for the network to include the transaction in a block; if the transaction remains in this state for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). @@ -366,7 +366,7 @@ The clawback transaction has been submitted to the blockchain. **Action:** Wait ## Vault state -These labels match high-level status shown in the Chia Cloud Wallet UI (heading names follow the in-app strings where noted). They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. Unless referring to the **Chia Cloud Wallet** product by name, descriptions use **vault** for your custody. +These labels match high-level status shown in the Chia Cloud Wallet UI (heading names follow the in-app strings where noted). They overlap with [Vault recovery states](#vault-recovery-states) when a recovery is in progress. Unless referring to the Chia Cloud Wallet product by name, descriptions use vault for your custody. ### Vault READY @@ -378,7 +378,7 @@ The vault singleton has been minted and is in the mempool; the vault is not full ### Vault VAULT_RECOVERY_TIMELOCK -The vault is in a recovery flow and the recovery timelock is active. You may be able to claw back the recovery or, after the timelock has passed, complete recovery; see **Recovery TIMELOCK** under [Vault recovery states](#vault-recovery-states). +The vault is in a recovery flow and the recovery timelock is active. You may be able to claw back the recovery or, after the timelock has passed, complete recovery; see Recovery TIMELOCK under [Vault recovery states](#vault-recovery-states). ### Vault VAULT_RECOVERY_TIMELOCK_COMPLETE From cc8d9e34de4b28e8b528d8c7a63fe9ebb04507c0 Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Wed, 6 May 2026 11:36:22 -0600 Subject: [PATCH 5/6] docs(cloud-wallet): clarify Transaction SIGNED copy; add docs prose Cursor rule Co-authored-by: Cursor --- .cursor/rules/docs-prose.mdc | 12 ++++++++++++ docs/cloud-wallet/tooltips.md | 4 ++-- 2 files changed, 14 insertions(+), 2 deletions(-) create mode 100644 .cursor/rules/docs-prose.mdc diff --git a/.cursor/rules/docs-prose.mdc b/.cursor/rules/docs-prose.mdc new file mode 100644 index 0000000000..96779fa723 --- /dev/null +++ b/.cursor/rules/docs-prose.mdc @@ -0,0 +1,12 @@ +--- +description: Chia docs prose style for Markdown under docs/ +globs: docs/**/*.md +alwaysApply: false +--- + +# Documentation prose (chia-docs) + +When editing or adding pages under `docs/`: + +- **Bold:** Do not stack emphasis across narrative sentences. Use bold sparingly for UI affordances, explicit step labels that match the product (for example lines starting with **Action:**), or rare single-term emphasis. Prefer plain prose for definitions and explanations. +- **Dashes:** Do not use em dashes (`—`) or en dashes as sentence punctuation. Use commas, periods, a clause in parentheses, or a hyphen-minus (`-`) where a break is needed. diff --git a/docs/cloud-wallet/tooltips.md b/docs/cloud-wallet/tooltips.md index 8c554e73cc..6ac40e3b74 100644 --- a/docs/cloud-wallet/tooltips.md +++ b/docs/cloud-wallet/tooltips.md @@ -256,9 +256,9 @@ The transaction is a draft. Your coins are still in your vault, but they are loc ### Transaction SIGNED -The transaction is fully signed on your side and has not necessarily been accepted into the mempool yet. The Chia Cloud Wallet will typically submit it automatically; once broadcast is accepted, the status moves to Transaction MEMPOOL. +The transaction is signed on your side; it has not been accepted into the mempool yet. The Chia Cloud Wallet will submit it automatically and once broadcast is accepted in the mempool, the status will update to Transaction MEMPOOL. -If the mempool is busy or the fee is too low, it can take noticeable time before submission succeeds—waits of up to about 45 minutes before the status advances beyond Transaction SIGNED are not unusual. +If the mempool is busy or the fee is too low, it can take noticeable time before submission succeeds. Waits of up to about 45 minutes before the status advances beyond Transaction SIGNED are not unusual. **Action:** Wait for the status to advance (usually to Transaction MEMPOOL); if the transaction stays in Transaction SIGNED for more than 45 minutes, please contact our support team with the in-app form or in [discord](https://discord.gg/chia). From dcbfda989e5aa06ef45dbe1479ea4bd0f65a0108 Mon Sep 17 00:00:00 2001 From: ClydeWallace22 <48610606+BrandtH22@users.noreply.github.com> Date: Wed, 6 May 2026 11:38:42 -0600 Subject: [PATCH 6/6] chore: drop Cursor docs-prose rule (moved to chia-ai-skills-library) Co-authored-by: Cursor --- .cursor/rules/docs-prose.mdc | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 .cursor/rules/docs-prose.mdc diff --git a/.cursor/rules/docs-prose.mdc b/.cursor/rules/docs-prose.mdc deleted file mode 100644 index 96779fa723..0000000000 --- a/.cursor/rules/docs-prose.mdc +++ /dev/null @@ -1,12 +0,0 @@ ---- -description: Chia docs prose style for Markdown under docs/ -globs: docs/**/*.md -alwaysApply: false ---- - -# Documentation prose (chia-docs) - -When editing or adding pages under `docs/`: - -- **Bold:** Do not stack emphasis across narrative sentences. Use bold sparingly for UI affordances, explicit step labels that match the product (for example lines starting with **Action:**), or rare single-term emphasis. Prefer plain prose for definitions and explanations. -- **Dashes:** Do not use em dashes (`—`) or en dashes as sentence punctuation. Use commas, periods, a clause in parentheses, or a hyphen-minus (`-`) where a break is needed.