The problem POC PROTOCOL solves

Here's a reference to our pitch deck as well :

https://www.canva.com/design/DAG-B8zsP_4/lZp36lBl0cJtmgl1ZGG4lg/view?utm_content=DAG-B8zsP_4&utm_campaign=designshare&utm_medium=link2&utm_source=uniquelinks&utlId=h05c8203c95

The Problem It Solves

Proof-of-Commitment turns staking, governance, and treasury management into a conviction-weighted system that rewards time, sustains token value, and keeps DAO control attack-resistant. The SDK is live on npm: https://www.npmjs.com/package/@proof-of-commitment/sdk

Core Fixes (short version)

• Conviction > Capital: Tiered multipliers (1.0x-2.0x) give long-term stakers outsized voting power while short-term whales stay neutralized.
• Deflationary flywheel: Stake/unstake/claim fees feed a buyback-and-burn loop, keeping rewards sustainable instead of inflationary.
• Attack resistance: Snapshots, staking locks, timelocks, and soulbound commitment NFTs block flash-loan voting, vote renting, and rushed executions.
• On-chain reputation: Each stake mints a dynamic NFT that proves commitment terms, tier, and penalty schedule so partners can verify alignment instantly.
• DAO-owned treasury: Commitment-weighted voting governs fees, burns, penalties, and treasury actions with built-in quorum/threshold safety defaults.

Why it matters

• Token holders get fair governance, verifiable reputation, and a deflationary asset instead of inflation-driven losses.
• DAOs and protocols gain a governance stack built to withstand flash-loan games while funding itself through protocol activity.
• Everyday DeFi users can choose commitment windows (7-365 days), exit early with transparent penalties, and watch progress via NFT visuals.

Differentiators at a glance

Built for shipping

• Contracts, front-end, and analytics connect through the Proof-of-Commitment SDK (@proof-of-commitment/sdk) so builders can integrate staking, governance, and telemetry with one TypeScript wrapper.
• The package exports focused entry points (staking, governance, analytics, nft) and works with modern viem-based stacks, making it easy to drop conviction-weighted governance into any Lisk dApp.

Challenges we ran into

Challenges I Ran Into

Market research showed a glaring gap: most “staking + governance” stacks couldn’t prove long-term commitment or fund their own deflation. Shipping Proof-of-Commitment meant redesigning tokenomics, multi-contract deployments, and frontend/web3 glue from scratch.

1. Turning a Market Gap into a Revenue Model

• What broke: The inherited “mint rewards forever” playbook would have nuked token value within weeks.
• Research sprint: Modeled emergency-burn penalties, halving curves, and capped supplies before landing on a protocol-fee flywheel that pays for its own burns.
• Fix: 0.5% stake / 1% unstake / 1% claim fees route into a treasury, and buybackAndBurn() lets the DAO retire supply on demand. Twenty targeted tests prove fees accrue correctly and burns never overshoot balances.
• Why it matters: Governance power now rides on commitment, while holders see real deflation tied to actual usage—not promises.

2. Orchestrating the Lisk Sepolia Stack

• Pain point: Staking protocol and DAO depend on each other, so a naive deploy bricked ownership wiring.
• Approach: Split the process into two phases—deploy token, NFT, and protocol first; deploy DAO second; then link them via setDAOGovernance() and NFT ownership transfers. Each step logs addresses into JSON consumed by the frontend and SDK.
• Result: Reproducible Hardhat scripts publish the entire suite, emit metadata for clients, and keep re-deploys safe even under network hiccups.

3. Verifying + Integrating Across the Stack

• Blockscout quirks: Verification needed a custom runner that retries when the explorer falsely claims a contract is “already verified,” while keeping constructor args and compiler settings perfectly aligned.
• Frontend sync: The admin dashboard initially mixed ethers v6 syntax with our v5 dependency. Audit swapped every provider/signer parse call back to v5 equivalents so governance actions (burns, fee updates) finally executed.
• Developer experience: These fixes feed the public TypeScript SDK (@proof-of-commitment/sdk), so anyone integrating from the npm package inherits the verified addresses, ABIs, and conviction-weighted flows without reliving the debugging tour.