mimblewimble/grin

Time locked transaction outputs

Open

#25 opened on Dec 23, 2016

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

Repository metrics

Stars
 (4,876 stars)
PR merge metrics
 (Avg merge 6d 11h) (25 merged PRs in 30d)

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

Research direction
Investigate how to add a time locked output field and signature to the transaction proof, and study existing implementations in other cryptocurrencies like Bitcoin's CLTV/CSV.
Tech stack
rust
Domain
blockchain
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustUnderstanding of Mimblewimble protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30