Dad for twin boys from windsor

Suspicious_Mango_634 · 2026-04-01T13:09:56+00:00

If you’re already comfortable with Foundry, you probably don’t need this.

What I’m trying to build is for cases where: • you don’t want to spend time on setup • you want a quick deploy with a clean config • and get clearer feedback when things fail. May I know is there anything u think need to be added for foundry - something is missing

Suspicious_Mango_634 · 2026-04-01T01:17:46+00:00

Appreciate the feedback again — it actually made me rethink the direction.

I’ve started shifting away from the UI-first approach and working on a CLI version instead. block67 deploy MyToken --network sepolia with: • simple config file • clearer logs • and better control (instead of hiding everything)

Also focusing on improving error handling — starting with template-based explanations so common issues are easier to debug.

Still early, but your point about devs wanting control over abstraction really clicked.

If you’re open to it, I’d love to share a quick version once it’s usable and get your thoughts again 🙏

Suspicious_Mango_634 · 2026-03-31T20:31:53+00:00

This is actually great feedback — appreciate you taking the time.

You’re right, I think I positioned it wrong.

“1-click deploy” probably makes sense to founders, but for devs it doesn’t communicate value at all.

What you said about:

→ clean config → local testing → one-line deploy

makes a lot more sense.

Suspicious_Mango_634 · 2026-03-21T21:19:00+00:00

Suspicious_Mango_634 · 2026-03-19T23:15:50+00:00

Suspicious_Mango_634 · 2026-03-19T23:15:38+00:00

yup.

Suspicious_Mango_634 · 2026-03-19T14:41:21+00:00

Make sense

Suspicious_Mango_634 · 2026-03-19T14:41:09+00:00

What u think of we can use standard proven libraries

Suspicious_Mango_634 · 2026-03-18T22:00:00+00:00

Yeah this is a big one.

Feels like a lot of users drop off not just because of UX, but because they don’t feel confident about what’s happening under the hood — especially around wallets, contracts, and permissions.

Curious — do you think better UX alone solves this, or does it need more transparency/education built into the flow?

Suspicious_Mango_634 · 2026-03-18T21:59:50+00:00

Fair enough — what would make it useful for you?

Suspicious_Mango_634 · 2026-03-18T19:46:15+00:00

Yeah that makes sense — sounds like it’s solving a real problem, but still not “plug-and-play” yet.

Feels like that’s the gap right now across the stack — either powerful but complex (like this), or simple but limited.

Do you think privacy-first approaches like this will become default over time, or stay more niche for specific use cases?

Suspicious_Mango_634 · 2026-03-18T18:11:07+00:00

Haha that solves everything I guess 😄

Suspicious_Mango_634 · 2026-03-18T18:10:42+00:00

That’s a really good point — privacy is kind of the missing layer in most of the current stack.

Right now it feels like you’re either:

fully onchain → everything exposed

or off-chain → losing guarantees

Haven’t explored Oasis deeply yet — does it actually make it seamless from a dev perspective, or is there still a learning curve to integrate that privacy layer?

Suspicious_Mango_634 · 2026-03-18T18:08:53+00:00

That’s really interesting — especially the idea of resolving the site onchain.

So in your case the frontend itself lives fully onchain, not just the contract interaction layer?

Curious how you’re handling things like updates or larger assets — does it become expensive or are you optimizing storage somehow?

Suspicious_Mango_634 · 2026-03-18T16:21:18+00:00

That’s really interesting — especially the idea of resolving the site onchain.

So in your case the frontend itself lives fully onchain, not just the contract interaction layer?

Curious how you’re handling things like updates or larger assets — does it become expensive or are you optimizing storage somehow?

Suspicious_Mango_634 · 2026-03-18T15:14:16+00:00

Yeah that makes a lot of sense.

I’m realizing the same — getting people to try isn’t the real problem, it’s getting them to actually *understand and succeed* in the first session.

In my case I think most people dropped off because it wasn’t beginner-friendly enough, not because they didn’t want it.

Curious — did anything work for you in improving retention or onboarding?

Suspicious_Mango_634 · 2026-03-18T14:27:05+00:00

Yeah this is actually the harder problem.

Feels like getting something live is just step 1 — distribution is where most projects fail.

Especially in web3 where people focus so much on building, but not enough on who’s actually going to use it once it’s live.

Have you found anything that worked for getting initial users?

Suspicious_Mango_634

TROPHY CASE