Hello guys, I'm Tony from Vietnam.
As the Vietnam's government started to legalize the digital asset combined with the International Financial Center just opened in Da Nang, VietNam.

Our company will be the first one to get the license regarding the RWA services.
I'm looking for professional Fullstack/Web3/Blockchain dev who can join us and take care of the tech fields.
We're warmly welcome you joined as co-founder with equity shared, or full packed services to get the tech done ASAP.
So please dm me for more information, TIA!

I started using the CoinMarketCap API because the free tier looked pretty generous compared to a lot of the other options.

Then I did a few historical data pulls and somehow burned through my credits way faster than I expected lol.

I only realized afterward that CMC doesn’t necessarily charge 1 credit per API request. From what I understand, the credit cost can go up depending on how much data the request returns.

For anyone who’s actually built something using their API, how do you usually work around this?

Do you cache most of the data locally, limit the amount of historical data you pull at once, or use some other setup to keep the credit usage under control?

I’m still pretty early into building this, so I’m also wondering if it makes more sense to switch providers now instead of designing everything around CMC.

CoinGecko is the main alternative I’ve been looking at, but I haven’t used their API much yet. Has anyone here used both? Is CoinGecko noticeably easier to work with when it comes to limits/usage, or is there another API you’d recommend?

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?

Estamos actualizando la DAO y proyectos integrados si alguien puede ayudar

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

Hello devs, hoping you'll find this interesting.

Sellers lend their NFT to the claw machine and earn APR when their cards are put in packs. If their card is pulled they receive their full asking price. NFTs are frozen in sellers own wallet.

Buyers create their own packs from the inventory. The packs themselves are credited a USDC amount which can be used to form a pack of any cards under the mean. Making packs a giftable, tradeable asset.

if any of this is cool to you i can drop the page or contracts etc answer questions

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!

We’ve been building the DNAGEN Mining App and this is a look at the current working prototype.

The idea is simple: start a 24-hour mining session, come back daily, and optionally increase your mining rate through different boost mechanics.

The app is still in development, so I’m interested in real feedback rather than promoting a finished product.

🎥 Here’s the mining app in action.

What would you add, remove, or change before launch?

Would you actually test an app like this?

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]

I’m completely new to Web3 wallets and made a beginner mistake. I withdrew $2.90 in USDT from OKX to my OKX Web3 wallet using the Plasma network because it was cheap, not realizing I would need native XPL tokens to pay network gas fees for any future transfers. Now my USDT is stuck because I don’t have any XPL to execute the send back to the exchange. The fee is literally 0.000018 XPL (<$0.01), but the confirmation button is completely grayed out. Buying $10+ of XPL on the exchange just to pay a fraction of a cent doesn't make sense for $2.90.

If a kind soul could send a tiny fraction of an XPL gas drop to my wallet address, I would be super grateful:

0x13a2b635beabef097febcf70f45247e780330377

Ill be so thankful if anyone helps me.

We’re currently developing a mobile Web3 reward/mining app and I’d like some feedback from other builders before we move toward beta. The current prototype uses a simple 24-hour session system. A user starts a session, progress persists even when the app is closed, and the accumulated balance continues across future sessions. Current systems include: • Base mining/reward rate • 24-hour persistent sessions • Optional ad-based boosts during the active session • Referral boosts based on genuinely active users • ERC-20 wallet integration • DNA Code-based permanent boosts • NFT-based boosts • Mining history and total balance tracking We’re currently testing the logic, persistence and UI before adding the remaining backend functionality. From a Web3 development perspective, what would you change or add before beta? I’m especially interested in opinions about wallet integration, preventing referral abuse, boost mechanics and keeping the system simple for new users.

Hello,

I am a bit curious. For anyone building (or built) an app of any kind in `web3`, for any target platform, do you have any requirements for storing user data that isn't just app data of some sort on a local disk (pc, phone, other device)?

If so, what engineering/product choices are you making to solve that?

I am interested to know if this is a problem anyone has actually encountered or if everyone just keeps it on-device.

Thanks.

One pattern keeps showing up in blockchain projects:
The technology becomes the product.
Teams start with questions like:
Which chain should we build on?
Do we need our own token?
Should this be decentralized?
Can we add AI agents?
How do we make it fully on-chain?
All reasonable technical questions.
But they often come before the much more important one:
**What problem does this solve better for the user?**
That's where a lot of technically impressive Web3 products seem to lose the plot.
A user doesn't care that a transaction went through an elegant smart contract architecture. They care that the payment was cheaper, the settlement was faster, they actually own the asset, or they can do something they couldn't do before.
The best blockchain implementation might actually be the one users barely notice.
We've seen a similar problem with tokens. If removing the token makes the product's value proposition disappear, was there ever a product — or just token economics looking for a use case?
Same with AI now.
Adding an agent to a Web3 product doesn't automatically make it useful. If a normal backend can solve the problem more reliably and cheaply, that's probably what should be used.
Blockchain is great when trust, ownership, verifiability, permissionless access or settlement actually matter.
But “we're using blockchain” isn't a value proposition.
Maybe the next generation of successful Web3 products won't feel particularly “Web3” at all.
**What's a blockchain product you think genuinely solves a user problem better because it's on-chain — not just one that couldn't exist without blockchain?**

The single biggest operational risk for early-stage founders remains hiring traditional hourly dev shops. Before partnering with any external dev team, I've learned to run them through this 5-point evaluation framework:

The 5-Point Evaluation (co-founder approved)

1. Quality of Questions

If a team asks zero questions, it’s an immediate red flag. It's impossible to deeply understand a project without asking anything. But quality matters. Weak devs ask easily googled questions about basic blockchain mechanics. Strong engineers ask highly specific questions focused entirely on your business logic, edge cases, and tokenomics.

2. Proposing Solutions, Not Problems (obvious one)

A weak team will message you saying, "We have a problem, how should we fix it?" A mature team says, "We hit a blocker. Here are three architectural workarounds, the trade-offs for each, and our recommendation."

3. Deep Ecosystem Knowledge

Coding isn't enough. If an agency claims they can build a top-tier lending protocol but doesn't understand the role of risk engines and oracles, they are tourists. Your developers need to know top-tier market leaders like Gauntlet, Steakhouse, Chaos Labs, and RedStone, and understand how their risk modeling and data feeds directly dictate market parameters. If they lack this context, their expertise is strictly surface-level.

4. Full Product Lifecycle Understanding

Writing code and calling it a day is a massive mistake. A real partner understands what happens outside the IDE. They account for security audit buffers, integration with risk providers and oracles before mainnet, and the proper setup of on-chain governance and admin functions.

5. High Agency & Proactivity

Elite teams care about your overall success, not just their Jira tickets. To quote a BD i work closely with:

“When a client is about to make a massive mistake, you have two choices: stay silent and watch them fail, or step in with your expertise, even uninvited, and say: 'We hear what you want to do, but here’s a better way so you don't globally screw this up.'”

Teams for 2026

You can try start with:

DeFi Wonderland — Best for Core DeFi & Governance

Consensys — Best for Enterprise Ethereum & Ecosystem Tooling

Woof Software — Best for Fixed-Outcome & High-Agency Architecture

LimeChain — Best for ZK & Custom DLT Solutions

For transparency, you can recommend your own or don’t recommend at all. But, I'd rather hear real founder experiences than pick someone arbitrarily to just fill the list. Anyway, I hope these practical tips help.

To sum up

In Web3, your dev team is your biggest operational risk. And honestly, don't let the quiet market stop you. It’s not just about the potential ROI it’s about actually laying the bricks for the next chapter of the web, that’s how I see it. 

If you have questions on vetting agencies, need advice, or just want to bounce ideas around, shoot me a DM. Always happy to chat.

I've been building RiJoL95 Explorer, an MIT-licensed, open-source and read-only multi-chain blockchain explorer.

My goal is to build a reusable explorer architecture that is not tied to a single blockchain or a single RPC provider.

The current version supports:

• Ethereum, BNB Smart Chain, Polygon, Base, Arbitrum One, and Gnosis
• Live network overview with block height, block timing, gas price, throughput, block load, and recent activity
• Block lists and detailed block pages
• Transaction lists and transaction details, including decoded methods, fees, receipts, sender/receiver, and native value
• Universal search for block numbers, block hashes, transaction hashes, and EVM addresses
• Address pages with native balances, contract detection, recent transactions, and ERC-20 transfers
• Token holdings and portfolio values when an indexed portfolio provider is configured
• Ethereum Accounts directory with live balances
• ERC-20 token information and available market prices
• Network health/status information
• Multiple RPC endpoints with validation, retry, and automatic failover
• Responsive desktop, tablet, and mobile UI
• Dark and Midnight themes

For core EVM blockchain data, the explorer communicates directly with JSON-RPC providers. It is completely read-only — it does not request seed phrases or private keys and it does not sign or submit transactions.

One thing I want to be transparent about: the project is currently EVM-focused.

The codebase already defines adapter boundaries for Bitcoin-like and Solana-like networks, but those implementations are not available yet. Address transaction and token-transfer history is also currently a bounded recent view rather than a complete historical index.

I'm continuing to develop the project and would really appreciate feedback from the open-source community, especially on the architecture, RPC/indexing approach, UI, and which blockchain family would be most useful to add next.

GitHub: https://github.com/rijol95-web3/rijol95-explorer

Issues, feedback, pull requests, and contributions are welcome.

I'm a motion designer hoping to get my foot in the door of the crypto and fintech industry- I'm curious, what brands and graphics are your favourites in the industry?

I personally love Revolut's graphic design and would love to work on a big brand like that one day.

If you guys know of any motion graphics or design work related to crypto and web3 or have any favourites in particular, I'd love to see it and study their work.

Which brands stand out to you and why?

Not sure how many people here have come across the project yet, so I thought I’d ask. If you’ve been following Acurast for a while, I’d be interested to hear what initially caught your attention or what you find interesting about the project.
And if you’ve only come across it recently, what was your first impression?
Would genuinely be nice to hear some thoughts from the PH Web3 community.

Hey everyone!

I’m a product/UI designer and I want to challenge myself with something different.

Instead of creating another random concept for my portfolio, I want to pick a real problem, design the entire product around it, and actually build it into a working web app.

I want to go through the full process:

• Finding and validating a real problem
• User research/interviews
• Defining the target users
• Mapping user journeys
• Product strategy
• Information architecture
• Wireframes
• UX flows
• High-fidelity UI
• Design system + components
• Prototyping
• Usability testing
• Landing page/marketing
• Building the actual product
• Launching it
• Getting real users and feedback
• Iterating based on what people actually use

The important thing is that it should solve a real problem, not just be another AI wrapper or a concept that sounds cool but nobody needs.

So if you could build a small web product today, what problem would you actually want someone to solve?

Tell me the problem, what you currently use to solve it, or something you wish existed.

I’m going to use the responses to find a problem worth investigating and then document the entire process of turning it into a real product.

Bonus: If you have a problem you've personally experienced, even better. I’d rather build something people actually need than something that just looks good in a portfolio.