NFT Royalty Tracking in Bitget Wallet: Why Creators Can’t See Secondary Sales Revenue

A digital artist mints a limited-edition NFT collection on Ethereum, setting a 10% creator royalty at the smart contract level. The initial sale goes smoothly through a marketplace, and the artist receives their share. Months later, secondary sales occur—collectors trade the pieces on OpenSea, Blur, and other platforms. Yet when the artist checks their portfolio in Bitget Wallet, they see the NFTs they created listed in their collection, but no clear accounting of royalty income from those secondary trades. The wallet shows holdings and transaction history, but the aggregation of creator revenue across multiple marketplaces remains invisible. This gap between what the blockchain records and what a wallet displays creates a practical problem for any artist depending on royalty income as part of their business model.

The issue is not that royalties are lost—they still settle on-chain when marketplaces honor the smart contract terms. The problem is visibility and reconciliation. A creator using Bitget Wallet as their primary asset management tool cannot easily monitor whether royalties are being paid, by which platforms, in what amounts, or whether secondary sales are occurring at all. Most NFT wallets, including those with marketplace integration, treat NFTs primarily as collectible holdings rather than as revenue-generating assets whose secondary performance matters to creators. The result is a blind spot in portfolio management that affects anyone whose income depends on understanding the full lifecycle of their digital assets.

The gap between on-chain royalty enforcement and wallet visibility

Royalties in the NFT space are enforced through smart contract code on the blockchain itself. When a creator deploys an NFT collection, they can set a royalty percentage—typically between 5% and 10%—that the smart contract automatically directs to a designated wallet address whenever the NFT changes hands. This mechanism is transparent and verifiable on-chain; every secondary sale is recorded, and the royalty payment is part of the transaction ledger. However, a wallet’s job is not to replicate the full blockchain state in its interface. Instead, wallets aggregate and summarize information to help users understand their assets quickly.

The distinction matters because it reveals why creator royalty tracking is absent from most NFT wallet designs, including Bitget Wallet’s marketplace features. The wallet displays which NFTs an address holds, their current market value, floor prices, and transaction history. These summaries require indexing data that is already organized for display—holdings are easy to compute from the state of the blockchain, and floor prices are queries to marketplace APIs. Royalty income, by contrast, requires tracking payments sent to a specific address across multiple marketplaces, interpreting which payments correspond to secondary sales of a creator’s collection versus other transactions, and associating those payments back to the original NFTs. The required data architecture is fundamentally different.

When a creator sells an NFT through OpenSea, the royalty may arrive as a separate transfer from the marketplace’s treasury contract or from an auction contract. When the same NFT is sold on Blur, Rarible, or a niche marketplace, the royalty protocol may differ. Some platforms honor royalties by default; others treat them as optional. Some newer platforms have moved away from enforcing on-chain royalties in favor of off-chain agreements. The wallet cannot meaningfully aggregate this without either building partnerships with every major marketplace to receive royalty event data, or implementing its own indexing service that scans the blockchain for all incoming transfers to the creator and attempts to classify them—a computationally expensive and error-prone task.

Bitget Wallet’s integration focuses on the marketplace-facing features that benefit both buyers and sellers: NFT discovery, purchasing directly through the wallet, gallery views, and floor price monitoring. These capabilities are valuable for the buying side and for creators who want to manage their collection within a single interface. However, they do not extend to post-sale tracking of creator income. The wallet remains an asset management tool rather than a business accounting system.

Why secondary sales visibility matters to creators

For many digital artists, royalties are not a passive bonus—they are a primary income stream. Unlike physical art, where the artist has no recourse after the initial sale, NFT royalties create a direct financial stake in the long-term trading activity of a collection. An artist might mint 100 pieces, sell 50 immediately at 2 Ethereum each, earning 100 ETH. If those pieces then trade actively among collectors at higher prices, the royalties accumulate. Over a year, secondary trading might generate 50 ETH in additional income. Losing visibility into that income stream means the artist cannot track revenue for tax purposes, cannot verify whether marketplaces are honoring the smart contract terms, and cannot assess which collections are generating ongoing returns.

Tax reporting is a concrete example of why this matters. In many jurisdictions, creator royalties are treated as ordinary income and must be reported to tax authorities. The artist needs to know the total amount received, the dates of transactions, the sources, and ideally the correlation to the underlying NFTs. A wallet that shows NFT holdings but not royalty flows makes tax compliance harder. The artist must either manually track royalty payments outside the wallet, or export transaction history and attempt to filter for the relevant transfers—a time-consuming and error-prone process.

Verification of marketplace behavior is the second concern. Smart contracts enforce royalties on-chain, but not all marketplaces use the same contract standard or honor royalties consistently. Some platforms have deprecated on-chain royalty enforcement in favor of optional off-chain models. A creator needs to know whether their royalties are actually being paid and by which platforms. Without wallet-level visibility, the creator must visit each marketplace separately, search for transaction history, and reconcile payments. If a marketplace is not honoring royalties, the creator might not notice until significant trading volume has already occurred.

Portfolio evaluation is the third reason. A creator assessing the performance of their NFT collections wants to know not just current floor price but total secondary trading volume and cumulative royalties. This information helps them decide whether to invest in additional artwork, retire underperforming collections, or market specific pieces more aggressively. A creator dashboard that displayed active buyers, recent trades, and accumulated royalties would be directly useful. Bitget Wallet’s current integration provides floor price monitoring and market data, but without the royalty component, the performance picture is incomplete.

The architectural challenge of cross-marketplace royalty aggregation

Building royalty tracking would require Bitget Wallet to solve several technical problems simultaneously. First, it must identify which addresses are creator wallets. The wallet already supports importing or creating addresses, but there is no explicit “creator mode” that flags an address as one that should track royalties. Adding such a mode would be a simple interface change, but it would inform a much larger data processing requirement.

Second, the wallet would need to continuously monitor blockchain transfers to the creator address and classify them as royalty payments. This is computationally expensive and requires sophisticated heuristics. A transfer from an address associated with OpenSea might be classified as a royalty, but how can the wallet determine which NFT the royalty corresponds to without additional data? An on-chain marketplace contract may emit events when royalties are paid, but not all contracts follow the same event standard. The wallet would need to either subscribe to event logs from every marketplace’s contract (requiring partnerships), or run its own indexing service that stores transaction history and attempts to infer the source based on contract addresses and transaction patterns.

Third, the wallet would need to link royalty payments back to specific NFTs in the creator’s collection. This requires knowing which NFTs the creator originally minted, which is straightforward if the creator deployed the contract themselves, but becomes harder if they minted on a platform’s shared contract. Once the link is established, the wallet must track not just that a royalty was received, but which specific edition or token ID generated it, in order to provide meaningful analytics.

Fourth, the wallet must handle the reality that royalty protocols vary by blockchain and marketplace. Ethereum has become the standard for on-chain royalties, but implementations differ. Solana and other blockchains have their own royalty specifications. Some newer marketplaces use token-gated or off-chain royalty systems. Building a truly cross-chain, cross-marketplace royalty aggregator would require supporting multiple standards and updating constantly as new ones emerge.

The Bitget Wallet extension already manages assets across 90+ blockchains, which demonstrates considerable infrastructure. However, adding creator-focused royalty tracking would require a different type of infrastructure—one that stores historical data, indexes marketplace events, and maintains mapping databases. This is a shift from being a stateless asset viewer to being a stateful data indexer, with corresponding increases in server costs, maintenance burden, and potential privacy implications.

Current workarounds and their limitations

Creators currently rely on several workarounds, none of which fully solve the problem. The first is marketplace-specific dashboards. OpenSea, for example, provides creator dashboards that show collection statistics, recent sales, and royalty earnings. The creator can visit each marketplace where their NFTs trade and manually check earnings. This approach works but is labor-intensive, especially for artists whose work is listed on dozens of platforms. Information is fragmented across multiple dashboards, and there is no single source of truth.

The second workaround is third-party analytics services. Websites like Rarity Tools, DeFi Pulse, and specialized NFT analytics platforms attempt to aggregate marketplace data and provide dashboards. Some of these services offer creator-specific views or royalty tracking features. However, they require the creator to sign up for an additional service, share wallet information, and trust the third party to maintain accurate data. These services often have limited marketplace coverage and may lag in updating real-time sales data.

The third workaround is manual blockchain inspection. A creator can export their wallet’s transaction history, filter for incoming transfers, and manually classify which ones are royalties. They can examine transactions on block explorers to identify sources and amounts. This approach is precise but extremely time-consuming and impractical for ongoing monitoring. It also requires technical knowledge that not all creators possess.

The fourth workaround is off-chain record-keeping. The creator manually logs royalty payments as they receive them, maintaining a spreadsheet or accounting software alongside their wallet. This approach works for tax reporting but adds administrative overhead and is prone to errors, especially when sales occur across multiple time zones and marketplaces are not synchronized.

Why wallets have not yet built this feature

The absence of NFT royalty tracking in major wallets reflects several converging factors. The first is that royalty compliance is not a wallet problem—it is a marketplace problem. The wallet’s job is to display what the user owns and to facilitate transactions. Whether marketplaces honor royalties is a question of marketplace contract design and enforcement, not wallet functionality. A wallet cannot make a marketplace pay royalties it is not configured to pay; the wallet can only display the results of what marketplaces do.

The second factor is economics. Building a royalty tracking feature would require significant development investment, server infrastructure, and ongoing maintenance. The benefit accrues primarily to creators—a subset of wallet users—rather than the broader user base. Most wallet users are traders or hodlers who care about portfolio value, not creators concerned with income tracking. From a business perspective, the return on investment is lower for a creator-focused feature than for features that benefit the majority of users.

The third factor is regulatory uncertainty. If a wallet begins aggregating financial data on behalf of creators—showing income, tracking balances, and providing reports—it may be viewed as offering accounting or financial advisory services. This could trigger licensing requirements or regulatory scrutiny in some jurisdictions. Staying focused on custody and asset management is safer legally and operationally.

The fourth factor is data accuracy challenges. Royalty tracking depends on correctly classifying transfers and maintaining fresh data. If the wallet shows a royalty amount that is incorrect due to indexing delays or classification errors, the creator might make business decisions based on false information. The liability for inaccuracy, and the effort required to get it right, are significant disincentives.

What a creator-focused NFT wallet would require

A wallet that genuinely served creators would need to go beyond merely displaying holdings. It would need a dedicated creator dashboard showing cumulative royalties received, broken down by collection, platform, and time period. This dashboard would require real-time or near-real-time data on secondary sales, pulling information from marketplace APIs, event logs, or both. The dashboard would include a royalty calculator that tracks total income against minting and transaction costs, providing a clear picture of net earnings.

The wallet would also need royalty alerts—notifications when secondary sales of the creator’s NFTs occur, along with the sale price and royalty amount. This would give creators immediate visibility into market activity rather than requiring them to manually check. The wallet could provide analytics on which pieces are trading most actively, which platforms are driving volume, and where the most active collectors are located geographically.

Transaction reporting for tax purposes would be essential. The wallet should allow creators to export royalty income in formats suitable for tax software or accountants—CSV files, PDF reports, or API access to the underlying data. It should clearly distinguish between royalty income, sales proceeds, and other transfers so that creators can correctly categorize transactions for reporting.

Integration with marketplace APIs would be necessary. Rather than the wallet attempting to infer which transfers are royalties by analyzing on-chain data, it could negotiate direct feeds from major marketplaces. This would require partnerships and likely some revenue sharing or sponsorship, but it would ensure accuracy and timeliness. A creator-focused wallet might position itself as a business tool rather than a consumer wallet, justifying the investment in these integrations.

The broader implication for NFT adoption as income assets

The gap between Bitget Wallet’s current capabilities and what creators need reflects a broader truth about the NFT ecosystem: most infrastructure is built for traders and collectors, not for creators earning income. This bias shapes what gets built, what gets funded, and ultimately what creators can realistically do with NFTs. A creator who cannot easily track their royalty income faces friction that a traditional artist selling through a gallery does not. A gallery provides invoices, payment records, and clear accounting. The blockchain provides a transparent ledger, but wallets have not yet translated that transparency into usable business tools.

As the NFT market matures, this gap may close. Creators are a powerful constituency—they control supply and shape community sentiment. A wallet that caters directly to creators, with built-in royalty tracking, business analytics, and tax reporting, could differentiate itself and attract both creators and the collectors who follow them. The technical challenges are significant but not insurmountable. The more fundamental question is whether the wallet industry sees creator income tracking as a feature worth building or an edge case outside the wallet’s scope.

For now, creators using Bitget Wallet or any similar NFT wallet should treat it as a portfolio management and transaction execution tool, not as a business accounting system. The wallet will show what NFTs are held and at what current value. But understanding secondary sales performance and tracking royalty income requires looking outside the wallet to marketplace dashboards, analytics services, or manual record-keeping. Until NFT marketplace data is properly aggregated at the wallet level, creators cannot rely on a single interface to manage their complete financial picture. The feature gap is not a minor oversight—it is a structural limitation that affects how creators can operate as independent businesses in the digital asset space.