Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 60 additions & 0 deletions data/projects/bips.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
---
title: 'Bitcoin Improvement Proposals'
dateAdded: '2026-08-08'
summary: "Bitcoin's public specification process and proposal archive."
nym: 'BIP Editors and Authors'
website: 'https://bips.dev/'
coverImage: '/static/images/projects/bips.svg'
containCoverImage: true
git: 'https://github.com/bitcoin/bips'
tags: ['Bitcoin', 'Protocol', 'Documentation']
fund: general
announcementLink: '/blog/jon-atack-receives-lts-grant'
---

Bitcoin Improvement Proposals (BIPs) are the public specification process and
archive for Bitcoin. They give authors a structured way to document protocol
changes, peer-to-peer behavior, wallet standards, application conventions, and
process updates so implementers can review the same technical proposal from the
same source of truth.

The [BIPs repository][repo] is the canonical publication medium. It stores each
proposal as a versioned text file, tracks edits through Git history, and makes
the latest accepted draft easy to retrieve. The rendered [bips.dev][bips-dev]
site gives developers and reviewers a faster way to browse those specifications.

## Why fund it?

Bitcoin development relies on written specifications when changes touch more
than one implementation, wallet, library, or user workflow. BIPs help turn
mailing list discussions and design sketches into stable documents that can be
reviewed, referenced, implemented, tested, and challenged over time.

That work is mostly coordination and maintenance. Authors have to define scope,

@jonatack jonatack Aug 8, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review, particularly of technical soundness and completeness, is the most time-consuming (and critical) aspect.

It has become a larger part of the BIP maintainership process, as we receive more and more LLM-generated submissions that are now trivial for authors to make but don't always make technical or conceptual sense and that (too often) skip the required mail list discussion step.

Also, moderation is an (annoying) aspect that can at times be time-consuming.

Scope discussions can also be long. The Ordinals BIP draft, for instance.

In summary, the role is called Editor, but in reality is maintainership, technical review, editor, scope and soundness guardian, and moderator.

write clear specifications, address objections, record rationale, and revise the
proposal as review improves it. Editors keep the process moving by checking
format, scope, metadata, licensing, status, and publication criteria.

OpenSats funds [Jon Atack][jon-announce], a Bitcoin Core contributor and BIP
editor, through the Long-Term Support program. His grant includes work on BIP
maintainership, technical and conceptual review, scope checks, moderation, and
publication work, especially where proposals affect Bitcoin's consensus rules,
decentralization, security, robustness, privacy, or user experience.

## What's next?

The BIP process was refreshed by [BIP 3][bip-3], which replaced the older BIP 2
process and clarified the role of BIP authors, deputies, editors, proposal
types, statuses, and publication criteria.

The repository remains active because Bitcoin remains active. Current and future
work includes new consensus proposals, peer-service changes, wallet
interoperability standards, application-level conventions, and process
improvements. Keeping the archive readable, reviewable, technically sound, in
scope, and current gives the ecosystem a durable place to debate technical
changes without tying publication to adoption.

[bip-3]: https://github.com/bitcoin/bips/blob/master/bip-0003.md
[bips-dev]: https://bips.dev/
[jon-announce]: /blog/jon-atack-receives-lts-grant
[repo]: https://github.com/bitcoin/bips
12 changes: 12 additions & 0 deletions public/static/images/projects/bips.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 6 additions & 2 deletions scripts/generate-page-og.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,9 @@ function renderRedSvg(logoDataUri) {

<image href="${logoDataUri}" x="${logoX}" y="${logoY}" width="${logoSize}" height="${logoSize}" />

<rect x="${PADDING}" y="${urlY - 36}" width="${CONTENT_WIDTH}" height="1" fill="#44403c" />
<rect x="${PADDING}" y="${
urlY - 36
}" width="${CONTENT_WIDTH}" height="1" fill="#44403c" />
<text x="${PADDING}" y="${urlY}" fill="#a8a29e" font-size="22" font-family="${INTER_FONT_FAMILY}" letter-spacing="1">${escapeXml(
pageUrl
)}</text>
Expand Down Expand Up @@ -562,7 +564,9 @@ async function writeImage(slug, svg) {
async function main() {
await ensureCleanDir(outputDir)
faviconDataUri = await loadFaviconDataUri()
const redLogoDataUri = await publicAssetToDataUri('/static/brand/logo-red.png')
const redLogoDataUri = await publicAssetToDataUri(
'/static/brand/logo-red.png'
)
if (!redLogoDataUri) {
throw new Error('Missing red logo at public/static/brand/logo-red.png')
}
Expand Down
9 changes: 8 additions & 1 deletion utils/projectClusters.ts
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,14 @@ export const CLUSTERS: Cluster[] = [
id: 'core',
title: 'Protocol Maintenance & Development',
blurb: 'Full nodes, validation, and core protocol work.',
slugs: ['bitcoin-core', 'libbitcoin', 'floresta', 'utreexod', 'asmap'],
slugs: [
'bitcoin-core',
'bips',
'libbitcoin',
'floresta',
'utreexod',
'asmap',
],
},
{
id: 'education',
Expand Down
Loading