Wrapped Native Tokens: Deposits, Withdrawals and Transfers
Model wrapped-native-token activity separately from native currency, preserving deposit and withdrawal evidence without double-counting conversions.
Overview
When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.
A wrapped native token is a contract representation of a network currency under that contract’s rules. Its token balance and the wallet’s native balance remain separate technical holdings.
Keep both asset identities
Wrapping usually exchanges native currency for token units, while unwrapping reverses that relationship. Do not merge the contract token with native currency before recording the underlying movements. Deposit and withdrawal events can have contract-specific interfaces, and ordinary Transfer events may not alone explain every conversion path.
Worked example: wrapping one unit
A wallet sends one native unit to a wrapper and receives one token unit in a simplified one-to-one design. It also pays a network fee. The result is a native decrease greater than one and a token increase of one. Treat the conversion as linked movements rather than an external income event inferred from the token inflow.
Validate the specific wrapper
Confirm the contract identity, units and redemption mechanism. Test deposits through another contract, withdrawal recipients and reverted operations. Keep transaction fees separate. An optional portfolio view may group economic exposure, but it should still let a reviewer expand the total into native and wrapped holdings with their original evidence and quantities.
A practical acceptance test
Model a one-unit wrap with a separate native execution fee. Assert a linked native decrease and wrapped-token increase, preserving both technical identities. An optional exposure-grouping view can combine their economic presentation without duplicating the underlying claim. A failed wrap should retain the fee outcome where applicable but must not create the expected wrapped holding.
Questions about the topic
Frequently asked questions
Are native and wrapped balances the same state field?
No. They belong to different technical assets.
Does every wrapper guarantee identical redemption rules?
No. Verify the particular contract and its operating assumptions.
Standards & technical documentation