We created an application called **Identity Attestation via Hiring Emails**.

DEV.to Submission – Postmark Challenge: Inbox Innovators

What I Built

We created an application called Identity Attestation via Hiring Emails.

The goal is to leverage Postmark’s inbound email parsing to automatically process hiring communications, extract structured KYC-like information from candidates and companies, and create identity attestations. This can help prevent hiring scams and establish trust between job seekers and recruiters.

Key features:

  • ✅ Postmark inbound email parsing webhook
  • ✅ Automatic data extraction into Supabase DB
  • ✅ Public Attestation View for jurors
  • ✅ Smart contracts deployed (ERC721 mint open)
  • ✅ Next.js frontend for browsing attestations

Demo

Deployment Instructions (Juror Mode)

Requirements:

  • Node.js (>=18)
  • pnpm installed
  • Supabase account (or use provided demo credentials)

Steps:

# 1️⃣ Clone the repo
 git clone https://github.com/YOUR-ORG/identity-attestation-hiring-email.git
 cd identity-attestation-hiring-email

# 2️⃣ Install frontend dependencies
 cd frontend && pnpm install

# 3️⃣ Setup .env
 cp .env.example .env
# Fill: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, POSTMARK_API_KEY, etc

# 4️⃣ Run frontend
 pnpm dev

Once running locally, you can simulate inbound emails via Postmark API or inspect current records via Supabase DB directly.

Code Repository

Full repo: GitHub – identity-attestation-hiring-email

How I Built It

Tech Stack:

  • Next.js 14 (React server components)
  • Supabase (Database + RLS + Storage)
  • Postmark (Inbound Email Parsing)
  • Wagmi & Viem (Smart contract interaction)
  • Foundry (Solidity contracts and deployment)
  • TypeScript, Tailwind CSS, ShadCN UI

Architecture:

  • Postmark sends parsed inbound emails to Next.js API route.
  • Next.js API inserts email data into Supabase table email_attestations.
  • Smart contract deployed (ERC721 mint open for future extensions).
  • Frontend UI lists attestations and shows candidate/company verification states.

Why this use case?

  • Many hiring scams today happen via email.
  • Bringing identity attestations to hiring conversations adds trust & verification layers.
  • Email-based onboarding allows gradual KYC-like attestations without centralized gatekeepers.

Team Members

Solo submission by @fsegall.

Thank you Postmark + DEV.to for this excellent challenge!

Leave a Reply