Giters

facebook / akd

An implementation of an auditable key directory

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

AKD Clients should prove the sequential nature of a history proof

slawlor opened this issue · comments

commented

To identify "missing" history, client verifiers of a key history proof should confirm that the proof updates are sequential (i.e. the version numbers increase by 1 starting from 0 (or 1, need to confirm initial version number))

This is a small verification change, and the information is available in the clients already, but presently would be a second step and should simply be included inside the key_history_verify call.