Obyte Improvement Proposal (formerly Byteball Improvement Proposal)
An Obyte Improvement Proposal (OIP) is a design document providing information to the Obyte community, or describing a new feature for Obyte or its processes or environment. The OIP should provide a concise technical specification of the feature and a rationale for the feature.
We intend OIPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Obyte. The OIP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the OIPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
Title: BBIP Purpose and Guidelines
Author: Peter Miklos @pmiklos
Comments-Summary: No comments yet.
License: BSD-2-Clause, OPL
Title: Consensus Timestamps
Author: Tony Churyumoff @tonych
Discussions-To: Discord #tech
Comments-Summary: No comments yet
Type: Standards Track
License: BSD-2-Clause and CC0-1.0