-
Upon implementing the send NFT functionality using MultiversX SDK-Core, it's observed that the sender and destination addresses in the transaction call are identical, leading to unsuccessful transfers…
-
### ⚠️ Please verify that this feature request has NOT been suggested before.
- [X] I checked and didn't find similar feature request
### 🏷️ Feature Request Type
UI Feature
### 🔖 Feature descripti…
-
Will attach wireframe privately
-
In the Cargo.toml for the example, the following version numbers are listed
![image](https://github.com/gfusee/novax-price-getter/assets/164737012/39e97750-1641-471b-a463-c804e3459421)
Do these …
-
-
I always get this
```
ReferenceError: navigator is not defined
at y (**\.next\server\chunks\2335.js:23:102029)
at nM (**\node_modules\next\dist\compiled\next-server\app-page.runtime.prod…
-
Current implementation is hard to adjust and maintain.
-
```
payload = message.toJSON()
// send payload to a backend for verification
signableMessage = ... cumbersome to recover the message from "payload" ...
```
Reported on Telegram. Workaround here…
-
Add a paragraph / note / warning to instruct users to pay attention to the output of `mxpy-up`:
- https://docs.multiversx.com/sdk-and-tools/sdk-py/installing-mxpy/
Related to: https://github.com/…
-