← Back to Explorer
On-Chain

phi-2 (2023)

phi-2 is a large language model released by Microsoft, released under the mit license, with a claimed knowledge cutoff of 2023-12-13. Its weights, configuration, and tokenizer files have been cryptographically hashed and permanently attested on Ethereum (Sepolia) by Weight Registry.

Description

Microsoft's small LLM trained on curated/synthetic high-quality data to outperform its parameter count on standard benchmarks.

Metadata

Type
LLM
Issuer
Microsoft
License
mit
Size
5.18 GB
Knowledge cutoff
2023-12-13
Source
https://huggingface.co/microsoft/phi-2
Revision
810d367871c1d460086d9f82db8696f2e0a0fcd0
Attester
0x6a94784135e413A474E6fA28d1A36C5d180B70c9

Hugging Face stats

555,680 downloads on Hugging Face · 3,523 likes · pipeline: text-generation · library: transformers

transformerssafetensorsphitext-generationnlpcodeentext-generation-inferenceendpoints_compatible

Weight Hashes

Combined commitment: a Merkle root over the weights, config, and tokenizer hashes together (not a raw weights-only hash) -- see this project's v2 on-chain schema.
Combined SHA-2560xef59d80f37310b3a4f5203d96f9b7a1ea5c78afb57f32b9cefb453ab0b94fe93
Combined SHA3-2560x04ed1b0a5ad50a34b35e0936c9d62130ead48fe6312fe4502022d1f8b016d164
Combined BLAKE30x646210bb7d8af754a2340a568cf91ddfd6d336c6a06a91869dc5a7f39718cd7a

Per-file breakdown

Computed locally prior to attestation; the combined hash above is the canonical on-chain commitment.

Config file
config.json · 735 B
SHA-256fbd955b298fdbd35fb81b3350a0d68d12616da7b7e9d81397ef632038ccc1111
SHA3-256be6eda19009bac465c838b4e2a203414046d876319ca991f2d2ee3baa8027b2a
BLAKE34dddee8360ed9efa3bd10b3529995f838c3015dbfcc7c7cf049ceae39fcbaf85
Tokenizer file
tokenizer.json · 2.02 MB
SHA-256337da36be7a71a6e88aa9148967a7bc8736f4b47c7de8e19ba92b89e80734cfc
SHA3-2565afe567dc9fcdb1ad8c6f965c70c78288ee7312c6e0d27204e2b409b764df671
BLAKE3217d3dafd71c44b34cec26f21af6b1badfe7a4cd12b2a56ea43fdf38e1d1bd01

Verify it yourself

Download the file(s) from the source below, then hash them locally (sha256sum <file> on Linux/macOS, certutil -hashfile <file> SHA256 on Windows) and compare the output against the hash(es) shown above.