Redatium User Guide

Redatium is a marketplace where you decide what to do with your own data — your steps and sleep, your bank transactions, anything you choose. You list it, set a price, and approve every request before anything leaves your phone. Buyers — researchers, brands, anyone interested — find datasets, request access, and pay you directly.

Two things make it different from most apps:

• You stay in control. Your data lives on your device until you approve a specific buyer for a specific request.
• You get paid directly. When someone buys your data, the payment goes to your wallet — not to a platform that takes a cut and resells your data behind your back.

Redatium has two apps that work together. You'll use one or both depending on what you want to do.

A wallet is your secure ID and your payment account, rolled into one. We use MetaMask — a free app most people use for crypto, but here you mostly use it for signing into Redatium and receiving payments.

You don't give us any. The wallet is your identity. We don't run KYC, we don't email you, and we don't have your phone number. Notifications inside the app are tied to your wallet address.

The mobile app reads from Android Health Connect, the system that aggregates data from Google Fit, Fitbit, Samsung Health, and most fitness apps. You decide which categories Redatium can see.

1. Open the mobile app and go to the Wallet tab (this is your "data wallet" — the home for everything you've connected).
2. Choose the Health source and start the connect flow.
3. Android's Health Connect screen opens — choose which data types you want to share (Steps, Heart Rate, Sleep, etc.) and tap Allow.
4. You're back in Redatium — connected sources appear in your data wallet.

The app supports a wide range of Health Connect record types — including Steps, Distance, Active Calories, Total Calories, Heart Rate, Resting Heart Rate, Sleep Sessions, Weight, Height, Blood Pressure, Oxygen Saturation, Body Temperature, Body Fat, Hydration, Nutrition, Exercise Sessions, Speed, VO₂Max, Cycling Cadence, Elevation Gained, Floors Climbed, Power, and a number of additional categories.

Through the EU's PSD2 open banking rules, you can authorise Redatium to read your bank account information so you can sell transaction data — without ever sharing your password.

1. In the Wallet tab, start the bank-connection flow.
2. The current build connects to National Bank of Greece (NBG) — additional banks may be added over time.
3. The app opens NBG's secure login page — sign in with your normal credentials.
4. Authorise read-access to your account information.
5. The app receives the accounts list — pick which ones to include.

Once a source is connected, packaging it into a sellable dataset takes a minute.

1. From the Wallet tab, start a new dataset.
2. Pick the source (e.g. Health → Steps).
3. Choose a time range.
4. Give it a name and a short description ("3 months of daily steps, anonymised, urban resident, runner").
5. Set a price in ETH.
6. Publish.

The dataset shows up in your data wallet and appears in the marketplace for buyers to browse.

When a buyer requests one of your datasets, you get a push notification — even if the app is closed.

1. You see an Android system notification: a new data request.
2. Tap it — the app opens to the Requests tab with the new request highlighted.
3. The request shows the buyer's address, the dataset, the offered price, and how long ago it arrived.
4. Tap to approve the request, or decline it.

Accepting doesn't transfer anything yet — it just signals the buyer that you're willing to fulfil it.

Once you've accepted a request and the buyer is ready, the actual transfer is one tap.

1. On the approved request, tap Transfer Now.
2. The app prepares the file as a torrent and registers the magnet URI with the backend so the buyer can connect.
3. MetaMask opens once for a channel setup signature. Approve it.
4. The transfer begins — pieces are served peer-to-peer to the buyer's browser, and payment for each piece is co-signed off-chain.
5. When all pieces are delivered, the channel is concluded by both parties.
6. To move your earnings to your wallet, withdraw the channel — MetaMask opens for the withdraw transaction, and the funds land in your wallet shortly after.

You're protected. The buyer's funds are locked in the channel from the moment the transfer starts. If the buyer goes offline before it completes, you can submit your latest signed state on-chain from the Channel tab and, after a short challenge window expires, claim the payment for what you've already delivered.

The Channel tab also surfaces any stuck balances — funds in channels that didn't conclude cleanly — and lets you finalise and withdraw them in one tap.

The webapp's Browse page is where you discover datasets.

1. Sign in and open Browse from the sidebar.
2. You see a table of datasets — each row shows the owner, data type, description, rating, and price.
3. Use the filter bar at the top: type, period, and rating, plus a search box.
4. Type a search term — results update as you type.
5. Page through results at the bottom (20 per page, newest first).

Each row shows the seller's star rating from past sales.

You can request one dataset or several in a single bulk request.

1. On the Browse page, tick the checkboxes next to the datasets you want.
2. A Request Data button appears at the top with the count.
3. Click it — a modal opens listing what you've selected.
4. Confirm. A toast confirms the request was sent and the row clears.
5. Visit the Requests page — your requests appear with status Pending.

When a seller approves, the status changes to Approved in real time (no need to refresh), the row briefly glows, and a Download action becomes available.

When a request is approved, downloading walks through a short sequence.

1. On the Requests page, start the download for the approved request.
2. The webapp opens a peer connection to the seller and prepares a state channel.
3. MetaMask opens — approve the deposit transaction (this funds the channel with enough ETH to cover the dataset price).
4. Pieces of the file stream in directly from the seller, and each piece is acknowledged with a co-signed state-channel update — no further MetaMask popups during the transfer.
5. When all pieces have arrived, the channel concludes and the file is offered to your browser as a normal download (it lands in your usual downloads folder).
6. The seller receives payment; any unused balance is returned to your wallet when the channel is finalised.

Your deposit is locked in the channel, but it isn't lost. If the seller never delivers or never co-signs the conclude, you can trigger a unilateral conclude on-chain from the Channel Management page. The contract enforces a challenge period; if the seller doesn't respond, the funds are returned to you minus whatever pieces had already been paid for.

The same page also lists any withdrawable on-chain balances from past channels, so you can recover funds with a single transaction.

After a successful download, you can rate the dataset and the seller from the marketplace. Ratings show up on the seller's future listings and help other buyers make decisions.

Two reasons:

1. Buyers pay in ETH — when you sell, you receive ETH. When you buy, you spend ETH.
2. Gas fees — every on-chain action (registering, opening a channel, withdrawing) costs a tiny network fee, paid in ETH.

A state channel is a private, two-party agreement between buyer and seller that lets you exchange many small payments off-chain, with only one on-chain transaction at each end.

In practice that means: one MetaMask popup at the start of a transfer, one to withdraw at the end, and zero in between — even if the file is split into many pieces. It's the reason transfers feel snappy instead of stop-and-start.

After a successful sale and a concluded channel, your earnings sit on-chain until you withdraw them to your wallet.

Conclude and withdraw are two separate on-chain steps. In the cooperative case, the app handles both around the same time; if something stalls, the Channel tab surfaces it so you can finish manually.

On Base Sepolia (the current testnet deployment), gas fees are effectively free — test-ETH from a faucet covers everything. When Redatium moves to mainnet Base, gas will be paid in real ETH; Base typically charges fractions of a cent for most actions and a few cents for the more expensive ones like opening or concluding a channel. Fees fluctuate with network demand.

On mobile, the Home screen surfaces your recent earnings, and the Channel tab shows the status of your open and recent channels (including anything pending withdraw). The current build doesn't include a built-in CSV export — for now, on-chain transactions can be verified via a block explorer using your wallet address.

Only what's in the dataset you packaged. If you create a dataset of "7 days of step counts", the buyer receives a file with 7 days of step counts and the metadata you wrote (name, description, your wallet address). They don't get:

• Your name, email, or phone number — we don't have them.
• Other categories of health data you didn't include.
• Anything from your bank if the dataset is a health dataset (or vice versa).
• Continuous access — they get one file, one time, for the request you approved.

Everything that isn't part of an approved, completed transfer. The raw health/banking data you connected stays in private app storage on your phone. Redatium's backend stores:

• Your wallet address (public anyway).
• The metadata of each dataset you publish (name, type, price, file size).
• Records of requests and transfers (which buyer, which seller, when, status).

It does not have a copy of any dataset file. Files move peer-to-peer between your device and the buyer's browser.

Every transfer requires your active tap. Specifically:

1. You explicitly approve each individual request before the buyer can start a transfer.
2. You explicitly tap Transfer Now to begin sending the file.
3. You sign the channel setup with your wallet.

There is no "always-on" data flow. No background syncing. No auto-approve. If you don't tap, nothing leaves.

Yes — you control everything.

• Datasets — remove a dataset from your data wallet and it disappears from the marketplace. Past sales aren't reversed (those files already left with buyers), but no new buyer can request it.
• Connected sources — disconnect Health Connect or your bank to stop the app reading any new data.
• Account — your wallet is your account. We don't store anything you can't see in the app.

• Lose your phone, keep your wallet — install MetaMask on a new phone with your recovery phrase, reinstall Redatium, sign in. Your published datasets and earnings are tied to the wallet, not the phone. Datasets without local files will need to be re-created from the source.
• Lose your wallet recovery phrase — there's no recovery. Wallets are non-custodial. Anyone with the phrase controls the wallet; without it, no one does. Write it down. Keep it offline.

Every transfer is protected by an on-chain adjudicator contract. If your counterparty goes offline or stops responding mid-transfer, you can force a resolution from the Channel tab (mobile) or Channel Management page (webapp) by raising a dispute. This submits your latest signed channel state on-chain and starts a challenge period. If the other party doesn't respond before it expires, funds are released automatically based on the signed evidence — buyers reclaim their unused deposit, sellers receive payment for whatever was delivered. There's no human review; the smart contract enforces the rules.

The mobile app uses Firebase Cloud Messaging to push notifications even when the app is closed. The notification currently wired in this build is new data request — when a buyer requests one of your datasets, an Android system notification appears even if Redatium isn't open.

Tapping the notification opens the Requests tab with the new request highlighted.

More notification types (transfer completed, payment received, channel needs attention) are likely to be added over time, but at the moment the only push you'll receive on the device is the new-request alert.

Both apps surface real-time updates while open:

• Mobile — the Requests tab auto-refreshes and highlights the changed item when a status flips.
• Webapp — a SignalR WebSocket connection delivers events the moment they happen. You'll see toasts and a bell-icon panel in the top bar; clicking an item takes you to the relevant page.