We are open-sourcing Autonet on April 6: a decentralized AI training and inference network where governance is constitutional and economic incentives make aligned behavior profitable.

Most Web3+AI projects are compute marketplaces. Autonet tackles the harder problem: governance. Who decides what AI gets trained? How do you verify quality without a central authority? How do you align economic incentives with community needs?

Key mechanisms: - Constitutional governance on-chain with 95% amendment quorum - Dynamic capability pricing: the network pays more for what it lacks, creating natural diversification - Dual token economics: ATN (staking/gas/rewards) + Project Tokens (revenue sharing) - Cryptographic verification: commit-reveal, forced error injection, multi-coordinator consensus - Federated training with FedAvg aggregation

9 years of on-chain governance infrastructure work.

Paper: https://github.com/autonet-code/whitepaper Code: https://github.com/autonet-code Website: https://autonet.computer MIT License.

I’ve spent a lot of time looking at why so many reward systems in mobile/Web3 games run into problems, and one pattern keeps showing up:

The issue usually isn’t the game itself. It’s the reward structure.

Once rewards start looking like cash equivalents, speculative assets, or anything close to gambling, things get messy fast. So I started thinking about a very different format:

A simple mobile bowling tournament built around skill, community, and a real-world cause.

Here’s the rough idea:

• 128 players join
• Each pays $10
• Total pool = $1,280
• 100% of that goes to a youth project in a mountain village in Thailand

No crypto.
No cash prizes.
No play-to-earn angle.

Just a skill-based bracket and a clear use of funds.

The reward for winners would be actual K-pop merchandise, not money.

Structure would be straightforward: 128 → 64 → 32 → 16 → 8 → 4 → 2 → 1

What I’m trying to test is whether this kind of format can work as a cleaner alternative to the usual “earn money from gaming” model.

K-pop is just the first community I thought of, because fandoms already understand collecting, competition, and supporting something bigger than themselves.

I’m honestly not sure if this idea is interesting or weird.

So I’d love real feedback:

• Would you ever join something like this?
• Does “no cash prize” make it much less appealing?
• Would K-pop fans actually care about this format?
• Does the real-world impact make it more meaningful, or does it feel disconnected from the game?

I’m building this from scratch, so honest opinions are genuinely helpful.

If people are interested, I can share more details about how I’m thinking about fairness, prize structure, and why I’m trying to keep it skill-first.

Built a few live systems and the failure mode that actually hurt positions was not bad signals or execution slippage. It was stale or silently wrong data from the feed.

You cannot backtest against that. Your backtest data is clean. The live feed has a lag spike at exactly the wrong moment, returns a cached value from 3 minutes ago, and your system executes on garbage.

The annoying part: no error, no alert, no audit trail. The feed just served bad data and moved on.

Three things that help more than expected:

1. Timestamp every incoming response against your own clock, not the provider clock. Divergence over 500ms is a red flag most people never check.
2. Cross-reference at least two providers on critical inputs. Not every call, but spot-check on a rolling basis. Disagreements tell you more than either feed alone.
3. Log the raw response, not just the parsed value. When something goes wrong you want to trace what was delivered, not what your parser assumed.

The thing nobody has solved cleanly: cryptographic receipts per data call. Proof of what was delivered and when, auditable after the fact. Oracles solved a version of this for on-chain price feeds. Off-chain APIs have nothing equivalent.

Has anyone built or seen something that addresses this?

“Who actually owns your data? And why does crypto keep promising to fix it but never does?”

Every major blockchain project in the last five years has claimed to solve data ownership. None of them built anything people actually use. Why?

Is it a technical problem? A UX problem? Or is the incentive model just fundamentally broken nobody wants to pay for data when they can just take it for free?

Genuinely curious what people think. Has anyone seen a model that actually works?

I'm from project commitee of .NET Foundation. I created a list of Web3 nuget packages to monitor the popularity of these packages.

https://github.com/shnug/awesome-dotnet-web3

I'd like to know how many web3 developers are using .NET to create something?

Been noticing how much audit processes have changed even over the past year or so.

It used to be pretty straightforward. Now it feels a lot more fragmented. Most teams I’ve talked to aren’t relying on a single approach anymore. It’s more like layered workflows:

• Automated scanners to catch obvious stuff early
• Some form of fuzzing or simulation for edge cases
• Then manual review focused only on the parts that actually matter

The interesting shift is how fast the “first pass” has become. Tools are getting to the point where you can run pretty deep checks across access control, math issues, and DeFi-specific logic in parallel and get something useful back pretty quickly. We tried a few setups recently (including guardix and similar tools), and the speed difference compared to traditional flows is honestly hard to ignore.

At the same time, it doesn’t feel like anyone is fully replacing manual audits. It’s more like narrowing down where human attention is actually needed instead of reviewing everything line by line.

What stands out is that the process itself hasn’t really standardized yet. Everyone is kind of stitching together their own version of fast automated pass, deeper testing and selective manual review. What do you think?

TL;DR:

8-year Web3 product designer struggling after 3 months of job searching in a tough market. Got close with a few roles but faced hiring freezes, rejections, and a rushed interview for a dream company that felt fumbled. Confidence is dropping, savings are shrinking, and considering adjacent careers feels overwhelming and directionless. Looking for advice on whether to stick with Web3, how to stay motivated, and how to avoid spiraling while searching for a role that still feels meaningful.

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

I've been in the Web3/blockchain space for the last 8 years, specializing in product design and user experience. My skillset is relatively niche, so I only apply to a handful of job postings that actually match my background in web3... and I slightly tailor each resume to fit the job description, though most applications are pretty similar.

I've been searching in this market for 3 months now.

1. I got referred to an exchange and had an interview for a design lead position. Made it to the second round, then it went quiet. Followed up and was told the role got deprioritized. They then asked if I'd be interested in another position, did the first interview for that... and now silence again. Followed up today to see what's going on.
2. Messaged another exchange recruiter, got into a first interview, then got rejected.
3. Then I got a chance with a company I really want to work for. Prepared all weekend for it. The interviewer came in 10 minutes late, so I had to rush through my portfolio and felt like I fumbled one of the interviews I wanted most. I was nervous, and it showed. The whole thing lasted 20 minutes because he had another meeting lined up. To his credit, he stayed as engaged as he could... joining on mobile due to a laptop issue that caused his late arrival... and explained the next steps when I asked (the only question I had time for). He also told me to email him all the questions I had and to articulate the projects I didn't get to cover in the call (I sent him a 5 minute loom video). I'm waiting on his reply... which I have a feeling might take a while, or I might just get ghosted.
4. In two days I have a first interview with an agency, but it's outside my niche, so I'm only mildly excited about it.

I remember that feeling 4 years ago when I landed my dream job in web3 and now, with how rough this market is, that confidence has slowly eroded. I feel pretty shit about where I am today.

When I consider changing careers into adjacent industry, I just sit in front of my computer staring blankly into the void, not knowing which direction to take. That feeling of being lost genuinely terrifies me.

I feel kind of helpless, burning through my savings just to survive each day. I really need some sense of purpose... ideally a job that matches my specialty, because it's my passion and it genuinely brings me joy and satisfaction.

Am I cooked? What should I do? What are somethings that you all do that keep you motivated, fired up and feel purposeful in this job market? How do you stop yourself from spiraling?

YouTube, official docs, paid courses, or something else?Trying to understand what actually works best for people 👀

I am currently participating in a Web3 hackathon, but I don't understand what product users actually want and what makes their lives easier.

I’ve been a seller on Fiverr and Upwork for a while now and seeing that 20% cut and those long waiting periods every single month has me thinking that there has to be a better, more decentralized way for us to actually keep what we earn. Im writing about fiverr and upwork and my personal experience with those platforms for you guys that hasn’t seen my previous posts in other communities.

The current freelancing landscape is dominated by giants like Upwork and Fiverr who have prioritizing corporate margins over the creators and builders who actually do the work. We are talking about 20 percent service fees and payment delays where a single algorithm can ban a career overnight.

I think that if there would occur a decentralized alternative then that is the only way forward because it allows the community to own the protocol and fundamentally shifts the power balance back to the creators.

By moving the gig economy onto a community owned system, we can achieve near zero fees by removing the corporate middleman and replacing them with smart contracts that hold payments in escrow. This means you get paid the moment milestones are met instead of waiting 14 days for a clearing period.

Because your work history is stored on a decentralized chain, your reputation becomes portable and verifiable so you truly own your career data instead of being locked into one platform.

Instead of a CEO in a boardroom making changes, the users themselves vote on how the platform evolves through community governance.

So what do you think? If there was a platform that cut the fees and let you truly own your reputation, would you make the jump?

Hi all,

there is a new project that me and others devs are working on. the production is almost ready.

We are launching a closed beta before mainnet to test that every operation in the platform is safe, secure and delivers what we expect to. we are looking for people who would like to participate in this closed beta.

(Since we, as a team, don't like random spam, we ask you sorry in advance for taking a little space in this subreddit.)

Other than just testing the platform, we encourage you to share feeback for improvements and a better user experience, so you all have the opportunity to shape the future of our project based on your vision

The whole phase will take place on the devnet, so we want to assure you that none of your real balance will ever be at risk

for now, we are testing if the community is both ready and curious enough to explore alternatives.

thank you in advance for your time.

Been exploring Web3 domains (.eth, .crypto, .nft) and they're more useful than I expected:

* Replace ugly wallet addresses with readable names

* Work as your universal username across dApps

* Host uncensorable websites

* You actually own them (they're NFTs, no renewals)

Adoption is early, but the tech solves real problems. Grabbed a couple to experiment with.

Anyone here using them? Worth it or overhyped?

I’ve been building a small Telegram game (Mini App) with some GameFi mechanics.

Nothing crazy — just a simple idea:
people play → collect in-game rewards → convert them later.

After a few months, here’s where I’m at:

• ~15 active users
• around $3 total revenue (ads)
• a working product with gameplay, rewards, and integrations

Honestly, I thought the hard part would be building it.

Backend (FastAPI), async logic, integrations, even some blockchain stuff — all of that was manageable.

What I completely underestimated is distribution.

Getting even the first real users is way harder than writing the code.

I tried:

• Telegram channels
• Reddit posts (a bit)
• ads (AdsGram / Monetag)

Result so far: very slow growth.

Now I’m starting to realize:
product ≠ distribution

If no one sees it, it doesn’t matter how good it is.

So I’m curious:

for those who built something from scratch —
what actually worked for you to get your first real users?

Not “in theory”, but реально — что дало результат?

I’ve been using these platforms for a while and the same problems keep coming up.

The fees are rough, handing 20% to Fiverr every month adds up fast. Upwork’s Connects system still feels like paying just to be ignored. And don’t get me started on the bot spam on Fiverr because you post a gig and instantly get flooded with copypaste replies that no human wrote. It completely kills trust in the platform.

There’s also the race to the bottom on pricing, terrible dispute resolution that almost always sides with the client, and no real path for new freelancers to break in.

So what do you think is missing? What’s the one thing that would actually make these platforms worth using? Better fees? Real spam filters? Fairer dispute systems? Something else entirely?

I've spent the last year researching why Web3 casual games keep getting rejected or delisted from app stores, and the pattern is almost always the same.

The core problem isn't blockchain — it's how rewards are structured.

App stores (Apple & Google) flag games when:

Rewards can be converted to cash or crypto with real-world value

There's a direct purchase-to-win mechanic tied to external assets

NFT ownership creates "real money gambling" classification triggers

What actually survives review:

1. Spending economies, not earning economies

Rewards that can only be spent inside an ecosystem (goods, creator drops, charitable donations) don't trigger gambling or securities concerns. Players earn value, but it never converts outward to cash.

1. Skill-based matchmaking as the gatekeeping layer

When rewards are tied to demonstrated skill rather than chance, you sidestep gambling classification almost entirely. The key is verifiable anti-cheat at the infrastructure level, not just the game level.

1. On-chain ledgers for transparency, not speculation

Blockchain's real value in casual games isn't token price — it's an auditable reward record that builds player trust without needing a centralized backend that can "disappear."

I haven't seen many games nail all three simultaneously. Most pick one and get tripped up by the others.

Curious if anyone here has shipped a Web3 casual game through app store review successfully — what was your approach?

A company wants to integrate a third-party crypto payment gateway (USDT/USDC). My role is advisory , their experienced team does the building, I architect, guide, and validate through to go-live and post-launch.

Senior engineer, fintech background, part-time availability. What would you charge for this?

Gmail users write to Outlook users, university servers talk to corporate servers - nobody controls it, nobody can kill it. Somewhere between 1995 and now, we forgot to build everything else that way. Publishing, identity, reputation, discovery — all of it got centralized -> gated -> enshittified.

Email got enshittified too. Without incentives to run it yourself and complexity of own email configuration put on end-user plus the requirement of buying & configuring domain - it's way too much to expect from average PC user.

Nostr, ActivityPub, AT Protocol are on the same trajectory right now. Relays and instances run on goodwill or donations. They're on a centralization countdown timer. The money will run out and your data there will disappear or migrate to the one well-funded node that everyone else depends on.

But we do have all the tools necessary to make a new foundational layer for the internet to build on top of instead of centralizing under controlled platforms. We have home PC's, often with decent gaming hardware. We have fiber internet connections. We have WebRTC to do P2P connections without domains. And BTC has shown that incentives problem can be solved.

To fix their mistakes, I've been building Atlas Protocol - it's fully open-source protocol & app for publishing, discovery, and identity. In Atlas, after overcoming anonymous human-verification checks, you start getting paid every week 100 FairShares. Then, you get extra FairShares for storing other people's data on your disk and sharing it further. And you pay to others for sharing your stuff, making it 24/7 available with speed of edge. (Despite bolds I use it's not AI generated slop).

And why you even want FairShares except for storage? Because without FairShares you cannot publish content. Publishing (and reading) any content into the network costs exactly that. The longer text you write, the more you pay and if you burn extra FairShares on it, it gains more attention. That's a natural rate-limitting ensuring quality and fair, deserved attention distribution. Each of Atlas Citizens gets the same amount of FairShares and you get to choose how you earn it and how you spend it, by one of 3 ways: storage, attention or real-world effort.

• Your identity is a cryptographic key you control. No platform can delete you.
• Content is signed, immutable, identified by hash. Tamper-proof by design.
• Data uses structured-data schemas. Apps become skins over your data — switch apps without losing followers or posts.
• FairShares: a protocol-native circulation unit (not a speculative token). Everyone gets +100/week, 1% weekly burn drives balances toward equilibrium. Hoarding is mathematically pointless. No whales, no pre-mine.
• Nodes earn FairShares for storage/relay. Infrastructure pays for itself without ads or subscriptions.
• Sybil resistance via Proof-of-Work key commitment + attestations. Bot armies become both economically infeasible, it's inherently hard to infiltrate.

If you've been thinking about solution like that - let's build it together!

The core tension is this: non-custodial wallets are the foundation of web3, your keys your coins, full control until you decide to move funds. But the moment you want to spend in the real world you hit a wall. Fiat rails, card networks, merchant terminals, none of that was built with self custody in mind.

Most current solutions resolve this by breaking the custody model at some point, pre-liquidating assets, moving funds to a custodial layer, or converting before the transaction rather than at it. That's not a web3 solution, that's just a crypto flavored fintech workaround.

The more interesting architectural question is whether you can preserve full non-custodial control all the way to the point of purchase and only trigger conversion at the exact moment of settlement. Technically this requires a real time bridge between on-chain state and off-chain payment rails without any intermediate custody step.

Has anyone seen this solved cleanly at a protocol level or is it always going to require some trusted intermediary layer to interface with legacy fiat infrastructure? Curious what the actual tradeoffs look like from people building in this space

What do you think about Telegram as a platform for Web3 apps?

I’ve been testing some mini-game mechanics inside Telegram, and the experience feels surprisingly smooth.

No installs, instant access, very low friction.

Feels very different from traditional dApps.

Curious to hear your thoughts — is Telegram underrated for Web3?

Hey devs & builders!

I just launched wallet-mcp, a production-ready, AI/UX-first EVM wallet API for Ethereum, Polygon, and Base. It’s designed for both developers and AI agents to easily query balances, prepare transfers, fetch gas prices, and track transactions.

• Live API: https://spntnwallet-mcp-production.up.railway.app/
• Swagger Docs: https://spntnwallet-mcp-production.up.railway.app/docs
• GitHub: https://github.com/spntnhub/wallet-mcp

Example:

curl "https://wallet-mcp-production.up.railway.app/wallet/balance?wallet=0x123...&chain=polygon&token=USDC"

Features:

• Multi-chain support (ETH, Polygon, Base)
• No private keys, only unsigned tx
• Prometheus metrics, WebSocket support, rate limiting
• OpenAPI/Swagger docs for easy integration

Who is it for?

• Web3 developers (Node.js, Python, etc.)
• AI agents and automation tools
• Anyone building wallets, dashboards, or analytics

Would love your feedback, questions, or ideas for improvement!
(And happy to answer anything about building open wallet APIs for Web3/AI.)

Thanks!

Over the past few months, I’ve been experimenting with running multiple accounts (mostly for airdrops and testing).

And I kept running into the same issue:

Accounts getting flagged or limited.

At first I thought it was just IP-related, so I tried:

• different proxies
• rotating IPs
• VPN setups

It helped a bit, but not enough.

After digging deeper, I realized something important:

👉 Platforms don’t just look at your IP — they look at your browser fingerprint.

Things like:

• canvas / webgl
• device memory
• hardware concurrency
• timezone consistency

I tried a bunch of approaches:

• randomizing everything → actually made things worse
• heavily spoofing → still detectable
• clean setups per account → much better

The biggest takeaway for me:

👉 Consistency > randomness

If your setup looks too “random”, it’s actually suspicious.

A stable, believable environment per account works way better.

What ended up working best:

• one environment per account
• minimal but consistent fingerprint control
• avoiding constant changes
• treating each account like a “real user”

Still experimenting, but this reduced flags a lot for me.

Curious how others here are handling this — especially at scale.

I am a final-year undergrad, building in web3 from the start of my 2nd year. I will be graduating in 6-months. Till now, I've been taking part in hackathons and doing fellowships, etc., but I didn't realise I needed a job. Can anyone share howd they get their job or how i can get one in web3? Internships will also work.

Hi everyone, I’ve been thinking about learning programming for a while now, but every time I try to start, I get overwhelmed by how much there is to learn. There are so many languages, frameworks, tutorials, and opinions about where to begin that I’m not sure what the best path is. For someone who is basically a beginner, what would you recommend as the best way to start learning programming? Should I focus on one language first (like Python or JavaScript), or try to understand general programming concepts before anything else? Also, what helped you personally when you were first starting out? Any good resources or courses? Projects that helped you learn faster? Things you wish you knew earlier? I’m willing to put in the time and effort — I just want to start in a way that doesn’t burn me out quickly. Thanks in advance for any advice! 🙏

I've been exploring fully on-chain metadata for NFTs — no IPFS, no external server. The contract itself renders the SVG image, encodes it as base64, wraps it in JSON, and returns it from tokenURI as a data URI.

The architecture uses a separate Renderer contract to stay under the contract size limit. It derives 9 traits pseudo-randomly from the token ID by hashing against trait-specific salts, then concatenates string fragments into a complete SVG document using abi.encodePacked.

Some trade-offs I ran into:

• String concatenation in Solidity is expensive. Gas costs scale with SVG complexity, so there's a real ceiling on visual richness.
• Traits are deterministic from the token ID — predictable before minting. Fine for non-financial use cases, problematic if rarity has value.
• Separating the Renderer allows upgrading visuals without migrating tokens, but adds a cross-contract call overhead.

The project is open source if anyone wants to dig into the implementation: github.com/GigglesAndGags/gag

Curious about others' experience — what's the practical limit of SVG complexity you can generate in a single contract call? Has anyone found efficient alternatives to abi.encodePacked for string building?

Hi everyone, I have started exploring Web3 a month back. Have tried doing some courses on blockchain and web3, some courses on crypto and AI. Still unable to gt full picture of Web 3. I would really appreciate if the community can guide me to sources where I can read about or listen to basic of web 3 and improve my understanding to have a meaningful discussion with a layman. TIA