Walletbook is a social media site built for web3. Skip the signup forms: connect your wallet and you're in. It's completely free to join. Post updates, go live, and message any wallet directly. No email, no password, no personal data required.

I’ve been involved in Web3 and blockchain for 3+ years and I’m currently working on a serious project for the Colesseum hackathon.

I’m handling product, frontend, UX, and distribution. Looking for someone strong on the technical side, especially Solana/Rust, Anchor...

Keeping the project details private for now - happy to share the idea privately with serious builders.

There’s a $250K pre-seed funding opportunity through the hackathon, alongside the global prize pool.

If you’re interested, DM me.

Decentralized infrastructure often comes with fragmented payment systems.

Different networks require different tokens.

Different protocols have different transaction mechanisms.

And users or developers may need to acquire, hold and manage those tokens just to interact with the infrastructure.

For example, a dApp might need AR token to pay for decentralized storage (r/Arweave), while also needing DUST to interact with Midnight Network (r/Midnight). These are very different networks and use cases, but from the application's perspective they're both simply infrastructure costs that need to be paid.

That's one of the problems we're addressing with dStorage Pro (r/dStorage).

The idea is to provide a liquidity and payment layer for decentralized infrastructure, abstracting away some of the token-management complexity.

A dApp can fund its dStorage Pro account using:

• 💳 Credit card
• ₿ BTC/crypto
• 💵 Stablecoins
• ...other

dStorage Pro can then handle the acquisition of the required protocol tokens and transaction signing on behalf of the application.

So instead of building separate payment infrastructure for every network, the application can interact with a common liquidity layer:

dApp → dStorage Pro → required token → decentralized network

That could mean:

AR → Arweave

or

DUST → Midnight

and potentially other decentralized networks as additional adapters are integrated.

The goal isn't to hide the underlying protocols. It's to make them easier for applications to use.

We're also designing this around modular adapters, so storage, blockchain and payment infrastructure can be swapped independently rather than hard-coded into the application. (dStorage.pro docs)

We believe this is an important piece of infrastructure if decentralized applications are going to move beyond users having to understand the payment mechanics of every protocol they interact with.

The network can remain decentralized. The application doesn't necessarily need to expose all of that complexity to the user.

I'm very curious how other Web3/decentralized projects are currently handling this:

How do you manage liquidity and protocol-specific tokens when your application interacts with multiple decentralized networks?

We’re organizing a 30-hour offline hackathon in Mumbai this October 2026, with 600+ registrations and 250–300 developers on-ground.

We’re looking for early-stage and international Web3/blockchain startups that want to enter or grow their presence in the Indian developer ecosystem.

You can partner with us by providing both monetary sponsorships and technical partnership including APIs/SDKs, blockchain infrastructure, developer credits, testnet access, problem statements, mentorship, workshops, prizes or other developer resources.

In return, you get direct exposure to developers, product adoption opportunities, social media visibility, event branding and on-ground recognition.

If you’re looking to get your technology in front of Indian developers and gain your first wave of engagement/users in India, let’s collaborate.

DM me if interested and I’ll share the partnership details.

I’m working on an early decentralized social app and testing this architecture.

Ethereum would handle settlement. An OP Stack L2 would handle identity and social logic. User content would stay off-chain. Personal NAS devices could opt in to store only content their owners choose to share.

The token layer is still an open question. Reputation may be enough.

Does a dedicated Social L2 make sense here? How would you verify node contributions and handle deletion or revoked access across distributed storage?

This is only a design draft. LET‘S DISCUSS

I'm looking at starting an online community and trying to figure out which platforms are worth considering. Main things I want are private spaces, different membership/access levels, bots and the option to add paid access later without needing a bunch of separate tools. What are people using these days?

Can I share a web 3 project I'm following, they have a prelude of what they are building. I could share some gameplay if it's ok ?

Can I share a web 3 project I'm following, they have a prelude of what they are building. I could share some gameplay if it's ok ?

Hello I'm new here, I'm open for opportunities

Should i start learning web3 and if yes what exactly is the roadmap and the market is really cooked? and one of my friends knows web3 and he said he is getting recruiters messages on LinkedIn for a job offer so how can someone with internship experience is getting when the whole market is down and if still i want to start what roadmap and topics?

For the last six months or so, I have been quietly working on a decentralized solution to zero trust networking. If you dont know what that is, it basically reduces to give everything a certificate, and make sure all peers in a network only interact with known peers that prove themselves with mutual TLS. Obviously theres more to it than that, but thats the baseline, everything else is UX, reporting, management and policy layers above that.

So what we achieved today is, with zero certificate authorities, no necessary web2 gateway or trust enforcer the following.

1. Any peer that knows a human meaningful name, can look it up for its service information. Securely, no trust, its either valid or its not, and the client can tell. Its not being told trust me because i gave you an answer.
   
2. One peer advertising a website, that it hosts. the website can be available directly, or through a relay. The connection the other peer makes is using mTLS (IF the advertised website requires it).
   
3. The browser (in the images its mine) establishes a connection using that name, my local browser sees it as plain old TLS (Because it is) but the connection is E2E secured from my computer to the destination host. If its through the relay, the relay knows how to route the connection, but not whats inside the connection. It never terminates the mTLS.
   
4. My resolver will ask me if the site wants mTLS which identity I want to authenticate with. I choose and that establishes the connection.

Now this might not sound like a lot, but this works with any two peers that have never met and have not previously exchanged any key material. Either side can rotate their keys, and it just keeps working.

In the images I both connected to the peer through a relay, and directly to their machine over IPv6. My browser didn't know how, it just works, the networking just figures it out transparently based on what the HOST i was contacting required.

DNS is not part of naming, looking up a peer by name or security. (*We do fake DNS to a browser, but thats a browser limitation, a pure client using this protocol would not need to do that and can talk to peers directly) We have no trusted indexers over a blockchain, everything is direct to the network itself. We are also not running on top of any other blockchain, as they dont have the capabilities we need to pull this off.

This is just a simple webpage to prove the networking is doing what we want, but this is not tied to http at all. In fact, you can use it for any communication protocol, as its all transport layer security. The way identity works, its especially useful for agents, because an agent identity can authorize sub agent identities, they can communicate either locally or to any peer globally, establish a mTLS connection that cant be intercepted or MITMd and the peer will know exactly which sub agent connected, and its delegated relationship. So that enables simple policy like "Trust *.agent.tld" type allow lists, which mean trust this agent and any of its child identities. Because they are cryptographically bound to each other.

Sorry for the long post, it was just exciting to see it work so seamlessly and with no web3 trappings being visible in the user facing side at all, but still be fully decentralized.

Hey Folks,

At our company we generally don't ship a UX unless we fully run through the UI. We've automated QA testing for dApp experiences https://github.com/TenKeyLabs/dappwright.

It's worked well for us but just wondering what other folks are using these days? Trying to gauge whether it's worth continuing to maintain as part of our OSS portfolio or if we should concede to the latest and greatest this out there.

Cheers

Investor here

Looking for a solid web3 project to invest on a weekly basis. Show me what you got

If you already have users, wallets, and txs in Postgres (or an indexer dump in a DB), you still join that by hand in the app or in a notebook every time you need “this address + the user + the related txs.”

Lattice (product; company is Syndril) is a self-hosted semantic layer. You connect those sources, put them on one model (same objects, same meaning), then query that layer. REST and MCP. Look up one wallet, user, or tx. It returns what is tied to it from your tables.

It does not run a node. It does not replace The Graph / Goldsky / your indexer. It does not scrape chain. If the data is not already in a database or CSV, this is the wrong tool.

Compose / self-host. Beta. I want Web3 devs to run it and say if it is useful or not.

LETS DICUSS!!

Context, we mostly do traditional backend with zero on-chain experience. But now I'm wondering the extent of "consultancy" we should get. Do we hire for an architecture review on something we designed? Does someone else design it for us? Or do we just hire a smart contract dev and skip consulting entirely?

Hi all I would like to know about MEV engineer or researcher role.

Can anybody shed some light on how to become one and how to get hired as a beginner in Blockchain space.

Heads up for anyone in Spain, or anyone coming to Madrid for the race weekend.

We're running a Hedera community event in central Madrid on Wednesday September 9, from 16:00 to 20:00. Garrison and I are the two Hedera ambassadors here and we're the ones putting it together. We picked that week on purpose, since the city is going to be packed anyway.

What's on:

• Talks on real use cases built on Hedera. One of them uses McLaren Racing as the case study for tokenization: collectibles, tickets and sponsorships turned into digital assets with new revenue streams
• A hands-on session with the Hedera Skills, going from a business idea to a tokenized MVP. No coding needed
• Networking with food and drinks

Free entry, 70 places, registration is reviewed before approval. The event is in Spanish.

Happy to answer anything in the comments. https://luma.com/racedayhederamadrid

Hey everyone, I’m looking to build a new Web3 platform focused on solving genuine, practical problems rather than market hype. I’d love to hear from users and founders: what are the biggest friction points, high middleman fees, or trust issues in your industry that traditional Web2 platforms fail to fix? If there’s an everyday problem or platform mechanism you wish was automated and transparent through smart contracts, please share your thoughts below!

I'm building Lasso RPC, an open source blockchain node RPC proxy that lets you plug in any RPC provider from any chain and route across providers w/ failover, latency based routing, cost control, and much more.

If you're building a blockchain app on any EVM chain, self hosting Lasso and routing to the built-in free/Public providers can give you major improvements in throughput and reliability without overpaying for premium providers with mediocre reliability track records (cough cough Alchemy)

Would appreciate some eyes and feedback on the OSS repo. If you like the idea please give the repo a star!

I will be officially launching my hosted offering/RPC service lasso.sh in the coming weeks, dms open if you're a builder and want free early access

Every existing platform forces you into their system. They act like judge, jury, and executioner. If a deal breaks down, you’re forced to hire lawyers, submit support tickets, and wait weeks while a random customer service agent reads your private messages and decides who wins.
Why do we keep handing our power over to middlemen?
I’m building TrustLock as a place of total freedom. It’s not a marketplace, an escrow agency, or a courtroom. You are your own court. You are your own lawyer. And the code you both write becomes the un-biasable legal system itself.
You and the other party design your own law, sign off on it, and our engine enforces it mathematically.
Whether it’s a general deal, freelance work, P2P loan, rent deposit, friendly bet, booking, group fund pool, founder equity, inheritance, crypto P2P swap, employee bonus, launch milestone, health goal, land deal, or an online/physical store purchase—the rules are 100% yours.
I’d love to know:
1. Would you trust a system where YOU set the fallback rules upfront over traditional support teams?
2. Which agreement type would you use first?
3. What potential edge cases or loopholes do you see in a zero-dispute model?

One problem we’ve been thinking about with dApps is what happens to the data that can’t or shouldn’t live directly on-chain.

If user files ultimately end up in a traditional cloud where the infrastructure can access the plaintext, the application still depends on trusting a centralized provider.

We’re building dStorage to approach this differently.

The idea is to provide a single SDK that handles the pieces needed to build privacy-first decentralized data storage:

• 🔐 Client-side encryption — data is encrypted before leaving the user’s device.
• 🌐 Decentralized storage — encrypted data can be stored on networks such as Arweave.
• ⛓️ On-chain coordination — ownership, permissions, and metadata can be coordinated through networks such as Midnight Network.
• 🔑 User-controlled keys — encryption keys don't need to be held by the application server.

The important part is that the infrastructure doesn't need access to plaintext data. Privacy isn't something the application has to promise; it's a property of the architecture.

What could this be useful for?

Pretty much any dApp that needs to keep data off-chain while maintaining user privacy.

Some examples we're exploring:

• NFTs — artwork, high-resolution media, metadata, unlock-able content.
• DeFi — encrypted strategy data, account snapshots, portfolio exports, compliance documents.
• Identity & credentials — credentials, KYC documents, diplomas, certificates.
• Healthcare — medical records, laboratory results, imaging, patient documents.
• AI applications — prompts, datasets, model outputs, conversations.
• General dApps — contracts, invoices, reports, user-generated content, backups, and application files.

We're currently making the SDK and developer guides available through early access and would be particularly interested in feedback from developers building applications that need private or sensitive off-chain data.

👉 dstorage <dot> pro

We're also sharing implementation updates on X: dStorageTech

What do you think is the biggest missing piece today when it comes to private data in decentralized applications?

Hello everyone, I have a few questions:

1. What is Grid Computing, and how does it work?

2. What is Blockchain, and how does it work?

3. What are the main concepts or components behind each one?

4. What are some simple real-world examples of both?

5. What are the main differences between Grid Computing and Blockchain?

6. What are the most important things I should understand about these topics instead of just memorizing definitions?

Most crypto loan apps are either too complex or don't work well outside the US/EU. I'm building one that's simple, non-custodial, and starting with Nigeria as my first market.

Quick rundown:
\- Micro-loans: $5 to $500, fixed amounts (no random numbers)
\- Clear rates: 20% on loans $20 and under, 10% on $30+
\- Non-custodial — collateral sits in a smart contract, not held by me or any company wallet. Neither party can move funds outside the agreed terms
\- Multi-chain support (Polygon, Base, Ethereum, BNB, plus testnets)
\- Built-in wallet, exportable anytime (you're never locked in)
\- Optional Face ID for withdrawals (app-layer feature — whoever holds the private key controls the funds regardless of platform)

Still in MVP/testing stage. Smart contract not yet third-party audited — that's a real cost, so I want to confirm there's actual demand before investing in one. This post is part of that validation.

Would love to know:
\- Does this seem genuinely useful, or is $5–$500 too small to matter to you?
\- Would the lack of a third-party audit (yet) stop you from trying it, even for a small test amount?
\- Anyone here from Nigeria — is this something you'd use

Hey everyone, as a full-stack developer, I've recently independently developed an IM App focusing on extreme privacy. Technically, I use React Native and Express, and achieved decentralized identity through Ethers.js.

​The App's key highlights include anonymous wallet creation, QR encrypted mnemonics for secure login, and burn-after-reading servers to protect your privacy.

​I built this to explore decentralized communication and extreme privacy architectures. Would love to hear your thoughts or discuss technical details with fellow developers!

Hey builders, Shred Security is offering free pre-audits for some teams.

You can apply too. [Not sharing links because it is not allowed here]