STEP 1
Build Individual Policies (ℜ1…ℜ7)
Each policy = 7 rules → SHA-256 → one policy hash ℍPi. Add as many as you want.
Quick Presets
ℜ1 · Role
🩺
Doctor
🚑
Paramedic
💊
Nurse
🧑⚕️
Health Asst
🔬
Researcher
🏥
Manager
ℜ2 · Location & ℜ3 · Department
ℜ4 · Start & ℜ5 · End & ℜ6 · Days
Mon
Tue
Wed
Thu
Fri
Sat
Sun
ℜ7 · Operations
Each click adds this policy's rules to the collection. Change fields and add more to build a Policy Class with many policies.
Live Preview (current form)
ℜ1 Role
ℜ2 Location
ℜ3 Dept
ℜ4-5 Time
ℜ6 Days
ℜ7 Ops
When you click Add to Collection, this policy gets hashed as ℍPi = SHA256(ℜ1‖ℜ2‖…‖ℜ7) and added below.
STEP 2
Policy Collection → Mother Hash (ℍPC)
Combine all policy hashes into a single mother hash — this is what goes on blockchain
Added Policies
0
📋
No policies added yet. Configure a policy on the left and click "Add to Collection".
Merkle Tree
Level 3 — Mother Hash (ℍPC)
—
Level 2 — Policy Hashes (ℍP1…ℍPn)
0 hashes
Level 1 — Rules
0 rules sets
Mother Hash ℍPC — stored on blockchain
Add policies and click "Generate Mother Hash" →
ℍPi = SHA256(ℜ1‖ℜ2‖…‖ℜ7) · ℍPC = SHA256(ℍP1‖ℍP2‖…‖ℍPn)
STEP 3
Single Operation Tests on Blockchain
Test each contract function individually — latency and gas measured from real transactions
storeMotherHash()
Stores the mother hash on-chain for the first time. Costs gas. MetaMask will popup once.
Latency —
Gas used —
Cost (ETH) —
Cost (USD) —
Block # —
Tx
—
getMotherHash()
Reads the stored hash from blockchain. Free — no gas, no MetaMask popup.
Latency —
Gas cost Free (view)
Hash found —
Hash
—
updateMotherHash()
Updates an existing hash. PC must already exist from the write above. Costs gas.
Latency —
Gas used —
Cost (ETH) —
Cost (USD) —
Block # —
Tx
—