12/ When we promote Solana Blink, we need to specifically point out the risks.
For example, if someone forges a blink, and the transaction/instruction behind it is malicious, and at the same time, the widget interface pretends to be you doing a swap (actually an authorization), the user's wallet may be emptied. (1) Don't blindly follow the understanding of EVM (2) Be sure to check what the wallet signs.
13/ Frame by Farcaster See also: Turning static embeds into interactive experiences.
Frames are implemented by extending the OpenGraph (OG) standard, allowing users to interact with them by clicking buttons.
https://docs.farcaster.xyz/learn/what-is-farcaster/frames
14/ The Blink workflow includes:
- User clicks on a link,
- Verify the validity of the link,
- Interface for viewing transaction details,
- Confirm the transaction,
- Integration with wallets and
- Execute transactions.
https://web3.bitget.com/en/academy/solana-blink-feature
15/ Currently, there are some different understandings of Action/Blink/Widget. Dialect defines Action as API and Blink as interface.
But I tend to think
- Action on-chain API,
- blink is the link (also manifested in actions.json), and
- Widget is the interface.
16/ Documentation:
Blinks, are clients that determine if URLs conform to the Actions spec, & introspect the underlying Actions APIs to construct interfaces for them.
Blinks, the blockchain link, is a client that determines whether a URL complies with the Actions specification. It reviews the Actions API and builds the interface.
https://docs.dialect.to/documentation/actions
