Try sending some ethereum to your wrapped Tari address. Sending it out of Phantom it states that the transaction fails, but the Ethereum makes it to the desired wallet. Most Ethereum tokens simply go by the primary Ethereum address don’t they? I don’t know haven’t traded any tokens on ethereum in over a year but I seem to recall that they all receive at the primary Ethereum address don’t they? OTOH, my wXTM (already present in wallet, shows a receiving address) address is not the same as the Ethereum address. Phantom wallet got all flustered and couldn’t handle it. But it still went thru.
You can find the addresses on the trans history(etherscan). Tari on chain trans is private.
Small clarification from the address-format side (I built a pure-Python Tari address toolkit, GhostKey, for this month’s contest):
Tari addresses are not Ethereum addresses — that’s why Phantom got confused. A mainnet Tari address is 35 bytes: 1 network byte, 1 feature-flags byte, then a 32-byte view key + 32-byte spend key compressed via ristretto255, plus a DammSum checksum. The 14DY79… / 14Ch… style base58 strings you see in wallets are that structure encoded — and wXTM bridging gives you an Ethereum-side address that is a completely different namespace.
If you ever want to check what a Tari address actually contains before trusting it:
python ghostkey.py inspect <address>
It decodes network, feature flags and both public keys, and verifies the checksum — fully offline, zero dependencies. Repo: GitHub - Alex20Sas12/ghostkey: 👻 GhostKey — zero-dependency pure-Python Tari address toolkit: RFC 9496 ristretto255, DammSum, base58/emoji encodings, offline keygen, vanity ghost mining. Tari October Build Contest 2026. · GitHub (MIT).
That seems pretty great. I didn’t try it yet but A ghost and a pumpkin. Very timely.