Peter Sopko
Peter Sopko
Basilisk will have Subscan, rather just hide it for now and once we will run on official testnets it can be add again. _Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/3280#issuecomment-1166582210_ //...
~Trying to burn NFT, my balance shows me zero on both Transfer / item detail, didn't catch that in screenshot, after refresh there's a balance, but still won't let me...
I'm trying to test KodaDot with Firefox incognito, and my console is very red. Seems that every click/operation within the app produces the same error. ` Uncaught (in promise) DOMException:...
tried everything I could think of up to this point: - reinstalling pnpm - making sure I have same version as @vikiival (7.3.0) - deleting and cloning app again -...
burning/consuming NFT in the end works, however it produces error in console and network, might wanna check this out  
Expanding from @roileo comment here: why do we need to show burned content? If it's burned, the offer shouldn't exist anymore _Originally posted by @roiLeo in https://github.com/kodadot/nft-gallery/pull/3575#pullrequestreview-1051999846_ Currently, burning NFT...
I'd like to see better user experience when it comes to switching between BSXKSM, current implementation is always redirecting back to landing page (suboptimal). Issue is labeled as research as...
we've had some issues with multiple sorting options before, the feature got introduced here: - https://github.com/kodadot/nft-gallery/pull/3067 later was fixed (in a hacky way) to not allow conflicting options at once...
Next candidate for refactor: - #3358 _Originally posted by @vikiival in https://github.com/kodadot/nft-gallery/issues/3310#issuecomment-1177253672_ I take it, that as @vikiival mentioned, we should refactor / rethink the way our current NFT storage...
We are still by default attaching 1 trait (carbonless) to every NFT which I find weird  and it would be perhaps desirable to get rid of it...