v31.1-roots.1 · Commit 1: [PATCH 01/17] build(roots): establish v31 portability foundation
doc/roots-features.md
Before: /dev/null · After: doc/roots-features.md
File metadata
new file mode 100644 index 0000000000000000000000000000000000000000..48a828421d2248b4362e480e8c5f0088978a010d
Download original patch · Release notes
Diff rows 401–442 of 442. Line numbers refer to the original before/after files.
+ Added− RemovedUnmarked lines are context.
Scroll the code area horizontally to read long lines. The two line-number columns refer to before and after.
doc/roots-features.md
ADDED
|
@@ -0,0 +1,442 @@ (continued)
|
|
|
401
|
+
| runtime-resources | build-portability |
|
|
402
|
+
| runtime-config | None |
|
|
403
|
+
| build-portability | None |
|
|
404
|
+
| identity-desktop | build-portability |
|
|
405
|
+
| maintenance-ci | None |
|
|
406
|
+
| maintenance-release | None |
|
|
407
|
+
| maintenance-docs | None |
|
|
408
|
+
| maintenance-native | None |
|
|
409
|
+
|
|
410
|
+
## Consensus and provenance boundary
|
|
411
|
+
|
|
412
|
+
Bitcoin Roots remains compatible with Bitcoin Core consensus. It does **not**
|
|
413
|
+
enforce RDTS/BIP110 consensus rules. Policy, relay, mempool, and mining-template
|
|
414
|
+
configuration must not make a consensus-valid block invalid.
|
|
415
|
+
|
|
416
|
+
Bitcoin Core v30.3 is the direct base. Bitcoin Knots history is useful only as
|
|
417
|
+
provenance for selected policy research; it is not imported as an upstream
|
|
418
|
+
dependency. The historical replay candidate and archived maintenance branch are
|
|
419
|
+
evidence for maintainers, not product specifications.
|
|
420
|
+
|
|
421
|
+
## Deliberate non-features
|
|
422
|
+
|
|
423
|
+
Roots does not ship or promise:
|
|
424
|
+
|
|
425
|
+
- RDTS/BIP110 consensus enforcement;
|
|
426
|
+
- Network Watch, block/transaction feeds, or block/mempool visualizers;
|
|
427
|
+
- Tor "pairing" credentials, proxy credentials, control-port secrets, or
|
|
428
|
+
private-key sharing surfaces;
|
|
429
|
+
- Tor endpoint sharing or a dedicated endpoint-sharing UI;
|
|
430
|
+
- CoinJoin, payjoin, silent automatic consolidation, a privacy score,
|
|
431
|
+
anonymity guarantee, address graph, chain-analysis dashboard, or payment
|
|
432
|
+
history redesign;
|
|
433
|
+
- the candidate's broad Knots common-maintenance, consensus/script, wallet, or
|
|
434
|
+
documentation overlays merely because they occurred in historical source;
|
|
435
|
+
- the discarded replay, frozen-state, generated-evidence, or promotion control
|
|
436
|
+
plane; or
|
|
437
|
+
- a VitePress documentation overlay, tonal/base16 font dependency, or other
|
|
438
|
+
separate visual identity layer.
|
|
439
|
+
|
|
440
|
+
For maintainers, `contrib/roots/README.md` (`contrib/roots/README.md`, source reference) documents
|
|
441
|
+
the Git-native maintenance workflow. For current build and runtime options, use
|
|
442
|
+
the generated manuals and the built binary help.
|