Solid update on the dev side. Cleaning up and stripping query parameters from the URL before hashing or comparing it is the exact right approach to stop basic duplication exploits.

However, looking at it from an adversarial perspective, how are you handling URL shorteners (like bit.ly or tinyurl) or redirect chains? If bad actors realize you are only parsing base URLs, they might use redirect layers to bypass the blockchain-level duplicate check. Also, using a specific admin keyword in the comments for immediate frontend filtering is a clever, lightweight moderation compromise that keeps data on-chain while keeping the frontend clean. Keep building, looking forward to seeing how the architecture handles scale.