Is onchain reputation more trustworthy than a CV?

Parts of it can be. A CV is self-reported. Onchain records issued or paid by identifiable third parties are harder to fabricate, because faking them requires deceiving those parties or spending real money through addresses tied to them. Self-issued records and raw wallet activity are no more trustworthy than a CV and are often easier to manufacture.

How do you verify that a wallet belongs to a candidate?

Ask the candidate to sign a specific message with the wallet, which proves control of it at that moment. Then check that the wallet connects to their other professional identity, such as linked profiles, past employers' confirmations, or public work associated with it. Control plus consistent history is much stronger than control alone.

What is a Sybil attack in onchain reputation?

A Sybil attack is creating many fake identities, in this case many wallets, to appear as multiple people or to inflate activity and reputation. It is cheap on most networks, which is why raw wallet counts and activity are weak signals. Reputation systems resist it by relying on credible issuers, costly actions, or verified identity.

Can a record be removed if it turns out to be false?

Usually not removed, since blockchain records are designed to be permanent. Many credential systems let the issuer revoke an attestation, which marks it invalid while leaving the history visible. When reading records, check whether an attestation has been revoked and whether the issuer supports revocation at all.

Can Onchain Reputation Be Faked?

Some of it can be, cheaply. Wallet age, transaction counts, and self-issued badges can be manufactured with many wallets and little money. Records are expensive to fake when they depend on someone else: attestations from known organisations, payments received from identifiable counterparties, and work reviewed and accepted by others. Trust a record in proportion to its cost to forge.

Tamper-proof is not the same as true

A blockchain makes records hard to change after the fact. It does not make them true. If someone creates a record of fake activity, the blockchain will preserve that fake record faithfully.

So the question for hiring is not whether a record is onchain. It is who created it, and what it would cost someone to create a misleading one. That cost is what gives a record value.

Cheap to fake

Wallet age and activity. Creating many wallets costs almost nothing, and generating transaction history is inexpensive on low-fee networks. Airdrop farming shows how easily activity can be manufactured at scale.
Self-issued badges and credentials. Anyone can create a token or attestation that says anything. Without a trusted issuer, it proves nothing.
Holdings. Tokens or NFTs can be borrowed, bought briefly, or moved between a person's own wallets.
Participation counts. Votes, proposals, and forum activity can be generated with little genuine contribution.

Expensive to fake

Records become costly to forge when they depend on a third party who has something to lose.

Attestations from known issuers

A credential issued by an identifiable organisation, such as a protocol team confirming a contributor delivered a milestone, requires deceiving or colluding with that organisation. Its value depends on the issuer's own reputation.

Payments from identifiable counterparties

Being paid for work by a known organisation's treasury or a recognised company's wallet is strong evidence that the work was accepted. Faking it means spending real money through an address others associate with that organisation.

Reviewed and merged work

Contributions accepted into widely used code, audits published under a firm's name, or bounties paid after review all involve an independent party judging the work.

Consistency over time

A long, coherent history of work with several independent counterparties is much harder to stage than any single record.

How hiring teams should read onchain records

Identify the issuer or payer of each record. Ignore anything self-issued.
Check the issuer's credibility. Is it a known organisation, and does it confirm the record through its own channels?
Link the record to the person. Confirm the candidate controls the wallet, for example by signing a message, and that the wallet ties to their other professional identity.
Look for independent corroboration. Several counterparties over time outweigh one impressive record.
Use it as a starting point for interviews. Ask the candidate to explain the work behind a record in depth.

For candidates: building a record worth trusting

If you want onchain history to help your job search, focus on records that others create about you. Take paid work, bounties, and grants from identifiable organisations. Ask teams you delivered for to issue attestations for completed milestones. Keep one primary wallet for professional work, link it openly to your other profiles, and avoid padding it with activity that means nothing.

A short, credible record beats a long, noisy one. Hiring teams who understand onchain data will look straight past volume to the issuers and payers, and noise makes the real signal harder to find. Be ready to walk through each record in an interview.

What onchain reputation is good for

Used well, onchain records answer a narrow but important question: did this person deliver specific work that someone else accepted and paid for? That is valuable in remote and contributor hiring, where references are hard to verify and CVs are easy to embellish. It does not answer questions about collaboration, judgement, or code quality, which still need interviews, work samples, and conversations with people who worked alongside the candidate.

Frequently asked questions

Is onchain reputation more trustworthy than a CV?: Parts of it can be. A CV is self-reported. Onchain records issued or paid by identifiable third parties are harder to fabricate, because faking them requires deceiving those parties or spending real money through addresses tied to them. Self-issued records and raw wallet activity are no more trustworthy than a CV and are often easier to manufacture.
How do you verify that a wallet belongs to a candidate?: Ask the candidate to sign a specific message with the wallet, which proves control of it at that moment. Then check that the wallet connects to their other professional identity, such as linked profiles, past employers' confirmations, or public work associated with it. Control plus consistent history is much stronger than control alone.
What is a Sybil attack in onchain reputation?: A Sybil attack is creating many fake identities, in this case many wallets, to appear as multiple people or to inflate activity and reputation. It is cheap on most networks, which is why raw wallet counts and activity are weak signals. Reputation systems resist it by relying on credible issuers, costly actions, or verified identity.
Can a record be removed if it turns out to be false?: Usually not removed, since blockchain records are designed to be permanent. Many credential systems let the issuer revoke an attestation, which marks it invalid while leaving the history visible. When reading records, check whether an attestation has been revoked and whether the issuer supports revocation at all.