Rupiah4X
Break local currency barriers with cross-chain IDRX swaps on every chain. Unlock global stablecoins instantly. No Banks. No Delays. Any Chain.
Demo
About
The problem it solves Access to global currencies remains limited for users in emerging markets like Indonesia, where traditional forex and remittance services are costly, slow, and often require bank accounts or centralized intermediaries. Local stablecoins like IDRX, while pegged to the Indonesian Rupiah, typically lack interoperability and real-world utility outside of local ecosystems. Simultaneously, major asset-backed stablecoins like USDC (USD), EURC (Euro), and XAUT (Gold) are fragmented across different blockchains, making cross-currency swaps complex, expensive, and dependent on centralized exchanges or bridges. Our project introduces a decentralized, intent-based cross-chain forex swap platform that uses IDRX as the entry point and Lisk, a scalable Layer 2 blockchain, as the execution layer. The platform allows users to directly and securely swap IDRX for stablecoins like USDC, EURC, and XAUT across supported chains—without relying on custodians, centralized bridges, or traditional forex rails. Using intent-based architecture and shared sequencing, the system matches user intents with off-chain solvers who execute swaps securely on-chain. This design ensures non-custodial, low-fee, and near-instant swaps, while maintaining cross-chain security and trust minimization. The result: users in Indonesia and similar markets can hold value in their local currency and access global assets instantly—turning IDRX into a true on-chain forex access point. The platform unlocks real-world utility for local stablecoins, bypasses banking limitations, and offers a new model for global currency access that is open, interoperable, and permissionless. By solving currency access barriers, reducing remittance friction, and eliminating centralized dependencies, this project redefines how people engage with forex in the Web3 era.
How it's made
Challenges we ran into We faced problems when integrating hyperlane to the lisk testnet. This is due to the hyperlane not providing the proxy address by default which is why we need to deploy the hyperlane from scratch like the relayers ourself. By deploying several contracts, we can then use the proxy address to enable hyperlane configuration. This then allows cross-chain communication to happen so that user can submit their intent and be filled by the solver.