Rivalidate

Demo

About

The problem it solves Hiring marketplaces struggle with credential fraud and slow verification processes. **Rivalidate** anchors credentials directly on **Base**, giving recruiters cryptographic proof that a candidate truly earned their certificates. Crucially, **issuers** — universities, bootcamps, licensing bodies, etc. — sign and publish those credentials, providing the authoritative link between a candidate and their achievements; without the issuer’s signature, a credential cannot be verified on-chain. Smart-wallet onboarding lowers the barrier for non-crypto users, and an integrated AI agent assists with on-chain actions such as DID creation, token swaps, and payments. The result is a trust layer for professional credentials combined with efficient, AI-powered recruiting tools. Traditional hiring relies on screenshots, PDFs, or phone calls to validate a résumé. Each manual check slows time-to-hire and still leaves room for fraud: | Pain Point | Impact | Rivalidate’s Fix | |------------|--------|------------------| | **Fake or inflated credentials** | Recruiters waste hours verifying each claim and still miss sophisticated forgeries. | Issuers publish cryptographically signed credentials to Base; recruiters get an instant green-check or red-flag. | | **Fragmented data silos** | Résumé data lives in dozens of HR tools; verification results aren’t portable. | Credentials are anchored on-chain and referenced by DID, so any HR system can fetch the same immutable proof. | | **High Web3 friction** | Candidates and employers unfamiliar with wallets avoid on-chain solutions. | Coinbase Smart Wallet onboarding works with email, social, or passkeys — no seed phrases required. | | **Trust gaps in remote hiring** | Global teams struggle to judge overseas certifications. | A global, public Base chain provides a universal source of truth, independent of geography. | By turning each claim into a verifiable credential minted (and, if revoked, transparently burned) on Base, Rivalidate removes the “trust but verify” loop and lets recruiters focus on candidate fit rather than detective work.

How it's made

Challenges we ran into | Challenge | Why It Was Hard | Approach & Solution | |-----------|-----------------|---------------------| | **On-chain ↔️ Off-chain orchestration** | Smart-contract calls must stay in strict sync with Next.js server state (e.g., account creation → NFT anchor). | Introduced an action queue in Drizzle + contract event listeners that update Postgres only after tx confirmation; retries handle L2 reorgs. | | **Wallet onboarding for mixed audiences** | Web2 users fear seed phrases; crypto-native users expect hardcore self-custody. | Integrated Coinbase Smart Wallet with “smartWalletOnly” preference, then exposed optional export for hardware-wallet users. | | **Extending AgentKit with custom actions** | Native AgentKit only covers generic ERC-20 flows. | Wrote a uniswapv2ActionProvider and a credential-mint action that wrap our contracts; added Zod schemas so the agent can validate parameters before calling. | | **Mirroring Coinbase Commerce payments on-chain** | Fiat checkout happens off-chain, but recruiters want on-chain proofs for audits. | Created a webhook that mints a zero-value “PaymentReceipt” NFT when a charge is marked CONFIRMED; the token links to the Commerce charge ID so auditors can cross-check. | | **Ensuring issuer accountability** | If an issuer’s private key is compromised, fake credentials could be minted. | Added a revocation registry and an optional multisig flow for high-value issuers; the AI agent can trigger “freeze” actions if anomaly detection flags unusual minting. | Together these solutions allowed Rivalidate to deliver a seamless, fraud-resistant credential layer while remaining usable by HR teams that have never touched a blockchain.