Universal sign links
HERE supports the new transaction format without having to pass signer_id. In this article we will explore the possibilities of this approach
In the previous wallet selector format, a fully encoded transaction was required to be passed, which required obtaining the signer_id beforehand. This added the need for each dApp to have a login functionality and made it impossible to create static links to sign transactions.
We have introduced a new transaction signing template that allows you to pass a list of actions and have the final transaction generated on the wallet side. This has several benefits:
- 1.Static Links: With the new template, it is possible to create static links for transaction signatures and use them in QR codes, for example. This enables you to make an airdrop to all event participants.
- 2.Signing Transactions Without Authorization: You can add a button to your site that allows users to post NFT or purchase transactions without requiring them to log in to their accounts. This prevents other developers from using NEAR.
- 3.Creating Templates: With this new feature, it is possible to create templates such as https://h4n.app/g/keypom/xxxx, which will immediately generate the transaction and redirect it for signature. This makes it easy to create a simple interface for many dApps.
base58 encode JSON
"type": "function call",
params list same as for NEAR rpc api
You can also sign a message with a private key without sending it to the blockchain. This is useful e.g. for authorization via a wallet
Base58 json encode:
"message": "auth message to sign",