@DarthRoison
edited
Upgrade request: Read.Cash should recognize SLP tokens I just realized that Read.Cash does not discern between ordinary BCH UTXOs and SLP Tokens. I tipped a post, and due the imprudence of keeping USDT in that same wallet, I actually burned a 3 USDT UTXO. After realizing this I moved my USDT to another account. Fortunately the burned UTXO was a low amount.
It would be great if Read.cash can improve to recognize SLP tokens UTXOs and not spend them, this will be done, to avoid accidents like the one that happened to me. In addition, I suggest to other Read.cash users not to commit a similar negligence until it has been announced that such possibility has been excluded.
5 comments
Wow what a great suggestion for this sites i hope it will come true and recognise him for this..
I disagree. Why complicate things unnecessarily for the maintainer. @read.cash is a one man show and it is already awesome as it is!
>Why complicate things unnecessarily for the maintainer I recognize that this may be correct. In that case, the maintainer will have to evaluate the pros and cons. If this is not applied, at least I have learned something and other users can be aware that keep SLP tokens in a Read.Cash wallet is bad practice.
As SLP tokens are an "extension" of BCH, I agree to an implementation of SLP on Read.Cash. Can it be a new dynamic thing to come? :0) Followed!
I think it would be enough for Read.cash to recognize if a UTXO corresponds to an output from an SLP token and not to spend those UTXOs. This avoids accidentally burning SLP tokens.