🏗️ Architecture Overview
🆔 NFT-Based Device Registry
Each robot is minted as an NFT (non-transferable) with metadata:
Type, specs, firmware version
Audit and performance history
Status (active, inactive, verified)
⚙️ Smart Task Contracts
Healthcare tasks are structured on-chain:
Type, priority, target device
Reward in $MRN
Required completion data (e.g. telemetry hash)
🔏 Verifiable Telemetry
Device signs telemetry or session logs.
On-chain hashes used for proof of work done.
Sensitive data stored off-chain (IPFS or encrypted blob), referenced via CID.
🪙 Incentive Engine
Token rewards distributed for task completion:
Robots/Operators earn $MRN
Patients earn for participation or improvement
Clinics can earn through uptime, compliance, or contribution
🔐 Privacy & Security
Telemetry and patient data remain off-chain, encrypted.
On-chain only
Hashed proofs
Device IDs
Task status
Optional integration of ZK proofs for advanced compliance or trials
⚙️ Ecosystem Stack
Blockchain
Solana (Anchor, SPL Tokens, PDAs)
Storage
IPFS / Arweave for telemetry and logs
Frontend
React + Wallet Adapter
Device Auth
Firmware-based signing or secure enclave keys
Oracles
Switchboard for attestation of sensor data
Last updated