Hackathon project 03 · Memekathon Seoul
11 / 12
MemeCore Cross-chain Yield Prototype
A MemeCore-focused DeFi prototype designed to expose external yield opportunities without making users operate a bridge directly.
- Role
- Frontend & Product UI/UX Lead · 2025
- Problem
- The interface needed to hide unnecessary bridge operation while remaining honest about cross-chain progress and risk.
- Strategy
- The product presented one yield goal, but the frontend kept account resolution, source action, cross-chain progress, position update, and history as distinct states.
- Outcome
- Received the user-confirmed 2nd Place result at Memekathon Seoul 2025.
2nd Place · user-confirmed · 2025
01
Problem definition
Why this problem had to be solved
This Memekathon project adapted the stablecoin and smart-account experience for MemeCore users, focusing on access to cross-chain yield without a separate bridge journey.
What users and the system were facing
MemeCore users needed a product path to DeFi opportunities beyond one chain.
A manual bridge journey would add network, asset, and transaction complexity before the main product action.
The prototype needed to distinguish demonstrated flows from broader yield claims.
Frontend ownership
I led the frontend and product UI/UX for this MemeCore submission. Other team members owned vault, bridge, token, account-abstraction, and optimization contracts and infrastructure.
MemeCore-focused product and responsive UI
Social-login and smart-account onboarding
Cross-chain yield position and action states
Demo flow, dashboard, and history presentation
02
Solution strategy
A system strategy carried into production
The product presented one yield goal, but the frontend kept account resolution, source action, cross-chain progress, position update, and history as distinct states.
System model
Social login resolves a smart account, which connects MemeCore context to cross-chain positions and deposit or withdrawal result states.
Product evidence
Selected product surfaces
Historical product interfaces. Values shown are captured UI states, not current TVL, APY, or performance claims.
Implementation decisions
Adapted onboarding and network context for the MemeCore environment.
Presented external yield access as one product action instead of a separate bridge task.
Connected balances, positions, and action history in one dashboard.
Kept implemented behavior distinct from proposed optimization and growth scenarios.
03
Outcome
What changed—and what I learned
Received the user-confirmed 2nd Place result at Memekathon Seoul 2025.
Appears as an official featured DeFi project on the Memekathon site.
Tested a MemeCore-specific cross-chain yield journey with a working prototype.
Learning
Removing bridge controls from the primary journey does not remove the need to explain delay, failure, and asset-location risk.
Today
I would add an explicit risk model, chain and contract status, message observability, and strict separation between measured outcomes and pitch scenarios.
Built with
Public links
Work together