<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Token Airdrop on Fatsale</title><link>https://docs.fatsale.org/docs/airdrop/</link><description>Recent content in Token Airdrop on Fatsale</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><atom:link href="https://docs.fatsale.org/docs/airdrop/index.xml" rel="self" type="application/rss+xml"/><item><title>Contract Mapping</title><link>https://docs.fatsale.org/docs/airdrop/mapping/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.fatsale.org/docs/airdrop/mapping/</guid><description>Introduction # During a project’s lifecycle, a team may need to replace its token contract. Because deployed blockchain contracts cannot be modified, the usual approach is token mapping: users exchange the old token for the new token at a configured ratio.
For example, Soca, which became popular in 2022, migrated from a high-tax contract to a zero-tax contract at a 1:1 ratio before listing on a centralized exchange.
1. Create a Mapping Contract # Select Contract Mapping as the airdrop type.</description></item></channel></rss>