MÆc’s Basic Improvement process leverages decentralized governance to enhance and expand the TEDDi software platform. Aligned with open-source principles and transparent development, MÆc utilizes this system for managing all proposed modifications and enhancements to TEDDi. This framework facilitates active participation from developers, users, governmental bodies, and corporate entities in TEDDi’s evolution. MÆc posits that this collaborative methodology is crucial for establishing a robust and decentralized governance model that maximizes value for all stakeholders.

Appointed Keeper: Michael A.

Contribute

First review BIP-1. Then clone the repository and add your BIP to it. There is a template BIP here. Then submit a Pull Request to MA8’s BIPs repository.

BIP status terms

  • Idea – An idea that is pre-draft. This is not tracked within the BIP Repository.
  • Draft – The first formally tracked stage of an BIP in development. A BIP is merged by an BIP Editor into the BIP repository when properly formatted.
  • Review – A BIP Author marks a BIP as ready for and requesting Peer Review.
  • Last Call – This is the final review window for an BIP before moving to FINAL. A BIP editor will assign Last Call status and set a review end date (`last-call-deadline`), typically 14 days later. If this period results in necessary normative changes it will revert the BIP to Review.
  • Final – This BIP represents the final standard. A Final BIP exists in a state of finality and should only be updated to correct errata and add non-normative clarifications.
  • Stagnant – Any BIP in Draft or Review if inactive for a period of 6 months or greater is moved to Stagnant. An BIP may be resurrected from this state by Authors or BIP Editors through moving it back to Draft.
  • Withdrawn – The BIP Author(s) have withdrawn the proposed BIP. This state has finality and can no longer be resurrected using this BIP number. If the idea is pursued at later date it is considered a new proposal.
  • Living – A special status for BIPs that are designed to be continually updated and not reach a state of finality. This includes most notably BIP-1.

BIP Types

BIPs are separated into a number of types, and each has its own list of BIPs.

Standard Track

Describes any change that affects most or all MA8 implementations, such as a change to the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using MA8. Furthermore Standard BIPs can be broken down into the following categories.

Core

Networking 

Interface

ERC

Meta

Informational