Synthetix V3 dismantles the V2x model where all stakers shared a single debt pool, replacing it with an account-centric architecture. In V2x, a user's debt was a proportional claim on a global, volatile liability. V3 introduces an Account as the atomic unit of the system, represented by a non-fungible token (NFT). This NFT is not merely a receipt; it is a permissioned object that owns all positions, collateral, and delegated permissions for a single user, enabling isolated risk and granular control.

Account-Based Position Model and NFT Account Migration
The Paradigm Shift to Account-Centric Architecture
How Synthetix V3 replaces the monolithic debt pool with NFT-based accounts, fundamentally altering position management, collateral segregation, and liquidation logic.
This shift has profound operational consequences. Collateral is no longer pooled globally but is segregated into distinct vaults owned by an account. Each account can delegate management permissions to a separate address, enabling features like cold storage custody with a hot execution wallet. Liquidation logic becomes localized: an undercollateralized position in one vault does not directly socialize losses across all stakers but is contained, with the specific vault's collateral subject to seizure by keeper bots. This requires a complete re-architecture of front-end interfaces, wallets, and keeper bots to understand the new account lifecycle, event schemas, and permissioning model.
For integrators, the migration from a single staking contract to an NFT-based account system is a breaking change. Wallets must now track and manage NFT accounts, exchanges must update their logic to query positions per account rather than per address, and keeper networks must monitor per-vault health factors instead of a single system-wide collateralization ratio. The new AccountCreated, PermissionGranted, and VaultLiquidation events replace the old global debt ledger signals, demanding a full rebuild of indexing pipelines and monitoring dashboards. Teams that fail to adapt their systems to this account-centric model will be unable to interact with the V3 protocol.
Quick Facts: V3 Account Model
Key operational and integration changes introduced by the NFT-based account model in Synthetix V3
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Account representation | Positions are no longer tied to a global debt pool. Each user gets an NFT-based account that holds segregated collateral and positions. | Wallets, front-end providers, indexers | Update UI/UX to display NFT accounts and their associated positions. Rebuild indexing logic to track per-account state instead of global pool state. |
Collateral management | Collateral is assigned to specific accounts, not pooled globally. Each account can have multiple collateral types managed independently. | Custodians, DeFi protocols, treasury managers | Audit collateral assignment flows. Verify that deposit and withdrawal functions interact with the correct account NFT. |
Liquidation logic | Liquidations target individual vaults within an account. There is no socialized loss across the system. | Keeper operators, risk teams | Update liquidation bots to monitor per-vault health factors. Test bot response to new liquidation event schemas. |
Event schemas | Account creation, position modification, and collateral changes emit new event structures incompatible with V2x indexing. | Data teams, analytics providers, subgraph maintainers | Rewrite subgraph handlers and Dune dashboards to parse V3 account and vault events. Validate data integrity against on-chain state. |
Account lifecycle | Accounts are created via a factory, can be transferred as NFTs, and have distinct states. This is a new concept vs. the V2x wallet-to-debt mapping. | Wallet integrators, exchange teams | Implement account creation and transfer flows. Handle edge cases where a user holds multiple account NFTs. |
Composability | Protocols integrating with Synthetix must interact with specific account NFTs, not generic user addresses. | DeFi protocols, aggregators, yield optimizers | Refactor smart contract integrations to accept account token IDs. Test composability paths with mock V3 accounts. |
Migration from V2x | Legacy V2x positions must be migrated to V3 NFT accounts. The migration path is a one-time, coordinated process. | All V2x integrators and stakers | Verify the canonical migration contract address and schedule. Prepare a user communication plan for the migration window. |
From Global Debt to Isolated Accounts
How Synthetix V3 replaces the monolithic debt pool with NFT-based accounts, fundamentally altering position management, collateral segregation, and liquidation logic.
The Synthetix V3 upgrade dismantles the V2x global debt pool, where all stakers shared a single, system-wide liability, and replaces it with an account-centric model built around non-fungible token (NFT) accounts. Each NFT account acts as a self-contained position container, isolating the collateral and debt of its owner. This shift means a user's position is no longer a share of a communal pool but a discrete, programmable object with its own collateral type, debt balance, and risk parameters. The core system contract, CoreProxy, now manages the lifecycle of these accounts, which are created, transferred, and settled as ERC-721 tokens.
Operationally, this change requires a complete re-architecture of all dependent systems. Front-end interfaces and wallets must now track and manage user-specific NFT accounts instead of querying a single global debt register. Keeper bots for liquidations can no longer rely on a global collateralization ratio; they must monitor each vault's specific health factor for individual accounts. The event schemas for position creation, modification, and settlement are entirely new, breaking all V2x subgraphs, Dune dashboards, and proprietary monitoring tools. Integrators must adopt the new AccountCreated, PositionModified, and AccountLiquidated event structures to track on-chain state.
The migration from V2x to V3 is not automatic. Legacy stakers must actively migrate their positions into the new account-based system, a process that involves interacting with migration contracts to convert their share of the global debt pool into a specific, isolated account with a defined collateral vault. This migration window is a critical operational period where teams must coordinate user communication, update their transaction flows, and validate the integrity of migrated positions. Failure to migrate before the V2x shutdown will result in forced settlement of legacy positions, a hard deadline that requires precise execution from all ecosystem participants.
For protocol architects and risk teams, this model introduces a new set of security and economic assumptions. Risk is now siloed per vault, meaning a failure in one collateral market (e.g., a synthetic asset de-pegging) does not automatically socialize losses across all stakers. However, this isolation places greater importance on the correct configuration of each vault's risk module, including issuance fees, caps, and oracle parameters. Chainscore Labs can provide a comprehensive review of account integration patterns, migration tooling, and the new liquidation engine to ensure teams are prepared for the operational and security implications of this fundamental architectural shift.
Affected Systems and Stakeholders
Wallet and Exchange Teams
The shift to NFT-based accounts breaks existing V2x integration assumptions. Front-ends can no longer rely on a single, global debt pool for position display. Instead, they must query the AccountProxy contract to resolve a user's NFT account ID and then fetch positions, collateral, and debt from that specific account's vaults.
Critical Actions:
- Rebuild position display logic to aggregate data per
accountId. - Update transaction construction to include the
accountIdas a parameter for all state-modifying functions. - Implement NFT transfer detection to handle account ownership changes, which may affect user access and session management.
Chainscore can review your integration architecture to ensure compatibility with the new account-centric event schemas and transaction flows.
Integration Impact Areas
The shift to NFT-based accounts fundamentally alters position management, collateral segregation, and liquidation logic. Integrators must assess how these changes ripple through their systems.
Wallet and Front-End Re-architecture
The V3 account model replaces a single, global debt pool with discrete, NFT-represented accounts. Wallets and front-ends can no longer assume a 1:1 user-to-position mapping. Interfaces must be rebuilt to handle account creation, NFT transfer flows, and multi-account management. Transaction construction changes significantly, as users will interact with their specific account token ID rather than a global proxy. Teams should audit their transaction simulation and confirmation UX to prevent users from interacting with the wrong account context.
Keeper Bot and Liquidation Logic Overhaul
Liquidation logic shifts from a socialized, global debt pool to vault-level solvency checks per NFT account. Keeper bots must be re-engineered to monitor individual account health factors, not a single system-wide collateralization ratio. The new engine introduces grace periods and isolated liquidation flows, requiring keepers to manage concurrent liquidation opportunities across many accounts. Bot operators need to implement new event listeners for account-specific solvency signals and update their gas strategies for the new, more granular liquidation transactions.
Event Schema and Indexing Pipeline Breakage
The V3 account system introduces new smart contract events for account creation, transfer, and management, while deprecating V2x global state events. Data teams and subgraph maintainers face a complete re-indexing of on-chain data. Dune dashboards, proprietary monitoring systems, and historical data APIs will break without a migration. Teams must map old event signatures to new ones and re-architect their data models to track positions at the account-token level rather than a global user level.
Composability and Smart Contract Integration Risk
Protocols that integrate with Synthetix, such as yield aggregators or money markets, can no longer assume a user's position is a simple ERC-20 balance. They must now interact with specific NFT account tokens, which introduces new approval flows and potential for locked funds if an account token is transferred. Integrators need to review their smart contract logic for handling deposits and withdrawals into specific accounts and assess the risk of a user's position becoming inaccessible if the linked NFT is moved to a contract that cannot interact with the Synthetix core system.
Collateral Segregation and Risk Isolation
The migration to NFT accounts enables true collateral segregation, where each account's debt is backed by its own specific collateral. This is a critical departure from the V2x shared debt pool, where all stakers bore systemic risk. For risk teams, this means monitoring shifts from a single system-level metric to a distribution of individual account health levels. The systemic risk of a cascading liquidation event is reduced, but the operational burden of monitoring and managing risk across a fragmented set of vaults increases significantly.
User Migration Tooling and State Transition
A migration mechanism will be required to transition user positions from the legacy V2x system into the new NFT-based accounts. The design of this tooling—whether it is a one-time snapshot, a user-initiated claim process, or a gradual transition—carries significant operational and security risks. Integrators must plan for a period of state inconsistency and provide clear user guidance. A flawed migration could result in stuck funds or incorrect debt assignments. Teams should stress-test the migration flow on testnet to validate the integrity of the state transition.
Migration and Compatibility Risks
Operational risks and breaking changes for systems that depend on Synthetix position management as the protocol transitions from the monolithic V2x debt pool to V3's NFT-based account architecture.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Position Representation | Positions move from a global debt ledger to isolated, non-fungible token accounts. Each account holds segregated collateral and specific market exposures. | Wallets, exchanges, portfolio dashboards | Redesign balance queries to track per-NFT positions instead of a single global debt balance. Verify NFT transfer and delegation logic. |
Account Lifecycle | Accounts are minted, transferred, and burned as NFTs. A single user can own multiple accounts, each with independent collateral and risk parameters. | Front-end interfaces, custody providers | Implement full NFT lifecycle support: mint, view, transfer, and burn. Update UI to handle multiple accounts per wallet address. |
Collateral Management | Collateral is deposited directly into a specific NFT account's vault, not a shared pool. Liquidation risk is isolated to the individual account. | DeFi aggregators, yield optimizers, institutional stakers | Update deposit and withdrawal flows to target specific NFT account IDs. Rebuild risk monitoring to track per-account health factors. |
Liquidation Logic | Liquidations target individual vaults within an NFT account. The socialized loss model of V2x is eliminated, changing keeper incentives and event schemas. | Keeper bot operators, risk teams | Rewrite liquidation bots to monitor per-vault health, execute account-specific liquidations, and parse the new liquidation event structure. |
Event Schemas | All position, collateral, and liquidation events are emitted with new signatures and include the NFT account ID as an indexed parameter. | Data indexers, analytics teams, Dune dashboard maintainers | Rebuild subgraphs and indexing pipelines to ingest V3 event schemas. Migrate historical data queries to the new account-centric model. |
Smart Contract Interfaces | Core interfaces for opening, modifying, and closing positions are replaced. V2x proxy contracts will eventually be deprecated. | Composable protocols, arbitrage bots, programmatic traders | Audit all integrations that call Synthetix position management functions. Migrate to V3 router and market contracts before V2x shutdown. |
Cross-Chain Position Portability | NFT accounts can potentially be represented or bridged across V3 deployments, introducing new trust assumptions for cross-chain state. | Bridge operators, cross-chain application developers | Verify the canonical account state on each chain. Do not assume an NFT account on one chain is valid on another without official bridge verification. |
Migration Tooling | A migration contract or interface will facilitate moving legacy V2x positions into V3 NFT accounts. This is a one-way, irreversible process. | All V2x stakers and integrators | Test the migration flow on testnet. Validate that migrated positions reflect correct debt and collateral. Plan for a coordinated migration window. |
Integration Readiness Checklist
A practical checklist for wallet teams, exchange integrators, front-end providers, and keeper operators preparing for the V3 account-based position model and NFT account migration. Each item identifies a critical change, why it matters, and what signal confirms readiness.
What to check: Confirm that your system can handle the full lifecycle of an NFT-based account, including minting (account creation), transferring, and burning.
Why it matters: In V3, every position is owned by an NFT, not a monolithic debt pool. Wallets and front-ends must display these NFTs correctly, and any transfer logic must account for the fact that moving the NFT moves the associated positions and collateral.
Readiness signal: Successful integration test on a V3 testnet (e.g., OP Sepolia) where your system can create an account NFT, display it in a wallet UI, and transfer it to another address, with all associated positions moving atomically.
Canonical Resources
Use these sources to validate Synthetix V3 account behavior, NFT account ownership, migration assumptions, contract interfaces, and governance-controlled parameters before updating production integrations.
Integration Review Checklist
Before production rollout, create a chain-specific checklist covering account NFT minting, account transfer handling, delegated permissions, collateral deposit and withdrawal paths, vault assignment, liquidation monitoring, event indexing, and migration rollback procedures. Wallets should clearly display whether the connected address owns the account NFT or only has delegated authority. Exchanges, custodians, and bots should test account transfers and permission revocation as first-class failure modes, not edge cases. Chainscore Labs can review these assumptions against the current V3 contracts and governance state.
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos

Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
Frequently Asked Questions
Common questions from integrators, wallet teams, and bot operators about the shift to NFT-based accounts and the new position management model in Synthetix V3.
In V3, each user's positions are held within a unique NFT account rather than a single monolithic debt pool. This means:
- Collateral Segregation: Each NFT account can hold multiple collateral types, and risk is isolated per account. A liquidation in one account does not socialize losses across all users.
- Permissioned Access: The NFT owner can delegate management permissions to other addresses, enabling third-party managers or automated strategies without custody transfer.
- Transferability: The entire account, including its positions and debt, can be transferred by transferring the NFT. This is a fundamental shift from V2x where positions were tied to an EOA.
Integrators must update their UIs to display positions at the account level, not the wallet level, and support NFT transfer flows.
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.


