HubPal.org

(Grok aided) HubPal: The first Project Platformization in Web 3 and Web 2 HubPal.org | ETHGlobal Hackathon, August 2025

HubPal pioneers project platformization—the first Web3 (and Web 2) solution to create, fund, and manage any project, from freelance gigs to infrastructure builds, with decentralized, tokenized workflows. Why groundbreaking? Platformizing projects is complex, with countless moving parts, especially in the analog world. HubPal simplifies this using blockchain primitives, targeting crypto devs and degens first to refine value propositions and solve real pain points.

[ We deconstructed* the project. Then componentized, modulized, etc. adding tokenization and tokenomics, into a decentralized platform with workflow, funding, with project management, etc. (*Over ~4 years. However, HubPal is the first time we are putting code together. The key spark of sorts was the idea to fit ENS and projects together… )]

Each project gets its own platform via ENS domains (e.g., projectAlice.hubpal.eth), with subnames (e.g., supplierBob.projectAlice.hubpal.eth) mapping to wallets and smart contracts. Built on Flow testnet, HubPal leverages: • ENS: Hierarchical identities for projects, suppliers, and stakeholders, bridging Web2 DNS. • Chainlink Functions: Verifies real-world triggers (e.g., Stripe invoices) for dynamic escrow releases. • PayPal & Circle: Fiat/crypto payments (PYUSD/USDC) with gasless UX via Circle Paymaster. • Walrus: Decentralized storage for project data (e.g., invoices, designs). • Hardhat: Robust contract development and testing.

MVP Scope For the hackathon, we demo one project with 3 milestones (supplies, labor, delivery): • Buyer stakes $500 in PYUSD/USDC via PayPal/Fern. • Supplier submits invoice (Stripe/self-attested); Chainlink Functions triggers payout to supplierBob.projectAlice.hubpal.eth. • Data stored on Walrus, linked via ENS. Deployed on Flow testnet with Hardhat.

Why HubPal? HubPal’s Projects-Payments-Platformization (PPPx) solves gaps: fragmented supply chains, high trust costs, and siloed identities. Our dynamic escrow-staking system releases funds only on verified milestones, blending Web2 usability (PayPal, Next UI) with Web3 trustlessness. We target blockchain users to iterate fast, then scale to all industries.

Sponsors & Prizes (Grok may make mistakes here.) • ENS ($10,000): Subnames for project hierarchy ("Best Use of ENS," "L2 Primary Names"). • Chainlink ($6,000): Functions for invoice triggers ("Best CCIP/CCT"). • PayPal ($10,000): PYUSD for stakes ("Grand Prize," "Innovative Payment"). • Circle ($10,000): USDC gasless payments ("Multichain USDC," "Gasless Experience"). • Walrus ($4,000): Stores invoices/designs ("Best App Using Walrus"). • Hardhat ($5,000): Contract deployment ("Best Projects"). License: MIT + Commons Clause Restriction

Remarks Post-Hackathon: Expand to equity/funding, multi-chain via LayerZero, and launch. We will target the Web 3 devs and degens first to work out the kinks and test the HubPal hypothesis. (We need everything and everybody. I dont code.. It's me, myself, and I ATM.) Join with us now, or join with us later.

How It’s Made

After the first day of the hackathon, I realized I didn’t have teammates — everyone I approached was already focused on their own projects. A few developers gave me tips, and I got a particularly valuable tip from the Chainlink representatives: try using v0.app (Vercel’s AI-powered coding assistant). Until then, I was planning to use only ChatGPT-5 (and briefly considered Lovable), but v0.app turned out to be the perfect fit.

Here’s how the build came together:

ChatGPT-5 as Architect & Guide: I had already worked with ChatGPT on the HubPal concept over time, iterating on GitHub READMEs and business models. When the hackathon started, I explained v0.app to ChatGPT in a couple of paragraphs, and it immediately began generating step-by-step prompts I could paste directly into v0.

Two-Phase Build:

The first build took about 7–8 hours. It was working, but when I tried to merge additional sections, it broke. After another 2–3 hours of debugging, I decided to start fresh.

The second build (the current one) took about 8–10 hours. This time, ChatGPT walked me through every detail — including how to load code to GitHub (which I had never done before, outside of uploading PDFs and business plans).

Partner Tech Benefits:

ENS gave projects, milestones, and participants their own blockchain identities.

Chainlink Oracles + CCIP connected QuickBooks events (real-world deliverables, invoices) to smart contracts for milestone funding.

PayPal PYUSD was used for staking + milestone payments, demonstrating a novel “pay-over-time” adaptation.

Walrus handled decentralized data storage.

v0.app itself became my “dev teammate” — writing, structuring, and scaffolding the frontend/backend without me needing coding skills.

Hacky / Notable Aspects:

This was my first real GitHub repo with code, built entirely through AI collaboration.

I effectively acted as the project manager + product designer, while two AIs (ChatGPT + v0.app) became my coding partners.

I even extended the build by feeding ChatGPT the sponsor requirements, and it created custom prompts to fit each sponsor’s integration into the platform.

In short: this project is a live demo of AI-assisted full-stack development, where someone with no coding background could deliver a working blockchain-integrated product in under 48 hours.