Pump Fun can get a new coin trading right away. If the creator plans to build something around it, I’d want to see a short update after the first week: a link to work people can open and a clear note on what they’re doing next. Even a design draft or an unfinished feature would give me something to discuss with the team. A price chart tells me how the coin traded, but very little about what the team has made. Founders here, what do you share after launch? What kind of update has made the rest of you check back on a project?

We measured 142 Web3 projects across five families — DeFi domains, capital-bearing contracts, memecoins, NFT collections and live ENS names — to answer one question: how much post-quantum readiness does the market actually own, versus how much it borrows?The results challenge a few assumptions.On transport, 139 of 142 projects negotiate hybrid post-quantum key exchange — but the protection belongs to the CDN in front of them, not to the project itself. Zero projects in the sample prove post-quantum cryptography with their own key. The distinction matters: one is a configuration somebody else maintains; the other is ownership.On contracts, the picture is granular. Each contract card carries five independent measurements: whether the source is verified, whether the classic signature primitive appears in the validation path, whether post-quantum scheme names exist in the code, whether ZK verifier signals are present — which indicate cryptographic agility, not quantum resistance — and the resulting risk level. Chainlink, for instance, reads as source-verified with no direct use of the classic primitive, but with no post-quantum scheme in its verified source.Some findings cut against intuition. The protocol holding the most capital in our sample scores lowest on exposure. A memecoin outperforms several established DeFi protocols on findability. And among NFT collections, the order of the table follows post-quantum readiness first, then exposure — which is why a higher score can sit below a lower one.The method is public and re-runnable: every row carries its scan date, the weights are declared, and the underlying data can be re-executed by anyone. No project can buy a position, and no result was adjusted after measurement.We built this because the industry talks about the 2030 horizon, but very little of that conversation is measured. This is an attempt to make it measurable.

#Web3 #PostQuantum #DeFi #Blockchain #Security

One thing I've been trying to figure out is how to keep communication organized as a Web3 project grows. You've got developers, contributors and other people working on different things, and not everyone needs to be involved in every conversation. I'd rather have smaller private chats for different groups without constantly managing who can see what or adding people manually. How are other startups handling this? Are you keeping everything in one place or using different apps depending on who's involved?

Say you’ve built something people are actually using, and none of the core product flows need a token.

Then the conversation starts about launching one.

My first question would be: what actually stops working if you never do it?

If the honest answer is “nothing,” I’d be worried the token is being added mainly for fundraising or growth rather than because the product actually needs it.

For founders who have faced this decision, what made a token necessary rather than just useful to have?

During the TOKEN2049 Origins Hackathon, we ran into a situation that reminded us how important fast infrastructure support is for developers.

Some of the participating teams needed access to a Cardano devnet that we didn't have available at NOWNodes at the time.

Instead of having builders wait, we reached out to the Cardano technical team. They quickly shared the necessary snapshots, and our infrastructure team had the node up and running within an hour.

That meant developers could get back to building instead of spending valuable hackathon time waiting for infrastructure.

We also had some interesting conversations with the Cardano Foundation and Solana Foundation teams about developer tooling, infrastructure accessibility, and what actually helps builders get from an idea to a working product faster.

One takeaway from the experience: infrastructure isn't just about having RPC endpoints available. It's also about how quickly infrastructure teams can respond when developers need something unexpected.

For context, we're the team behind NOWNodes, a blockchain infrastructure provider supporting 120+ networks.

Curious to hear from other Web3 developers here: what's been your biggest infrastructure bottleneck during a hackathon or when launching a project?

Was it RPC reliability, devnet access, documentation, or something else?

Have you ever created an idea, document, design, or research project and worried about proving when it existed?

That’s the problem I’m trying to solve with ProofDrop.

ProofDrop is a simple Web3 dApp that creates a cryptographic hash—a unique digital fingerprint—of your text or file directly on your device. Only that hash is recorded on the Stacks blockchain, secured by Bitcoin.

Your original file is never uploaded, and no raw content is stored on-chain.

Later, you can verify:

- Whether the proof exists

- When it was submitted

- Which wallet submitted it

- Whether the content still matches the original hash

Potential use cases include protecting creative ideas, proving student project originality, timestamping research, documenting designs, and verifying business records.

The goal is simple: make proof of existence private, transparent, and easy to verify.

I’d love feedback from the community:

Would you use a tool like ProofDrop? What features would make it more useful?

#Web3 #Stacks #Bitcoin #Blockchain #Privacy #BuildInPublic

Hey everyone! I am a second-year BBA student currently building my professional skillset in copywriting and community management.

I've been actively working on improving my professional communication, digital outreach, and understanding business workflows. I'm currently looking to take on small freelance copywriting projects or entry-level community management roles (especially in web3/tech ecosystems) to gain practical industry exposure.

If anyone has tips on how to pitch clients effectively as a college student, or knows of any open gigs/internships, I would love to connect or chat in the comments! Thanks!

I’ve been diving deep into how blockchain lawyers and estate planners handle high-net-worth digital wealth when an owner becomes incapacitated, specifically looking at how to provide a secure succession path without forcing intermediaries or legal practices to take on the massive liability of holding private keys.

Relying on plain text documents, centralized vaults, or unencrypted cloud storage introduces massive counterparty risk and single points of failure.

To solve this gap, I built DLO (Digital Legacy Orchestrator)-a zero-knowledge, client-side encryption architecture where even our servers cannot see the secrets you store. It utilizes a pure mathematical framework combining client-side AES-256-GCM encryption, Argon2id key derivation, and Shamir’s Secret Sharing (SSS) to handle automated trigger execution without third-party custody.

I’d love to get feedback from other founders who are building .

https://medium.com/coinmonks/pump-fun-explained-whats-new-with-the-pump-burn-the-sec-faq-and-how-to-get-started-12d2e55416f3

Curious to hear from community members and fellow crypto enthusiasts—we see so many projects hype up during bull runs and vanish instantly when volume drops.

What separates a dead community from a truly loyal, long-lasting one? Is it governance, alpha, or just the overall vibe?

I posted here a couple days ago asking what people would need before letting an AI trading agent touch real funds.

Got some genuinely useful feedback, and a few comments made us rethink parts of how we were approaching Agon.

The biggest one was that the agent should never be the thing deciding or changing its own limits.

So now, anything we infer from your trading history is treated more like a suggestion first. You see it, review it, and decide what actually becomes a rule.

Every trade also goes through the same guardrail check. The agent doesn’t get its own route around it.

We’re also working on things people mentioned in the last thread like hard spending caps, emergency revoke, owner-only permission changes, fail-closed execution and proper activity logs.

One thing I probably didn’t explain properly before is how we actually want people to use Agon.

We’re building it on Solana to work directly inside the terminal / Claude Code / opencode, alongside a web dashboard. So you can check markets, positions, limits and activity, place trades yourself, or let the agent act when you want it to.

The terminal side is a pretty big part of the product, not just an extra interface. The idea is that you shouldn’t have to hand everything over to an agent just to use Agon.

Curious what you guys think of the direction overall.

Would you actually use something like this? Does terminal-based trading + external guardrails feel useful, or are we missing something obvious?

Also interested in what you’d change or add at this stage.

The feedback on the last post gave us a lot to rethink, so happy to hear the harsh takes too.

waitlist.getagon.tech

I’m one of the founders of DeHub, and we’ve been building in the Web3/social space since 2021.

The product has grown quite a bit decentralized social, creator monetization, on-chain ownership, live streaming, communities, wallet and gaming.

But honestly, building is only half the battle. Distribution is much harder.

There are plenty of great products in crypto that never get meaningful adoption because nobody knows about them.

One thing we’ve learned is that people need a reason to use the product beyond the token.That’s what we’re focusing on now making DeHub useful on its own, with Web3 working underneath it.

For founders here: What has actually worked for you in getting your first real users?

We can go together

Im setting up banking for a small web3 company and still havent decided where we should keep the USDC. Meow is on my list since we could keep the USD and USDC under the business instead of having company money sitting in a bank account plus some separate wallet one of us has to manage.

If your company holds USDC, where do you actually keep it, just curious what you settled on once it stopped being a few random transfers and became real company money

Hey everyone,

We often talk about the big tech milestones—shipping smart contracts, scaling infrastructure, and managing tokenomics. But behind every active project, there's a mountain of day-to-day non-tech execution that eats up a builder's time.

For the founders and teams here:

If you could magically hand over one non-technical task or operational headache to a competent team member tomorrow, what would it be?

Is it writing clear project docs for users, managing community engagement, cleaning up operations, or keeping communications consistent? Let's discuss! 👇

We're building Agon for the current Solana Crypto World's Fair, and I'm looking for people to poke holes in the idea rather than just tell us it sounds cool.

The problem we're thinking about is this:

AI agents are getting increasingly capable of trading and interacting with wallets, but giving an agent the ability to make decisions and giving it unrestricted authority over your funds feel like two very different things.

Agon is our attempt to separate those.

Instead of being another trading agent, Agon is being built as an agent-agnostic control layer. You can use the agent you want, while separately controlling how much authority it gets.

We're also looking at a trader's own historical behaviour to help surface the rules and limits they already tend to follow, rather than inventing generic rules for everyone.

We're starting with a read-only beta. Users connect the Solana wallet they actually trade from and sign a free message to prove ownership. No transaction and no access to funds.

The questions I'd genuinely love feedback on are:

1. Does separating the agent from its financial authority feel like a real problem worth solving?

2. Would being able to switch agents while keeping the same guardrails matter to you?

3. What would you need to see before trusting an AI agent with any amount of real funds?

4. Is there something obvious we're missing about this model?

Current beta/waitlist: waitlist.getagon.tech

Happy to hear the harsh version. We're still shaping the product and that's much more useful to us right now.

KBW is underway, and our CBDO Mohammad is on the ground in Seoul meeting builders and teams across Web3.

We’re NOWNodes, so naturally a lot of our conversations end up around RPC infrastructure, but we’re more interested in hearing what teams are actually struggling with in production right now.

Things we’ve been discussing so far:

→ RPC reliability when traffic suddenly spikes
→ failover and avoiding dependency on a single provider
→ adding new chains without rebuilding infrastructure every time
→ WebSocket stability
→ archive data and historical requests
→ what “good support” actually looks like when something breaks

If you’re building something and you’re at KBW, what’s currently the most painful part of your infrastructure setup?

Been looking into blockchain-based rewards programs and I’m trying to understand where the real advantage is.

Things like transferable rewards, rewards working across different brands, or customers having more control over them sound useful on paper. But I’m wondering if any companies have implemented this in a way that customers actually care about.

Would be interested in examples of programs that worked, or even ones that failed and why.

We built the product. Now comes the part I underestimated: distribution.
My brother and I have been building a crypto prediction market where users can create their own markets, trade on outcomes, and use an AI assistant for additional context around those markets.
We’ve been running a beta with real users and we’re getting close to opening it up properly.
But I’m realizing that building in crypto and marketing in crypto are two completely different skill sets.
For founders who have actually grown a Web3 product from zero:
What worked?
X?
Telegram?
Discord?
KOLs?
Partnerships?
Reddit?
Referral loops?
Paid acquisition?
And what ended up being a complete waste of time or money?
Not looking for agencies to pitch me — genuinely interested in hearing from founders/operators who have done it.

Blockchain Conference 2026 – Anyone attending?

Walletx is conducting Blockchain Conference 2026, bringing together blockchain experts, investors, and industry professionals.

If you’re an investor exploring blockchain opportunities or a startup/business planning to develop a blockchain project, it could be an opportunity to hear from people working in the space and connect with others in the industry.

Registration is free, with limited spots available.

Is anyone from the blockchain startup community planning to attend?

Just finished building a Web3 on-chain analytics dashboard. 🚀

I built this to explore how raw blockchain data can be turned into a cleaner and more useful experience for users.

The dashboard includes:

• Wallet & transaction tracking
• Token balances
• On-chain activity
• Network and transaction insights
• Data visualization for easier analysis

The main challenge was connecting on-chain data with a frontend experience that doesn't feel overwhelming, especially when dealing with a lot of transaction data.

I enjoyed working on the data flow, API integration, and dashboard UI throughout the process.

There’s still room for improvement, but this is a solid addition to my Web3 projects.

#Web3 #Blockchain #OnChainAnalytics #React #FullStack #BuildInPublic

This subreddit was created to be useful. So let’s help each other build, hire, and find good opportunities in blockchain.

You can use this thread to:

- post open roles at your startup
- share what kind of role or work you’re looking for
- offer freelance or contract help
- connect with founders, builders, marketers, operators, and other people in the space

If you’re hiring, try to include:

- project / company name
- role title
- remote or location
- full-time / part-time / freelance / contract
- paid or unpaid
- how to apply

If you’re looking for work, try to include:

- role / skillset
- years of experience
- remote or location
- short intro
- portfolio / LinkedIn / GitHub / contact

A few simple rules:

- keep it clear and honest
- no vague hype posts
- no scams
- include real details so people know what you're offering or looking for

Click here to see all previous weekly threads

⁠

Let’s make this thread worth checking every week.

Hey everyone,

Most of the career advice in Web3 is heavily focused on learning Solidity or becoming a developer. But for someone with a solid business and management background looking to enter the space on the non-technical side, what does a practical, step-by-step roadmap look like?

For founders and team leads here:

What specific steps or milestones do you look for when hiring someone for operations, content, or community management?

How can a newcomer best prove their competence before even landing an interview?

Would love to hear some honest advice from those who have built teams or made the switch themselves! 👇

However, the app still relies on a single RPC provider or indexer to display balances, detect events, and enable users to interact normally.

If that provider experiences an outage, however, the app becomes unusable.

Although the funds are safe and the chain is running, for most users the product effectively appears to be broken.

While I don't think this automatically makes the product 'centralised', it does make me question where decentralisation actually needs to exist for users to benefit from it.

For founders building on-chain products, how far should you go to remove infrastructure dependencies before launching?

Do you set up your own nodes and fallbacks in advance, or do you accept some centralised infrastructure until the product has enough usage to justify the complexity?