Data Pond Non-Profit
Partner
Data Pond Non-Profit datapond.earth

UniMarc & Web3

The web3 library for sovereign data

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
Become a partner See the framework

Developer integration

Partner launch planned

Late2026

  • 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 launch is planned for late 2026, 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 launch planned for late 2026. Direct wallet integration is not part of the current offer.

Live in the public npm package

The framework is already running.

Explore @the_library/public and try its ORM, front-end adapters, persistence pipeline and Web3 book downloader in your own project.

Explore the package on npm
  1. 01 ORM · FRONT END

    One data model. Four front ends.

    Generated Book, Tag, Person and Post models connect to reactive adapters for Vue, React, Solid and Astro. Model reads and edits flow through the same shared schema.

  2. 02 ACTIONS · STATS

    Useful actions are already tracked.

    Records can capture visits, downloads, ratings, shares and activity on individual parts such as book chapters. Lists for visited, downloaded and favourite records are ready to use.

  3. 03 PERSISTENCE

    Edits persist as you work.

    ORM edits and local engagement actions enter the patch queue and are saved in IndexedDB. On the next boot, the models and local stats are rebuilt from saved history.

  4. 04 BOOKS · ASSETS

    Built for large books and images.

    Web workers fetch and process Arweave PDFs, decrypt and decompress files, and render page images. Parallel queues, prefetching and browser caches make repeat opens faster.

OFFLINE BY DESIGN

Once a book or image has been downloaded and cached, the service worker can serve it offline across reloads. Apps can request persistent browser storage; available space and eviction remain controlled by the browser. Local engagement stats stay on that device and are not sent to the blockchain.

A taste of the live package

Small calls. Useful building blocks.

These examples come from the public @the_library/public API documentation. They show book access, local engagement and framework integration—not the future partner launch sample.

  1. 01 READ A BOOK

    Fetch the PDF or a page image.

    import { GetPdf, GetImage } from '@the_library/public/downloader';

const pdf = await GetPdf(txId, { priority: 'high' });
const page = await GetImage(txId, 5);

    The package fetches, processes and caches book files and rendered page previews.

  2. 02 TRACK ENGAGEMENT

    Actions live on the model.

    import { Book } from '@the_library/public/models/models';
import { Rating } from '@the_library/public/models';

const book = await Book.LoadAsync(bookId);
book.visit();
book.rating = Rating.Keep;

    Visits and ratings use the local patch pipeline and persist in IndexedDB; they are not sent to the blockchain.

  3. 03 BUILD REACTIVE UI

    Follow download state in Vue.

    import { useFileStatus } from '@the_library/public/downloader/vue';

const status = useFileStatus(txId);

    Vue, React and Solid adapters expose reactive download and rendering progress.

API reference and more examples: @the_library/public on npm ↗

A public-domain corpus. Your design.

Build a library your way.

The framework gives open-code developers a foundation for creating new ways to discover, read and discuss public-domain books. Design a library or forum in the shape that serves your readers.

  1. 01 DISCOVER

    A library with your point of view.

    Shape a public-domain collection around a language, subject, place, period or community. Choose how people browse and read it.

  2. 02 CREATE

    A reading room, archive or learning space.

    Build the experience that fits your audience—from a focused catalog to a guided way through books and related materials.

  3. 03 PARTICIPATE

    A forum connected to the library.

    Forum support is in development, including a level-check action and forum definitions, so developers can design community spaces around their collections.

Open Code is copyrighted and governed by its licence; it is not open-source software.

Our promise

D.I.C. Licence

A familiar web2 experience. Decentralized web3 infrastructure. One licence for sharing knowledge.

Decentralized
Knowledge shared through decentralized infrastructure.
Integral
Reuse with no paywall, no commercial use, no ads and no social media integration.
Creative Commons
Attribution. No modification. Non-commercial use.
Read the D.I.C. Licence dsafe.legal/documentation/#dic-licence

The code behind the promise

  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.

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

+ K Knowledge

D.I.C. + Knowledge gives us the D.I.C.K. Safe label, shortened to Ꭰ-SAFE.

The mark uses the Cherokee letter Ꭰ (U+13A0) in place of the Latin D.

Ꭰ-SAFE The knowledge label

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

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

  2. Compatibility with the ancient ecosystem

    Supports standards that integrates all book libraries in the world

  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

The network

The D-SAFE Network

Five startups built on the D-Open Code Sovereign Licence and the D-Code Model, each solving a different piece of the same problem: knowledge infrastructure that outlasts any single company.

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.

Apply to partner Read the licence

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