bitcoinmachinecode/NOTICE at main · BobClawblaw/bitcoinmachinecode · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Bitcoin Machine Code (bmc)
Copyright 2026 BobClawblaw and contributors

This product is licensed under the Apache License, Version 2.0. See LICENSE.

----------------------------------------------------------------------
AUTHORSHIP, AND WHAT THAT MEANS FOR THIS GRANT
----------------------------------------------------------------------

Every line of assembly and C in this tree was written by an AI system under
the direction of a human operator, who specified, reviewed, tested and
accepted each change. There is no hand-written code here to separate out.

The copyright status of such work is unsettled. Some jurisdictions,
including the United States, hold that material generated by a machine
without sufficient human creative control does not attract copyright at all;
how much human direction is "sufficient" has not been decided for work made
this way. Nothing in this file is a claim either way.

The licence in LICENSE is therefore granted to the extent that copyright
subsists in this work and is owned by the copyright holder named above. Where
no copyright subsists, no permission is needed from anyone and none is
claimed. Either way, the disclaimer of warranty and the limitation of
liability in sections 7 and 8 of the Apache License are what the next section
is about, and they are meant to be read.

If you are making a commercial or legal decision that depends on who owns
this code, do not rely on this file. Ask a lawyer.

----------------------------------------------------------------------
STATUS -- READ BEFORE RUNNING THIS
----------------------------------------------------------------------

This is experimental, unaudited, consensus-critical software.

It has been verified differentially against Bitcoin Core -- a full mainnet
initial block download from genesis, ending with a UTXO set whose MuHash is
identical to Core's at the same height, repeatedly -- and it has been through
internal and external security review. It has NOT had an independent human
audit of its consensus and cryptographic assembly.

A consensus bug in a Bitcoin node loses money. Run this for study and
evaluation, on a machine you can afford to lose, with no funds near it. For a
node that holds value, run Bitcoin Core (https://bitcoincore.org).

The Apache License disclaims all warranties and limits liability. That is not
boilerplate here; it is the point.

----------------------------------------------------------------------
THIRD-PARTY MATERIAL
----------------------------------------------------------------------

asm/tests/bip340_test_vectors.csv
    The BIP-340 (Schnorr signatures for secp256k1) reference test vectors,
    from the bitcoin/bips repository. BIP-340 is published under
    BSD-2-Clause, its code under BSD-2-Clause OR MIT OR CC0-1.0.

Generated tables read from Bitcoin Core's source
    validation/gen_script_flags.py reads Bitcoin Core's own
    kernel/chainparams.cpp and script/interpreter.h on the machine running it
    and emits an activation table (heights, flag bit positions, and two
    historical block hashes) into bitcoin_script_flags.asm. What is emitted
    is consensus fact rather than expression, and no Bitcoin Core source is
    copied into or redistributed with this tree. Bitcoin Core is MIT-licensed
    (https://github.com/bitcoin/bitcoin).

Protocol specifications
    This node implements the Bitcoin protocol and the BIPs named in README.md
    and docs/. Implementing a specification is not a derivative work of it.