What if your app could keep secrets and never lose data, without your users ever touching a crypto token?

🧩 The recipe

• Midnight keeps the logic private. Zero-knowledge proofs let your app prove something is true without revealing the data behind it.
• Arweave keeps the data. It's decentralized storage built to last.
• dStorage puts them together. Files are encrypted on the user's device before they go anywhere, so only the right people can read them.

Picture a medical record, a signed contract or a family photo album. It's locked on your phone, stored on r/Arweave and shared through r/Midnight, and nobody in between can peek.

🚀 No wallet needed

Every decentralized network wants its own token, plus a wallet to hold it. Not anymore with dStorage Pro: it now handles Arweave payments for you, buying the AR and paying the network, just like it already does for Midnight fees. Topping up Pro is easy, as it now supports 💳 credit and debit cards and 🌎 local payment methods.

And here's the key part: Pro only pays the bill. Files are encrypted on the user's device, and Midnight's zero-knowledge proofs are created there too, so Pro never sees the files or the private data behind the proofs, and never holds the encryption keys.

Your users keep full ownership and privacy. No wallet, and nothing given up.

💬 What would you build with it?

We're curious where this fits for you. Are there apps you've held back on because asking users to set up a wallet was a dealbreaker? Or data you'd want stored permanently but kept private? Questions, doubts and criticism are all welcome, especially about the trust model.

We'll be in the comments. If you want to dig into how it works, the docs are here: dstorage.pro/docs

Is there any way to swap AO right now?

Services like Wander Wallet and Permaswap have been saying “now available during migration” for weeks already.

Hi everyone. I’m trying to get help with a serious issue involving Arweave on Keystone 3 Pro.

At the end of May I first used Keystone with Arweave. I connected my Keystone to Wander via QR and received my AR. Everything worked normally.

A few weeks later, I tried to send AR. My Keystone restarted immediately after scanning the QR code from Wander. I tried several times with the same result.

I contacted official Keystone support and followed their instructions: update firmware, update Wander, charge the device, reconnect Wander and retry signing.

After updating, Arweave required an “additional setup” that wasn't present when I originally created the wallet. After completing it, Keystone generated a completely different Arweave address. My original funded address was gone.

I then tested a second Keystone 3 Pro with the same seed phrase. Neither device generates my original Arweave address anymore. After updating both to firmware 3.1.0, they now generate the SAME new address, but it is still not my original funded address. All other networks generate identical addresses on both devices.

This makes me suspect that Keystone changed the way Arweave keys/addresses are derived from the seed between firmware versions. Since Arweave doesn't have a universally adopted BIP44-style derivation standard for its RSA wallets, this seems technically possible.

I've been working with Keystone support for over a month and have provided extensive diagnostics, both devices, firmware information and a video reproducing the issue.

I urgently need to recover access to the ORIGINAL Arweave address. Does anyone here know what derivation algorithm/path Keystone uses for Arweave, and whether it changed between firmware versions?

Any technical help would be greatly appreciated.

I had this conversation with Claude, and the outcome surprised me. I am sharing it with you, seeking experts to validate or confront this thought.

"Pay in stable value, not in tokens. A storage endowment holding tokenised T-bills rather than the native token. Node operators get paid from a yield stream denominated in something that tracks their actual costs. Arweave's endowment model with the volatility removed.

Hedge the operator's real exposure. A node operator's costs are electricity, hardware, and bandwidth. Those are commodity and equity exposures. If tokenised energy or semiconductor exposure is a composable ERC-20, an operator can hold a hedge against their own cost base inside the same contract that pays them.

Fee routing that pays in something stable. The exact accumulator has entirely different economics since now the money does enter from outside the system. That's the distinction that made the memecoin version zero-sum.

Collateralised service guarantees. Slashing bonds posted in stable-value RWAs rather than the volatile native token, so the guarantee doesn't evaporate in the drawdown when you most need it to hold.

The structural reason this matters: DePIN economics are zero-sum in exactly the way the memecoins are, when the only inflow is token speculation. Miners sell to cover costs, price falls, more miners sell. Connecting an external cashflow, real yield, real hedges, is the thing that breaks that loop. Tokenised RWAs are the mechanism for doing it."

I've created this tool to fix the infinite loading and node blocking issues on pages hosted on Arweave.

For those who understand how dApps work, it will be very easy to set up: 🔗Arweave-Local-Proxy-Viewer

Key details:

• It works for any Arweave site that is giving a local CORS error.
• Bypasses node blocks directly on your local machine.

Note*: If you struggle with the setup or don't know much about dApps, try asking an AI for assistance!*

See post on X:

https://x.com/grindtilldusk/status/2089826534744035748?s=46

It appears that Arweave's discord is not maintained, and full of spam bots. Is there a better place to find discussion, or is Arweave just dead in terms of socials?

As far as i could remember, the economics of arweave was built on an assumption that the cost of storage gets lower as time goes by.

However we're going through a bizzar time when the harddisks getting increasingly expensive in the last 3 years.

If this trend continues, will arweave die soon? How soon?

I’ve tried to wrap arweave tokens but they are now stuck at wrapping stage, it’s been 3 days now, could not get in contact with permadao too… any ideas what to do?

Hello community,

today I want to present you my project I was tinkering around for a while:

🕯️ Eternal Rest Pets

A permanent memorial garden for the pets we've loved and lost. 🐾

Claim a plot, build a gravestone, and leave flowers, candles, and tributes in a cozy pixel-art world. Everything lives forever on the Arweave permaweb — no servers, no subscriptions, no expiry.
A Demo mode to try out the project is included, o cost in demo mode.

You can find it here:

https://eternalrestpets.ar.io/

Sorry for the repost, i wanted to add screenshots, but edit didnt allowed me to :/

✅ NFTs with AI descriptions ✅ DAO governance proposals ✅ Web3 blogs & articles ✅ Music & videos from decentralized platforms ✅ Crypto news from 6 sources ✅ Social posts from Hive, Nostr, DeSo, Lens & more

❌ What you WON'T find: Your local pizza place. Google Maps. Wikipedia.

We're not Presearch. We're not Brave. We're not trying to replace Google.

We index Web3. All of it. One search bar.

🐝 zeteoing.com

Welcome to Zeteoing.com. We will be live on May 15th. Cone search our database that holds over 3 million records and climbing.

We have articles, blogs, nfts, and more from Arweave alone. Plus, we have sourced records from Hive,Mirror, Steemit,Nostr, Deso, and more.

Looking for media? We have just added Audis and Threespeak.

Do you want to check a wallet? We show the balance, transactins, whale, and dormant indicators for 7 chains like BTC, ETH, XRP, Matic, LTC, DOGE, and Sol. More will be added soon.

Come check us out on May 15th.

www.Zeteoing.com

#Arweave #Hiveblocks #NFTs # Zeteoing # Nostr

If you look at my recent post. I built a web3 search engine with a wallet look up and a forum... It will have Arweave, IPFS, Mirror, and others. Plus, a lot of nfts

.

Built to bring wallet lookup, decentralized search, and community discussion into one place.

Most Web3 tools do one thing well and leave the rest fragmented. You check a wallet in one place, search assets somewhere else, and if you want context or discussion, you are forced to dig through Discord, Telegram, X, or Reddit to piece it together yourself.

This was built to solve that problem.

Search wallets. Explore decentralized content. Surface digital assets. Then discuss what you find — without leaving the platform.

Instead of bouncing between explorers, marketplaces, and social platforms, this brings search, context, and conversation together in one system.

The goal is simple:

Make Web3 easier to search, easier to understand, and easier to talk about.

We’re getting close to opening beta and looking for a small group of early testers to help break it, pressure test it, and shape what comes next.

If you work in Web3, track on-chain activity, collect digital assets, or want early access, comment “beta” or send me a message.

I am building something that the Web3 community will want to use.

DM me for details,

Thanks

Anyone know the reason why it got blacklisted?

Basedmods was using Arveave to host some mods from RPGhq

Which is a bit surprising, even if I don't agree with their policies, I thought blacklisting was used for illegal stuff.

I feel like this opens up a can of worms where everyone can agree or pressure any gateways to block any content one disagrees with.

We just launched the AO blog, a place to go a bit deeper than short posts and actually explain what’s being built.

First post is a pretty foundational one: Unlocking Trust-Minimized Arweave Gateways with HyperBEAM

Up until now, most access to Arweave has relied on a single gateway (arweave.net). It works, but it’s still a centralized point in the stack.

HyperBEAM changes that by turning gateways into a decentralized, verifiable network:

• Any node can run a gateway
• No single point of failure
• Clients can verify responses instead of just trusting the endpoint

So instead of one gateway → you get a network of them, aligned with the trust model of the permaweb.

This feels like an important step toward making the whole stack actually trustless end-to-end.