🌸 Polkadot Solidity Hackathon 2026 — Cebu Edition 🌷
"In the Philippines, we don't have a donation problem. We have a trust problem. Etc. etc., we need to work on an opening hook AHAHAHAHHA"
ClarityChain is a transparent donation platform built on Polkadot Hub where organizations and individuals can create campaigns and receive funds with one critical constraint in that they can only send those funds by to whitelisted vendors.
The capaign creator cannot withdraw to their personal wallet, the transaction is rejected at the smart contract level before it even reaches the blockchain. Every donation received, every vendor approved, and every withdrawal made is permanently visible on the public dashboard.
ClarityChain has five distinct user groups, each with a different role and level of trust in the system.
Anyone with a crypto wallet can donate to any active campaign. TThey connect their wallet, pick a campaign, enter an amount, and confirm.
These are the individuals or organizations running donation/relief campaigns. They create campaigns, receive donations into the campaign contract, and submit withdrawal requests to associated vendors who supply the goods or services needed for the donation effort. Critically, they cannot withdraw to their own wallet. What separates a trustworthy campaign from an unknown one is whether the creator has been verified (denoted with a checkmark beside the creator's address visible in the campaign card) by publicly linking their wallet address to a verified identity through the organization's official channels.
Vendors are the final destination of donated funds. They are businesses, suppliers, and organizations that provide the goods or services that relief efforts require such as rice suppliers, construction material providers, medical supply companies, logistics organizations. They receive payment in exchange for goods delivered to actual recipients. They are called vendors deliberately because the relationship is commercial, not charitable. An campaign creator partners with a vendor, having detailed, public instructions on what to do with the received donations. This removes the creator as a financial intermediary entirely. Vendors must be proposed and whitelisted through the multi-sig governance process before they can receive any funds.
Validators are the governance layer of ClarityChain. They are trusted community representatives, a multi-sig group of wallet addresses whose collective approval is required before any vendor can be whitelisted. A minimum of 3 out of the configured validator set must sign off. Every approval is logged on-chain, permanently, with the validator's wallet address attached. This means if a fraudulent vendor is ever approved, there is an immutable public trail of exactly which validators signed off creating accountability for the validators themselves.
The general public does not need a wallet to use ClarityChain. They can browse active campaigns, view the full transaction history on the Public Feed, trace fund flows from donor to campaign to vendor, and verify that withdrawals only went to named, approved vendors. The Public Feed is ClarityChain's primary accountability tool for non-technical users as it translates on-chain events into human-readable entries that anyone can follow. Block explorer data is available for technically literate auditors, journalists, and watchdogs who want to verify beyond what the UI displays.
- Browse active campaigns on the Donate tab
- Connect a MetaMask wallet
- Enter a donation amount in PAS and confirm the transaction
- Connect the organization's wallet
- Create a campaign with a name and fundraising goal. Campaigns can be created immediately without waiting to identify vendors first.
- Receive donations into the campaign contract as they come in
- Identify and propose vendors appropriate to the campaign's needs along with detailed and public instructions on what each vendor is expected to execute upon receiving the funds
- Submit withdrawals to the associated vendors' addresses
- Submit a vendor proposal through the Vendor Governance tab. Any wallet can propose, including vendors themselves.
- Provide a business name and at least one verification link (DTI registration, Facebook business page, official website, etc.)
- Wait for the multi-sig validator approval process to complete
- Once whitelisted, receive withdrawal transactions from campaign creators.
- Fulfill the procurement obligation, deliver the goods or services to the recipients as agreed off-chain with the campaign creator.
- Monitor the Vendor Governance tab for pending vendor proposals
- Review each proposal's submitted verification links independently.
- Sign approvals on-chain if the vendor passes review, each signature is a public, permanent attestation of your judgment
- Reach the threshold (3 of the configured validator set) to automatically whitelist the vendor
- Exercise the same process for any future governance decisions
- Visit the Public Feed tab, no wallet required
- Browse the complete chronological history of every on-chain event: campaigns created, donations received, vendor proposals, validator approvals, and withdrawals
- Click into any campaign to see its specific transaction history
- Follow the money, every peso that entered a campaign can be traced to the exact vendor address it left to
- Cross-reference vendor addresses with their publicly submitted verification links to independently assess legitimacy
- If anything looks suspicious like unusual withdrawal patterns, an unfamiliar vendor, unexpected amounts raise it publicly through community channels
Any governance action only executes when at least 3 of those wallets sign it. No single person can whitelist a vendor alone. They need a majority across at least three independent parties simultaneously.
Validators are set at contract deployment time by the ClarityChain team. In a real-world deployment, this requires the team to establish relationships with credible organizations. Government units like DSWD or LGUs, established journalists, civic organizations, academic institutions, and established NGOs with clean track records.
Anyone can submit a vendor proposal, including vendors themselves. The proposal requires:
- Business name
- Wallet address
- At least one verification link (DTI registration, official website, Facebook business page, etc.)
This goes into a pending queue on the Vendor Governance tab. Validators independently review the submitted links and sign their approval on-chain. Once the required threshold is reached, the vendor is automatically whitelisted. The entire process is public and permanent.
Everything. Every transaction is permanently on-chain and accessible through two layers:
The Public Feed (for everyone): Human-readable event log showing campaigns created, donations received, vendor proposals submitted, validator approvals signed, and withdrawals sent. No wallet required to view.
The Block Explorer (for auditors): Raw transaction data at https://blockscout-testnet.polkadot.io. Every transaction hash, every wallet address, every wei transferred. For journalists, watchdogs, and technically literate individuals who want to verify beyond what the UI shows. The contract source code is verified on the explorer, anyone can read the Solidity and confirm it does exactly what ClarityChain claims.
Blockchain addresses are pseudonymous by default. A wallet address proves cryptographic ownership but reveals no personal information. For ClarityChain, this means:
- Donors can remain anonymous if they choose. Their privacy is protected.
- Campaign creators are pseudonymous by default but are strongly encouraged to publicly link their wallet address to their organization through official channels. A campaign from an unlinked, unknown wallet should receive less donor trust than one from a wallet publicly announced by a verified organization.
- Vendors are pseudonymous by default but their business name and verification links are public as part of the whitelisting process, providing a meaningful accountability layer.
- Validators are expected to deanonymize themselves fully. They are public figures accepting a public governance role. Their wallet addresses being known is what makes validator accountability possible.
| Network | Address |
|---|---|
| Polkadot Hub TestNet (Passet Hub) | 0xbf0a89253c1f590dcb25a4e5b7ef4b7ef691d585 |
Block Explorer (verified ✅): https://blockscout-testnet.polkadot.io/address/0xbf0a89253c1f590dcb25a4e5b7ef4b7ef691d585
The contract source code is verified on Blockscout. Anyone can read the Solidity directly on the explorer and confirm it does exactly what this README describes.
git clone https://github.com/YOUR_USERNAME/ClarityChain.git
cd ClarityChaincd storage-contract
npm installCreate a .env file in the storage-contract/ folder (use .env.example as reference):
PRIVATE_KEY=0xYourMetaMaskPrivateKeyHere
To get your MetaMask private key: MetaMask → Account Details → Export Private Key. Never share this or commit it to GitHub.
Add the network to MetaMask manually:
| Field | Value |
|---|---|
| Network Name | Polkadot Hub TestNet |
| Chain ID | 420420417 |
| RPC URL | https://services.polkadothub-rpc.com/testnet |
| Currency Symbol | PAS |
Get free testnet PAS from the faucet: https://faucet.polkadot.io
cd storage-contract
npx hardhat compileYou should see Successfully compiled 1 Solidity file.
npx hardhat testcp storage-contract/artifacts/contracts/ClarityChain.sol/ClarityChain.json dapp/abis/ClarityChain.jsonThen open dapp/app/utils/contract.ts
Update CONTRACT_ADDRESS to the new deployed address.
cd dapp
npm install
npm run devOpen http://localhost:3000 in your browser.
You only need this if you're deploying a fresh instance. The contract is already live — see address above.
Open scripts/deploy-claritychain.ts and fill in the VALIDATORS array with 3–5 wallet addresses:
const VALIDATORS: `0x${string}`[] = [
"0xWallet1Address",
"0xWallet2Address",
"0xWallet3Address",
];Then:
npx hardhat run scripts/deploy-claritychain.ts --network polkadotTestNetSave the printed contract address and update dapp/app/utils/contract.ts.
storage-contract/contracts/ClarityChain.sol
The entire backend logic. Key functions: createCampaign(), donate(), withdrawToVendor(), proposeVendor(), approveVendor(). The require(whitelistedVendors[vendor], "ClarityChain: Vendor not whitelisted -- REJECTED") line inside withdrawToVendor() is the core mechanic — everything else supports it.
dapp/app/utils/viem.ts
Chain configuration and viem client setup. If the RPC endpoint changes, update it here.
dapp/app/utils/contract.ts
Contract address and ABI export. If you redeploy, update CONTRACT_ADDRESS here.
dapp/app/utils/errors.ts
Translates raw contract revert strings and viem errors into human-readable messages. All components use this for consistent error handling.
Team Lead: John Dymier Borgonia — BSCS 3 John Zillion Reyes — BSCS 3 Jeremiah Ramos — BSIT 3
- Event: 🌹 Polkadot Solidity Hackathon 2026: Cebu Edition 🌺
- Category: Category 1 — DeFi / Stablecoin-enabled dApps
- Powered by: Polkadot and OpenGuild
- Demo Day: March 15, 2026
Bottom line:
All trust credible issues are off-chain problems and are not ClarityChain's main selling point. Paper trail, transparency, and traceability ARE. ClarityChain solves a financial and spending problem not an identity and trust problem.
Q: How is ClarityChain different from Giveth or The Giving Block?
Giveth and The Giving Block are transparency layers on top of existing donation flows, they show you where money went after the fact. An NGO on Giveth can still withdraw to their personal wallet and post a receipt later. On ClarityChain, that transaction is technically impossible. The contract has one exit: a whitelisted vendor address. We are not asking donors to trust the NGO's reporting. We are making the NGO's choices structurally limited by code. The constraint is architectural, not behavioral.
Q: Why use vendors at all? Why not send money directly to disaster victims?
Disaster victims typically do not have crypto wallet, sdon't have smartphones, and are in no position to interact with a blockchain application during a crisis. The realistic model is that an NGO procures goods from vendors, vendors deliver goods to recipients. ClarityChain sits between the NGO and the vendor, not between the vendor and the recipient. This is out of scope and realistically cannot be on-chain.
Q: What stops an an individual or organization from creating a fake campaign and collecting donations?
Two things. First, the vendor-lock mechanic means that even if a fraudulent campaign collects donations, they cannot withdraw to their personal wallet. The money is trapped in the contract until it goes to a whitelisted vendor. Second, campaign creators are visible on the Public Feed. A campaign from an unlinked, unknown wallet should receive less donor trust. This is the same social layer that governs trust in all public fundraising, donors verify the campaign creator's identity through official channels before donating. ClarityChain makes the financial side transparent; the identity verification layer is the NGO's responsibility to establish off-chain.
Q: The validator addresses are hardcoded, what if a validator's wallet is compromised?
Validator addresses are intentionally public as accountability requires visibility. What is private is the key controlling each address, which each validator is individually responsible for securing. If a validator's key were compromised, the correct response is to redeploy the contract with a new validator set. This is a known limitation of the current implementation and is already on our roadmap which is the dynamic validator add/remove via the existing multi-sig threshold, so the validator set can be updated without redeployment.
Q: Does ClarityChain work for individuals, or only for formal NGOs?
Currently the platform is optimized for organizations with a designated person who can manage a wallet. However, any individual with a crypto wallet can create a campaign. The difference is trust, an unverified individual campaign will receive less donor confidence than one created by a wallet publicly linked to a registered organization.
Q: What about people who want to donate but don't have crypto wallets?
This is an acknowledged scope boundary. ClarityChain handles the spending side of donations. Traditional donors using GCash, bank transfers, or cash still work through existing NGO infrastructure, an NGO treasurer collects fiat, converts to crypto, and deposits into the contract. The transparency mechanic applies to everything after that conversion. Researching a fiat on-ramp integration (e.g., local fintech APIs) is on the roadmap, but it introduces KYC and regulatory complexity that is out of scope for the current phase.
Q: What is on your roadmap beyond the current implementation?
- A report system post hackathon for flagging suspicious activities, anything sus.
- Regarding vendor validation pending issue, a separate, validator notification system could be implemented but should not be part of ClarityChain to prevent scope creep.
- Regarding individual volunteers, an honest scope decision and frame it such a way that it is forward-looking by acknowledging that willing users are a valid use case and an individual can go through the entire verification and function as a vendor and would be a feature implemented post hackathon.
- Regarding vendor validation pending issue, a separate, validator notification system could be implemented but should not be part of ClarityChain to prevent scope creep.
🔗🌸 Built for Cebu. Built for trust. Built on Polkadot. 🌷🔗