ipfs-shipyard / ipfs-shipyard/pm-idm

Make signature timestamps trustworthy

Open
#191 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backend discussion task
Dominant language
No language data
Stars
64
Forks
7
PR merge metrics
No merged PRs in 30d

Description

Description

Ideally, a signature time stamp would be trustworthy. Here’s a few ideas:

  • The relying party asking for a signature defines a timestamp. If the person signs it, it means that he attests that the timestamp is correct
  • Use a blockchain anchor, such as a block, so that both parties can verify the block timestamp
  • Use a timestamp attester service

We need to brainstorm this subject and commit to a solution.

Acceptance Criteria

  • TODO

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or implementation entry points. Start by comparing the proposed relying-party timestamp, blockchain anchor, and timestamp attester approaches, then define a committed solution and acceptance criteria for verifiable signature timestamps.

Written by the indexing model from the issue text.

Assessment

Tech stack
blockchain
Domain
cryptography, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.