Years of activity. No reputation.
To crypto, a wallet from 2017 and one created today look exactly the same.
How long have you been onchain, and what does your wallet say about you?
Tested @meleemarkets beta today and found an interesting friction point.
There is a Bug Reports option in the Discord server, but the report goes into a private ticket.
That means testers can’t easily see:
• what has already been reported
• whether someone found the same issue
• what feedback is already being discussed
When the infrastructure is structured properly, it can reduce the manual work for both testers and teams while making the feedback more useful and actionable.
Bitcoin is back above $85K, and we’re already seeing a lot of new opportunities in the market, with new projects going live, opening testnets, and launching incentive programs.
But it raises the same question again: are the users participating happy with the experience, are project teams actually getting what they need?
Or are we still relying on infrastructure that was never built for this scale of activity?
Testing @HypernovaX today.
While exploring the app, we ran into an interesting feedback infrastructure issue: there’s no clear way to submit a video when reporting a bug or UX problem.
But allowing video uploads also creates another challenge. Open feedback channels can be abused with unrelated or malicious content, making moderation harder.
So the real problem isn’t simply “allow videos.”
It’s building feedback infrastructure that makes useful submissions easy while keeping the channel clean and manageable.
We tested https://t.co/6Ytmj2uqEz’s testnet and also looked at the community infrastructure around it.
The testnet was active, and users in the Telegram community were actively asking questions and discussing how to participate. But when we had useful feedback to share, there wasn’t an obvious or structured way to submit it.
In a busy community, announcements, questions, discussions, and feedback all flow through the same stream. As a result, even valuable feedback can easily get buried before the team has a chance to notice or act on it.
The interesting problem isn’t whether users are giving feedback.
It’s whether the right feedback is easy for the team to discover, organize, and act on.