Versioning & Multichain Compatibility
Action Spec Version Compatibility
Different Blink clients, such as wallets, update at different rates. This means they might not support the latest features, which can lead to situations where Blink is rendered incorrectly--elements not being visible or displayed correctly, for example, or being completely non-functional.
Now, you can specify the spec version the Action API server is using like X-Action-Version: 2.1.3 as an example.
For backwards compatibility, Blink clients will treat the absence of the X-Action-Version header as the last pre-compatibility release.
Multi-Chain Compatibility
Prior to the implementation of sRFC 31, the Action specification did not specify which chain to target other than the recent blockhash being invalid on another network. In order to ensure consistent encoding and identification of blockchain networks, the specification now utilizes chain agnostic standards that are gaining traction in the industry, specifically CAIPs.
Now, you can specify a specific blockchain for the Action to target by including a header in the GET and POST requests, like X-Blockchain-Ids: solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp for Solana Mainnet-Beta and X-Blockchain-Ids: solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 for Solana Devnet. The IDs use CAIP-2 compatible strings.
For backwards compatibility, Blink clients will treat the absence of the X-Blockchain-Ids header as a Solana mainnet action.
Chain ID Mapping
| Blockchain | Devnet | Testnet | Mainnet |
|---|---|---|---|
Solana |
|
| |
Eclipse |
|
|
|
Last updated