Sunrova: a public, on-chain daily record of off-grid solar for schools and clinics

Hi Omer, nice to see a project that puts the record first and the token after. I read the project paper and the Registry rules already cover a lot: days reported once, corrections as separate records, and the multisig can revoke the oracle. A few things I’d look at before testnet:

  1. Who can post a correction? If the oracle key can, a leaked key can still rewrite history through corrections, even with write once days. I’d keep corrections behind the multisig, or at least store which oracle address posted each report, so after a revocation you can see exactly which days came from the bad key.

  2. The plausibility check lives in the file the oracle writes, so it’s the oracle checking itself. You already store capacity in watt peak on chain, so the Registry can reject any day above something like capacity times 12 hours of full sun. That ceiling is very loose, but it catches a unit bug or a typo that adds three zeros, and nobody has to trust the oracle for it.

  3. Silence only shows up if the oracle posts it. If the oracle is down for a week, those days don’t exist on chain yet. I’d have the public page treat any day after the install date without a report as “no report” on its own, and keep a backfilled day visibly different from one posted on time.

Good luck with the Kenya pilot!

1 Like