Skip to content

Client chaning not described #37

@wbl

Description

@wbl

[Ceri] The introduction states that “the Roughtime protocol provides cryptographic proof of malfeasance, enabling clients to detect and prove to a third party a server's attempts to influence the time a client computes” but the mechanism by which clients detect this malfeasance, chaining Roughtime requests/responses, is not described in this paper. To prove the thesis of the paper, a description of how clients accomplish chaining and how they can detect malfeasance within the chain should be included since those are essential parts of the protocol’s usage. Examples of what clients do once they detect malfeasance would then fit well into the separate Roughtime ecosystem paper.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions