Verified work history for independent engineers

Ship work.
Get it signed.
Carry the proof.

Turn a merged public GitHub pull request into a portable work receipt—confirmed by a maintainer and anchored to a neutral Solana credential registry.

Import a merged PR →View a proof
Work receiptIllustrative
1
Artifact proofproofport/ledger · PR #281 · merged commit 9e8f0d3…
2
Issuer proofIssuer identity and assurance would be shown explicitly
3
Chain proofDevelopment preview · no Solana account or explorer record
Public merged PRs onlyNo scores or five-star reviewsIssuer authority shown explicitlyPortable signed JSON bundle
One receipt, three proofs

Narrow claims are stronger claims.

ProofPort does not claim the chain makes an issuer honest. It separates machine-derived evidence, the person making the claim, and the registry state so a verifier can judge each layer.

1

Artifact proof

GitHub supplies stable repository, author, merge, commit, and timestamp facts. The normalized snapshot is hashed before a request is shared.

2

Issuer proof

The issuer’s GitHub identity, repository relationship, assurance level, and Ed25519 authorization are displayed—not collapsed into a vague checkmark.

3

Chain proof

Solana Attestation Service supplies the credential, schema, authorized signer, network, expiry, and current account lifecycle state.

Why onchain

Your history should outlive the platform.

A signed Web2 credential proves a claim. Solana supplies the neutral registry that lets unrelated clients issue credentials, developers carry them, and employers verify issuer and lifecycle state without depending on ProofPort’s database.

Solana cannot prove an issuer is honest. ProofPort exposes issuer identity and assurance instead of treating every onchain claim as equally trustworthy.