← Voltar
70/100r/solana · @Resident_Anteater_35 · Wevolv3 · Development

Token-2022 utility extensions are more useful than they look

Abrir no Reddit ↗
💡 Por que é um lead: [PROJECT/ENGAGEMENT] Founder sharing technical insights on Token-2022 extensions, a relevant Web3 discussion where Wevolv3 can add value on development and growth. 📇 site:https://andreyobruchkov1996.substack.com/p/the-utility-extensions-completing

Post original

Most Token-2022 discussions focus on Transfer Hooks and Confidential Transfers. I spent some time testing four of the smaller extensions on Devnet, and they cover a surprising amount of application-level logic. The four extensions are: Permanent Delegate Non-Transferable Tokens Default Account State Required Transfer Memos Permanent Delegate gives one authority transfer and burn rights across every account associated with a mint. That is useful for regulated assets, subscriptions, and recovery workflows, but it also creates an authority that users need to understand before accepting the token. Non-Transferable makes the restriction part of the mint itself. There is no wrapper program or freeze workaround. Transfers fail at the token program level, while the holder can still burn the asset. The interesting part is combining it with Permanent Delegate. You can model prepaid API or compute credits as fungible tokens that users can hold but cannot resell. The protocol backend burns credits as the service is consumed. Default Account State covers a different problem. New token accounts can begin frozen and remain unusable until an authority explicitly thaws them. That gives regulated protocols a native account-level approval flow. Required Transfer Memos is applied by the receiving token account rather than the mint. It forces incoming transfers to include transaction context, which is useful for exchange deposits and treasury accounting. The trade-off is clear: Token-2022 removes a lot of custom wrapper code, but it moves more policy and authority into the token configuration itself. Wallets and explorers need to make those permissions very visible. I documented the Devnet tests, SPL CLI commands, and Solscan transactions here: https://andreyobruchkov1996.substack.com/p/the-utility-extensions-completing Which of these extensions would you trust in a production asset, and what warnings should wallets show before a user receives one?   submitted by   /u/Resident_Anteater_35 [link]   [comments]

Rascunhos

Sem rascunho (score abaixo do threshold). Ajuste o threshold em Configurações se quiser gerar rascunho para leads com score menor.

Status