P2PKH
E183408
P2PKH (Pay-to-PubKey-Hash) is a common Bitcoin transaction output type where funds are locked to the hash of a public key and can be spent by presenting the corresponding public key and a valid digital signature.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Pay-to-PubKey-Hash | 2 |
| P2PKH canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1613560 — 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: P2PKH Context triple: [Bitcoin Core, supportsAddressType, P2PKH]
-
A.
satoshi
A satoshi is the smallest divisible unit of the cryptocurrency Bitcoin, representing one hundred millionth of a single bitcoin.
-
B.
PKCS #1
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
-
C.
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.
-
D.
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.
-
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: P2PKH Target entity description: P2PKH (Pay-to-PubKey-Hash) is a common Bitcoin transaction output type where funds are locked to the hash of a public key and can be spent by presenting the corresponding public key and a valid digital signature.
-
A.
satoshi
A satoshi is the smallest divisible unit of the cryptocurrency Bitcoin, representing one hundred millionth of a single bitcoin.
-
B.
PKCS #1
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
-
C.
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.
-
D.
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.
-
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 (48)
| Predicate | Object |
|---|---|
| instanceOf | Bitcoin transaction output type ⓘ |
| abbreviationOf |
P2PKH
self-linksurface differs
ⓘ
surface form:
Pay-to-PubKey-Hash
|
| addressExamplePrefix | 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa ⓘ |
| addressFormat | Base58Check ⓘ |
| addressPrefixMainnet | 1 ⓘ |
| addressPrefixTestnet | m or n ⓘ |
| addressType | non-segwit ⓘ |
| backwardsCompatibleWith | original Bitcoin protocol rules ⓘ |
| category | legacy Bitcoin address type ⓘ |
| contrastedWith |
P2SH
ⓘ
P2TR ⓘ P2WPKH ⓘ |
| designGoal |
improved usability for users
ⓘ
shorter addresses than pay-to-pubkey ⓘ |
| doesNotNativelySupport | multisignature scripts ⓘ |
| dominantIn | Bitcoin transactions for many years ⓘ |
| feeEfficiencyComparedToSegwit | lower ⓘ |
| fullName |
P2PKH
self-linksurface differs
ⓘ
surface form:
Pay-to-PubKey-Hash
|
| hashConstruction | HASH160 (RIPEMD-160(SHA-256(pubkey))) ⓘ |
| hashFunction |
RIPEMD-160
ⓘ
SHA-256 ⓘ |
| introducedIn | early Bitcoin protocol ⓘ |
| lockingScriptName | scriptPubKey ⓘ |
| locksFundsTo | public key hash ⓘ |
| network |
Bitcoin
ⓘ
surface form:
Bitcoin mainnet
Bitcoin testnet ⓘ |
| outputClassification | pay-to-public-key-hash ⓘ |
| outputScriptPattern | OP_DUP OP_HASH160 <PubKeyHash> OP_EQUALVERIFY OP_CHECKSIG ⓘ |
| requiresToSpend |
digital signature
ⓘ
public key ⓘ |
| scriptLanguage | Bitcoin Script ⓘ |
| scriptSigContains |
public key
ⓘ
signature ⓘ |
| scriptType | standard output script ⓘ |
| securityDependsOn |
Elliptic Curve Digital Signature Algorithm
ⓘ
surface form:
ECDSA over secp256k1
|
| spendCondition | knowledge of corresponding private key ⓘ |
| spendRisk | public key revealed on first spend ⓘ |
| spendSize | larger than equivalent segwit spend ⓘ |
| standardness | standard output in Bitcoin Core policy ⓘ |
| supports | single-signature payments ⓘ |
| unlockingScriptName | scriptSig ⓘ |
| usedFor |
paying individuals
ⓘ
simple wallet addresses ⓘ |
| usedIn | Bitcoin ⓘ |
| validationStep |
check that provided pubkey hashes to scriptPubKey hash
ⓘ
verify ECDSA signature against provided pubkey ⓘ |
| visibleInBlockchainAs | script pattern with OP_DUP OP_HASH160 ⓘ |
| witnessUsage | none ⓘ |
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: P2PKH Description of subject: P2PKH (Pay-to-PubKey-Hash) is a common Bitcoin transaction output type where funds are locked to the hash of a public key and can be spent by presenting the corresponding public key and a valid digital signature.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.