· srfc 34 - standardized relayer api summary this rfc proposes a standard api that teams can adopt/implement to enable on-chain activity without end users holding sol (gas … · srfc 33 - sign message in actions/blinks tldr add the ability for actions and blinks to ask users to sign a plaintext message. · an implementation of on-chain image storage to the current metaplex nft standard this standard utilizes the existing fields of the metaplex nft program to be able to store an on … · solana’s current emission mechanism is a fixed, time-based formula that was activated on epoch 150, a year after genesis on. The mechanism is not aware … To improve defi ux, we can eliminate gas fees for market takers by allowing them to sign an idl-encoded message … I focus on our engineering operations at chorus one, and i don’t … This allows for … · hi, i would like to share some feedback on the governance process surrounding simd-123 and simd-228. This is a common and no-cost way to validate a … Welcome to the solana developer forums · discussions about specific simds (solana improvement documents), and general proposals that may become simds. · srfc-35 - address/domain association specification summary solana addresses can be publicly linked to domain names using dns txt records or a well-known file. · srfc 36 - typed message payload rendering in wallets tldr; · i don’t want solana to offer technically inferior solutions to stakers; But i also don’t want to create a system which puts even more friction in front of validators just getting started. If applicable, specify the simd issue # in the topic title.
Solana'S 2027 Roadmap: The Key To Internet Capital Markets Domination
· srfc 34 - standardized relayer api summary this rfc proposes a standard api that teams can adopt/implement to enable on-chain activity without end users...
