OriginTrail
  • Get started with OriginTrail
  • OriginTrail Ecosystem — Call for Papers (Coming Soon)
  • Key Concepts
    • Decentralized Knowledge Graph (DKG)
    • DKG key concepts
  • Build with DKG
    • Quickstart (test drive the DKG in 5 mins)
      • Quickstart with Node.js
      • Quickstart with Python
    • ChatDKG builder toolkit
      • DKG SDK
        • Development environment setup
        • DKG Javascript SDK (dkg.js)
          • Interact with DKG paranets
          • Knowledge submission & curation
          • Paranet's incentives pool implementation
        • DKG Python SDK (dkg.py)
      • DKG paranets
        • Deploying a DKG paranet
        • Building with DKG paranets
        • Syncing a DKG Paranet
        • Initial Paranet Offerings (IPOs)
          • IPO specification
          • Launching your IPO
          • Paranet's incentives pool
          • IPO voting
      • AI agents
        • ElizaOS DKG agent
        • Custom DKG Python agent
        • Custom DKG JavaScript agent
    • DKG Edge Node
      • DKG Edge Node architecture
      • Get started with the Edge Node boilerplate
        • Automated setup with the installer
        • Manual setup
        • Usage example
      • Customize & build with the Edge Node
      • Knowledge Mining and dRAG examples
      • DKG Edge Node inception program
      • DKG Edge Node API documentation
    • DKG Core Node
      • Run a V8 Core Node on testnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
      • Run a V8 Core Node on mainnet
        • Preparation for V8 DKG Core Node deployment
        • V8 DKG Core Node installation
  • Delegated staking
    • Delegated staking—Introduction
      • Step-by-step staking
      • Redelegating stake
  • Integrated Blockchains
    • Base blockchain
      • Connect to Base
    • Gnosis chain
      • Connect to Gnosis
    • NeuroWeb
    • Teleport instructions - NeuroWeb
    • Bridging to Moonbeam
    • Deployed smart contracts
  • Bounties & rewards
    • General bug bounty
    • Code contributions & V8 bug bounty
  • Whitepapers & RFCs
    • OriginTrail whitepaper
    • OriginTrail RFCs
  • Useful Resources
    • What's new with OriginTrail V8
    • DKG V8 guidebook
      • Protocol updates
      • Feature roadmap
      • How to upgrade to V8?
    • Public nodes
    • Tutorials
    • Test token faucet
    • Development principles
    • Community created resources
    • Linked data & knowledge graphs
    • Available networks, network details and RPCs
    • OT Node Engine implementation details
      • Modules
      • Command Executor
    • Contribution guidelines
      • Guidelines for automated test contributions
    • Explore the OriginTrail ecosystem
Powered by GitBook
On this page
  • The RFC lifecycle
  • The RFC rules & best practices
  • Can I contribute to RFCs?

Was this helpful?

Edit on GitHub
  1. Whitepapers & RFCs

OriginTrail RFCs

PreviousOriginTrail whitepaperNextWhat's new with OriginTrail V8

Last updated 3 months ago

Was this helpful?

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 from OT-RFC-07 on October 12, 2020.

The RFC lifecycle

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

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

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

  • 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 that 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 the “Final” stage is performed by developers to indicate the specific client release that has implemented the RFC

  • All RFC-related discussions should be directed to the dedicated 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 .

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!

this repository
the RFC Repository Kanban
RFC issues
here