Cross-Chain NFT Portfolio: Three NFT Models, One View (2026)
Cross-Chain NFT Portfolio: Three NFT Models, One View (2026)
Reviewed by Wag3s Editorial Team — verified against the three distinct NFT models (EVM ERC-721/1155, Solana Metaplex/cNFT, Bitcoin Ordinals) and their incompatible discovery/identity · Last reviewed May 2026
Cross-Chain NFT Portfolio: Three NFT Models, One View
"NFT" is a single word for three unrelated machines: a contract+tokenId on EVM, a Merkle-tree entry behind an indexer on Solana, an inscribed satoshi in a UTXO on Bitcoin. A portfolio that assumes one model silently drops the other two. This guide is the cross-model NFT problem.
TL;DR
- Three incompatible models: EVM (contract + tokenId, ERC-721/1155), Solana (Metaplex account / cNFT via indexer), Bitcoin (inscribed sat / UTXO).
- No shared identifier — each NFT keeps its native identity; don't flatten to one ID scheme.
- Aggregation is a discovery + identity problem, not a multi-marketplace feed.
- Loss happens at discovery gaps — missed cNFTs, Ordinals read with a token model, NFTs on less-common chains.
- Each model needs its own discovery method — one method can't cover all three.
- Tax is per item, per jurisdiction, unchanged by chain — aggregation just supplies the complete, correctly-identified set.
Three machines, one word
| Model | An NFT is… | Discovery |
|---|---|---|
| EVM (ERC-721/1155) | A contract address + tokenId | Contract/tokenId enumeration across chains held |
| Solana (Metaplex) | A mint account, or a cNFT Merkle entry | Account read + indexer for compressed |
| Bitcoin (Ordinals) | Content inscribed on a numbered sat | Ordinal-aware UTXO tracing |
These are not variants of one thing. A tracker built on the EVM contract+tokenId assumption is structurally blind to Solana cNFTs and Bitcoin Ordinals — the NFT analogue of the non-EVM aggregation problem.
The identity problem
Each model identifies an NFT differently — contract+tokenId (EVM), mint / cNFT asset id via indexer (Solana), inscription on a numbered sat (Bitcoin). There is no shared identifier. A cross-chain view must hold each NFT's native identity, not force one scheme. Collapsing them to a single ID format loses provenance and can merge or drop distinct NFTs — a silent correctness failure, not a display nit.
Where assets vanish
Cross-chain NFT portfolios lose assets at discovery gaps:
- compressed Solana NFTs missed (no indexer used);
- Ordinals missed (tool used a token-contract model on Bitcoin);
- EVM NFTs missed on less-common chains.
It is a completeness failure, amplified by model heterogeneity — the same root cause as multi-chain reconciliation, specific to NFTs.
One discovery method cannot work
Each model needs its own discovery:
- EVM → contract/tokenId enumeration across every chain held;
- Solana → account reads (uncompressed) + indexer (compressed);
- Bitcoin → ordinal-aware UTXO tracing.
A complete NFT portfolio runs the right discovery per model and then unifies the results without flattening their native identities.
Tax is per item, per jurisdiction
Tax does not change by which chain an NFT lives on: each NFT is still its own lot with its own basis and disposal (see NFT cost basis and disposal). The aggregation layer's job is a complete, correctly-identified set so the jurisdiction-specific treatment applies to the right items. The chains differ; the per-item tax discipline does not.
Practical guidance
- Run model-specific discovery — EVM contract/tokenId, Solana account+indexer, Bitcoin ordinal-aware.
- Preserve each NFT's native identity — don't flatten to one ID scheme.
- Treat discovery gaps as completeness failures (cNFTs, Ordinals, rare chains).
- Unify into one view without merging distinct NFTs.
- Keep per-item lots for tax across all models; confirm jurisdiction treatment.
- Reconcile each model to its chain with an audit trail.
How vendor tools handle cross-chain NFTs
Koinly and Zerion aggregate NFTs across chains to varying depth. Confirm the tool runs model-specific discovery (EVM/Solana-incl-cNFT/Bitcoin-Ordinals), preserves native identities, and treats missing cNFTs/Ordinals as completeness gaps — an EVM-only NFT model silently drops two of the three worlds.
How Wag3s helps
Wag3s Folio runs model-specific NFT discovery — EVM contract/tokenId, Solana account plus cNFT indexer, Bitcoin ordinal-aware UTXO — unifies them into one view without flattening native identities, and keeps per-item lots for the jurisdiction-specific tax treatment. See the Folio product page.
Further reading
- Bitcoin Ordinals Portfolio Tracking
- Solana NFT & Compressed cNFT Tracking
- NFT Portfolio Valuation
- NFT Cost Basis and Disposal Tracking
- Multi-Chain Portfolio Aggregation Beyond EVM
- Multi-Chain Reconciliation
Sources
- Three distinct NFT models: EVM ERC-721/1155 (contract + tokenId); Solana Metaplex account / compressed NFT via indexer; Bitcoin Ordinals (inscribed sat tracked via UTXOs)
- No shared cross-model identifier — native identity must be preserved; discovery is model-specific
- Completeness failures from model heterogeneity (missed cNFTs/Ordinals); per-item, jurisdiction-specific tax unchanged by chain
Wag3s vs Cryptio: two different bets on Web3 accounting
Cryptio is the incumbent for enterprise Web3 accounting. Wag3s is the newer challenger built for the full stack. Here's where they differ in practice.
Watch-Only Portfolio Tracking: Full Visibility Without the Keys (2026)
A watch-only setup monitors balances and history with no private key in reach — a public address, a read-only exchange API key, or a Bitcoin xpub/zpub that derives every address of an HD wallet. Why watch-only is the correct default for tracking, and the xpub completeness-vs-privacy trade.
Every chain, integration, and competitor mentioned in this article gets its own page — coverage detail, comparison signals, and the audit trail your finance team needs.
- Chain
Bitcoin
UTXO-aware cost basis, Lightning, Ordinals, BRC-20.
View page - Chain
Solana
SPL tokens, native stake, Jupiter, Metaplex NFTs.
View page - Chain
Ethereum
ERC-20, DeFi, gas, restaking — the largest ecosystem.
View page - Integration
NetSuite integration
Mid-market and enterprise crypto subledger.
View page - Integration
QuickBooks integration
SMB GL with daily JE sync.
View page - Integration
Safe integration
DAO and corporate multi-sig accounting.
View page