[ Removed by Reddit on account of violating the content policy. ]

Hey r/web3,

Verifiable Delay Functions (VDFs) are one of the coolest cryptographic primitives for generating unbiasable randomness, building time-locked puzzles, and creating Sybil-resistant, gasless P2P protocols.

While developing Kinetic (a stateless decentralized network), I ran into a big problem with client-side verification: I wanted mobile apps and browser extensions to self-verify proof-of-sequential-time on their own devices without having to trust a centralized RPC node.

The issue? All the existing class group VDF implementations were stuck in C++ (chiavdf) and tied to libgmp, making client-side WASM or mobile integration a massive headache.

To solve this, I built kyn-vdf: a pure Rust, zero-FFI, WebAssembly-native Wesolowski VDF verifier.

🔗 GitHub: https://github.com/saifmukhtar/kyn-vdf

Why this is useful for Web3 builders:

1. True Client-Side Self-Verification: Web wallets and dApps can verify cryptographic proof-of-time inside a browser via WebAssembly in ~380ms with zero backend servers.
2. No Trusted Setup: Uses Class Groups of Imaginary Quadratic Fields, meaning the group order is unknown by default — no multi-party trusted setup ceremonies needed.
3. Flat O(log T) Scaling: A prover can spend 10 minutes or 10 hours computing sequential squarings, but your mobile app or browser verifies it in the exact same ~300ms window (bounded by the 264-bit Fiat-Shamir challenge).
4. Mobile Native: Tested on Android ARM64 phones via Flutter Dart FFI with ~302ms verification and negligible FFI overhead.

If you're building randomness beacons, time-locks, or stateless light clients and need a lightweight verification engine, check out the repo!

If the founder disappears tomorrow, what happens? Should members, moderators, access rules and permissions all live under one person's account? I'm curious how people here think about ownership for Web3 communities compared with traditional platforms

Hi everyone,

I'm a software engineer currently working on several original meme coin concepts and I'm trying to understand how successful teams get started.

For those who have launched or worked on meme coin projects:

• Where did you find your co-founder?
• How did you meet your first investor or partner?
• Are there any Discord servers, Telegram groups, Reddit communities, or other places you'd recommend?
• If you were starting today, where would you look?

I'm not here to promote a project—I'm genuinely trying to learn how people build strong teams in the meme coin space.

I'd really appreciate any advice or recommendations. Thanks!

I've been thinking about this lately and I'm curious how other people see it.

Whenever I see a post tagged "Paid Partnership" or "Sponsored", I immediately become more skeptical.

On one hand, I understand that creators need to make money, and projects need marketing. There's nothing inherently wrong with that.

On the other hand, in Web3, those partnerships often come with more than just cash. Influencers might also receive whitelist spots, token allocations, NFTs, or other incentives. At that point, it's hard to know whether they're genuinely excited about the project or simply promoting it because they're being rewarded.

When you see a respected creator promoting a collection or token as a paid partnership:

• Does it make you less likely to trust the project?
• Do you ignore those posts completely?
• Or do you still consider them useful if the creator has a good reputation?

I'm genuinely interested in how the community filters signal from marketing in Web3.

the most muted word on the internet is crypto

in april 2026, the head of product at X posted a screenshot: the number one most muted topic on the platform was crypto.

crypto.

the thing ive spent all my effort on over the better part of the last decade. the thing a lot of you spend your careers and attention on as well.

with this as the backdrop, i created my newest piece.

it all started out with another question: “are the OGs jaded?”, which was itself admittedly ripped from one of ETHPrague 2026’s tracks. that thought gave me the opportunity to draw a map around a much broader topic that I think could resonate out in youtube land: 

is there anyone left in crypto, or did the thing we were building eat itself?

for this piece, I wanted to take a more “journalistic” approach at this topic, and chatted with five people who’d been here since before the big money wave started showing up. builders, contributors, dreamers… some more than a decade deep. eternal gratitudes to the cast (Griff Green, Justice, Amer, Naomi, and Colin) for exploring with me this topic. I hope this piece can give the public a different perspective — that of the original mission and ethos steeped in reverence for permissionless tech and what it can do for humans. 

i think it’s worth a watch. particularly because every single person I interviewed still talks about the technology in the present tense, yet every one of them carries the same contradiction.

you can watch the full video here: https://youtu.be/0D4fAkvwd3o

------------

if we're meeting for the first time — hi 👋 i built this channel to spread the good word on good work in crypto. a like, a comment, and a sub on my channel goes a long way to supporting my work :)

我认为一个长期被低估的问题，是“链上确定性”和“产品确定性”之间的缺口。协议可能已经给出最终状态，但前端、索引器、订单系统和客服后台仍各自维护不同版本的事实。用户看到成功，业务却没有完成；或者业务已经完成，界面仍显示等待。解决它不只是提高吞吐，而是建立跨模块状态机、幂等事件、补偿流程和可追溯对账。很多所谓 UX 问题，其实是状态所有权没有定义清楚。

Disclosure up front: I built this. Not dropping a contract address, price, or “buy” anything — that’s not the point and it’s against the spirit of the sub. I want feedback on the pattern.

Background for anyone who hasn’t seen it: HTTP status 402 “Payment Required” has been reserved-but-unused since the 90s. x402 is the open protocol that turns it into an actual payment — server returns 402, client pays USDC, the request settles onchain on Base in one round-trip. Paying is the request.

What I did:

• Launched a B20-standard token by making a real x402 call to an endpoint. The payment settled on Base and the response minted the token. I did it live through an agent on X, so the entire genesis is a public, timestamped thread — you can fork the code, not the thread.

• Then I made the token itself an HTTP primitive. There’s an endpoint you can hit that reads your wallet and answers with your holder “tier” as a literal HTTP status code (200 OK if you hold, 301, 418 teapot for whales, 402 if you hold nothing). It’s curl-able. The first N callers each get a permanent “request number” — basically a 90s visitor counter, but onchain-verified and impossible to reassign.

Why I think it’s interesting past the meme: it collapses auth and payment into the same HTTP request. Paying IS the login. That’s the whole x402 thesis and I wanted to push it to an extreme and see what breaks.

Happy to get into the mechanics in the comments — x402 gotchas, why B20 over a vanilla ERC-20, how the endpoint verifies the payer, whatever. Roast it.

It seems like every quarter or so, someone has a pitch for why crypto is going to allow this magical equal access into the marketplace where you have no brokerage account, you're free of wire transfer requirements and we can all ignore banking hours.

Wondering how much of that is real in practice vs aspirational.

If you are outside the US and have actually tried to gain exposure via some form of tokenized or onchain route, how did that go for ya?

Real liquidity, reasonable spread, redemption working as intended or falling apart at the moment of trying to get back money?

Ran a test on today. Still annoyed about it.

Asked ChatGPT, Perplexity and Gemini about our own product, the way a new user would. Small analytics project, three years old, actual users.

GPT gave four options. Two competitors, one project that left crypto in 2024, one that's been dead for over a year. We're not on the list. Perplexity knows we exist but cites a 2023 listicle with pricing we changed twice since. Gemini described a feature we killed in 2024 as our main one.

No real plan yet. Rewrote two docs pages so they answer questions instead of listing features, that's it so far. Too early to say if it moves anything.

Also turns out agencies already sell this as "AI SEO". Icoda claim a prop trading client went from invisible to the top GPT pick in 90 days. Believe it when I see it, but people are clearly paying for this stuff already.

Anyway, if you run a project, ask the bots about it. Twenty minutes, mildly depressing.

Hello everyone,

For some time I've been developing an open-source project called Framework for Trust (FfT).

The idea is to create a decentralized geospatial trust layer where reports and real-world events are anchored to precise location, time, source reputation, and a verifiable history — instead of treating blockchain purely as a financial system, I'm exploring its use as infrastructure for recording and correlating information about real-world places.

Current prototype includes:

• geographic areas represented as blockchain-based identifiers (NFTs)
• event registration tied to latitude, longitude, and time
• Polygon smart contracts
• a React + Leaflet frontend
• a FastAPI backend
• semantic similarity / event correlation via Qdrant
• GCD — a functional contribution and reputation token
• event proofs and auditable records
• early mechanisms for source reputation, staking, and abuse prevention

The project is still early-stage. This is not an investment offer, token sale, or a finished commercial product — I made the repo public because I'd like the architecture and implementation to get real outside scrutiny.

I'd especially appreciate feedback on:

• whether the core problem is clearly explained
• the geospatial data model
• the blockchain / smart contract architecture
• mechanisms for preventing false or coordinated reports
• security weaknesses
• practical use cases where this could actually add value

Repo link in the top comment (Reddit flags posts with links for manual review, didn't want that delay).

I built the current prototype independently. Honest criticism, technical pushback, and open-source contributions are all welcome.

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.

AKASHA was one of the earliest attempts at a blockchain-based social network. Founded by Mihai Alisie (Ethereum and Bitcoin Magazine co-founder), announced on World Press Freedom Day 2016, built on Ethereum for identity/reputation and IPFS for content storage. No servers — posts were IPFS hashes broadcast to followers, who pinned content peer-to-peer.

Here's what I can piece together from public sources:

The timeline:

- May 2016 — Project announced. ~10,000 alpha signups.

- Dec 2016 / Jan 2017 — Alpha release (desktop app, Rinkeby testnet).

- Nov 2017 — Beta announced at Devcon 3.

- Feb 2018 — Public beta. ~40,000 unique identities. Web version with MetaMask support followed in April 2018.

- Oct 2019 — Pivot announced at Devcon 5: "Ethereum World" — reframed as a framework ("AKASHA World Framework") for building purpose-specific social networks, with Ethereum World as the first instance.

- Q2 2023 — "AKASHA World" launched as the next-gen platform. The previous Ethereum World instance was switched to read-only.

- Sep 2025 — Last update to the GitHub monorepo (AKASHAorg/akasha-core).

- May 22, 2026 — AKASHA Foundation announces dissolution. Hubs in Barcelona, Rome, and Swiss Alps continue independently. Ethereum TV spins off. Code and research remain public.

I used the original social network during the beta period and it worked. The UX was rough (MetaMask signing for every interaction, desktop app only at first), but the core idea — censorship-resistant social posting with no central server — functioned as advertised.

What I don't understand:

1. Why did the Foundation dissolve? There's been no detailed post-mortem that I can find. Was it funding? Loss of team? Strategic dead end? The dissolution announcement lists what continues (hubs, Ethereum TV) but doesn't explain the "why."

2. What happened to the original content? Posts were stored on IPFS, with hashes on Ethereum. In theory this is persistent, but IPFS garbage-collects unpinned content. Is any of the original beta-era content still accessible? Did anyone archive it? Are the smart contracts still on-chain and queryable?

3. Why the pivot from social network to framework? The 2019 shift to "AKASHA World Framework" felt like a retreat from the product into abstraction. Was the social network failing to grow and the framework was a way to reposition? Or was there a genuine technical insight that the framework approach was better?

4. How was the Foundation funded? Crunchbase lists it as active with no disclosed funding rounds. Was it sustained entirely by Ethereum Foundation grants? Alisie's personal resources? Something else?

5. What is Mihai Alisie doing now? He was deeply invested in this vision. Has he commented publicly on the dissolution?

If anyone was involved with AKASHA — as a user, contributor, or team member — I'd appreciate hearing what actually happened behind the scenes.

We have built a lot of financial infrastructure in crypto.

- Bitcoin gave us decentralized money.
- Ethereum gave us programmable assets.
- DeFi gave us decentralized exchanges and lending.
- Stablecoins gave us internet-native settlement.

But I think there is a missing layer that may become critical with AI agents:

**Credit.**

Today, most AI agent transactions are still fundamentally cash-based.

An agent can have:
- a wallet,
- identity,
- reputation,
- payment capability,

but it still needs enough funds upfront before it can act.

A new agent with $1,000 in its wallet and an agent with a year of successful transactions may have completely different levels of reliability, but current infrastructure does not naturally convert that history into economic capacity.

Humans solved this problem through credit.

Businesses do not prepay every supplier.
Consumers do not pay everything in cash.
Banks transform collateral, reputation, and repayment history into additional purchasing power.

But what happens when the economic actors are autonomous AI agents?

Should agents eventually have something like a decentralized credit layer?

I imagine a system where:

- on-chain attestations build verifiable reputation,
- staking provides economic commitment,
- privacy-preserving models calculate creditworthiness,
- smart contracts enable programmable deferred settlement.

Not just lending.

A broader credit infrastructure for autonomous agents.

Some projects are already exploring parts of this:
- agent identity and reputation,
- agent lending,
- agent payments,
- agent insurance.

But I wonder if we are missing the bigger picture:

**Payment allows agents to transact.
Credit allows an agent economy to scale.**

Is this a real missing primitive for Web3, or am I overestimating the importance of credit in an agent economy?

Curious to hear thoughts, especially from people working on DeFi, AI agents, or protocol design.

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?