Skip to content

Roadmap

Jump to bottom Edit New page
lehnberg edited this page Feb 27, 2020 · 4 revisions

This document outlines items and timelines for known deliverables for Grin. By design, Grin’s roadmap is minimal. It is an open source, community-driven project, and there is no development team working full time in an office somewhere. Volunteer contributions are essential for progress, and these cannot easily be slotted into gantt charts or sprints.

2020

Full details: https://forum.grin.mw/t/grin2020-roadmap/7096

Development

  • Kernel types. Complete specification of and implement relative kernels as outlined in mimblewimble/grin-rfcs#19
  • Transaction building. Establish an approach that will be robust and good enough be a viable baseline for building grin transactions, and can replace unsafe http methods.
  • Output linkability. Explore ideas and approaches to obfuscate the transaction graph, both in the mempool/p2p layer, and on the blockchain itself.
  • P2P layer. Iterate on dandelion, explore Erlay, explore encrypting node traffic, and determine whether I2P support is something that should be dropped or targeted for implementation.
  • Syncing and IBD. Take advantage of unspent bitmap commitment added in v3.0.0 to split IBD among many peers to improve latency, speed, and reliability. Explore FlyClient as a viable approach to light clients for mobiles and other devices, in order to reduce the reliance on hosted nodes.
  • Proof-of-work. Prepare final tweak of ASIC Resistant secondary proof-of-work algorithm.
  • Mining protocol. Research Stratum v2 and establish whether it's a viable solution to reduce mining pool centralization.
  • Testing. Integration tests, regression tests, unit tests. Processes, tools, and formalizing approaches.
  • Releasing. Binary packaging, release processes, planning.
  • Network upgrades. What should happen after the last scheduled hard fork in Jan 2021?

Developer experience (DX)

  • Documentation. Promote documentation to a first class citizen in Grin.
  • Exchange integrations. Provide better integration instructions for exchanges. Best practices, examples, and components as required.
  • Wallet integrations. Provide better guidance for wallet projects on how to support Grin.
  • Merchant integrations. Provide instructions for merchants on how to accept payments in Grin from their users in a manner that is privacy preserving and secure.

Community

  • Onboarding. Make it easier for newcomers to begin contributing to the project.
  • grincon2. Better planning, better lead times, raise quality, and attendance.
  • Website. Improve communication and content on the Grin website.
  • Meetups. Facilitate meetup organization and "local community start packages".

Governance

  • Moderation. Establish an indepent Moderation team.
  • Vision. Define Grin trade-offs and design goals.
  • Funding proposals. Formalize a process, encourage submissions.
  • Resilience. Avoid creating any more single point of failures, share access and privileges.
  • 2021 Roadmap. Improve on the roadmap planning process for the next year. More structure, milestones, and make it more inclusive.

2019

Q3

Q4

  • Arrange grincon1 conference in Berlin
  • Conclude scoping, planning, and implementation work ahead of network upgrade

2020

Q1

  • Conduct Scheduled Hard Fork upgrade to Grin v3.0

Q2

  • Conclude scoping, planning, and implementation work ahead of network upgrade

Q3

  • Conduct Scheduled Hard Fork upgrade to Grin v4.0

Q4

  • Conclude scoping, planning, and implementation work ahead of network upgrade

2021

Q1

  • Conduct Scheduled Hard Fork upgrade to Grin v5.0

git clone https://github.com/mimblewimble/docs.wiki

Basics

Contributing

Development

Mining

Infrastructure

Exchange integrations

R&D

Grin Community

Grin Governance

Risk Management

Grin Internals

Misc

Clone this wiki locally