🧩 Problem Statement
Currently, sensor alert history is only stored in the browser’s DOM table (dynamically rendered in index.html).
This creates several limitations:
💡 Proposed Solution
Store all sensor alert history on-chain using the smart contract.
Enhance BikeSecurity.sol to maintain a per-user alert history, ensuring alerts are:
- 🧾 Persistent
- 🔐 Tamper-proof
- 🔍 Publicly verifiable
🌐 Frontend (index.html)
🎯 Expected Outcome
- ✅ Persistent, tamper-proof alert history
- ✅ Improved trust and transparency
- ✅ Better alignment with Web3 principles
- ✅ More meaningful use of blockchain storage
Hiiii @prasan474 , I'd love to work on this issue and contribute
Do review it and assign it to me !!
🧩 Problem Statement
Currently, sensor alert history is only stored in the browser’s DOM table (dynamically rendered in
index.html).This creates several limitations:
💡 Proposed Solution
Store all sensor alert history on-chain using the smart contract.
Enhance
BikeSecurity.solto maintain a per-user alert history, ensuring alerts are:🌐 Frontend (
index.html)Replace static DOM-based alert table with:
getAlertHistory()Dynamically render alert history from blockchain data
🎯 Expected Outcome
Hiiii @prasan474 , I'd love to work on this issue and contribute
Do review it and assign it to me !!