Segregated Witness
E183405
Segregated Witness is a Bitcoin protocol upgrade that separates signature data from transaction data to increase block capacity, improve scalability, and fix transaction malleability.
All labels observed (4)
| Label | Occurrences |
|---|---|
| BIP141 | 1 |
| BIP144 | 1 |
| SegWit | 1 |
| Segregated Witness canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1613537 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: Segregated Witness Context triple: [Bitcoin Core, supportsFeature, Segregated Witness]
-
A.
satoshi
A satoshi is the smallest divisible unit of the cryptocurrency Bitcoin, representing one hundred millionth of a single bitcoin.
-
B.
Merkle
Merkle is a surname most prominently associated with Ralph Merkle, a pioneering computer scientist and cryptographer known for his foundational work in public-key cryptography and Merkle trees.
-
C.
BitC
BitC is a systems programming language designed for safety, low-level control, and formal verification, drawing on ideas from Modula-3 and capability-based security.
-
D.
Bitcoin Core
Bitcoin Core is the open-source software implementation that serves as the primary full node and wallet for the Bitcoin network, maintaining the blockchain and enforcing consensus rules.
-
E.
Merkle tree
A Merkle tree is a cryptographic data structure that uses a tree of hash values to efficiently and securely verify the integrity and consistency of large sets of data.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Segregated Witness Target entity description: Segregated Witness is a Bitcoin protocol upgrade that separates signature data from transaction data to increase block capacity, improve scalability, and fix transaction malleability.
-
A.
satoshi
A satoshi is the smallest divisible unit of the cryptocurrency Bitcoin, representing one hundred millionth of a single bitcoin.
-
B.
Merkle
Merkle is a surname most prominently associated with Ralph Merkle, a pioneering computer scientist and cryptographer known for his foundational work in public-key cryptography and Merkle trees.
-
C.
BitC
BitC is a systems programming language designed for safety, low-level control, and formal verification, drawing on ideas from Modula-3 and capability-based security.
-
D.
Bitcoin Core
Bitcoin Core is the open-source software implementation that serves as the primary full node and wallet for the Bitcoin network, maintaining the blockchain and enforcing consensus rules.
-
E.
Merkle tree
A Merkle tree is a cryptographic data structure that uses a tree of hash values to efficiently and securely verify the integrity and consistency of large sets of data.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Bitcoin protocol upgrade
ⓘ
consensus rule change ⓘ soft fork ⓘ |
| activationDate | 2017-08-24 ⓘ |
| activationMethod | BIP9 version bits ⓘ |
| addsField | witness data to transactions ⓘ |
| affects | transaction ID calculation ⓘ |
| alsoKnownAs |
Segregated Witness
ⓘ
surface form:
SegWit
|
| appliesTo |
Bitcoin
ⓘ
surface form:
Bitcoin network
|
| backwardsCompatibleWith | non-upgraded nodes (as soft fork) ⓘ |
| category |
Bitcoin scalability solution
ⓘ
cryptocurrency protocol feature ⓘ |
| changes | transaction serialization format ⓘ |
| compatibleWith |
Pay-to-Witness-Public-Key-Hash (P2WPKH)
ⓘ
Pay-to-Witness-Script-Hash (P2WSH) ⓘ nested SegWit in P2SH ⓘ |
| controversy | subject of community debate before activation ⓘ |
| designGoal | minimize disruption to existing Bitcoin ecosystem ⓘ |
| developmentCommunity | Bitcoin Core developers ⓘ |
| enables |
Lightning Network
ⓘ
more transactions per block ⓘ |
| firstActivatedOn | Bitcoin mainnet ⓘ |
| firstSignaledBy | Bitcoin miners ⓘ |
| improves |
security of multi-signature transactions
ⓘ
signature hashing efficiency ⓘ |
| influenced | design of later Bitcoin upgrades ⓘ |
| introducesConcept |
block weight
ⓘ
witness discount ⓘ |
| maxBlockWeight | 4000000 weight units ⓘ |
| movesDataTo | witness structure ⓘ |
| prevents | third parties from changing txid without invalidating signature ⓘ |
| proposedBy | Pieter Wuille ⓘ |
| purpose |
enable second-layer protocols
ⓘ
fix transaction malleability ⓘ improve Bitcoin scalability ⓘ increase effective block capacity ⓘ |
| redefines | block size limit in terms of weight ⓘ |
| reduces |
average transaction fees (relative to capacity)
ⓘ
incentive to use non-standard transaction forms for fee savings ⓘ transaction malleability ⓘ |
| relatedProposal | SegWit2x ⓘ |
| requires | miner signaling threshold for activation ⓘ |
| separates | signature data from transaction data ⓘ |
| specifiedIn |
Segregated Witness
self-linksurface differs
ⓘ
surface form:
BIP141
BIP143 ⓘ Segregated Witness self-linksurface differs ⓘ
surface form:
BIP144
BIP145 ⓘ |
| usedBy |
many Bitcoin exchanges
ⓘ
many Bitcoin wallets ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: Segregated Witness Description of subject: Segregated Witness is a Bitcoin protocol upgrade that separates signature data from transaction data to increase block capacity, improve scalability, and fix transaction malleability.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.