I used to think good content needed to be perfect before putting it out.
But working in Web3 taught me something different.
Iβve seen average creators get opportunities simply because they kept showing up, sharing their ideas, and making their work visible. Meanwhile, talented people with valuable knowledge stayed unnoticed because they were waiting for the perfect time or perfect piece.
Quality matters, but nobody can recognize value they never get to see.
Perfection keeps you polishing. Visibility puts you in the room.
You asked me for $1, I sent it, and now you're checking my wallet on the block explorer? ππ
Your money doesn't have to be everyone's business.
On public blockchains, wallet addresses, transaction amounts and the movement of funds can be viewed by anyone. This means people can inspect your wallet activity and sometimes connect transactions to your financial activity.
But with GLOAM, it is different.
@gloamtrade brings privacy to public blockchains, allowing you to move money privately across Robinhood Chain, Tempo, Base and Ethereum.
Getting started is simple. You can sign up using your email address, via https://t.co/gS1Y7d57QE.
With Gloam, you can move funds into a private balance and make payments without publicly exposing the amount sent or the connection between you and the recipient.
People can see certain blockchain transactions, but they don't automatically get access to your entire financial activity.
Gloam is about having more control over what you reveal.
I took a tour of the app to show you how it works and some of the features available.ππΏ
Day 6 of 100 founders in 30 days.
This was the day I wanted to quit the most, web3 feels slow and my replies feel slow.
Everyone around me seems to be moving faster.
When you start measuring yourself against other people, even a good day begins to look like proof that you are behind.
I did not feel like working. I worked anyway.
1. LeaseBase (free property management software for independent landlords, from a founder in Sacramento).
I tested from mobile version, I went through the homepage, partnerships, about, guides, compliance and payments pages, with screenshots and the page text.
Here is what happened:
=> Start Free took me to a CloudFront error page saying the request could not be satisfied.
=> Sign in took me to the same error page.
=> The Book a Walkthrough button did nothing. No page change at all.
=> Check Your Compliance opened a run your compliance page, and its run button hit the same error.
Then the messaging, the site says free forever with no credit card, yet it also shows paid pricing tiers.
That makes me unsure who the plan is for.
The homepage also claims 68 plus landlords across 12 states and i first read that as 32 cities, which tells me it is easy to get wrong at a glance.
I think the broken signup path is a major find and the honest limit is that I do not know whether it was a temporary outage.
But if a visitor cannot sign up, nothing after that matters.
2. UseThatApp (a merchant of record and marketplace for independent web apps).
I started this one on 14 November, i could not sign up to test the product, so this audit rests on public pages only.
I read the site text, the docs, the pricing, the FAQ, and the affiliate and subscriber pages, plus two screenshots from my phone.
My belief is that the site should say which countries or jurisdictions are unsupported, right where a visitor hits the signup block.
If you are going to stop someone at the door, tell them before they walk up to it.
3. STASHER:
I submitted a 15 page product testing report to the STASHER Bug Bounty Program on 14 November.
It has seven findings, and I tested mainly from my phone and a wallet in-app browser.
I also posted it in their community Telegram group, where someone praised it and the owner confirmed the bounty is still ongoing.
Web3 is slow right now. It is also reforming. I am staying.
If you are in a slow season, show up anyway.
The middle is where most people disappear.
RAZZYx
Comment WEB2 and I'll look at yours.
i find this very funny when women say stuffs like this btw and just like i always say
itβs always online yβall have a choice
many of you claim to be working, yet you canβt even provide the least of the least for yourself
a man is always doing it for you, most of the things you have now, your business couldnβt afford not until a man came into your life and just decides to be nice
the wedding finally came and the man took care of most of the wedding expenses alone including yours but you have money
when it comes to the home finally, youβre hardly contributing anything
your hair appointments, skin care and the rest he still takes care of it
what God forsaken business? come on leave that rubbish you call a business before i descend on you
are you okayyyy?
Day 7/30: Getting users is only one part of Web3 growth.
Documenting my Journey, Growth and Observation
A Web3 project can spend money on KOLs, incentives, partnerships and community campaigns, yet still struggle to build an active user base.
The question isn't just how many people discovered your project.
It's what happened after they arrived.
I've been researching early-stage Web3 projects, and one pattern worth examining is the gap between attracting attention and creating a meaningful user experience.
Consider Farcaster.
When TechCrunch tested Farcaster's onboarding in February 2024, account setup took about four minutes. The platform also populated the new user's feed by letting them select interests and follow suggested accounts.
It addressed two common barriers:
* Making newcomers navigate crypto wallet setup before joining.
* Leaving new users with an empty feed and nobody to interact with.
Farcaster made the first experience easier to understand and use. TechCrunch
But acquisition and activation weren't the whole story.
In June 2024, The Block reported that Farcaster's daily posting activity had fallen from a peak of more than 1.5 million casts per day to below 700,000. Its coverage discussed how activity had grown around Frames and the associated incentives, then slowed. The Block
The lesson isn't that Farcaster failed. It's that attracting users and sustaining participation are different growth challenges.
Every Web3 project needs to examine six stages:
1\. Discovery: Are the right people finding your project?
2\. Understanding: Can they explain what your product does and why it matters?
3\. Onboarding: Can they get started without unnecessary friction?
4\. Activation: Do they experience the product's actual value?
5\. Retention: What gives them a reason to return?
6\. Advocacy: Are satisfied users willing to recommend it?
My own community experience reinforced this thinking.
I worked on improving an announcement-heavy Discord community of approximately 400 members through onboarding, AMAs, engagement prompts and moderation.
The important lesson was that having members in a server doesn't automatically create participation.
The same applies to product growth.
A large Telegram community doesn't guarantee active users. High impressions don't guarantee adoption. A successful launch doesn't guarantee retention.
Project teams should be asking:
* Where are potential users dropping off?
* What is stopping newcomers from taking their first meaningful action?
* Do users understand the value of the product?
* What happens after their first interaction?
* Why should they return when incentives disappear?
These are questions worth investigating before increasing acquisition spending.
Growth research, product education, onboarding, content, community activation and partnerships should not operate as disconnected activities.
They should support one user journey.
Acquisition brings people in. Activation helps them experience value. Retention gives growth a foundation.
That's the difference between attracting an audience and building a product people continue to use.
30days of Web3 Growth | Day 6/30:
Documenting my journey, growth, and Observations
THE 3 STORIES EVERY WEB3 PROJECT PAGE MUST TELL.
A Web3 project can publish every day, announce partnerships and ship new features, yet still fail to communicate why anyone should care.
The problem isn't always a lack of content. Sometimes, it's a lack of a clear story.
Every project page needs to communicate three things:
1\. The Problem
What specific problem are you solving? Who experiences it, and why does it matter?
2\. The Product
What are you building, how does it work, and what practical value does it deliver?
Features explain what your product has. Benefits explain why people need it.
3\. The Proof
What evidence supports your claims?
Show product development, meaningful milestones, execution, real usage, and community progress. Don't just announce progress. Make it visible.
While researching early-stage Web3 projects, I've noticed how easily product communication gets buried beneath announcements and technical updates.
I've also worked to improve an announcement-heavy Discord community of around 400 members through onboarding, AMAs, engagement prompts, and moderation.
That experience reinforced an important lesson: having members doesn't mean you have an engaged community. Impressions don't mean people understand your product.
Project teams should ask themselves:
* Can a new visitor understand the problem you solve?
* Can they explain your product's value?
* Can they find evidence of your progress?
If your page cannot answer these questions, publishing more content may not fix the problem.
The problem earns attention. The product communicates value. The proof builds trust. Together, they create a story people can understand, believe in, and act on.
Day 5 of 100 founders in 30 days.
I disappeared for 5 days.
Life got busy, the replies were slow and started to feel stagnant, like I was pushing hard on a door that would not move.
Somewhere in that stretch I thought about quitting and am not going to pretend I did not, then I remembered the promise I made.
I said I would document the whole journey. Not only the wins, and the slow days, the doubt, and the days nothing seems to work.
So I am not giving up, and since I owe you all the story, here is everything I did while it felt like I was doing nothing.
1. ImagineMyHouse (AI interior, exterior and floor plan visuals).
I tested the free tier from my phone in mobile Safari, a free account starts with 20 credits and every design costs 10, so you get two designs.
That is two tries to fall in love with a product.
I ran two interiors and compared them with the kitchen example on the homepage.
To me, my results looked more AI generated than the examples the website shows. That is my opinion, and I only have two samples.
Then something broke. I uploaded an image without choosing a room type, like living room or bedroom, and the design failed. It was not my network.
That is a verified fact for my session only, and I do not know how many people hit it.
On pricing, I do not think it is bad, i do want to ask why the packs all end in 9.90.
My view is that 20 free credits is too small. A visitor needs room to see a result they love, and two designs, with a missed step that can fail, is a thin window.
2. Burnproof (a read only scanner for vibe coded apps).
Burnproof checks apps built on tools like Lovable, Bolt, Cursor, v0 and Replit for leaked provider keys, open Supabase data and missing security headers. It is run by NextPlay Solutions.
I went through the homepage, the agencies page, a sample report, the ownership page and the FAQ.
Then I did the scary part. I ran the free scan on my own project. It came back low risk, with a bill risk of 12 out of 100 and only some missing security headers. It read 4 scripts.
It did not run the Supabase check, so a clean result does not cover that. It is humbling to test your own work.
Now my read on Burnproof, which is not measured.
I saw no case studies or customer testing. The site is mostly text and needs a visual upgrade.
The homepage does not make you feel the pain enough, and I could not tell who the main customer is. To be fair, the clarity is okay.
How they get customers and how they onboard them are separate questions, and I am looking at those next.
3. BugByBug.
I reached out to the founder by DM. He replied on Discord and agreed to a call. His v2 launches in under a month.
We spoke on 9 November after a TikTok referral, and the call was cut short by network trouble.
I noticed his Discord is new, with about 5 channels, and needs a guide.
Then came the real work. He sent me an OpenTelemetry guide so I could plug BugByBug into my own project.
The guide assumed React and Vite. My site is plain HTML and JavaScript, which was my fault by the at coz i told him that tho.
A teammate and I checked every step one at a time, and the step by step guide did not fully work. It took long.
On 11 November I finally got it running on a separate test copy on Vercel, and the first test error showed up in their Error Station.
I then sent him my review in my own black and orange branding, with the problems stated precisely.
Here is my concern. If it took two of us this long, how will a vibe coder follow it alone? You cannot guide every user one by one with PDFs and calls.
Before launch, BugByBug needs Discord setup, a plan for getting customers, a clearer product message and a step by step onboarding guide.
I am behind on the numbers and am not done.
If you feel stuck right now, post the messy day anyway. Someone out there needs to see it.
RAZZYx Strategic Problem Solver
Comment WEB2 and I'll look at yours.
And if life has delayed you, don't be too hard on yourself. You may be watching people your age graduate, get jobs, start businesses, move into their own places and figure things out while you're still trying to make your own life work.
Keep trying, don't worry our time will come
Day 7/30: Getting users is only one part of Web3 growth.
Documenting my Journey, Growth and Observation
A Web3 project can spend money on KOLs, incentives, partnerships and community campaigns, yet still struggle to build an active user base.
The question isn't just how many people discovered your project.
It's what happened after they arrived.
I've been researching early-stage Web3 projects, and one pattern worth examining is the gap between attracting attention and creating a meaningful user experience.
Consider Farcaster.
When TechCrunch tested Farcaster's onboarding in February 2024, account setup took about four minutes. The platform also populated the new user's feed by letting them select interests and follow suggested accounts.
It addressed two common barriers:
* Making newcomers navigate crypto wallet setup before joining.
* Leaving new users with an empty feed and nobody to interact with.
Farcaster made the first experience easier to understand and use. TechCrunch
But acquisition and activation weren't the whole story.
In June 2024, The Block reported that Farcaster's daily posting activity had fallen from a peak of more than 1.5 million casts per day to below 700,000. Its coverage discussed how activity had grown around Frames and the associated incentives, then slowed. The Block
The lesson isn't that Farcaster failed. It's that attracting users and sustaining participation are different growth challenges.
Every Web3 project needs to examine six stages:
1\. Discovery: Are the right people finding your project?
2\. Understanding: Can they explain what your product does and why it matters?
3\. Onboarding: Can they get started without unnecessary friction?
4\. Activation: Do they experience the product's actual value?
5\. Retention: What gives them a reason to return?
6\. Advocacy: Are satisfied users willing to recommend it?
My own community experience reinforced this thinking.
I worked on improving an announcement-heavy Discord community of approximately 400 members through onboarding, AMAs, engagement prompts and moderation.
The important lesson was that having members in a server doesn't automatically create participation.
The same applies to product growth.
A large Telegram community doesn't guarantee active users. High impressions don't guarantee adoption. A successful launch doesn't guarantee retention.
Project teams should be asking:
* Where are potential users dropping off?
* What is stopping newcomers from taking their first meaningful action?
* Do users understand the value of the product?
* What happens after their first interaction?
* Why should they return when incentives disappear?
These are questions worth investigating before increasing acquisition spending.
Growth research, product education, onboarding, content, community activation and partnerships should not operate as disconnected activities.
They should support one user journey.
Acquisition brings people in. Activation helps them experience value. Retention gives growth a foundation.
That's the difference between attracting an audience and building a product people continue to use.
HyperHaul is a living pirate sea on Elysium. Fish, sail, fight and build your fleet.
The waitlist is open:
π $3,000 for the top 100 on the leaderboard (1st gets $300)
ποΈ NFT whitelist for the top 300
πͺ A numbered Founding Captain badge in the game for everyone on the list
Points for joining, for every task and for every friend you bring.
https://t.co/pi0UYWvH6H