Data Pond Non-Profit datapond.earth

UniMarc & Web3

The web3 Data Framework for the Public domain.

A web framework that implements the open data framework and standardises access to web3 — so the people using your app get the experience they already know from web2.

  1. web2experience
  2. web3infrastructure

Developer integration

Code sample coming

Dec2027

  • One standard partner integration
  • Stripe bank-card transactions
  • No direct wallet connection
Wallet support Future direct-wallet support is undecided.

The problem

Web3 still asks people to behave like blockchain users

Wallet connections, chain-specific integrations and fragmented data models make web3 feel unfamiliar. Data Pond standardises that infrastructure behind the web2 experience people already know.

  • Every app should not have to invent its own blockchain integration.

  • Direct wallet connections create friction and are not part of the current framework offer.

  • Open Code needs one shared data model, canonical infrastructure and clear licence terms.

The crossroads

Web2 on the surface. Web3 underneath.

People shouldn’t need to learn a blockchain to use one. The framework keeps the gestures they know from web2 and does the web3 work behind them. Direct wallet integration is not supported.

web2 The gesture web3 Underneath
Create an account Account creation stays inside the app — no external wallet connection.
Save their work Changes save in the browser first, then sync on-chain. Transaction payment uses a Stripe bank card.
Recover access by email An on-chain recovery registry links the account to a hash of their email.
Open a book Served from permanent Arweave storage, its collection anchored on-chain with a SHA-256 fingerprint.

The framework

The open data framework, implemented.

One standard way into web3 for every partner app — so no team has to write its own blockchain code, and every app speaks to the same open data.

  1. 01 INTEGRATE

    One standard integration

    The partner code sample arrives in December 2027, providing one supported path into the framework.

  2. 02 REGISTRY

    No hard-coded addresses

    Contract addresses and ABIs load from the published registry, with an on-chain fallback. When a contract is migrated, your app follows.

  3. 03 MODELS

    One shared data model

    Generated data models for Vue, React, Solid and Astro, so every partner app reads and writes the same records.

  4. 04 SYNC

    Local first, then on-chain

    Changes are saved in the browser first and synced on-chain after, so the interface doesn’t have to wait for a block.

  5. 05 STORAGE

    Permanent, provable storage

    Works live on Arweave. Each collection is anchored on-chain with its SHA-256 fingerprint, so anyone can check a copy.

  6. 06 PAYMENT

    Bank card, not wallet

    Transactions use Stripe bank-card payment for now. Direct wallet integration is not supported; future support is undecided.

Partner code sample coming December 2027. Direct wallet integration is not part of the current offer.

The promise

The web2 experience and web3 infrastructure converge on one promise.

Read the D-Open Code Sovereign Licence registry.worldbibliotech.com/licence
  1. Open Code.

    The code is visible for inspection, but remains copyrighted and subject to the D-Open Code Sovereign Licence. Open Code is not open source.

  2. Free to use.

    The licence permits use, copying and distribution without a licence fee, subject to all of its terms and conditions.

  3. No code change allowed.

    The licence grants no right to modify, adapt, patch or fork the code. Unauthorised changes infringe copyright and may result in legal action.

Who it’s for

One framework, four kinds of partner.

From the D-SAFE network’s own startups to public archives: teams that want web3’s permanence and proof without writing their own blockchain code.

  1. D-SAFE Network — UniMarc

    Need one standard framework to build on, instead of each team writing its own blockchain code.

  2. Web3 transition developers

    Need web3 infrastructure with a web2 experience, without direct wallet integration.

  3. Open Code partners

    Need visible, copyrighted code they can use, copy and distribute under clear terms, without modifying it.

  4. Public digital archives

    Need permanent, verifiable storage connected through one shared data model.

Roadmap

From framework launch to the developer community.

  1. 2025 Delivered

    Focus

    • Research
  2. 2026 Delivered

    Focus

    • Framework and registry launch

    Go to market

    • Partner programme

    Lead generation

    • Open Code partner outreach
  3. 2027 Next

    Focus

    • Developer code sample — December
    • MARC certifications
    • Developer community
    • Grant applications

    Go to market

    • Partner integrations
    • Grant programme applications

    Lead generation

    • Standards body engagement

Become a partner

Connect your web app to the ecosystem.

Use the Open Code framework under its terms and conditions to bring web3 to your users with the experience of web2. Tell us about your app — what it does, who uses it, and what you’d like to connect.

datapond.earth

What partnering means

  1. 01 Use the framework unmodified The code remains copyrighted. No edits, patches, derivatives, forks or redirection to other ledgers or databases.
  2. 02 Keep public data open No paywalls and no mandatory login in front of the ecosystem’s public data.
  3. 03 Serve D-SAFE content Content your app serves through the framework meets the D-SAFE label standards.
Data Pond · Ꭰ-SAFE REGISTRY © 2026 DATAPOND Ꭰ-Library PTY LTD · ACN 695 045 071