Skip to content

Commit 8d20fab

Browse files
hardingharding
committed
Topics: add new topics (bitschmidty)
1 parent 1acc7ec commit 8d20fab

File tree

9 files changed

+432
-0
lines changed

9 files changed

+432
-0
lines changed

‎_includes/references.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,12 @@
33
[compatibility matrix]: /en/compatibility/
44
[optech email]: mailto:[email protected]
55
[rss feed]: /feed.xml
6+
[topic v2 p2p transport]: / {% comment %}FIXME: /en/topics/v2-p2p-transport/{% endcomment %}
7+
68

79
{% comment %}<!-- reused (or likely to be reused) external links, alphabetical order -->{% endcomment %}
810
[bip-anyprevout]: https://github.com/ajtowns/bips/blob/bip-anyprevout/bip-anyprevout.mediawiki
11+
[bip-cleanup]: https://github.com/TheBlueMatt/bips/blob/cleanup-softfork/bip-XXXX.mediawiki
912
[bip-coshv]: https://github.com/JeremyRubin/bips/blob/op-checkoutputshashverify/bip-coshv.mediawiki
1013
[bip-schnorr]: https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki
1114
[bip-taproot]: https://github.com/sipa/bips/blob/bip-schnorr/bip-taproot.mediawiki

‎_topics/en/bech32.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: Bech32
3+
aliases:
4+
- BIP173
5+
- Native segwit address
6+
7+
## Required. At least one category to which this topic belongs. See
8+
## schema for options
9+
categories:
10+
- Scripts and Addresses
11+
12+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
13+
excerpt: >
14+
**Bech32** is an address format used to pay native segwit outputs.
15+
16+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
17+
extended_summary: |
18+
Using only 32 letters and numbers, the bech32 address format is case
19+
insensitive and includes an error-correction code that can catch
20+
almost all address typos (and even identify where the typos occur in
21+
some cases). Addresses encode a segwit version, making them forward
22+
compatible with a large range of conceivable upgrades.
23+
24+
## Optional. Produces a Markdown link with either "[title][]" or
25+
## "[title](link)"
26+
primary_sources:
27+
- title: BIP173
28+
- title: Bech32 reference code
29+
link: https://github.com/sipa/bech32
30+
31+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
32+
## true" to bold entry
33+
optech_mentions:
34+
- title: "Bech32 sending support (24-part series)"
35+
url: /en/bech32-sending-support/
36+
date: 2019-03-19
37+
feature: true
38+
39+
- title: Bech32 security update for C implementations
40+
url: /en/newsletters/2018/11/06#bech32-security-update-for-c-implementation
41+
date: 2018-11-06
42+
43+
## Optional. Same format as "primary_sources" above
44+
see_also:
45+
- title: Javascript bech32 demo decoder
46+
link: http://bitcoin.sipa.be/bech32/demo/demo.html
47+
---

‎_topics/en/block-explorers.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Block explorers
3+
4+
## Optional. An entry will be added to the topics index for each alias
5+
#aliases:
6+
# - Foo
7+
8+
## Required. At least one category to which this topic belongs. See
9+
## schema for options
10+
categories:
11+
- Privacy Problems
12+
- Developer Tools
13+
14+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
15+
excerpt: >
16+
**Block explorers** are tools that maintain an index of transactions
17+
and their relationships to each other, allowing fast look up of
18+
information useful to wallets, users, and developers.
19+
20+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
21+
extended_summary: |
22+
Although many users find block explorers to be a convenient way to
23+
look up information about their own transactions, their searches may
24+
be logged and used to associate their transactions with their IP
25+
address, browser cookies, and other identifying information. The
26+
large indexes block explorers keep also aren't expected to scale well
27+
as the size and complexity of the block chain grows.
28+
29+
## Optional. Produces a Markdown link with either "[title][]" or
30+
## "[title](link)"
31+
primary_sources:
32+
- title: Esplora open source block explorer
33+
link: https://github.com/Blockstream/esplora
34+
35+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
36+
## true" to bold entry
37+
optech_mentions:
38+
- title: Modern open source block explorer
39+
url: /en/newsletters/2018/12/11/#modern-block-explorer-open-sourced
40+
date: 2018-12-11
41+
42+
- title: Esplora updated
43+
url: /en/newsletters/2019/03/19/#esplora-updated
44+
date: 2019-03-19
45+
46+
## Optional. Same format as "primary_sources" above
47+
# see_also:
48+
# - title:
49+
# link:
50+
---

‎_topics/en/consensus-cleanup-soft-fork.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: Consensus Cleanup soft fork
3+
4+
## Required. At least one category to which this topic belongs. See
5+
## schema for options
6+
categories:
7+
- Soft Forks
8+
- Scripts and Addresses
9+
- Mining
10+
11+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
12+
excerpt: >
13+
**Consensus Cleanup soft fork** is a proposal to address several
14+
issues in Bitcoin's consensus rules that date back to the original
15+
version of Bitcoin released in 2009.
16+
17+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
18+
#extended_summary: |
19+
20+
## Optional. Produces a Markdown link with either "[title][]" or
21+
## "[title](link)"
22+
primary_sources:
23+
- title: bip-cleanup
24+
25+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
26+
## true" to bold entry
27+
optech_mentions:
28+
- title: Cleanup soft fork proposal
29+
url: /en/newsletters/2019/03/05#cleanup-soft-fork-proposal
30+
date: 2019-03-05
31+
32+
- title: Consensus cleanup background
33+
url: /en/newsletters/2019/03/05#appendix-consensus-cleanup-background
34+
date: 2019-03-05
35+
36+
- title: "Consensus cleanup discussion: codeseparator & sighash types"
37+
url: /en/newsletters/2019/03/12/#cleanup-soft-fork-proposal-discussion
38+
date: 2019-03-12
39+
40+
- title: "CoreDev.tech discussion: cleanup soft fork"
41+
url: /en/newsletters/2019/06/12/#cleanup-discussion
42+
date: 2019-06-12
43+
44+
## Optional. Same format as "primary_sources" above
45+
# see_also:
46+
# - title:
47+
# link:
48+
---

‎_topics/en/covenants.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Covenants
3+
4+
## Required. At least one category to which this topic belongs. See
5+
## schema for options
6+
categories:
7+
- Scripts and Addresses
8+
- Soft Forks
9+
10+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
11+
excerpt: >
12+
**Covenants** are a category of proposed changes to Bitcoin's
13+
consensus rules that would allow a script to prevent an authorized
14+
spender from spending to certain other scripts.
15+
16+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
17+
extended_summary: |
18+
For example, a covenant may normally only allow spending to a
19+
whitelisted set of scripts, such as returning bitcoins to the user's own
20+
balance or spending to a staging address that only allows spending to
21+
any arbitrary address after a period of time.
22+
23+
## Optional. Produces a Markdown link with either "[title][]" or
24+
## "[title](link)"
25+
primary_sources:
26+
- title: Enhancing Bitcoin transactions with covenants
27+
link: https://fc17.ifca.ai/bitcoin/papers/bitcoin17-final28.pdf
28+
29+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
30+
## true" to bold entry
31+
optech_mentions:
32+
- title: "Scaling Bitcoin Tokyo 2018, Script Roundtable: OP_CHECKSIGFROMSTACK"
33+
url: /en/newsletters/2018/10/09/#discussion-the-evolution-of-bitcoin-script
34+
date: 2018-10-09
35+
36+
- title: "New proposed opcode: OP_CHECKOUTPUTHASHVERIFY"
37+
url: /en/newsletters/2019/05/29/#proposed-new-opcode-for-transaction-output-commitments
38+
date: 2019-05-29
39+
40+
- title: "CoreDev.tech discussion: potential script changes"
41+
url: /en/newsletters/2019/06/12/#potential-script-changes
42+
date: 2019-06-12
43+
44+
- title: Bitcoin vaults without covenants
45+
url: /en/newsletters/2019/08/14#bitcoin-vaults-without-covenants
46+
date: 2019-08-14
47+
48+
## Optional. Same format as "primary_sources" above
49+
see_also:
50+
- title: An early description of covenants in Bitcoin
51+
link: https://bitcointalk.org/index.php?topic=278122.0
52+
---

‎_topics/en/dandelion.md

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Dandelion
3+
aliases:
4+
- BIP156
5+
6+
categories:
7+
- P2P Network Protocol
8+
- Privacy Enhancements
9+
10+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
11+
excerpt: >
12+
**Dandelion** is a privacy-enhancement proposal to allow transactions
13+
to first propagate serially from one node to one other node before
14+
being broadcast from one node to all of its peers.
15+
16+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
17+
extended_summary: |
18+
This propagation behavior would help hide which node originated the
19+
transaction, especially if some of the nodes involved in the initial
20+
serial relay ("stem phase") encrypted their Bitcoin protocol traffic
21+
using either Tor or something like [v2 P2P transport][topic v2 p2p
22+
transport].
23+
24+
## Optional. Produces a Markdown link with either "[title][]" or
25+
## "[title](link)"
26+
primary_sources:
27+
- title: BIP156
28+
29+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
30+
## true" to bold entry
31+
optech_mentions:
32+
- title: What's the BIP156 hold-up in Bitcoin Core?
33+
url: /en/newsletters/2019/01/29/#what-s-the-hold-up-implementing-bip156-dandelion-in-bitcoin-core
34+
date: 2019-01-29
35+
36+
- title: PRs that need more review or development
37+
url: /en/newsletters/2019/02/19/#bitcoin-core-freeze-week
38+
date: 2019-02-19
39+
40+
- title: Erlay comaptible with BIP156
41+
url: /en/newsletters/2019/06/05/#erlay-proposed
42+
date: 2019-06-05
43+
44+
- title: Discussion of Dandelion route selection
45+
url: /en/newsletters/2018/07/03/#dandelion-transaction-relay
46+
date: 2018-07-03
47+
48+
- title: Dandelion DoS-resistant stem routing being researched
49+
url: /en/newsletters/2018/08/21/#dandelion-protocol-dos-resistant-stem-routing
50+
date: 2018-08-21
51+
52+
- title: "2018 year-in-review notable developments: BIP156 Dandelion"
53+
url: /en/newsletters/2018/12/28/#dandelion
54+
date: 2018-12-28
55+
56+
## Optional. Same format as "primary_sources" above
57+
# see_also:
58+
# - title:
59+
# link:
60+
---

‎_topics/en/sidechains.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: Sidechains
3+
4+
## Required. At least one category to which this topic belongs. See
5+
## schema for options
6+
categories:
7+
- Contract Protocols
8+
9+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
10+
excerpt: >
11+
**Sidechains** (also called **Two-Way Pegged Sidechains**) are block
12+
chains whose native unit of currency is the same as another block
13+
chain.
14+
15+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
16+
extended_summary: |
17+
In the context of Bitcoin, sidechains use a mechanism where bitcoins
18+
are deposited into a contract on the Bitcoin block chain and an equal
19+
number of bitcoins are created on the sidechain for spending. Users
20+
on the sidechain can then send sidechain bitcoins to a special
21+
contract that destroys them and releases a corresponding amount of the
22+
bitcoins previously deposited to the contract on the Bitcoin block
23+
chain.
24+
25+
**Federated sidechains** have depositors send their mainnet bitcoins
26+
to a multisig contract controlled by a federation of signatories who
27+
also control the production of blocks on the sidechain.
28+
29+
**Drivechains** are a type of proposed decentralized sidechain where
30+
depositors send their mainnet bitcoins into a contract controlled by
31+
anonymous Bitcoin miners who also control the production of blocks on
32+
the sidechain.
33+
34+
## Optional. Produces a Markdown link with either "[title][]" or
35+
## "[title](link)"
36+
primary_sources:
37+
- title: Enabling Blockchain Innovations with Pegged Sidechains
38+
link: https://www.blockstream.com/sidechains.pdf
39+
40+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
41+
## true" to bold entry
42+
optech_mentions:
43+
- title: Elements Project bech32-like addresses
44+
url: /en/bech32-sending-support/#other-addresses-formats-based-on-bech32
45+
date: 2019-04-30
46+
47+
- title: "Notable changes: BIP301"
48+
url: /en/newsletters/2019/07/31/#bips-643
49+
date: 2019-07-31
50+
51+
## Optional. Same format as "primary_sources" above
52+
# see_also:
53+
# - title:
54+
# link:
55+
---

‎_topics/en/signet.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Signet
3+
4+
## Optional. An entry will be added to the topics index for each alias
5+
#aliases:
6+
# - Foo
7+
8+
## Required. At least one category to which this topic belongs. See
9+
## schema for options
10+
categories:
11+
- Developer Tools
12+
13+
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
14+
excerpt: >
15+
**Signet** is both a tool that allows developers to create networks
16+
for testing interactions between different Bitcoin software and the
17+
name of the most popular of these testing networks.
18+
19+
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
20+
extended_summary: |
21+
Blocks on signets are only valid if they're signed by a key used to
22+
create that signet. This gives the creator complete control over
23+
block production, allowing them to choose the rate of block production
24+
or when forks occur. This can provide a much better controlled
25+
network environment than proof-of-work testnets where adversarial
26+
miners can use various tricks to make the network practically unusable
27+
for long periods of time.
28+
29+
## Optional. Produces a Markdown link with either "[title][]" or
30+
## "[title](link)"
31+
primary_sources:
32+
- title: Signet
33+
link: https://en.bitcoin.it/wiki/Signet
34+
35+
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
36+
## true" to bold entry
37+
optech_mentions:
38+
- title: Feedback requested on signet
39+
url: /en/newsletters/2019/03/12/#feedback-requested-on-signet
40+
date: 2019-03-12
41+
42+
- title: "CoreDev.tech discussion: signet"
43+
url: /en/newsletters/2019/06/12#signet
44+
date: 2019-06-12
45+
46+
- title: Progress on signet
47+
url: /en/newsletters/2019/07/24/#progress-on-signet
48+
date: 2019-07-24
49+
50+
- title: C-Lightning adds support for signet
51+
url: /en/newsletters/2019/07/24/#c-lightning-2816
52+
date: 2019-07-24
53+
54+
- title: C-Lightning 0.7.2.1 released with support for signet
55+
url: /en/newsletters/2019/08/21/#upgrade-to-c-lightning-0-7-2-1
56+
date: 2019-08-21
57+
58+
- title: Eltoo demo implementation using custom signet
59+
url: /en/newsletters/2019/09/11/#eltoo-sample-implementation-and-discussion
60+
date: 2019-09-11
61+
62+
## Optional. Same format as "primary_sources" above
63+
see_also:
64+
- title: "Bicoin Core #16411: signet support"
65+
link: https://github.com/bitcoin/bitcoin/pull/16411
66+
---

0 commit comments

Comments
 (0)