# Chapter III: The Path We Build

> #### ✅ TLDR: Inside the OVERTAKE Architecture
>
>
>
> **ACT I – Escrow System**\
> Secure peer to peer trading using smart contracts, multisig logic, and off chain coordination.
>
>
>
> **ACT II – Verified Game Integration**\
> Connect to game servers to trade real in game assets with on chain proofs and dynamic NFT structures.
>
>
>
> **ACT III – Embedded Infrastructure**\
> Provide APIs and SDKs to embed trading, wallet, and token utilities directly inside game clients.

<figure><img src="https://2052872636-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpnWnXIxhiM4hNuHXacbX%2Fuploads%2Fk7cVIT7ct5GlJX99KgTO%2FImage%204.png?alt=media&#x26;token=a3cb79a5-9173-4a21-abbb-897c5b16060f" alt=""><figcaption></figcaption></figure>

While Chapter 3 focused on what we are building, this chapter explains how we are building it.\
OVERTAKE is not just a marketplace, it is a multi-phase architecture designed to evolve from a product into infrastructure. Each phase introduces a core capability that moves us closer to protocol-level integration with the gaming economy.



## ACT I: On-Chain Escrow System

The first phase establishes programmable trust between users by replacing Web2-style trading with a smart contract-based escrow system. This system enables secure peer-to-peer transactions of game accounts and items, backed by on-chain logic and off-chain delivery coordination.

We leverage Sui's object-centric model and programmable transaction blocks to implement decentralized escrow using 2-of-3 multisig logic, enabling the platform to mediate disputes without holding custody.

{% @mermaid/diagram content="sequenceDiagram
    participant Buyer as 🧍 Buyer
    participant Seller as 🎮 Seller
    participant Escrow as 🛡️ Escrow Protocol
    participant Platform as 🏢 Platform

    Buyer->>Escrow: Lock funds in escrow
    Seller-->>Buyer: Deliver item off-chain
    Buyer->>Escrow: Sign release
    Seller->>Escrow: Sign release
    Escrow->>Seller: Release funds (2 of 3 signatures)

    alt One party does not sign
        Escrow->>Platform: Dispute triggered
        Platform->>Escrow: Review and sign
        alt Platform favors Seller
            Escrow->>Seller: Release funds
        else Platform favors Buyer
            Escrow->>Buyer: Refund funds
        end
    end

" %}



**Core Technical Feature: Escrow System**

<table><thead><tr><th width="234.6666259765625">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>Escrow Object</strong></td><td>On-chain Move object containing payment amount, participant addresses, trade status, and required signatures.</td></tr><tr><td><strong>2-of-3 Multisig</strong></td><td>Trade is resolved when any two of buyer, seller, and platform sign off on the release.</td></tr><tr><td><strong>zkLogin</strong></td><td>Users onboard using email or social login, automatically creating non-custodial Sui wallets.</td></tr><tr><td><strong>Sponsored Gas</strong></td><td>All transactions are gasless for the user, with OVERTAKE sponsoring key flows.</td></tr><tr><td><strong>AI-Based Fraud Detection</strong></td><td>Off-chain models identify high-risk trades and flag suspicious activity pre-escrow.</td></tr></tbody></table>



## ACT II: Game Integration for Verified Asset Trading



The second phase moves beyond basic peer to peer trading.\
OVERTAKE connects directly with game publishers to enable the trading of verified in-game assets, such as accounts, currencies, or high-value items. These assets are no longer just tokens. They are validated representations of items within actual games, tied to server data and governed by the rules of the game environment itself.

This removes the need for escrow. Instead of relying on user coordination or dispute resolution, asset authenticity and ownership are verified at the source — the game publisher. This allows players to trade with confidence, knowing that the assets they buy and sell are legitimate, linked, and functional.

This phase builds on real-world implementation experience.\
During the launch of **Somnis: Rumble Rush**, OVERTAKE collaborated closely with the developer **MetaEdition** to build a Web3 marketplace that connected both to Immutable blockchain and directly to the game’s backend.\
Through this deployment, we proved our ability to manage live tokenized assets, verify ownership from off-chain databases, and support real-time transactions in a live game environment.

Looking forward on Sui, we take this further.\
We leverage Sui's support for **nested and dynamic NFTs** to create asset structures that can represent complex states (such as an account with an inventory, or a weapon with upgrade history) and update them over time while preserving full verifiability.



{% @mermaid/diagram content="sequenceDiagram
    participant Seller as Seller
    participant GameServer as Game Server
    participant OVERTAKE as OVERTAKE
    participant Blockchain as Block chain
    participant Buyer as Buyer

    Seller->>GameServer: Request tokenize game assets (account, items)
    Note over GameServer: Freeze user account
    GameServer-->>OVERTAKE: Request token mint to user
    OVERTAKE->>Blockchain: Mint Nested NFT (contains Dynamic NFTs)
    Note right of OVERTAKE: Account NFT includes items as nested Dynamic NFTs
    OVERTAKE->>GameServer: Send signal for successful mint
    Note over GameServer: Take over user's game assets
    Seller->>Blockchain: List NFT on marketplace

    Buyer<<->>Blockchain: Purchase NFT

    Buyer->>Blockchain: Convert token to game assets
    Blockchain->>OVERTAKE: Convert token to game assets
    OVERTAKE->>GameServer: Signal for token to game asset conversion
    Note over GameServer: Give user's game assets
    Buyer->>GameServer: Play with purchased game assets

" fullWidth="false" %}



**Core Technical Feature: Verified Game Asset Integration**

<table><thead><tr><th width="233.333251953125">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>Off-Chain Asset Mirroring</strong></td><td>Game-side data such as accounts or items is mirrored on-chain as Sui objects.</td></tr><tr><td><strong>Publisher Attestation</strong></td><td>Game servers provide signed proofs or authenticated APIs to verify ownership and asset state.</td></tr><tr><td><strong>Asset Registry Contracts</strong></td><td>On-chain registries define valid collections, asset types, and associated games for validation and filtering.</td></tr><tr><td><strong>Dynamic NFTs</strong></td><td>Assets can evolve over time. Attributes like level, power, or equipment status can be updated through programmable logic while maintaining verifiability and consistency with off-chain state.</td></tr><tr><td><strong>Nested NFTs</strong></td><td>A single NFT can contain child objects such as inventory, equipped items, or other linked assets.</td></tr></tbody></table>

##

## ACT III: Embeddings as Infrastructure



In the final phase, OVERTAKE becomes invisible infrastructure.\
Rather than operating a standalone marketplace, we provide modular APIs and SDKs that allow developers to embed trading functionality directly into their games.

This includes tools for listing assets, purchasing, wallet creation, escrow logic, staking, and $TAKE token utility — all accessible through client-side libraries and management dashboards.



{% @mermaid/diagram content="flowchart TB
    subgraph SDK[OVERTAKE Modular SDK]
        A1[ZK Login Wallet Creation]
        A2[Item and Account Listing]
        A3[Item and Account Trading]
        A4[$TAKE Utility Features]
    end

    SDK --> G1[Game A]
    SDK --> G2[Game B]
    SDK --> G3[Game C]

    G1 -.-> G2
    G2 -.-> G3
    G3 -.-> G1

    %% Annotations
    G1 -. Cross-game Trading Enabled .-> G2
    G2 -. Cross-game Trading Enabled .-> G3
    G3 -. Cross-game Trading Enabled .-> G1

" %}



**Core Technical Feature: Embedded SDK & API Layer**

<table><thead><tr><th width="238">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>Developer SDKs</strong></td><td>JavaScript, Unity, and Unreal SDKs for in-game trading integration.</td></tr><tr><td><strong>Marketplace API</strong></td><td>REST and GraphQL endpoints for trade data, asset listings, and escrow status.</td></tr><tr><td><strong>Wallet Integration</strong></td><td>zkLogin and external wallet connection support via SDK abstraction.</td></tr><tr><td><strong>Token Utility Hooks</strong></td><td>APIs for staking, trust scores, and discount logic tied to $TAKE.</td></tr><tr><td><strong>Publisher Dashboard</strong></td><td>Custom dashboards for analytics, trade volume, wallet binding, and revenue share.</td></tr></tbody></table>



Each ACT builds on the one before it.\
We start by enabling secure transactions through escrow, then transition to asset-level integration, and finally deliver our full infrastructure stack directly into games.

This layered architecture is how OVERTAKE moves from product to protocol — and how we deliver real ownership, liquidity, and value to players and developers alike.







