Distinguish account from wallet identity
Firebase sign-in handles the account. Nonce/signature verification proves control of the connected wallet; the two flows answer different identity questions.
Web3 · Full-stack / Development prototype
InvoChain
Connect wallet verification, Ethereum invoice records, generated PDFs and IPFS document retrieval in one application.
01 / THE PROBLEM
Invoices need a readable document, an identified recipient and a payment record. InvoChain connects these responsibilities across a web interface, smart contracts and document storage.
02 / FOLLOW THE WORKFLOW
A simplified example of the documented flow. Sample outputs are authored illustrations, not live model predictions.
Firebase identity + wallet verification
Account login → nonce → signature
Connect the account and prove wallet control.
Synthetic example, no transaction
Invoice #001 · 0.05 ETH
Create an invoice with recipient and amount.
Document storage path
Invoice PDF → Pinata → content ID
Generate a PDF and store it through IPFS.
Illustrative payment record
Ethereum transaction → invoice status
Confirm payment through the connected wallet.
Step 1 of 4 · Identity
03 / ENGINEERING
Firebase sign-in handles the account. Nonce/signature verification proves control of the connected wallet; the two flows answer different identity questions.
Express and pdf-lib generate the PDF, with Pinata for IPFS storage. Ethers.js connects the React interface to Solidity contracts and MetaMask transaction approval.
The interface supports creation, payment status and PDF retrieval. Network confirmations and document gateway availability are separate parts of the user journey.
04 / EVIDENCE & LIMITS
The README documents invoice creation, wallet verification, PDF generation, Pinata upload and ETH payment tracking. It includes development and test commands but no dated throughput, gas-use or external security audit result used here.
A readable blockchain record does not guarantee an error-free application. Gas costs, confirmation delays, gateway availability and document privacy need explicit handling. No audited-security, permanent-storage or fraud-prevention claim is made.
05 / READ THE SOURCE
Based on public repository documentation reviewed on 7 November 2026. Results are attributed to the project’s recorded evaluations; they were not rerun for this portfolio.
TOOLS BEHIND THE WORK
Explore the stack. Drag the ribbon or select a tool.