deprecation notices

Author: feruzm

src/content/docs/common/posting.md

@@ -29,7 +29,7 @@ Downvotes or moderation actions may follow these behaviors. Repeat offenders can
 - **Use relevant tags**: Pick 1–5 tags that match your topic (e.g., `travel`, `photography`, `introduction`). Keep them lowercase; hyphens are allowed.
 - **Format for readability**: Use headings, lists, and images to break up text.
 - **Set fair beneficiaries** if sharing rewards with collaborators.
-- **Respect community rules**: Many communities have their own posting standards — read them before submitting.
+- **Respect community rules**: Many communities have their own posting standards - read them before submitting.
 
 ---
 

src/content/docs/developers/sdk.mdx

@@ -7,7 +7,7 @@ description: Framework-agnostic data layer for Hive apps with first-class React
 
 The Ecency SDK (`@ecency/sdk`) is a framework-agnostic data layer for Hive applications with
 first-class **React Query** support. It provides **165+ query option builders**, **76+ mutation
-hooks**, and a shared configuration layer — all with **zero runtime dependencies**.
+hooks**, and a shared configuration layer - all with **zero runtime dependencies**.
 
 Published on [npm](https://www.npmjs.com/package/@ecency/sdk) under the MIT license.
 
@@ -17,10 +17,10 @@ Published on [npm](https://www.npmjs.com/package/@ecency/sdk) under the MIT lice
 |---|---|
 | Query builders | 165+ composable query option builders |
 | Mutation hooks | 76+ hooks for all blockchain write operations |
-| Cache keys | Centralized `QueryKeys` — single source of truth |
+| Cache keys | Centralized `QueryKeys` - single source of truth |
 | Auth methods | Private key, Keychain, HiveSigner, HiveAuth |
 | Platform support | Web, React Native, Node.js (SSR) |
-| Runtime deps | **Zero** — only peer dependencies |
+| Runtime deps | **Zero** - only peer dependencies |
 | Bundle size | ~182 KB |
 | Build targets | Browser ESM + Node ESM/CJS (dual builds via tsup) |
 
@@ -32,9 +32,9 @@ Published on [npm](https://www.npmjs.com/package/@ecency/sdk) under the MIT lice
   promotions, games, ai, integrations, auth, bridge, core, private-api
 - **Central configuration** via `ConfigManager` (RPC nodes, QueryClient, DMCA filtering, image host)
 - **Platform adapter pattern** for cross-platform auth and broadcasting
-- **Smart auth fallback** — automatically tries alternative signing methods on failure
-- **RPC node failover** — multi-node configuration with automatic failover
-- **Blockchain error parsing** — user-friendly error messages with typed error categories
+- **Smart auth fallback** - automatically tries alternative signing methods on failure
+- **RPC node failover** - multi-node configuration with automatic failover
+- **Blockchain error parsing** - user-friendly error messages with typed error categories
 
 ## Why React Query?
 
@@ -183,21 +183,21 @@ The Ecency SDK with React Query solves all of these:
 
 - Reduced API calls by 70-90% through intelligent caching
 - Instant UI updates with optimistic mutations
-- Zero manual cache management — React Query handles invalidation
+- Zero manual cache management - React Query handles invalidation
 - Better UX with background updates and retry logic
 - Faster perceived performance with prefetching and SSR
-- Less code — no custom loading/error/caching logic needed
+- Less code - no custom loading/error/caching logic needed
 
 ### How other apps can benefit
 
 Any Hive application can leverage this SDK to:
 
-1. **Drop custom data fetching code** — use pre-built query options for all common Hive
+1. **Drop custom data fetching code** - use pre-built query options for all common Hive
    operations
-2. **Share cache across features** — one query for account data serves entire app
+2. **Share cache across features** - one query for account data serves entire app
 3. **Add real-time features** easily with `refetchInterval` and optimistic updates
 4. **Improve SEO** with SSR-ready queries that prefetch on server
-5. **Reduce bundle size** — share the SDK's type-safe queries instead of custom fetch logic
+5. **Reduce bundle size** - share the SDK's type-safe queries instead of custom fetch logic
 
 **Example: Building a Hive blog reader**
 
@@ -266,7 +266,7 @@ npm install @hiveio/dhive hivesigner
 npm install react @tanstack/react-query
 ```
 
-React and React Query are optional — the SDK's query option builders and utility functions
+React and React Query are optional - the SDK's query option builders and utility functions
 work without them in server-side or non-React contexts.
 
 ## Quick start
@@ -301,7 +301,7 @@ import { ConfigManager, makeQueryClient } from "@ecency/sdk";
 // Set QueryClient (required for React Query integration)
 ConfigManager.setQueryClient(makeQueryClient());
 
-// Custom RPC nodes (optional — defaults to 6 public nodes)
+// Custom RPC nodes (optional - defaults to 6 public nodes)
 ConfigManager.setHiveNodes([
   "https://api.hive.blog",
   "https://api.deathwing.me",
@@ -315,14 +315,14 @@ ConfigManager.setDmcaLists({
   posts: ["@author/permlink"],
 });
 
-// Custom image CDN host (optional — defaults to images.ecency.com)
+// Custom image CDN host (optional - defaults to images.ecency.com)
 ConfigManager.setImageHost("https://images.ecency.com");
 ```
 
-The SDK includes **automatic RPC node failover** — if the primary node fails, requests are
+The SDK includes **automatic RPC node failover** - if the primary node fails, requests are
 retried on alternate nodes from the configured list.
 
-## QueryKeys — centralized cache management
+## QueryKeys - centralized cache management
 
 All cache keys are defined in a single `QueryKeys` export, organized by domain. Use these
 as the single source of truth for cache invalidation.
@@ -408,13 +408,13 @@ automatic fallback between signing methods:
 import type { AuthContextV2, PlatformAdapter } from "@ecency/sdk";
 
 const adapter: PlatformAdapter = {
-  // Storage — retrieve credentials from your platform's storage
+  // Storage - retrieve credentials from your platform's storage
   getUser: async (username) => getUserFromStore(username),
   getPostingKey: async (username) => getKeyFromStorage(username),
   getAccessToken: async (username) => getTokenFromStorage(username),
   getLoginType: async (username) => getAuthMethod(username),
 
-  // UI feedback — show messages in your platform's style
+  // UI feedback - show messages in your platform's style
   showError: (msg) => toast.error(msg),
   showSuccess: (msg) => toast.success(msg),
 
@@ -426,7 +426,7 @@ const adapter: PlatformAdapter = {
     return showHiveAuthModal(username, ops, keyType);
   },
 
-  // Auth upgrade UI — shown when posting-key user attempts an active-key operation
+  // Auth upgrade UI - shown when posting-key user attempts an active-key operation
   showAuthUpgradeUI: async (authority, operation) => {
     return showUpgradeDialog(authority, operation);
     // Returns: 'key' | 'keychain' | 'hivesigner' | 'hiveauth' | false
@@ -442,7 +442,7 @@ const auth: AuthContextV2 = {
 const { mutateAsync } = useVote(username, auth);
 ```
 
-**Smart auth fallback** — when `enableFallback` is true, the SDK automatically:
+**Smart auth fallback** - when `enableFallback` is true, the SDK automatically:
 
 1. Detects the user's login method via `adapter.getLoginType()`
 2. Attempts to broadcast with that method
@@ -471,7 +471,7 @@ await mutateAsync({
 });
 ```
 
-With a platform adapter, the SDK handles active operations automatically —
+With a platform adapter, the SDK handles active operations automatically -
 prompting the user to upgrade auth if needed.
 
 ## Error handling
@@ -496,9 +496,9 @@ try {
     showMessage("Not enough Resource Credits to broadcast this transaction.");
   } else if (shouldTriggerAuthFallback(error)) {
     // SDK handles this automatically with adapter, but you can customize
-    showMessage("Authentication failed — trying alternative method...");
+    showMessage("Authentication failed - trying alternative method...");
   } else if (isNetworkError(error)) {
-    showMessage("Network error — please check your connection.");
+    showMessage("Network error - please check your connection.");
   } else {
     const [message, type] = formatError(error);
     showMessage(message);
@@ -544,27 +544,27 @@ src/modules/
 | posts | 30 | 20 | Post/comment CRUD, voting, drafts, schedules, images |
 | accounts | 26 | 19 | Account data, relationships, profile, bookmarks |
 | wallet | 23 | 25 | Balances, delegations, transfers, conversions |
-| hive-engine | 10 | — | Hive Engine token queries |
+| hive-engine | 10 | - | Hive Engine token queries |
 | market | 9 | 3 | Prices, order book, trade history |
-| search | 7 | — | Topic, account, post search |
+| search | 7 | - | Topic, account, post search |
 | communities | 7 | 8 | Community data, subscriptions, mutations |
-| spk | 6 | — | SPK wallet, market, rewards |
+| spk | 6 | - | SPK wallet, market, rewards |
 | notifications | 5 | 3 | Notification lists, settings |
 | proposals | 5 | 3 | Governance proposals, voting |
 | core | 4 | 3 | Chain properties, dynamic props, broadcasting |
 | analytics | 4 | 2 | Curation, leaderboard, page stats |
 | promotions | 4 | 2 | Promotion pricing, Boost+ |
 | points | 4 | 2 | Points balance, transactions |
-| resource-credits | 3 | — | RC stats |
+| resource-credits | 3 | - | RC stats |
 | witnesses | 2 | 3 | Witness voting, proxy |
 | operations | 2 | 4 | Operation signing |
 | ai | 2 | 2 | Image generation pricing |
 | games | 2 | 2 | Game status |
 
 ## SSR / RSC notes
 
-- Query option builders are safe to use on the server — they return plain objects.
-- Mutation hooks (`use*`) are client-only — they use React hooks internally.
+- Query option builders are safe to use on the server - they return plain objects.
+- Mutation hooks (`use*`) are client-only - they use React hooks internally.
 - If you use Next.js App Router, keep hook usage in `"use client"` components.
 - Use `queryClient.prefetchQuery()` on the server to hydrate data for instant client rendering.
 

src/content/docs/developers/wallets.mdx

@@ -10,10 +10,20 @@ wallet-related operations across the Ecency website and mobile app. The new
 `@ecency/wallets` package gives us a single, dedicated layer for creating and
 managing wallets while keeping the rest of the Ecency stack lightweight.
 
-## Standard seed phrase, multi-chain addresses
+## Multi-chain addresses
+
+<Aside type="caution">
+  The seed-phrase-based wallet creation flow is being discontinued. Managing
+  a separate seed phrase added complexity to signups and transaction signing.
+  Ecency is integrating **MetaMask** to handle external chain wallets instead.
+  If your application generated wallets using the mnemonic flow described below,
+  guide users to the [seed phrase migration guide](/guides/seed-phrase-migration/)
+  so they can move funds to an external wallet.
+</Aside>
 
-We utilize a blockchain-standard seed phrase to derive wallet addresses across
-different blockchains. A single mnemonic can be used to:
+The `@ecency/wallets` package previously used a blockchain-standard seed phrase
+to derive wallet addresses across different blockchains. A single mnemonic
+could:
 
 1. Generate addresses for multiple supported chains without asking the user to
    juggle several keys.
@@ -23,9 +33,9 @@ different blockchains. A single mnemonic can be used to:
    client enforce its own encryption and secure storage policies.
 
 <Aside type="note">
-  The seed phrase never leaves the client. When a wallet needs to be backed up
-  or restored, the mnemonic is provided by the user, and derived addresses are
-  synced to Ecency services only after local encryption is applied.
+  The seed phrase never left the client. When a wallet needed to be backed up
+  or restored, the mnemonic was provided by the user, and derived addresses were
+  synced to Ecency services only after local encryption was applied.
 </Aside>
 
 ## What `@ecency/wallets` handles
@@ -40,12 +50,15 @@ responsible for:
 - Publishing public wallet metadata to Ecency services when users choose to
   make their addresses available.
 
-## Example: derive addresses from a mnemonic
+## Example: derive addresses from a mnemonic (legacy)
+
+<Aside type="caution">
+  This mnemonic-based flow is being phased out. The example below is kept for
+  reference only. New integrations should not rely on seed phrase generation.
+</Aside>
 
-The snippet below shows the general flow for creating a mnemonic and deriving a
-set of addresses. The exact API surface may evolve, but the key steps—create or
-import a seed, derive addresses for requested chains, and persist only the
-public details—remain the same.
+The snippet below shows the legacy flow for creating a mnemonic and deriving a
+set of addresses.
 
 export const exampleCode = `
 import { createWalletClient } from '@ecency/wallets';

src/content/docs/developers/x402.mdx

@@ -5,7 +5,7 @@ description: Monetize APIs and content with zero-fee HBD micropayments using the
 
 # x402 Payments
 
-The [`@hiveio/x402`](https://www.npmjs.com/package/@hiveio/x402) package brings the [x402 payment protocol](https://www.x402.org/) to Hive. It lets any API or content endpoint accept **HBD micropayments** — zero fees, 3-second finality, no credit cards.
+The [`@hiveio/x402`](https://www.npmjs.com/package/@hiveio/x402) package brings the [x402 payment protocol](https://www.x402.org/) to Hive. It lets any API or content endpoint accept **HBD micropayments** - zero fees, 3-second finality, no credit cards.
 
 Published on [npm](https://www.npmjs.com/package/@hiveio/x402) under the MIT license. Source on [GitHub](https://github.com/ecency/hive-x402).
 
@@ -41,7 +41,7 @@ Client                    Server                   Facilitator
 
 | Feature | Details |
 |---|---|
-| Currency | HBD (Hive Backed Dollars) — pegged to ~$1 USD |
+| Currency | HBD (Hive Backed Dollars) - pegged to ~$1 USD |
 | Transaction fees | **Zero** |
 | Finality | ~3 seconds (1 Hive block) |
 | Middleware | Express, Next.js App Router, Hono |
@@ -58,7 +58,7 @@ npm install @hiveio/x402
 pnpm add @hiveio/x402
 ```
 
-The package uses **subpath exports** — import only what you need:
+The package uses **subpath exports** - import only what you need:
 
 ```ts
 import { ... } from "@hiveio/x402/types";
@@ -88,8 +88,8 @@ app.get(
     description: "Premium API access",
   }),
   (req, res) => {
-    // req.payer  — the Hive account that paid
-    // req.txId   — the on-chain transaction ID
+    // req.payer  - the Hive account that paid
+    // req.txId   - the on-chain transaction ID
     res.json({ message: "Premium content", payer: req.payer });
   }
 );
@@ -292,8 +292,8 @@ parseHBD("0.050 HBD"); // 0.05
 
 HBD (Hive Backed Dollars) is ideal for micropayments:
 
-- **Zero transaction fees** — unlike EVM chains, Hive transfers cost nothing
-- **~$1 USD peg** — algorithmic stablecoin, no wrapping or bridging needed
-- **3-second finality** — one block confirmation
-- **No gas estimation** — predictable, simple transfers
-- **3-second block time** — fast enough for real-time API access
+- **Zero transaction fees** - unlike EVM chains, Hive transfers cost nothing
+- **~$1 USD peg** - algorithmic stablecoin, no wrapping or bridging needed
+- **3-second finality** - one block confirmation
+- **No gas estimation** - predictable, simple transfers
+- **3-second block time** - fast enough for real-time API access

src/content/docs/ecency/ecency-vs-others.md

@@ -5,7 +5,7 @@ description: Compare Ecency with other Hive frontends like PeakD and Hive.blog.
 
 # Ecency vs Other Hive Frontends
 
-Hive has a rich ecosystem of frontends — apps and websites that let you interact with the blockchain. Ecency is one of the most feature-rich and modern options available, but it’s helpful to understand how it compares to others.
+Hive has a rich ecosystem of frontends - apps and websites that let you interact with the blockchain. Ecency is one of the most feature-rich and modern options available, but it’s helpful to understand how it compares to others.
 
 ---
 
@@ -18,7 +18,7 @@ A **frontend** is an interface that connects to Hive’s decentralized backend.
 - Manage their Hive account
 - Interact with communities
 
-Each frontend uses the same Hive blockchain data — but presents it differently.
+Each frontend uses the same Hive blockchain data - but presents it differently.
 
 ---
 

src/content/docs/ecency/notifications-drafts-bookmarks.md

@@ -58,7 +58,7 @@ Use bookmarks to **save posts** for later reading or reference. You can also boo
 - Great for tutorials, inspiration, or curating
 - Bookmark any post with the 🔖 icon
 - Bookmark or Favorite any author with ❤️ icon and get notified when they publish new content 
-- Bookmarks are **private** — only you can see them
+- Bookmarks are **private** - only you can see them
 
 ### Accessing Bookmarks
 

src/content/docs/ecency/publish.mdx

@@ -35,8 +35,8 @@ You can import an existing blog post or article into the editor instead of start
 
 ### Supported sources
 
-- **Hive posts** — URLs from Ecency, PeakD, Hive.blog, and other Hive front-ends. The original markdown and tags are preserved.
-- **External articles** — URLs from any public website. The article text and images are extracted automatically, and a source attribution is appended at the end.
+- **Hive posts** - URLs from Ecency, PeakD, Hive.blog, and other Hive front-ends. The original markdown and tags are preserved.
+- **External articles** - URLs from any public website. The article text and images are extracted automatically, and a source attribution is appended at the end.
 
 :::caution
 Only import content that you own or have permission to republish.

src/content/docs/ecency/wallets/about.md

@@ -28,7 +28,7 @@ You can view balances, recent transactions, and perform key actions across these
 
 ### External Chain Tokens
 
-Ecency Wallets can generate lightweight wallets for supported blockchains such as **Bitcoin (BTC)**, **Ethereum (ETH)**, **BNB Chain (BNB)**, **Solana (SOL)**, **Aptos (APT)**, **Tron (TRX)**, and **Ton (TON)**. These direct integrations give you full control and self custody, letting you track and transfer cross-chain tokens alongside your Hive assets without leaving Ecency. See the [cross-chain wallet quickstart](/ecency/wallets/cross-chain-wallets/) for setup steps.
+Ecency Wallets support lightweight wallets for blockchains such as **Bitcoin (BTC)**, **Ethereum (ETH)**, **BNB Chain (BNB)**, **Solana (SOL)**, **Aptos (APT)**, **Tron (TRX)**, and **Ton (TON)**. These direct integrations give you full control and self custody, letting you track and transfer cross-chain tokens alongside your Hive assets without leaving Ecency. The cross-chain wallet structure is being upgraded - see [cross-chain wallets](/ecency/wallets/cross-chain-wallets/) for details and the [seed phrase migration guide](/guides/seed-phrase-migration/) if you have funds in a wallet created with a seed phrase.
 
 ---
 
@@ -54,7 +54,7 @@ Convert Hive Power back into liquid HIVE over a 13-week period (weekly payouts).
 - Transfer it to others
 - Use it outside Hive ecosystem
 
-> Be mindful — powering down reduces your voting and RC capacity.
+> Be mindful - powering down reduces your voting and RC capacity.
 
 ---
 
@@ -104,7 +104,7 @@ Transferring HBD into savings earns you 15-20% (subject to governance settings)
 - Always store your **active key** securely (required for transfers).
 - Use **Hive Keychain** or **Ecency mobile app** for safer transactions.
 - Never share your **owner key**.
-- For cross-chain wallets, back up any **seed phrases** shown during address generation.
+- If you have a cross-chain wallet created with a seed phrase, keep the phrase safe until you have [migrated your funds](/guides/seed-phrase-migration/).
 
 ---