The Bintan Project: Data On-Chain Workflow

1. 📁 Data Preparation

The project produces: Geodata (spatial info) & Reports & indexes (metadata, reports). All files are listed in a Manifest, which acts as a directory.

2. 🔐 File–Hash Pair Creation

Each file is assigned a unique hash — its fingerprint. Then they are paired together to form a File–Hash Pair. This guarantees every data item can later be verified against its original form.

3. ☁️ IPFS Upload

The File–Hash Pairs are uploaded to IPFS, where each pair receives:

A File Digest — a compact representation of the pair.

A File Digest CID — the unique IPFS address for that digest.

These digests serve as the foundation for what’s later recorded on-chain.

4. 🔗 On-Chain Transaction

In this step, the File Digest CID is embedded inside a blockchain transaction.Once the transaction is confirmed on-chain, it serves as a timestamped record proving that the dataset existed at that specific block time.

✅ Think of it like mailing a sealed envelope — the envelope (transaction) is what’s publicly recorded on-chain, and inside it is a note (the digest CID) pointing to your data on IPFS.

5. 🧠 Retrieve Data Smart Contract

The Retrieve Data Smart Contract functions as a public interface to access dataset records.The contract can locate the corresponding on-chain transaction and read the content embedded in it, including the File Digest CID, and then use this CID to retrieve the dataset and its related data from IPFS.

This allows anyone to obtain the dataset’s reference and retrieve the related data from IPFS — directly and transparently.

6. 🖥️ User Interfaces

Two main interfaces make the system transparent and accessible:

Napital Dashboard: Uses a traditional interface to neatly present the projetc data we store.

Napital Onchain Viewer: Retrieves IPFS data via the smart contract on the blockchain. Visually and clearly display the full set of retrieved data.