Hot take: a lot of dev programs are built around certificates, prizes, or grants, but most developers actually just want to build skills and get a career going. Are we designing incentives around the wrong motivation?

Read something a while back that put numbers on this, survey of like 27k developers who joined web3 training programs. Only 7% cared about the certificate. Only 6% were in it for a startup or grant/bounty. Everyone else just wanted skills and a job.

Meanwhile most outreach programs in this space are still built around hackathon prizes, grants, and certs, basically optimizing for the 6-7% while ignoring what the majority actually showed up for.

Curious if people building or running these programs have noticed the same gap.

(Disclosure: work at Rise In, that's their data, happy to share the link if anyone wants the full report.)

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?

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?

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.

Right now, Web3 doesn't have a truly free naming system.

That means millions of developers and users are stuck relying on either centralized registrars or expensive decentralized alternatives just to own a digital identity.

I wanted to fix that.

So I built Kinetic.

What is Kinetic?

Kinetic is a stateless, zero-fee, peer-to-peer naming system.

It lets anyone in the world claim a decentralized domain name securely, without needing a bank account, credit card, or any cryptocurrency at all.

Instead of central servers or heavy blockchains with gas fees, Kinetic runs as a lightweight background daemon in rust.

It handles name registration, publishes DNS records, and gives you access to .kin domains through split-DNS.

Planning to launch publicly on Tuesday, July 21st.

Edit: We're taking a little more time before the public launch while we finish verifying the governance logic. We want to make sure there are no protocol-level logic bugs that could require a hard fork later. Quality and stability are more important than rushing the release.

I've noticed many companies stopped celebrating community size.

Focus has significantly shifted from 100k Telegram members

To:
• How many people came back this week?
• How many transactions happened because users found value? (not for incentives)
• How many developers are building on the protocol
• How much revenue is being generated?
• Are contributors staying after the campaign ends?

Mind you, this isn't just a web3 trend.

When Satya Nadella took over Microsoft, the focus shifted from protecting legacy businesses to building products people actually used.

At Meta, Mark Zuckerberg has repeatedly emphasized meaningful engagement over surface-level reach, especially as AI changes how products are discovered and used.

Down to crypto, we've seen the market reward projects with real usage over those with inflated social numbers.

To build a durable company today, you must understand something:

Attention is rented. Retention is earned.

A few years ago, shipping faster than everyone else was enough.

Today, product ideas get copied in weeks.

Features become table stakes.

The companies pulling ahead aren't simply building communities around their products.

They're building products that become more valuable because people participate.

That's why we're seeing it across:

• Creator economies - where audiences become contributors.
• Prediction markets and sports trading - where every participant improves market depth and price discovery.
• Consumer crypto - where identity, memes, and shared ownership drive adoption as much as tech.

Here, culture is no marketing literature. It has become a growth engine.

The teams that understand this won't just acquire users.

They'll build ecosystems people choose to belong to.

This might be slightly heretical for web3, but I keep wondering if provenance is actually more interesting than ownership.

Ownership tells you who has something now.

Provenance tells you where it came from, how it changed, what it influenced, who contributed, what it became.

With AI, remixes, sampling, forks, memes, code, music, all of it getting mashed together constantly, that feels like it might matter more and more.

Do people think provenance is going to become a big deal, or is it still too niche?

We spend so much energy debating L2s, onchain identity frameworks, consensus mechanisms, chain superiority, etc.

But if you look at actual day-to-day use cases, the rails driving Web3 adoption aren’t flashy tech stacks or narratives.

It’s just assets(dollars) moving across borders seamlessly.

Almost every serious infrastructure discussion right now revolves around Stablecoins.

Because they actually solve the cross-border, and settlement friction points that web2 still controls.

As of today, this is “the best adoption pilot” for the ecosystem.

The true decentralized web will be built on the back of boring utility as this.

Hey Web3 enthusiasts!

I'm new here in this forum so I might have overlooked something. Bear with me then!

So I'm still looking for an easy to use Web3 social network or social media site.

I tried various over the years and they were all hard to use, buggy and made me pay and/or jump through hoops just to join.

Plus even when I managed to the communities were small and mostly focused on crypto etc. itself.

Are there tools made for the general public as well, not just the geeks?

I'm somewhat active on Mastodon but it still feels more like a missing link between Web2 and 3.

It's more like logging in at someone else's WordPress installation.

Lately I failed to even set up a profile on Diamond App because you need to pay and use a wallet first.

As of now I'm still mostly stuck with billionaire led social networks like Facebook, LinkedIn or Reddit.

Any suggestions?

And yes, I have used the search feature and clicked some links but most were broken by now.

Hi everyone!

After several months of learning Solidity, I finally deployed my biggest project to Arbitrum One Mainnet.

The game currently supports:

• PvE
• PvP
• Guilds
• Guild rankings
• Achievement NFTs
• IPFS metadata
• Multi-chain deployment

The project is completely open source and uses:

• Solidity
• Foundry
• ethers.js
• TypeScript

GitHub:
https://github.com/brunolcarli/simpleRPG

Demo:
ethereum-simple-rpg-game.vercel.app/

I'm always looking for feedback from the Web3 community. If you had to add one feature to an on-chain RPG, what would it be?

Ideas that later define ecosystems rarely begin as obvious.

A few years ago:

→ “Prediction markets” were dead liquidity graveyards
→ “Decentralized AI” felt speculative
→ “Restaking” was not in mainstream crypto conversations
→ “DePIN” was reduced to “hardware projects.”

Today, capital, talent, and attention are moving aggressively into each.

The pattern is familiar.

Breakthrough companies are often built during the period when the idea still feels inconvenient to explain

That phase where interest feels limited, and the early audience seem unconvinced is not always a warning sign.

Sometimes it is evidence that you are early.

Being early does not guarantee success.

Execution still decides outcomes.

But if you are building something thoughtful and finding yourself explaining the same concept repeatedly before people see it

that discomfort alone is not a reason to change direction.

Some of the strongest positions are built before consensus arrives.

If everyone immediately understands your startup idea,

there is a chance you are arriving after the market has already taken off.

Every time I sit down to build a smart contract, I hit the same wall. Decentralization, security, scalability, you only get 2.

The more audits I do, the more obvious this becomes. Yet every project markets itself as having all three nailed.

99% of crypto projects marketing "decentralized AND scalable AND secure" are scamming you on at least one of those words.

The trilemma is real. Pretending it doesn't exist is how people lose money.

Do you actually factor this in when picking projects, or is everyone just ignoring it until they get burned?

As we all know gta 6 is the most hyped game as of now and it's probably launching around November. Gta 6 would be pretty realistic for it to attract VR users. Plus there would be in app purchases obviously, buying and selling inside the game and all of this does hint that gta 6 can be a metaverse project in itself too. Even if it's not , it should boost web3 and other nft projects. What's your take on this ?

Hello,
I have been a Kraken verified user since 20219, until last week I got email to verify my address. Out of their two verification methods, I was skeptical about their GPS method and opted for document upload. Their system is not a le to verify my Utility bills.

I created a support ticket about it, no response since 11 days.

So I went on r/krakensupport to ask others if they got any updates and Kraken banned me apparently because that comment violates their rules. I asked them about how it violates, no response.

And if you browse their two official subs here, it is now clear to me that they are carefully removing any post or comment that would threaten their authority.

So I am posting on this neutral ground here to ask:

What other solutions are available to non US people to be able to fill wallet with crypto to use - I’m into NFT and I’m not able to load my wallet now.

Because it would appear that it’s no more reliable to use the once “reliable” Kraken.

Audits review one commit, but smart contracts, ZK circuits, verifiers, dependencies, and proving artifacts keep changing afterward.

​

Should high-risk changes automatically block CI, or should every case require human review?

​

Curious how Web3 teams handle this today: repeated audits, baseline comparisons, artifact hashes, or something else?

I'm building a multichain crypto wallet alone. No VC, no team. Alpha just dropped. Here's the honest status

About 2 months ago I got frustrated enough with the current wallet landscape that I decided to just build my own.

Not as a side project. As a real competitor.

The problem I kept hitting:

ETH on MetaMask. SOL on Phantom. BTC on a separate wallet. XRP on yet another one. Every chain has its own app, its own seed phrase to manage. It's 2025 and we still don't have one wallet that actually does everything well.

So I built Wally.

Wally has dApp integration as metamask and phantom wallet.

One browser extension. Every major chain. Single seed phrase. Clean UI. No bloat.

Honest alpha status right now:

✅ Full EVM (ETH, BSC, Polygon, Arbitrum, Base and more)

✅ Solana + SPL tokens

✅ XRP

✅ dApp connections

✅ AES-256-GCM vault encryption

🔜 UTXO balances (BTC, LTC etc) — next week

🔜 UTXO sending — shortly after

🔜 Beta — once UTXO is complete

What I'm not doing:

No VC money. No transaction tracking. No data selling. No referral spam.

Why post now before beta?

Honestly I want real feedback from real users before I call it beta. Alpha testers who find issues now shape what Wally becomes. That matters more to me than a clean launch announcement.

Attached is some screenshots of the extension/app.

Feel free to give feedback.

Edit: well I am not allowed to attach any screenshots unfortunately:(

Also launching Wally Street NFTs — a free Genesis collection on Solana for early supporters. Market Emotions series. Bull, Bear, Chop, Pump. Mint requires Wally wallet.

Solo dev from Sweden 🇸🇪🐋 — happy to answer literally any technical question.

What's happened in the crypto/web3 ecosystem more broadly? Is everything being abandoned to build onchain TradFi? What happened to decentralization and changing the shape of finance? Was that just a necessary step on the ladder towards more of the same, but this time on blockchains?

It seemed straightforward to me that a web3 worth a damn would do two things-

1. Abstract computing resources and protocols to recreate web2 in decentralized form
   
2. Create a currency that is beyond any state’s control

I assumed this would come with some computing overhead at first, something that would eventually be made moot with ASICs once it became popular. I assumed the currency would be closely tied to the cost of computing resources and that would compel people to rent their computers out to the network as nodes.

If this were possible it should have happened by now. I’m starting to wonder if it’s the math (maybe centralization will always win) or if other forces are at work.

Hey 

I've been building AI agents for Web3 for a while now, and I decided to open-source my toolkit. It's called web3-agent-kit and it's designed for developers who want to build AI-powered onchain tools.

What it does:
- Multi-chain support (Ethereum, Base, Polygon, Arbitrum, BSC, Solana)
- DeFi integrations (Uniswap, Raydium, Aave, etc.)
- Built-in spend governor for safe agent operations
- LLM integration (OpenAI, Anthropic, Claude)
- Real-time balance and portfolio tracking

GitHub: https://github.com/ulsreall/web3-agent-kit

MIT licensed. Would love feedback from the community.

What features would you like to see next?

Think about that for a second.

When the car showed up, there were people who said it was too complicated. Too expensive. Too unreliable. Horses had worked for thousands of years — why change?

The car didn’t care.

Right now there’s a whole crowd saying crypto is too complicated. That normal people don’t want wallets. That banks work just fine. That we should hide the blockchain so it doesn’t scare anyone.

These are the same people who would’ve voted to keep the horse.

I just sent money across borders in USDC on Solana. It arrived before I put my phone in my pocket. Cost me less than a cent. No bank approved it. No intermediary took a cut. No business days. No forms.

Meanwhile SWIFT — the system the financial world tells you is “how international money moves” — takes up to 5 days and eats up to 6% of your transfer in fees.

One of these is the horse.

One of these is the car.

You don’t have to like it. You don’t have to understand every technical detail.

But the road is already being built.

And it’s not being built for the people still looking for a place to water their horse.

People keep arguing about whether Web3 is “real” or just hype.

Meanwhile:

• Billions in real money are moving through DeFi protocols without a bank’s permission  
• Artists are getting paid directly by fans with zero middlemen taking 30%  
• DAOs are making real governance decisions with real money on the table  
• People in countries with broken currencies are using stablecoins to actually survive

You know what Web3 doesn’t do? Ask for your opinion.

The internet didn’t wait for newspapers to approve it. Email didn’t wait for the post office to give it a green light. Web3 is doing the exact same thing right now, in real time, whether your favorite tech pundit thinks it’s a scam or not.

The people calling it dead are the same people who said smartphones were a toy.

You don’t have to love it. You don’t have to invest in it. But if you’re a developer, a creator, a business owner, or just someone who moves money around — ignoring it isn’t neutral. It’s falling behind.

The door is open. Some people will walk through it. Some people will stand outside complaining the door exists.

That’s fine. Both groups have always existed.

Which one are you?

a few months ago I posted an idea about a method of decentralized communication without needing a server to pass the messages through; essentially a dead-drop system; and someone told me that if I wasn't serious about it, or wasn't willing to put in the work, that It was worthless. so I spent the last few months working out the ideas; and then spent time working out learning what my amateur brain could about protocols; and got familiar with Claude's help and spent a lot of time on this project. and well, now its time to put up or shut up.

I built an open protocol for messaging where the server is *structurally* unable to link who's talking to whom — not "we promise not to log it," but the architecture never has the data to begin with.

Zero registration, identity derived from secrets you hold, a dead-drop transport that can't see the social graph.

It's a working draft, AGPL, and almost certainly has holes I can't see. Genuinely want people to try to break it.

Spec + reference code: github.com/cottenwess/sovereign-comms

I’ve been in crypto/Web3 for a while and lately I can’t shake this feeling that everything is kind of… scattered.

Before it felt like there was always "the thing" everyone was excited about:
DeFi, NFTs, L2s, etc.

Now it feels more like:

• Bitcoin is doing its own macro/ETF thing
• Ethereum is just quietly building
• L2s are everywhere but none of them feel like “the main one”
• new apps keep launching but nothing really sticks yet

It’s not necessarily bad, it just feels less focused than before.

Maybe that’s what maturity looks like and I’m just used to hype cycles.

Do you guys also feel like Web3 lost a bit of its direction… or is this actually the healthiest phase so far?

Went looking for prior art on this and found almost nothing. Either nobody's solving it, or everyone's quietly going native. Curious which.

The problem: if you build a self-custody PWA, iOS evicts it from memory after a few minutes in the background. SessionStorage dies with the web view. Every resume, the user is back at the login screen.

Native apps don't have this. They persist state to disk and pretend they never died. PWAs are ephemeral by design.

The easy fix: wrap in Capacitor, ship a native app, problem solved in one config line.

Why we didn't: App Store distribution puts every user in Apple's purchase records. For a product whose whole pitch is "no email, no phone, no identifiable user list," that's not acceptable. So we stay PWA-first and have to live within the constraints.

What worked: WebAuthn PRF extension.

Short version: your Touch ID / Face ID chip can hand back a deterministic 32-byte secret, derived from a salt you give it, only after a successful biometric scan. We use that secret as the AES key that encrypts the session key at rest in IndexedDB.

Result: the encrypted blob on disk is dead weight without a real fingerprint or face. iOS can evict the PWA all it wants. Next open, one Face ID scan and the session is back. No password retype, no compromise on self-custody.

Things I learned the hard way: Safari returns the PRF result on get() not create(). iOS 18+ required for standalone PWA. WebAuthn calls only work inside a user gesture, not timers. And crypto-subtle-decrypt takes three args, not two, cost me an evening.

The honest question: how anonymous does your user base actually need to be? Most projects that claim privacy-first don't really need to avoid the App Store. They just say they do. Which makes me wonder if there are maybe 12 of us in the world doing hardware-bound at-rest encryption in a PWA.

Anyone else? Especially curious about the pre-iOS-18 fallback story.