transparency-dev / transparency-dev/tessera
Feature: Preordered Logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 238
- Forks
- 56
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 35
Description
Preordered Logs was supported by Trillian v1. In this mode there is no sequencer or queue, and the user writes each new leaf to an explicit index. We could support this by having a new lifecycle state that only exposed a single method such as func Set(ctx context.Context, index uint64, entry *Entry) error.
The major blocker to implementing this feature is a good use-case in the modern transparency world. This issue will be addressed when we have upvotes and comments from the community giving a desire signal, and ideally concrete use-cases for the feature.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the proposed lifecycle state and the Set(ctx context.Context, index uint64, entry *Entry) error entry point described in the issue, and compare it with the Trillian v1 preordered-log model. The issue is not ready for implementation: done first requires community upvotes, comments, and concrete modern transparency use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100