search

multiversx / mx-chain-go

⚡ The official implementation of the MultiversX blockchain protocol, written in golang.
https://multiversx.com
GNU General Public License v3.0
929 stars 202 forks source link

[FEAT] Transaction-Hook needs to allow the receiver to be "SELF" or optional. #3672

Closed janniksam closed 2 years ago

janniksam commented 2 years ago

What do I want:

I request the receiver, which is passed to the /hook/transaction, to be either optional or a specific magic value (e. g. "SELF"). When the client that calls the hook is not supplying the receiver or this constant, I need it to be a self-transaction to the wallet logged into.

Why do I need this:

I am writing a telegram bot. Basically, the users can choose an amount x and a token identifier y. The telegram bot will then generate the transaction-hook url and when opening this link, the user will log into whatever wallet he wants.

But since all ESDT/NFT transfers need to be self-transactions and I don't have the receiver address, I actually can't build my scenario. This missing feature is basically destroying my whole plan...

constantintovisi commented 2 years ago

We just released relased a fix on the web wallet that makes the receiver field optional if the receiver address is already contained in the data field as it is the case for the NFTs transfers.

janniksam commented 2 years ago

Thank you @constantintovisi. With "released a fix on the web wallet" you mean on all 3 networks? 👍