The problem StakeLiGames solves

Disclosure: I admit that I've re-used code from a 3 weeks old personal side project, and now have updated the dashboard to dynamically fetch & display completed + currently ongoing stakes on-chain, alongside dynamic staking + implementing an algorithm for no change/return of staked amount based on result submission via MetaMask wallet connection - nothing is static anymore.
Additionally, I've induced security upgrades by upgrading Next.js to the vulnerability-free version, shielding it from the recent issue that affected a few versions of React & Next, alongside keeping Git history clean & free from secrets.
Stake your LinkedIn Games performance through this on-chain staking protocol using stablecoins (USDC) to earn rewards tied to real, verifiable gameplay results. Built on the Sepolia TestNet, with Algorand blockchain as an inspiration, with** PyTeal** (Python smart contracts), Solidity, TypeScript and Next.js, featuring a** TailWind**-driven UI and multi-mode compatibility tailored for hackathon-scale demos and production-ready deployment.​

Achieved 3 perfect 100 Lighthouse scores across Performance, Best Practices, and SEO, along with a 92/100 score for Accessibility, demonstrating strong focus on UX, reliability, and technical optimization.​

The smart contract is currently deployed to an Ethereum address on the Sepolia testnet, enabling safe on-chain experimentation, end-to-end demo flows, and easy extensibility for future mainnet rollout.

Challenges I ran into

• Deploying the contract successfully.
  Had to redeploy multiple times due to bugs like in ABI, protocol logic etc.

• Switching from mainnet Ethereum to Sepolia testnet for easier access & better UX.

• Fixing ABI bug while recording stakes on the dashboard – followed code multithreading & object-oriented principles to fix it.

• Deployment bugs while on Vercel, despite locally working – fixed by making the code clean, scalable & optimized.

• Making the code & MVP secret-display free…fixed via following of code security principles.

• Implemented dynamic fetching of completed contracts and rendering them on the dashboard, giving users real-time visibility into finished staking sessions.

• Disabled repeat result submissions for completed contracts to prevent duplicate actions and ensure a smoother, more intuitive UX.