<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Token Registration on Bitsy Wiki</title>
    <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/</link>
    <description>Recent content in Token Registration on Bitsy Wiki</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://wiki.bitsy.services/wiki/economics/defi/token-registration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Making the Icon</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/icon/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/icon/</guid>
      <description>&lt;p&gt;A token icon is displayed at 20 to 24 pixels in a wallet balance row, which is the size at which it does its actual work. Everything else — the 256-pixel version in the repository, the 512-pixel version on the project page — is a downscale target. Design for the 20-pixel render, then produce the eight files the registrars ask for from one vector source.&lt;/p&gt;&#xA;&lt;h2 id=&#34;constraints-that-come-from-the-render-size&#34;&gt;Constraints that come from the render size&lt;a class=&#34;anchor&#34; href=&#34;#constraints-that-come-from-the-render-size&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;One mark, no wordmark.&lt;/strong&gt; The symbol is already printed next to the icon in every interface that shows it. Lettering inside a 20-pixel square is four or five pixels tall and resolves to a smear.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Stroke weight at or above 6% of the canvas.&lt;/strong&gt; A 256-pixel canvas wants strokes of 16 pixels or more, which land at about 1.25 pixels in a 20-pixel row; below about 13 pixels the downscale drops them under one pixel and the antialiaser turns them into grey haze.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Two colors, high contrast.&lt;/strong&gt; Gradients average out at small sizes, so a gradient icon renders as its mean color and stops being distinguishable from every other icon whose mean is a similar blue.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Give the mark its own disc.&lt;/strong&gt; Surfaces disagree about their background: Etherscan is light, most wallets default to dark, and a transparent icon that is pure black or pure white vanishes on one of them. A filled circle behind the mark makes the icon background-independent and also survives the circular cropping several wallets apply.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Keep the mark inside 80% of the canvas.&lt;/strong&gt; Interfaces that crop to a circle cut the corners off a square icon, and MetaMask&amp;rsquo;s icon style guide asks for artwork &amp;ldquo;within 80% of the canvas&amp;rdquo;. The background disc is not artwork in that sense; the mark on it is.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;the-source-file&#34;&gt;The source file&lt;a class=&#34;anchor&#34; href=&#34;#the-source-file&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Author in SVG and rasterize from it. A hand-drawn 256-pixel bitmap cannot produce a clean 32-pixel version, but the reverse works every time.&lt;/p&gt;</description>
    </item>
    <item>
      <title>On-Chain Metadata</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/on-chain-metadata/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/on-chain-metadata/</guid>
      <description>&lt;p&gt;Two mechanisms let a token carry its own icon without a company&amp;rsquo;s approval: a metadata document referenced from the contract, and a wallet method your interface can call to push the icon at the user directly. Neither needs a form, a fee, or a queue, and both work in the same block the contract is deployed in.&lt;/p&gt;&#xA;&lt;h2 id=&#34;erc-1046-a-tokenuri-on-a-fungible-token&#34;&gt;ERC-1046: a &lt;code&gt;tokenURI&lt;/code&gt; on a fungible token&lt;a class=&#34;anchor&#34; href=&#34;#erc-1046-a-tokenuri-on-a-fungible-token&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/ethereum/eip&#34;&gt;ERC&lt;/a&gt;-1046 is Final, and adds one function to &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/ethereum/erc-20&#34;&gt;ERC-20&lt;/a&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Token Lists</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/token-lists/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/token-lists/</guid>
      <description>&lt;p&gt;A token list is a JSON document that maps chain identifier and contract address to a name, symbol, decimals count and logo URL. It is the only registration route where you are the publisher rather than the applicant: you write the file, you host it, and a user adds it to their interface by pasting a URL. Uniswap wrote the specification in 2020 and most swap interfaces and several wallets read the format.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Block Explorers</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/block-explorers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/block-explorers/</guid>
      <description>&lt;p&gt;A block explorer&amp;rsquo;s token page is the first result when anyone searches a contract address, and its logo, description and links come from the explorer&amp;rsquo;s own database, not the chain. Two explorer families cover most EVM chains — Ethereum Virtual Machine chains — and each has its own page here:&lt;/p&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;&lt;/th&gt;&#xA;          &lt;th&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/etherscan&#34;&gt;Etherscan&lt;/a&gt; family&lt;/th&gt;&#xA;          &lt;th&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/blockscout&#34;&gt;Blockscout&lt;/a&gt;&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Covers&lt;/td&gt;&#xA;          &lt;td&gt;Etherscan, Basescan, Arbiscan, Polygonscan, BscScan, OP Mainnet&amp;rsquo;s Etherscan, and the rest of the thirty-odd explorers Etherscan lists&lt;/td&gt;&#xA;          &lt;td&gt;Blockscout-hosted instances, including Ethereum, Base, Arbitrum One, OP Mainnet and Polygon&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Channel&lt;/td&gt;&#xA;          &lt;td&gt;Token Update Application Form, one per explorer&lt;/td&gt;&#xA;          &lt;td&gt;token info application form, one per instance&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Prerequisites&lt;/td&gt;&#xA;          &lt;td&gt;verified source, then a signed ownership proof&lt;/td&gt;&#xA;          &lt;td&gt;verified source, then a signed ownership proof&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Who may sign&lt;/td&gt;&#xA;          &lt;td&gt;the creator Etherscan displays; its one readable article on factory deployments sends them to support&lt;/td&gt;&#xA;          &lt;td&gt;creator or &lt;code&gt;owner()&lt;/code&gt;; the web front end also offers the sender of a factory deployment, backend unconfirmed&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Logo&lt;/td&gt;&#xA;          &lt;td&gt;a link to a 32 × 32 SVG or 64 × 64 PNG&lt;/td&gt;&#xA;          &lt;td&gt;a link to an SVG or a 48 × 48 PNG&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Cost&lt;/td&gt;&#xA;          &lt;td&gt;free; paid priority support, price shown after submitting&lt;/td&gt;&#xA;          &lt;td&gt;free; 99 USDC or USDT for a decision within seven days&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;Reads aggregators&lt;/td&gt;&#xA;          &lt;td&gt;CoinMarketCap, for market data&lt;/td&gt;&#xA;          &lt;td&gt;CoinGecko for logos and project data; both for market data&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;Both are free to use, both need the contract&amp;rsquo;s source code verified first, and both key everything by chain, so a token on six chains is six Etherscan-family submissions and, since Blockscout hosts no BNB Smart Chain explorer, up to five Blockscout ones — fewer where a CoinGecko listing already supplies the data. Neither documents token information carrying over from an implementation contract to the clones created from it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Data Aggregators</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/aggregators/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/aggregators/</guid>
      <description>&lt;p&gt;Market-data sites come in two kinds, and registering with each kind means something different. &lt;strong&gt;Aggregators&lt;/strong&gt; — CoinGecko and CoinMarketCap — hold one reviewed record per asset, with every chain&amp;rsquo;s contract address in it, and a token team applies for that record. &lt;strong&gt;Pool trackers&lt;/strong&gt; — GeckoTerminal, Dexscreener and DEXTools — index trading pairs on decentralized exchanges automatically, one page per chain, and what a token team buys is the profile attached to a page. DefiLlama is a third case: it lists protocols by the value they hold, not tokens.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wallet Registries</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/wallet-registries/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/wallet-registries/</guid>
      <description>&lt;p&gt;Before token lists existed, wallets shipped their icons as a directory of files in a public repository, and adding a token meant opening a pull request against it. Three of those repositories still take submissions, and each now has its own page. They differ less in format than in who they let in:&lt;/p&gt;&#xA;&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Registry&lt;/th&gt;&#xA;          &lt;th&gt;Channel&lt;/th&gt;&#xA;          &lt;th&gt;Cost&lt;/th&gt;&#xA;          &lt;th&gt;Bar to entry&lt;/th&gt;&#xA;          &lt;th&gt;Pace&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/trust-wallet&#34;&gt;Trust Wallet&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td&gt;pull request to &lt;code&gt;trustwallet/assets&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;500 TWT or 2.5 BNB per pull request&lt;/td&gt;&#xA;          &lt;td&gt;CoinMarketCap listing, audit, 10,000 holders and 15,000 transactions&lt;/td&gt;&#xA;          &lt;td&gt;human review after the fee is paid&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/metamask&#34;&gt;MetaMask&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td&gt;pull request to &lt;code&gt;MetaMask/contract-metadata&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;none&lt;/td&gt;&#xA;          &lt;td&gt;signs of activity, a website citing the address&lt;/td&gt;&#xA;          &lt;td&gt;310 pull requests open; one outside submission took eight weeks&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/ethereum-lists&#34;&gt;ethereum-lists&lt;/a&gt;&lt;/td&gt;&#xA;          &lt;td&gt;pull request to &lt;code&gt;ethereum-lists/tokens&lt;/code&gt;&lt;/td&gt;&#xA;          &lt;td&gt;none&lt;/td&gt;&#xA;          &lt;td&gt;a valid file; sixteen chains only&lt;/td&gt;&#xA;          &lt;td&gt;months between merges&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;All three key a token by its checksummed address inside a per-chain folder, so a token deployed at the same address on six chains is six sets of files, whichever registry takes it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on Uniswap</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/uniswap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/uniswap/</guid>
      <description>&lt;p&gt;There is no Uniswap form for a token image. The logo beside a token on app.uniswap.org, the interface to the &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/uniswap&#34;&gt;Uniswap protocol&lt;/a&gt;, is a string called &lt;code&gt;project.logoUrl&lt;/code&gt;. Uniswap&amp;rsquo;s own backend hands it to the interface when the page loads, and it is copied from &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/coingecko&#34;&gt;CoinGecko&lt;/a&gt;. Uniswap Labs states the rule in as many words: &amp;ldquo;Uniswap Labs sources token information and token logos from CoinGecko.&amp;rdquo; Change the logo on CoinGecko, wait about 48 hours, and it changes on Uniswap.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on Etherscan</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/etherscan/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/etherscan/</guid>
      <description>&lt;p&gt;Etherscan&amp;rsquo;s token page — the first search result for a contract address — shows a logo, description and project links only after someone who has proved control of the contract submits them through Etherscan&amp;rsquo;s Token Update Application Form. The update is free and needs no liquidity or holder count. It has three prerequisites, in order: an Etherscan account, source code verified on the explorer, and a signed message proving ownership of the contract address. Each explorer in the Etherscan family — Basescan, Arbiscan, BscScan and the rest — takes its own submission.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on Blockscout</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/blockscout/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/blockscout/</guid>
      <description>&lt;p&gt;Blockscout is an open-source block explorer, and the company behind it hosts it for many chains, each as a separate instance with its own address such as &lt;code&gt;eth.blockscout.com&lt;/code&gt;. A token&amp;rsquo;s project information on a Blockscout explorer — logo, description, website, links — comes from one of two places: a &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/coingecko&#34;&gt;CoinGecko&lt;/a&gt; listing, which Blockscout reads automatically — it queries &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/coinmarketcap&#34;&gt;CoinMarketCap&lt;/a&gt; too, but for market data — or a token info application submitted to that instance by the token&amp;rsquo;s owner. The application requires a verified contract and a signed ownership proof, takes the logo as a link rather than an upload, and is reviewed either with no guaranteed timeline or, for 99 USDC or USDT, within seven days.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on GeckoTerminal</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/geckoterminal/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/geckoterminal/</guid>
      <description>&lt;p&gt;GeckoTerminal is CoinGecko&amp;rsquo;s tracker for decentralized exchange pools. It indexes pools on the exchanges it supports automatically and for free, so a token appears there — with a price chart and a trade history — once its first pool is on a supported exchange, and nobody has to apply. What a token team can submit is the &lt;em&gt;token info&lt;/em&gt; attached to that token on one chain: logo, banner, description, website, social links and categories. As of September 2026 that submission costs $199 and is reviewed within 24 hours.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on Dexscreener</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/dexscreener/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/dexscreener/</guid>
      <description>&lt;p&gt;Dexscreener is a chart and pair tracker for &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/dex&#34;&gt;decentralized exchanges (DEXs)&lt;/a&gt;. It lists every pool on the exchanges it supports without an application — &amp;ldquo;as soon as they are added to a &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/liquidity-pool&#34;&gt;liquidity pool&lt;/a&gt; and have at least one transaction&amp;rdquo; — so a token&amp;rsquo;s price chart appears with no involvement from its team. What a team can buy is the token&amp;rsquo;s profile: the icon, header image, description, website and social links shown beside the chart. The product is called Enhanced Token Info, it costs $299, and it is processed within minutes to twelve hours. It is one of the few routes that puts a logo beside a token in its first week.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on DEXTools</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/dextools/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/dextools/</guid>
      <description>&lt;p&gt;DEXTools is a trading dashboard for &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/dex&#34;&gt;decentralized exchange (DEX)&lt;/a&gt; pairs. It does not list tokens in any sense a team applies for — &amp;ldquo;DEXTools does not &amp;rsquo;list&amp;rsquo; tokens! but instead pulls data directly from the blockchain in real time&amp;rdquo; — so a pair appears as soon as the token trades on a supported exchange. The token&amp;rsquo;s profile beside the pair — logo, banner, a 140-character description, categories and social links — comes either from CoinGecko, for tokens listed there, or from a paid marketplace order called &lt;em&gt;Token Info &amp;amp; Social Updates&lt;/em&gt;, displayed at $195.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on CoinGecko</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/coingecko/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/coingecko/</guid>
      <description>&lt;p&gt;A CoinGecko listing is a coin page: one record per asset, carrying a name, symbol, logo, description, links, supply figures, and a map from each blockchain the asset lives on to its contract address there. The record is created when a request form on CoinGecko&amp;rsquo;s partner platform passes a staff review. Review is free and takes up to five days, or 24 hours for $1,000. There is one hard prerequisite: the token must already be trading on an exchange CoinGecko tracks.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on CoinMarketCap</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/coinmarketcap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/coinmarketcap/</guid>
      <description>&lt;p&gt;CoinMarketCap (CMC) says &amp;ldquo;the majority of assets are now listed automatically&amp;rdquo;: its DexScan service creates a page for each trading pair on a &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/dex&#34;&gt;decentralized exchange (DEX)&lt;/a&gt; from on-chain data, without a name check, a logo or a review. What a token team applies for is a &lt;strong&gt;verified listing&lt;/strong&gt; — one reviewed coin page with a project name, logo, links, supply figures and every chain&amp;rsquo;s contract address, identified by a Unified Cryptoasset ID (UCID). The application is a request form on CoinMarketCap&amp;rsquo;s support site. The free route has, in CoinMarketCap&amp;rsquo;s words, outcomes that &amp;ldquo;can range from days to months/years&amp;rdquo;; the paid one, CMC Priority (CMCP), costs USD 5,000 per page with a turnaround of about a business day.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on DefiLlama</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/defillama/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/defillama/</guid>
      <description>&lt;p&gt;DefiLlama lists protocols, not tokens. A listing is a page showing a protocol&amp;rsquo;s total value locked (TVL) — the value of the assets its contracts hold — and it is created by a pull request to the &lt;code&gt;DefiLlama/DefiLlama-Adapters&lt;/code&gt; repository adding an &lt;em&gt;adapter&lt;/em&gt;: a small JavaScript module that computes that value from on-chain data. The protocol&amp;rsquo;s name, logo, links and token are not files in the pull request. They are answers to a questionnaire in the pull request&amp;rsquo;s description, which DefiLlama&amp;rsquo;s staff turn into the listing themselves. No fee appears anywhere in the documented process.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on MetaMask</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/metamask/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/metamask/</guid>
      <description>&lt;p&gt;MetaMask has no listing form. The name and icon it shows for a token come from its Token API, a MetaMask service that merges token lists from a dozen or more third parties — swap routers, bridges, &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/coingecko&#34;&gt;CoinGecko&lt;/a&gt;, &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/coinmarketcap&#34;&gt;CoinMarketCap&lt;/a&gt;, Trust Wallet — and counts, for each token on each chain, how many of those lists carry it. A token on enough of them is detected automatically in a user&amp;rsquo;s wallet; the default threshold in MetaMask&amp;rsquo;s current code is three. Getting a token in front of MetaMask users therefore means one of three things: be on enough upstream lists, get an entry into MetaMask&amp;rsquo;s own &lt;code&gt;contract-metadata&lt;/code&gt; repository, which counts as one of those lists, or have your own interface call &lt;a href=&#34;https://wiki.bitsy.services/wiki/economics/defi/token-registration/on-chain-metadata#pushing-the-icon-at-the-wallet&#34;&gt;&lt;code&gt;wallet_watchAsset&lt;/code&gt;&lt;/a&gt;, which needs nobody&amp;rsquo;s approval.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on Trust Wallet</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/trust-wallet/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/trust-wallet/</guid>
      <description>&lt;p&gt;Trust Wallet takes a token&amp;rsquo;s logo and description from &lt;code&gt;trustwallet/assets&lt;/code&gt;, a public GitHub repository with one folder per token per chain. Each folder holds exactly two files, &lt;code&gt;logo.png&lt;/code&gt; and &lt;code&gt;info.json&lt;/code&gt;, and getting a token in means a pull request that adds them, a fee of 500 TWT — Trust Wallet&amp;rsquo;s own token — or 2.5 BNB per pull request, and a review against criteria that include 10,000 holders. The repository&amp;rsquo;s README states the consequence directly: &amp;ldquo;brand new tokens are not accepted&amp;rdquo;. For a token launched this month, this page is a description of a milestone rather than a step.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Registering on ethereum-lists</title>
      <link>https://wiki.bitsy.services/wiki/economics/defi/token-registration/ethereum-lists/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://wiki.bitsy.services/wiki/economics/defi/token-registration/ethereum-lists/</guid>
      <description>&lt;p&gt;&lt;code&gt;ethereum-lists/tokens&lt;/code&gt; is a community-maintained GitHub repository holding one JSON file per token per chain, named after the token&amp;rsquo;s address. A build step assembles the files into combined lists, and hardware-wallet firmware and a few older wallets import the result. Adding a token is a pull request with one file: no fee, no holder count, no audit. The cost is pace and coverage. The last token pull request merged on 4 April 2026, and the repository knows sixteen chains, which include Ethereum, Arbitrum and BNB Smart Chain but not Base, OP Mainnet or Polygon.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
