A lot of "no backend" web3 projects still quietly have a server doing indexing/state logic that isn't really optional. Wanted to share how BitClaw is actually put together, since the answer to "where does the state live" is a bit more interesting than usual:

Contracts: written in sCrypt — TypeScript-like syntax, compiles to Bitcoin Script. No separate contract language to learn if you're already a JS/TS dev. Deployed as real UTXOs; a generic adapter layer (constructor params, state props, methods) means any module can attach a contract without a bespoke spend path per feature.

Workflow layer on top: multi-step processes — branch / quorum-signoff / conditional-payout / sub-workflow — that chain contract calls together. A headless runner executes these unattended (systemd service, not a browser tab someone has to keep open), and a separate "keeper" service watches for on-chain conditions resolving and auto-fires the next contract call (a payout, a refund) with no human clicking anything.

No server database, but indexers are real and necessary: the "no backend" claim only holds up if you're honest that reading chain state directly (walking OP_RETURN history to reconstruct "what's the current state of this thing") doesn't scale for a live UI. So there are per-topic indexers (BC_SNAP1-signed snapshots) that pre-compute read views — but they're not a source of truth, they're a cache: every snapshot is signed by a scoped key, the client verifies the signature locally, and if an indexer disappears or lies, the client falls back to scanning the chain directly. Multiple people can run the same indexer against the same public anchor data — it's not my server or nothing.

The interesting design tension: indexers make it feel like a normal app (fast reads, filtering, search), while the actual authority for "is this true" stays on-chain and independently re-derivable. Curious how other web3 projects have drawn that line — where do you let an indexer be "just a cache" vs. where does it quietly become load-bearing?

Are web3 hackathons actually useful for beginners, or do they mostly help people who already know what they're doing?

I've been slowly learning a few Solidity basics, deployed a couple things on testnet but I keep seeing hackathon announcements and I'm not sure if I'd just be dead weight on a team, or if it's actually a reasonable way to learn faster than tutorials alone.

For people who've done one: did you go in knowing what you were doing, or did you learn most of it during the event itself? And if you went in underprepared, was it still worth it or just frustrating?

Hey guys, I’m looking into projects or builders that can help enlighten me with some on/off ramp insights they had with providers they implemented in their platform:

1. Who owned the wallets and end users - did the provider deliver straight to your users, or through wallets you managed? Who owned the user relationship?

2. What’s been the biggest ongoing pain with your ramp provider - the thing that still creates support tickets, drop-offs, or manual work today?

3. If you were choosing a provider again, what would you check first that you didn’t check the first time?

Hey, I am absolutely new in web3 domain, and I want to know what are the top topics and things going in web3.

Like I am a software developer I know in current market AI revolution is hot topic, I want to know exactly same for web3.

So it would be appreciated if you help me to know.