Thanks, this is a useful critique.

On the keep-alive idea: SOV has something close to it. Every citizen appoints guardians, and if a key is lost or stolen, two guardians approving within 72 hours make the nodes re-key the account, so the old key can no longer spend. Your extra step, warning the people who dealt with the old key after the alert time, is a good idea and I’ll take it to the roadmap discussion.

On spoofing: enrolment is a palm scan plus a live face check, both on your own phone, and the nodes refuse any palm or face that matches someone already enrolled. So a printed copy of an enrolled person’s palm cannot open a second account. What you describe, a fabricated capture at enrolment, is the real attack, and the whitepaper says so plainly: liveness is checked in the app today, not by the nodes. Server-verifiable liveness is next on the roadmap (section 10).

Eye-movement video with a moving target is a good liveness idea, and your point about camera quality is exactly the trade-off: the live face check today runs on an ordinary phone front camera. Either way, no photo or video of your palm or face is ever stored or sent; the app turns each scan into a set of numbers and the nodes keep only protected templates.

Whitepaper: https://sov-network.github.io/whitepaper.html (I’m one of the developers.)