Bug where collateral is used up while interacting with smart contracts
See original GitHub issueHi @alessandrokonrad! Thanks for making such a killer wallet š
Iām the developer of jpg.store and weāve had two users run into issues with collateral.
Case 1: A user set collateral, and without removing it the UTXO somehow disappeared from their wallet.
Case 2: Iāve also seen in some instances a user will have collateral UTXO in their wallet, but Nami doesnāt seem to recognize it and requires them to reset it.
Any idea of why this might be happening? Could cardano.getUtxos()
be including the collateral UTXO?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Troubleshooting Staking - Medium
Go to NAMI wallet; Click on Profile; Click Collateral; Input password; Confirm ā Be sure to have ~5 ada within your wallet while...
Read more >Nami (@NamiWallet) / Twitter
It fixes some bugs and adds the concept of collateral into the UI, which allows Nami now to interact with smart contracts aka...
Read more >How smart contracts are transforming banks and financial ...
Both parties can interact and respond in real-time to āif-when-thenā conditions of the contract. It allows parties to transact anonymously ifĀ ...
Read more >Using NFTs As Collateral: We Asked Franklinisbored
Once agreed upon, the NFT is locked into a smart contract for a set amount of time or until the borrowed amount (plus...
Read more >Collateral Module - Maker Protocol Technical Docs
When a user desires to enter the system and interact with the dss contracts, they must use one of the join contracts. If...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay since the bug was in a previous version he may have spent the collateral utxo normally already. Thatās why itās still wrong in the new version. Simply removing and readding should fix it. Then this behaviour should not happen again (hopefully).
Hey, Iāll look into this. Maybe I forgot something, since I simply seperate the collateral UTxO from the other UTxO, but maybe there is something going wrong and so the collateral is consumed as normal UTxO. Could you let me know which Nami version the users are on. I had a bug a few week ago, which I already fixed.