Coinbase Wallet pulls metadata from BirdEye, CoinGecko and CoinMarketCap. Search volume rose from ~220 to ~910 daily and swap conversion improved from 2. #CoinbaseWallet #ERC20 #TokenMetadata tokpie.io/blog/how-to-add-to…

2/2 wrapped.bet 🧮 ELI-Vitalik Construction. For an unordered pair {A, B}, the wrapped share is an SPL Token-2022 mint at PDA(["lp_mint", sort(A,B), token_program]) — deliberately independent of the source AMM, so all venues’ LPs for the pair collapse to one fungible claim. Authority is a program PDA; metadata (Token-2022 MetadataPointer → self TokenMetadata) is set by the creator. A 1 bp TransferFeeConfig is native on the mint. Verification (the trust model). Wrap takes the candidate AMM pool account and: 1.AmmKind::from_program_id(pool.owner) — the pool must be owned by an allow-listed AMM program (Raydium v4/CPMM, PumpSwap, Meteora). The owning program is the trust anchor; you cannot fabricate a pool because only that program can author its bytes. 2.pool.lp_mint == supplied_lp_mint (reject LpMintMismatch). 3.sort(pool.mintA, pool.mintB) == sort(pair) (reject PairMismatch). 4.Escrow is the canonical ATA(authority, lp_mint, lp_token_program); the LP token program is read from the mint’s owner, not assumed. The byte offsets for each AMM’s pool layout were validated against live mainnet pools. Accounting. ERC-4626-style shares, but enforced on-chain and decimal-aware: LP amounts from heterogeneous mints are normalized to a common scale before summing reserves; redemptions denormalize back. shares = deposit·supply/reserves, assets = shares·reserves/supply, both floored. Crucially, reserves are summed only over an AMM-verified LP registry stored in PairConfig — so a donation of a worthless token into an authority-owned ATA can’t inflate NAV; only LPs that passed pool verification count. Fee invariant. Each mint/burn applies three 1 bp legs. The NAV leg is burned (Δsupply < 0, Δreserves = 0); creator/deployer legs are paid in shares. Combined with permissionless donations (Δreserves > 0, Δsupply = 0), d(reserves/supply) ≥ 0 holds across all protocol operations — NAV per share is monotonically non-decreasing by construction. The only “loss” vector is external (impermanent loss in the underlying pool itself), which is orthogonal to the wrapper. Composition (the zap). Because mint/burn amounts are path-dependent on realized swap/deposit outputs, the zap is a sequenced multi-tx flow rather than one atomic instruction: wrap-SOL ∥ Jupiter(SOL→leg) → AMM.addLiquidity → Wrap. It’s signed in one signAllTransactions and submitted via rapid-fire sendRawTransaction through a staked (Helius) path, polling status per leg — empirically more reliable than the public Jito bundle endpoint, though a Jito atomic path remains available behind JITO_BE. Exit is the mirror: Unwrap → AMM.removeLiquidity → Jupiter(leg→SOL). The result is a venue-agnostic, fee-compounding index token over a pair’s aggregate on-chain liquidity, with verifiable accounting and a single-asset (SOL) entry/exit.

@LayerZero_Labs I need your help tldr I built a thing on ton for fun n profit, now my following wants easier access w their solana bags starswar.fun/ I'm building a bridge for $PROOFV3 — a custom Solana Token-2022 token (CLWeikxiw8pC9JEtZt14fqDzYfXF7uVwLuvnJPkrE7av) — to TON using your OFT standard. I've done all the homework and hit one wall. What I've got ready: — Solana OFT Adapter: fully ready to deploy via your devtools. PROOFV3 only uses metadataPointer tokenMetadata extensions, so it's in the best-case Token-2022 compatibility tier. No custom wrapper needed. — TON Jetton contracts: I adapted the minter wallet from your ZRO Jetton reference in packages/layerzero-v2/ton/src/jettons/zro/. FunC contracts written, TypeScript wrappers done, deployment scripts ready. — Cross-chain config: layerzero.config.ts wired for Solana EID 30168 ↔ TON EID 30343, enforced options set, DVN config templated. Where I'm stuck: The TON BaseOApp integration layer — the FunC framework that handles lzReceive/lzSend and connects to the Jetton minter — isn't in your public devtools yet. I can see you've deployed OFTs on TON (ZRO, USDT0) so the infra clearly exists, but there's no public "examples/oft-ton" equivalent to examples/oft-solana for third-party devs. The ask: Can I get early access to the TON OFT developer toolkit, or guidance on integrating my Jetton contracts with the BaseOApp? Happy to be a guinea pig for the first community-deployed custom OFT on TON. Full writeup of everything I've built the research below. ideally I can just bridge solana tokens willie nillie but I don't believe you'd entertain that I am tasking @srirachaenjoyer with following up for now, because this blocker allows me to finally (mercifully) sleep manus.im/share/hWUR2iyqpSnBZ…

Trying to add your token to OKX Wallet but the logo/price won’t show? 🧪 It’s a 4-layer integration: contract, metadata, liquidity for price discovery, reputation. Full guide: tokpie.io/blog/how-to-add-to… #OKXWallet #TokenMetadata #Liquidity

We’ve improved our webhook notifications! (again) What’s new 👇 👉 Clear sender and recipient fields (from, to) 👉 Rich tokenMetadata for better token context 👉 Additional transaction data like gas usage and timestamps

Coinbase Wallet pulls metadata from BirdEye, CoinGecko and CoinMarketCap. Search volume rose from ~220 to ~910 daily and swap conversion improved from 2. #CoinbaseWallet #ERC20 #TokenMetadata tokpie.io/blog/how-to-add-to…

Clitcoin Community-Driven Token Clitcoin is a culture-first, community-driven token built on narrative, creativity, and long-term conviction. There’s no central team calling the shots the community now fully controls the project through the CTO (Community Take Over). Key Facts: •Contract Address (CA): 8TfcukxCWzsnLbbNcznqt4LFnSuoT9hm41S15bjppump •Telegram: t.me/clitcoinctooff… •X: x.com/the1clitcoin •Authorities: Mint, Freeze, Update → N/A (fully decentralized) •Token Extensions: metadataPointer → NULL, tokenMetadata → NULL Clitcoin is about transparency, shared ownership, and collective execution. Memes, coordination, and contribution drive growth not hype. If you’re here early, you matter. If you stay, you help define what Clitcoin becomes. @the1clitcoin

Clitcoin CTO is live. Old team vanished after a 92.25M CLIT sell into the Pump vault. Safety: mint, freeze, update authority are N A. Token 2022 extensions: metadataPointer and tokenMetadata, both NULL. $Buttcoin is running. Time to complete the anatomy meme. Receipts below.

Don't be fooled by metadata issues, #OILCOIN (Oil Coin) CA: Cwn9d1E636CPBTgtPXZAuqn6TgUh6mPpUMBr3w7kpump Project C3 team is working on a solution for the original Dev metadata on sites like Jupiter Swap, Raydium, etc. Stay tuned for updates! #OILCOIN #ProjectC3 #DeadCoinAlchemy #SlickCart #DrRug #TokenMetadata #OnChainAssets #Solana #CrudeContracts

🧠 Made a token… but want to fix the name or image? You can update the metadata—if you didn’t revoke the rights. Here's what to check: solanatokencreator.com/post/… #Solana #TokenMetadata #CryptoTips #Web3Dev

🧬 Behind the Scenes: How TokenForge.tools Uses Decentralized Storage for Your Token Metadata When you mint a token, where your metadata lives matters. At TokenForge.tools, we don’t just slap it on a server—we decentralize it. Here’s how 👇 📦 Powered by IPFS Your token’s name, logo, and metadata are stored on IPFS—a peer-to-peer, immutable storage system. No centralized servers, no risk of takedown. ✅ Immutable records ✅ Public & verifiable ✅ Censorship-resistant ✅ Fully compatible with Solana’s standards 🔍 Why this matters: Centralized platforms can change or delete your token data IPFS ensures your token branding and info stays safe, permanent, and transparent. Your project earns trust from users and exchanges with verifiable, decentralized metadata With TokenForge.tools, you don’t just mint—you build with integrity, using the same tech trusted by top Web3 platforms. 🧠 Decentralization isn’t just a buzzword. It’s baked into every step. 👉 Launch with confidence: tokenforge.tools 🔗 Follow: @tokenforge_sol #IPFS #TokenMetadata #SolanaTools #Web3Infrastructure #DecentralizedStorage #TokenForgeTools #Solana #SolanaGems

AirShip supports Token 2022, but not all extensions are supported by ZK Compression yet. The following extensions are supported: • MetadataPointer • TokenMetadata • InterestBearingConfig • GroupPointer • GroupMemberPointer • TokenGroup • TokenGroupMember Tokens using unsupported extensions cannot be airdropped at this time.

ok but like, do you know anyone doing anything marginally interesting wrt dynamic metadata? const tokenMetadata = { name: "stacc tweeted", symbol: "stacc", description: "this token is purely for entertainment and for the most part u just shouldn't buy it, it's whatever I tweeted last", metadataUri: "freestacc2.ngrok.app/api/x", }; 9KtcbYjhMGQYx3VjYjUKhs7dmRgYxwJXSGga4ipEtqEX

ok but like, do you know anyone doing anything marginally interesting wrt dynamic metadata? const tokenMetadata = { name: "stacc tweeted", symbol: "stacc", description: "this token is purely for entertainment and for the most part u just shouldn't buy it, it's whatever I tweeted last", metadataUri: "freestacc2.ngrok.app/api/x", };

ENS6gbdvhmCGPscuCu47Jjk2KkPP2iUNJfkqKDV2UY3w const tokenMetadata = { name: "RANDOM PICTURE", symbol: "RPP", description: "If it isn't clear, this is another test to see if I can perfect how to orca positions in perfectly before unleashing the kraken. A random profile picture for every viewer", metadataUri: "freestacc2.ngrok.app/api/ste…", };

// Deploy on Pump.fun: KOKORO Token Metadata const tokenMetadata = { tokenName: "KOKORO", // name tokenSymbol: "KOKORO", // symbol website: "kokoroxai.com", // website x: "x.com/KokoroXAi/" // X };

New Release: Cashonize v0.1.4 builds for Windows & Android New in this release: changes the default IPFS gateway for faster tokenmetadata Further v0.1.4 improves signMessage dialog pop-up and big internal reworks in preparation for CashConnect github.com/cashonize/cashoni…

Ethereum standards aren’t enshrined. They are conventions, just like solana. You can build your own tooling that uses tokenmetadata or token22 for NFTs, or roll your own version of tokenmetadata and get it intergraded into marketplaces. Solana ended up with a healthier market imho, opensea api’s were the definition of an NFT on Ethereum for a long time.

Wdyt of adding `include_kinobi_idl!()` to TokenMetadata? Before putting out proposal, curious if this makes sense to you

شبكة #البلوكتشين من الطبقة الأولى، #سولانا، حصلت على معيار جديد لـ #الرموز_غير_القابلة_للاستبدال، يُسمى #ميتابليكس_كور، ويَعِد المطورين بسكٍّ أرخص وأسهل للرموز. #Solana #Core #TokenMetadata #NFT #Minting ar.cointelegraph.com/news/so…