$BDX
Cooling DownSnapshot Window: 2026-09-25 08:10 UTC Β· β Back to Crypto Overview
Social Momentum Summary
Total Engagement - Comments: 55, Retweets: 0, Likes: 52, Impressions: 270
Verbatim Community Citations & Social Evidence 5 source posts analyzed
After farming airdrops for so many years, through multiple dealings with project teams and mods, I've confirmed that the saturn @saturn_credit team is the most visionary and responsible team out thereβI'll share some specific examples when the opportunity arises later. Right now
Does this count as diversifying my skills? #Toobit
Here's the hint: agentic commerce Your AI agent finds it, compares it, buys it. Greencart makes sure it pays you back. Shopping is about to stop being something you do yourself.
ERC-8423, burnedBy(tokenId) for ERC-721: should it record the owner or the caller? ERC-8423 is a proposal I'm authoring that adds a single view function to ERC-721, burnedBy(tokenId), so that other contracts can read who burned a token. Indexers get this from the Transfer to address(0), but contracts can't read logs, so a custodian that didn't take part in the burn has no standard place to look. Two examples: a contract that accrues rewards to a token id, and value that reaches a contract after the burn. The spec records the from of the burn's Transfer event, that is the owner at burn time, not msg.sender. If an approved operator burns the token, returns the owner. Two reasons:
θ·εζ‘ι±θΏθ―΄ζ³ε¬ηηηε