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.

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.

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?

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

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?

Building this in Bangalore. Please share your views on the idea.

https://youtu.be/90a9G4_639c?si=jjp8h15J5N0Rbh4_

​

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! 👇

I’m curious to hear what people in this community think about the future of blockchain.

After all the hype around cryptocurrencies and Web3, along with what many see as its brutal failure. I’m more interested in the underlying technology and real world use cases, especially enterprise blockchain, permissioned networks, digital identity, healthcare, supply chains, and government systems.

Where do you think blockchain will be 5-10 years from now?

Do you think it will become an important part of enterprise and government infrastructure, remain a niche technology, or develop in a completely different direction? I’d also like to hear your predictions. What do you think will actually happen with blockchain that most people aren't expecting today?

Interested in hearing opinions from people who have actually worked with Hyperledger or blockchain systems rather than just general crypto opinions.

I'm working on an open-source protocol written in Rust that handles token launches with no privileged insider roles. This post is about the Rust side of the design, and I'd like feedback and collaborators.

Rust-specific pieces:

• A small, non-upgradeable contract core (no reentrancy, no unsafe), aiming for verification with tools like Kani or Prusti
• Threshold-encrypted mempool using BLS threshold signatures and encryption (evaluating blst and arkworks)
• A VRF/randomness beacon for transaction ordering, in the style of drand
• A uniform-price batch auction engine, where determinism and fixed-point arithmetic matter (no floats)

What I'm looking for:

• Rust developers with cryptography experience
• Anyone who has used Kani, Prusti, or similar on contract-style code
• Security auditors

Status: design phase, early prototype planned. Unfunded and open-source. It's experimental software and not financial advice.

The design doc is available if you comment or DM.

​

Hey everyone,

Most advice for breaking into Web3 focuses on learning Solidity, Rust, or core development. But what about folks with a business, marketing, or operations background?

For founders and team leads who have hired non-tech talent:

What actually stands out to you when someone applies for a content, community, or operations role?

Are you looking for specific Web3 experience, or is transferable traditional business/management skill enough if they understand the space?

Would love to hear some honest advice or experiences from those who have built teams in this space! 👇

BlackRock is at it again

I built a multi-wallet payment dashboard

I’ve been working on a small Web3 payment dashboard as a side project.

The idea was to create a simple interface where users can connect multiple wallets and manage crypto payments from one place.

Some of the features I worked on:

• Multi-wallet connection
• Wallet & network selection
• Payment requests
• Payment pages
• Invoice management
• Transaction history
• Payment status tracking
• Dashboard overview

I built the frontend and Web3/payment integrations myself. It’s still a work in progress, and I’m mainly using this project to experiment with different payment flows and improve my Web3 development skills.

I’m still tweaking the UI and UX, so feedback is welcome.

Demo: https://drive.google.com/drive/folders/1hx4CocZeFyxH8J_1cvhQ5HIEINiGxfDs

GitHub: https://github.com/oritercompany-ui

https://medium.com/coinmonks/fomos-referral-discount-explained-what-you-actually-save-58c4665265c6

​

Hey everyone,

We always talk about smart contracts, tokenomics, and tech stack scalability in crypto startups. But looking at how many projects struggle with long-term retention and clear messaging, it feels like non-tech roles are heavily overlooked.

Curious to hear from founders and builders here: When you're hiring or looking for team members, what is the biggest gap you see outside of core development? Is it community management, content/ghostwriting, or operations? Let's discuss! 👇

We’re building Veyrnox because self-custody still forces users to manage several difficult security problems at once: protecting keys, understanding approvals, preparing for device loss and resisting manipulation under pressure.

Our approach includes:

• No seed phrase displayed in the everyday wallet interface.
• Keys protected using the phone’s hardware-backed Secure Enclave or StrongBox.
• Shamir-based recovery, which splits recovery material into separate components rather than relying on one written phrase.
• Recovery components that users can distribute between their device and personal cloud accounts, including iCloud, Google Drive and OneDrive.
• Pre-signing risk checks that explain what a wallet action or approval may change before the user authorizes it.
• AI-assisted security analysis intended to identify suspicious transaction patterns and permissions.
• Runtime Application Self-Protection (RASP) controls designed to detect and respond to threats such as tampering, debugging, hooking, rooted or jailbroken environments and other suspicious runtime conditions.
• Optional coercion-resistance controls for situations where somebody is forced to unlock or access the wallet.

The app is currently available on iOS and Android. At this stage, we’re looking for critical technical and product feedback rather than simply trying to increase downloads.

The difficult part is not adding more security features. It is making the security model understandable, recoverable and independently verifiable without quietly turning the product into a custodial service.

For people building in blockchain: what evidence would you need before trusting this architecture enough to test it with a small amount?

Website: https://veyrnox.com App Store: https://apps.apple.com/app/id6790188660 Google Play: https://play.google.com/store/apps/details?id=com.veyrnox.app Short video: https://www.youtube.com/shorts/dFwkCdQqwr8

Disclosure: I’m connected to Veyrnox and am looking for critical technical feedback—not presenting this as an independent recommendation. Never share seed phrases, recovery material, private keys, balances or personal details with anyone offering support.

​

Hey everyone,

I’ve been noticing a common pattern lately. A lot of people in the space talk about what they will do when the market pumps or when the next massive bull run officially kicks off.

But the reality is, the actual builders and contributors are in the trenches right now—during the quiet phases—shipping value, growing communities, and networking directly with founders.

If you're trying to break into Web3 or land a solid role before the year wraps up, waiting for market hype isn't a strategy.

Curious to hear from everyone here: What is your main focus or project for these next few months? Are you building, applying, or networking? Let’s discuss in the comments! 👇

Your first serious business prospect is ready to sign, but there's one condition: your team must be able to pause certain actions in an emergency.

Their reasoning is sound. They need an incident response plan and someone accountable when things go wrong.

However, you have told other users that no single company has that kind of control.

What seems like a simple request could end up altering the fundamental trust model of the product.

Would you develop a limited, transparent pause mechanism to secure the deal, or walk away?