Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Follow up the changes in RFC0006 Merkle Proof #182

Closed
doitian opened this issue Jan 11, 2019 · 2 comments
Closed

Follow up the changes in RFC0006 Merkle Proof #182

doitian opened this issue Jan 11, 2019 · 2 comments
Assignees
@quake
Labels
p:could-have Priority: desirable but not necessary s:available Status: This issue is available for implementation. t:enhancement Type: Feature, refactoring.

Comments

@doitian
Copy link
Member

doitian commented Jan 11, 2019

See nervosnetwork/rfcs#62
@doitian doitian added s:available Status: This issue is available for implementation. p:could-have Priority: desirable but not necessary t:enhancement Type: Feature, refactoring. labels Jan 14, 2019
@doitian
Copy link
Member Author

doitian commented Jan 14, 2019

Review Log
Last Reviewed At — 2019-01-14

Move to backlog

@doitian
Copy link
Member Author

doitian commented Jan 30, 2019

Closed by #232

@doitian doitian closed this as completed Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@quake quake

Labels
p:could-have Priority: desirable but not necessary s:available Status: This issue is available for implementation. t:enhancement Type: Feature, refactoring.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@quake @doitian