rollinindough

1/ Non-profits accepting crypto face a weird problem: Everything is transparent… but no one can actually understand it. Donors don’t want Etherscan links. They want a simple, verifiable breakdown of where money went. So I built a solution

1/5 Most blockchains are built on a broken assumption: “Whoever holds the private key has full control.” But that model is starting to break as onchain apps become more complex, AI agents, DAOs, institutional custody, automated systems. We need something new.

1/ I just published a deep dive on building Privacy-Preserving Federated Learning using Oasis Sapphire Not the usual NFT/oracle stuff, this is real ML infrastructure with confidential compute. dev.to/rollingindo/pr…

1/ Most AI agents today are powerful… but forget everything. Every new session = reset. Every model switch = lost context. That’s the real bottleneck in AI systems right now.

1/ Want to run private, trustless NFT auctions on blockchain? With Oasis Sapphire, bids can be fully confidential, yet the winner is verifiable on-chain. I just built a sealed-bid NFT auction tutorial!

1/ Most “onchain” trading platforms aren’t actually trustless. Yes, funds are onchain. Yes, transactions are transparent. But the most important logic? Still happens off-chain.

I wrote a tutorial on building a privacy-preserving AI oracle using Oasis Network and its confidential runtime Sapphire ParaTime. It shows how to run AI inference on sensitive data without exposing inputs on-chain. Thread: dev.to/rollingindo/bu…

1/ Decentralized storage solved one major problem: data availability. But it still struggles with something equally important: Privacy and access control. Here’s why encryption and programmable access layers are becoming essential for Web3 storage 🧵

Building a Cross-Chain Confidential Trust Score Oracle with @OasisProtocol #web3 #privacy #oasisnetwork dev.to/rollingindo/bu…

1/ Flashback Labs is a real world example of what happens when personal AI is built on confidential infrastructure instead of traditional cloud storage. medium.com/p/1e7f67db0471

1/ Fully transparent smart contracts are overfitted to tokens. If your only primitive is public state, you constrain what can exist on chain. I wrote about this through the lens of @newonoasis Network and confidential execution

Web3 devs: we optimized for transparency and called it a feature. But full public state is a constraint, not a default for serious apps. I wrote a breakdown of Oasis Network from a systems design perspective 👇

@OasisProtocol 10/ If you are a backend engineer, AI engineer, or founder building real software, this matters. Privacy is not optional infrastructure. It is foundational! #web3 #privacy

@OasisProtocol 9/ From a system design perspective: - Public chains handle settlement. - Oasis handles sensitive execution. Public where it makes sense. Private where it is required.

1/Most blockchains are built around one assumption: everything should be public. That works for transfers. It completely breaks real applications. I wrote a guide explaining @OasisProtocol from a Web2 engineer’s perspective 👇 @rayQuGR/oasis-network-explained-like-youre-a-web2-engineer-b60d339ca198?postPublishedType=repub" target="_blank" rel="nofollow noopener">medium.com/@rayQuGR/oasis…