ginny-stacks

Thanks Nick, here are my comments: - [x] **1) Suspicious token mark inconsistency** A token is marked as suspicious in the table, but this mark is missing on the ID...

Thanks for addressing the feedback @nick-stacks ! There are just some standing fixes: - [x] **1) Link styling and wrapping** - The link styling is not visible in its normal...

Thanks @nick-stacks , looking good! My only last comment is that this column should hug contents in height, as it used to do before: Other than that, it's approved 👍

Here's the QA review: - [x] **1) Update bridge links:** Update “Get sBTC” button and “How can I get sBTC?” links to point to https://sbtc.stacks.co/ (this was changed recently). ----------------------------------...

> @ginny-stacks Regarding #7, we are actually using the token image we get from the Token Metadata API. I think the optimal solution is to update the token image the...

Thanks! It looks great, just one last small tweak: - On the FAQ cards, it would be great to add the interaction to close them upon clicking anywhere outside the...

Hi @Hero-Gamer, thanks for bringing this to our attention. As you mentioned, I don't think adding more characters is the right solution here. These spam patterns can become more sophisticated...

I don’t recall this being possible with non-STX transfers, but I could be mistaken. The work required here is primarily engineering. We'd need to parse the contract call to surface...

Hi Werner, thank you for bringing up this issues. When you mention `"they should be checkable next to each other so they can be easily compared for troubleshooting purposes."`, can...

Please see screenshots attached and let me know what you think. @andres I don’t think a block fullness visualization makes sense here, the percentages are usually so small (correct me...