mimblewimble/grin

Time locked transaction outputs

Open

#25 opened on Dec 23, 2016

View on GitHub
 (24 comments) (0 reactions) (0 assignees)Rust (4,876 stars) (991 forks)batch import
enhancementhelp wantedresearch

Description

How do we support them? Would likely require another output field and a signature. Maybe add to the transaction proof signature.

This would be great to have for higher level contract supports like payment channels, lightning, etc.

Contributor guide

Tech stack
rust
Domain
backendsecurity
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Rust programmingMimblewimble protocol basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the current transaction output structure and transaction proof signature in the Grin codebase. Review comments in the issue for design ideas, specifically the suggestion to add an output field and signature. Consider how time locked outputs are implemented in other cryptocurrencies and how they could be integrated into the Mimblewimble scheme. Look at the existing kernel and output modules in the source code for potential modification points.