# dHEDGE → Chamber Chamber is the next chapter of **dHEDGE**. Same team, same core contracts, same DAO. The rebrand reflects a sharper focus on what the protocol has become good at: bounded, programmable vaults that safely host human, automated, and AI-led trading. If you're a current dHEDGE user — manager or depositor — nothing urgent changes. Your vault, your shares, your fees, and your DHT balance all carry through. ## What stays the same * **Existing vaults.** Every live dHEDGE vault continues to operate under Chamber. Same address, same holdings, same manager. * **Vault shares.** Shares (vault receipt tokens) are unchanged. No migration required. * **DHT token.** The DHT token is unchanged — same contract, same supply. See [DHT (legacy)](/governance-and-token/dht-legacy.md) for its current role. * **The DAO.** Same DAO, same proposals. Voting is by wallet DHT balance on Snapshot — see [Governance](/governance-and-token/overview.md). DHT staking and vDHT are discontinued; see [Legacy staking](/governance-and-token/dht-staking.md) for context. * **Treasury.** Same onchain treasury, ongoing buybacks. See [Treasury](/treasury-and-protocol-economics/overview.md). * **Toros Finance.** Toros remains the ecosystem's leveraged-token brand and continues to operate as before — see [Ecosystem → Toros Finance](/ecosystem/toros-finance.md). * **mStable and Flat Money.** Both remain live under the Chamber ecosystem umbrella. * **Guard System.** Same contract-level enforcement as dHEDGE's v2 vaults. * **All audits, fee limits, and onchain mechanics.** In short: if it's onchain, it's unchanged. ## What's changed Mostly framing, not mechanics. * **The name.** dHEDGE → Chamber. Domains, branding, and marketing pivot to Chamber. * **Hero positioning.** Chamber's public message leads with **AI-assisted and automated management** — not just human-run vaults. The [Chamber MCP server](/manage/ai-assisted-management.md) is front-and-centre. * **App URL.** The app is moving to [**chamberfi.com**](https://chamberfi.com/). The existing `dhedge.org` URL will redirect to the new domain. ## What depositors need to do **Nothing.** Your existing position on dHEDGE is an existing position on Chamber. Log in to the new app, see the same vaults, same shares, same balance. Withdrawals and deposits work exactly as before. ## What managers need to do **Nothing urgent.** Your existing vault is your existing vault. Fees, assets, traders, and settings all carry through unchanged. A few things worth refreshing: * **Strategy description on your vault page.** If you wrote it under the dHEDGE branding, you may want to update any mentions to Chamber. * **Referral links.** Links generated under dHEDGE continue to work. If you distribute them widely, the underlying URL will update to a Chamber domain — existing links redirect. See the [Manager playbook](/manage/manager-playbook.md) for post-rebrand manager guidance. ## What builders need to do **Very little.** Contract addresses are unchanged. The [subgraph](/build/subgraph.md), [SDK](/build/sdk.md), and [Data API](/build/data-api.md) continue to work. If you're deploying fresh integrations, use the Chamber-branded entry points where they exist — they point at the same underlying infrastructure. ## Why rebrand at all Two reasons, both practical: 1. **The product has evolved.** dHEDGE started as a general-purpose onchain asset management protocol. Chamber's current strength — bounded vaults that safely host AI and automated trading — is a specific, narrower, more useful positioning. 2. **AI trading is the wedge.** The MCP server, Trader delegation, and Guard System together make Chamber one of the first vault platforms that can safely host agent-led capital. Leading with that is honest to what Chamber now is. None of this is a new protocol. It's the same vault infrastructure, given a name that matches what it does. ## Related * [What is Chamber](/introduction/what-is-chamber.md) * [Governance](/governance-and-token/overview.md) * [Treasury](/treasury-and-protocol-economics/overview.md) * [Ecosystem](/ecosystem/overview.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.chamberfi.com/introduction/dhedge-to-chamber.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.