-
-
Explore DataCrypt: The Cosmic Archive turning scientific dead-ends into assets. Browse verified experiments and live network stats
-
Set the Stage: Input public metadata, select your domain, and set an ETH unlock price for your research.
-
Verify Details: Inspect abstracts, author IDs, and timestamps to validate experiments before blockchain storage.
-
Mint & Earn: Encrypt raw findings, mint a permanent Research NFT, and earn ETH whenever peers access your data.
Inspiration
The inspiration for FailVault (DataCrypt) stems from a critical inefficiency in global research: Positive Publication Bias.
Millions of hours and billions of dollars are wasted every year because researchers unknowingly repeat experiments that have already failed elsewhere.
We wanted to create a platform where "failure" isn't a dead end, but a valuable asset that can be secured, shared, and monetized to accelerate scientific discovery.
What it does
FailVault is a Decentralized Science (DeSci) marketplace that allows researchers to mint their negative results as IP-NFTs.
- Monetize Failure: Researchers set an unlock price in ETH for their findings.
- Secure IP: Public metadata is searchable, while critical findings and raw datasets are encrypted and accessible only to buyers.
- Immutable Proof: Every experiment is timestamped on the Polygon Amoy Testnet, providing permanent proof of discovery and ownership.
How we built it
We engineered a full-stack dApp utilizing:
Frontend:
A high-performance Next.js 14 application styled with a "Cosmic Deep Blue" Tailwind CSS theme and Lucide React icons.Blockchain:
Solidity smart contracts deployed on the Polygon Amoy Testnet to handle NFT minting and ownership logic.Backend & Storage:
Supabase for robust metadata management and indexing.Web3 Integration:
Ethers.js for handling MetaMask interactions and automated network-guard switching.
Challenges we ran into
The Hydration Nightmare
We faced critical hydration errors when building our dynamic starfield background.
Because Math.random() generated different values on the server and client, the UI tree mismatched.
Solution:
We moved all randomized coordinate generation into a useEffect hook to ensure stable client-side rendering.
The RPC Error Wall
We encountered persistent Internal JSON-RPC errors during testing.
This was caused by cross-chain UX friction, as MetaMask often defaulted to Ethereum Mainnet while our contract was deployed on Amoy.
Solution:
We engineered a programmatic "network guard" that intercepts transactions and forces the correct Polygon Amoy context automatically.
Accomplishments that we're proud of
- Successfully creating a seamless bridge between traditional database storage (Supabase) and immutable blockchain storage.
- Achieving a premium "Cosmic" aesthetic that makes scientific data entry feel futuristic and engaging.
- Building a programmatic network-switching system that lowers the barrier for non-crypto-native researchers.
What we learned
- Deep insights into the DeSci (Decentralized Science) ecosystem.
- Handling sensitive data in hybrid on-chain/off-chain architectures.
- Managing complex React lifecycles to prevent hydration mismatches.
- Optimizing smart contract gas usage for data-heavy transactions on Polygon.
What's next for DataCrypt
On-Chain Encryption:
Implementing fully decentralized encryption using Lit Protocol.DAO Governance:
Enabling community-driven validation through a peer-review staking system.Cross-Chain Expansion:
Deploying on additional EVM-compatible chains to scale the research marketplace.
Built With
- amoy
- blockchain
- css3
- ether.js
- hardhat
- ipfs
- javascript
- lucide
- metamask
- polygon
- react
- solidity
- supabase
- tailwind
- typescript
Log in or sign up for Devpost to join the conversation.