The problem PeridotVault solves

The main problem in the local gaming industry is the high initial barrier. For small developers, the USD 100 listing fee on global platforms is often the first obstacle, even though they may not be commercially ready. Many developers just want to try publishing, testing, or asking for feedback, but are forced to spend money up front. In addition, the game testing process often involves real money, which is risky and not conducive to experimentation. As a result, many local games remain at the prototype stage and never reach the public. Peridot addresses this need: lowering the entry barrier (from USD 100 to USD 10) and providing a safe space for developers to experiment, including testing without real money, so that more Indonesian game IPs can be born and thrive within their own ecosystem.

Challenges I ran into

1. Designing a Multi-Chain System Without Fragmenting UX

One major challenge was building PeridotVault as a multi-chain platform while keeping the user experience consistent. Different chains expose different RPC behaviors, confirmation times, event formats, and wallet capabilities—which easily leads to fragmented logic and UX inconsistency.

How we solved it:
We introduced a chain-agnostic abstraction layer:

• Each supported chain exposes a unified interface for ownership checks and transactions
• Chain-specific logic is isolated behind adapters
• The Mini-App consumes a single normalized data model

This allowed us to deploy and optimize specifically for Base during the hackathon, while keeping the architecture future-proof for additional chains.

2. Implementing a Hybrid Onchain–Offchain Architecture

Purely onchain solutions quickly became impractical for a consumer app:

• Scanning ownership events on every load was slow
• RPC limits affected reliability
• UI responsiveness suffered under real usage

At the same time, moving too much logic offchain would weaken ownership guarantees.

How we solved it:
We adopted a hybrid architecture:

• Onchain: license ownership, verification, and critical state
• Offchain: indexing, aggregation, caching, and UX state
• Onchain data remains the single source of truth Offchain services only reflect and accelerate what is provably onchain.

This balance allowed PeridotVault to scale without sacrificing trustlessness.