Coixa Whitepaper

1. Introduction

Coixa is a non-custodial wallet and decentralized finance (DeFi) access layer built specifically for the Pi ecosystem. It is designed to provide users with direct control over their assets while enabling interaction with Pi-native decentralized applications through a unified, external interface.

Coixa is built primarily for Pi users operating in an open-network context, where decentralized applications extend beyond a single embedded environment. It also serves ecosystem partners and developers as a standardized access layer for decentralized authentication, wallet connectivity, and transaction signing.

Unlike the standard Pi Wallet, which is optimized for use within the Pi application and Pi Browser environment, Coixa is optimized for the open network. It is designed to enable Pi wallet connectivity across external mobile applications and desktop browsers, allowing users to interact with Pi-native dApps outside of the Pi Browser context.

Within the Pi ecosystem, Coixa functions strictly as an interface layer rather than an intermediary. It does not custody assets, operate accounts, or act on behalf of users. Its role is to expose wallet functionality and DeFi interaction in a way that preserves user control and minimizes trust assumptions.

2. The Problem

As the Pi ecosystem transitions toward open network usage and broader utility, several structural limitations become increasingly apparent for both users and developers. These constraints are primarily infrastructural rather than conceptual.

2.1 User Limitations

Currently, Pi users face limited access to decentralized financial functionality through external, non-custodial tooling. Wallet experiences are often confined to specific environments, requiring users to switch contexts to manage assets or interact with decentralized applications.

In many cases, existing workflows are not optimized for complex interactions or consistent mobile-first execution. Transaction approval, signing flows, and DeFi interactions can introduce friction, particularly as applications become more sophisticated.

2.2 Developer Limitations

From a developer perspective, the core limitation is that decentralized applications are largely constrained to the Pi Browser environment. This restricts where and how Pi-native dApps can operate and limits their ability to integrate with standard Web3 tooling.

Currently, there is no dedicated external signing and connectivity layer that allows dApps to request decentralized authentication and secure, user-approved signatures outside of the Pi Browser. As a result, developers struggle to build applications that support complex, multi-step interactions, advanced DeFi workflows, or cross-platform usage.

The absence of a standardized signing interface increases development complexity, reduces composability, and makes it difficult to build sophisticated tools that operate consistently across browsers and devices.

3. Design Principles

Coixa is guided by explicit design principles that prioritize user control, security, and clarity over rapid feature expansion.

• Non-custodial by default
  Users retain sole control of their private keys. Coixa does not hold, recover, or transfer keys on behalf of users.
• Security-first architecture
  Design decisions favor conservative security assumptions, even when this introduces constraints or limits surface-level convenience.
• Mobile-first execution
  Core interactions are designed for mobile environments, reflecting how most Pi users access the ecosystem.
• Minimal trust assumptions
  Coixa minimizes reliance on off-chain components and avoids opaque execution paths.
• Clear separation of concerns
  Wallet key management, transaction signing, and network interaction are explicitly separated to avoid ambiguous responsibility boundaries.

These principles involve trade-offs, including a narrower initial scope and slower expansion in favor of correctness and reliability.

4. Coixa Architecture (High-Level)

Coixa's architecture is structured to provide wallet functionality and decentralized application access while maintaining clear boundaries around custody, execution, and network interaction.

Wallet Layer

The wallet layer is responsible for key generation, storage, and user authorization. Private keys are generated locally on the user's device, encrypted, and stored locally. Keys are never transmitted to Coixa servers. An optional cloud backup mechanism is planned as a strictly user-controlled feature.

On supported devices, the wallet is designed to leverage hardware-backed secure environments, such as secure enclaves or equivalent trusted execution environments, to isolate sensitive key material from the application layer.

Transaction Signing and Execution

All transactions are constructed and signed locally by the user's wallet. Every operation requires explicit user approval. Coixa cannot sign, modify, or execute transactions independently.

Signed transactions are submitted to the network without Coixa acting as a custodian or proxy authority.

Protocol Connectivity

Coixa is designed to interact directly with the Pi blockchain through supported network interfaces and node APIs. Transaction payloads generated and signed by the wallet are broadcast to the network without reliance on the Pi Browser as an intermediary.

This connectivity layer enables decentralized applications to request wallet connections and signatures from external environments, including desktop browsers and third-party mobile applications.

DeFi Gateway Abstraction

Coixa provides an interface layer for interacting with DeFi functionality natively supported by the underlying blockchain. This abstraction is intended to simplify user interaction while preserving protocol behavior, execution semantics, and custody guarantees.

Throughout the architecture, Coixa operates strictly as an interface and coordination layer, not as a custodian or execution authority.

5. Roadmap

Coixa's development is structured to prioritize open-network usability while maintaining a conservative approach to security and custody.

Phase 1: Wallet and Connectivity Foundation

This phase focuses on establishing a secure non-custodial wallet alongside standardized decentralized application connectivity. Core objectives include:

• Local key management and transaction signing
• Mobile-first wallet usability
• External dApp connectivity and signature requests

Standardized connectivity is treated as a foundational capability, enabling Pi-native dApps to operate outside the Pi Browser environment.

Phase 2: Extended Integration Layer

This phase is intended to expand connectivity through additional interfaces, including browser-based extensions. The goal is to improve developer ergonomics and provide consistent signing and authorization flows across platforms.

Long-Term Vision

Over the long term, Coixa is intended to support broader interoperability, including multi-chain compatibility and cross-ecosystem DeFi access. This direction represents design intent and remains subject to technical, ecosystem, and regulatory constraints.

6. Security and Custody Model

Coixa's security model is intentionally conservative and explicit, emphasizing local execution, user consent, and minimal trust assumptions.

Private keys are generated locally on the user's device and encrypted at rest. On supported hardware, Coixa is designed to utilize secure execution environments to isolate key material from the application layer.

All transaction signing occurs locally and requires explicit user approval. Coixa cannot access private keys or move funds unilaterally.

Prior to mainnet deployment of critical components, wallet logic and related interfaces are intended to undergo independent third-party security review. This approach is intended to reduce implementation risk rather than eliminate it entirely.

Users remain fully responsible for key management, backup decisions, and transaction authorization. By design, Coixa cannot act on user assets without consent, reducing systemic custody and platform-level risk.

7. Regulatory Posture

Coixa is a non-custodial software platform that provides infrastructure and tooling for wallet interaction and decentralized application access. It does not act as a financial intermediary, custodian, or broker.

Coixa does not provide legal, financial, or investment advice. Regulatory considerations may vary, and users are responsible for understanding applicable requirements in their respective jurisdictions.

8. Sustainability and Governance (Future Concept)

8.1 Sustainability Model

To ensure long-term maintenance of servers and security audits, Coixa implements a sustainable fee structure:

• Value-Added Services: A minimal service fee (e.g., 0.1% - 0.3%) is applied to convenience features such as in-wallet swaps, bridging, or fiat on-ramps.
• Revenue Allocation: Revenue is directed towards protocol maintenance, developer grants, and the Community Treasury.

8.2 $COIXA Governance (Future Concept)

$COIXA is currently a conceptual governance coordination tool. If implemented, its purpose will be:

1. Governance: Voting on protocol parameter changes (e.g., supported dApps, fee structures).
2. Incentives: Rewarding developers who integrate the Coixa Connect SDK. Note: No token supply or sale details are defined at this stage. Users should be wary of scams claiming to sell Coixa tokens.

This concept remains undeveloped. No supply parameters, economic models, or distribution details are defined at this stage.

9. Conclusion

Coixa is designed as infrastructure first. Its focus is on providing non-custodial access, explicit security boundaries, and practical usability within the Pi open-network ecosystem.

The project prioritizes access before expansion, correctness before complexity, and trust before scale. Future development is approached with restraint, acknowledging uncertainty rather than promising outcomes.