Гаманець для Magpie

What is Magpie (MGP)?

Magpie sits on top of protocols that use vote-escrow tokenomics - the Curve-style model where a governance token has to be locked for a fixed term to carry voting weight. Instead of every user locking tokens themselves, Magpie pools them, does the locking centrally through its own contracts, and uses the resulting voting power on behalf of the pool. MGP is the token of that layer: it carries governance weight over how Magpie directs the votes it controls.

What a holder should know

MGP is not a single-chain token. It was launched on BNB Smart Chain, where Magpie started with Wombat Exchange, and it also exists on Arbitrum, where the Magpie family expanded to other vote-escrow protocols. The balances are separate. A transfer sent out on one chain does not appear on the other, and the two are bridged, not mirrored.

There is also a family resemblance to watch. Magpie's sub-protocols each issue their own token, and they all sound alike. MGP is the base token of the Magpie ecosystem; the others belong to individual integrations and are not interchangeable with it, even though they appear side by side in the same interfaces.

Supported networks in Tangem (2): Arbitrum One, BNB Smart Chain.

Because MGP exists in two places, Tangem keeps a distinct balance for each network and names the network on the transaction screen before the card signs - worth a glance, since an EVM address looks identical on both and only the sender knows which chain the recipient is watching. Holding MGP across chains is simply easier when each side is shown separately rather than added together.