Lately, we’ve been talking about how to handle “on-chain privacy.” To be blunt, my expectations for ordinary users are pretty low: whatever you put on-chain is, by default, something others can trace back—it's only a matter of how high or low the cost is. Don’t expect a clear, one-click “compliance” button either; more often than not, it’s about explaining after the fact, drawing the lines as you go… What I can do is simply not entangle identity information and addresses at random—if I can reduce exposure, I’ll reduce it as much as possible.



Over the past couple of days, that mainstream public chain is due for an upgrade. In the group, everyone is guessing whether ecosystem projects will migrate. I’m actually more concerned about whether the various “privacy tools” before and after the upgrade will be watched even more closely. By then, if the chain gets congested and you keep refreshing/retrying in your wallet while queuing to confirm, it’s easy for your mindset to fall apart—then one slip of the hand and you click a link you shouldn’t… In any case, I’d rather go slower and not dig a hole for myself. That’s it for now.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • Comment
  • Repost
  • Share
Comment
Add a comment
Add a comment
No comments