mimblewimble/grin

Time locked transaction outputs

Open

#25 建立於 2016年12月23日

在 GitHub 查看
 (24 留言) (0 反應) (0 負責人)Rust (4,876 star) (991 fork)batch import
enhancementhelp wantedresearch

描述

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.

貢獻者指南

技術棧
rust
領域
backendsecurity
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Rust programmingMimblewimble protocol basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
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.