OriginTrail RFCs

The OriginTrail development is transparent and being guided by public debate through the Trace Alliance working groups, as well as through technical discussions within the community through the technical Requests for Comments (OT-RFCs).

The RFCs have formerly been part of the official documentation and have moved to this repository from OT-RFC-07 on October 12th 2020.

The RFC lifecycle

There are three stages for an OT-RFC, easily visible in the RFC Repository Kanban.

  • DRAFT stage: the RFC is associated DRAFT status in the period of writing and collaborating on the RFC. Once the discussions are completed, the RFC moves to Accepted stage

  • ACCEPTED stage: The accepted RFCs are to be implemented by the OriginTrail developers, serving as technical specification

  • FINAL stage: Once RFCs have been implemented and merged into the codebase, they are considered FINAL

The RFC rules & best practices

  • RFCs move to the β€œAccepted” stage by the core developers, after discussions with relevant Trace Alliance working group task forces and the community

  • A β€œlast call” can be issued for a RFC which is close to moving out of the draft stage to notify the community to provide the final feedback (about a week before acceptance)

  • Moving the RFC to β€œFinal” stage is performed by developers, responsible to indicate the specific client release that has implemented the RFC

  • All RFC related discussions should be directed to the dedicated RFC issues page to promote a constructive, structured and long-term debate on the RFC, avoiding less structured channels such as chat rooms and social media.

The RFC Github repository can be found here.

Can I contribute to RFCs?

Absolutely! You can propose your own RFCs or comment and provide feedback on the existing ones in the pipeline. The OriginTrail community welcomes inputs and will greatly appreciate any improvement proposals!

Last updated