Skip to main content

Bitmark Improvement Proposals (BIPs)

BIPs are design documents providing information to the Bitmark community or describing new features for Bitmark.

What is a BIP?​

A Bitmark Improvement Proposal (BIP) is a formal document that:

  • Describes a new feature or change
  • Provides technical specification
  • Documents design rationale
  • Tracks implementation status

BIPs are modeled after Bitcoin's BIP process.

BIP Types​

TypeDescription
Standards TrackChanges affecting consensus, protocol, or interoperability
InformationalDesign issues, guidelines, or information
ProcessChanges to BIP process itself

BIP Statuses​

StatusMeaning
DraftUnder development
ProposedReady for community review
FinalAccepted and implemented
ActiveOngoing standards
RejectedNot accepted
WithdrawnRemoved by author
SupersededReplaced by another BIP

BIP Index​

Consensus BIPs​

BIPTitleStatusType
100Original Design - Fair Launch and Core PrinciplesFinalInformational
101Multi-Algorithm Proof-of-Work (mPoW)FinalStandards Track
102Coin Emission Model (CEM)FinalStandards Track

Process BIPs​

BIPTitleStatusType
2BIP ProcessActiveProcess

Draft BIPs​

BIPTitleStatusType
3Marks Exchange ProtocolDraftStandards Track
4Atomic SwapsDraftStandards Track
5Private Key OffsetDraftStandards Track

Key BIPs Explained​

BIP-100: Original Design​

Documents Bitmark's launch parameters and design philosophy:

  • Genesis block specifications
  • Fair launch principles
  • Original network parameters
  • Stakeholder balance approach

Read BIP-100 →

BIP-101: Multi-Algorithm PoW​

The major hard fork introducing:

  • Eight mining algorithms
  • Dark Gravity Wave v3 difficulty
  • Surge Protector and Resurrector
  • Merge mining support

Read BIP-101 →

BIP-102: Coin Emission Model​

Post-fork monetary policy:

  • Emission-based subsidy thresholds
  • Per-algorithm distribution
  • Subsidy Scaling Factor
  • Maximum supply calculations

Read BIP-102 →

Creating a BIP​

Process​

  1. Discuss: Share idea in community channels
  2. Draft: Write BIP using the template
  3. Submit: Create pull request to BIP repository
  4. Review: Community and developer review
  5. Revise: Address feedback
  6. Accept: Merge when consensus reached

Template​

<pre>
BIP: <number>
Title: <title>
Author: <author name and email>
Status: Draft
Type: <Standards Track | Informational | Process>
Created: <date>
License: MIT
</pre>

==Abstract==
Short description of the proposal.

==Motivation==
Why is this change needed?

==Specification==
Technical details of the proposal.

==Rationale==
Design decisions and alternatives considered.

==Backward Compatibility==
Impact on existing systems.

==Reference Implementation==
Links to implementation code.

==Copyright==
This document is licensed under the MIT License.

Repository​

BIPs are maintained at github.com/project-bitmark/BIP.