IPI
IPI Public Testnet — Live

IPI Independent Protocol Infrastructure

Tap it. Approve it. Prove it.

IPI connects physical product identity, checkout, wallet approval and chain-backed ownership in one connected system.

Pay in a physical store with IPI Card, approve the complete operation in IPI Wallet and receive the merchant-provided receipt, warranty context, authenticity and ownership records in the same flow.

See how it works Explore the live network

Built in public. The IPI Terminal and secure product authentication are currently in active development.

IN-STORE CHECKOUT / PRODUCT 0184 IPI Tap ready
IPI TERMINALPHYSICAL STORE
Product identifiedProduct 0184Verified product context
✓
Merchant
Example Store
Operation
Product purchase
Total
24.00 IPI
Waiting for customer tap
Customer actionTap IPI Card

Card introduces the wallet-bound authorization factor. It carries no independent balance or recovery seed.

IPI WALLETCONNECTED
✓
Operation approved24.00 IPI · Product 0184
Delivered to your WalletAUTOMATIC AFTER APPROVAL
  • 01
    Receipt / invoiceMerchant and payment trail
    ✓
  • 02
    Warranty contextTerms selected by the issuer
    ✓
  • 03
    Authenticity recordIdentity and disclosed provenance
    ✓
  • 04
    Ownership recordAccepted by the customer
    ✓
Payment confirmed Wallet bundle delivered Network record verifiable

Automatic for the customerExplicitly approvedIndependently verifiable

Public testnet onlineLive chain and public verification APIs — Public repositories— original projects · GitHub live
22 Typed IPI Tap operationsDefined in the engineering protocol source
3 Execution environmentsNative settlement · EVM · CosmWasm
The complete flow

From the store counter to a Wallet that remembers.

Most checkout systems stop after the payment succeeds.

IPI can deliver the product relationship with it.

  1. 01

    Identify the product

    IPI Terminal reads the product identity and assembles the merchant, item, amount and operation.

  2. 02

    Tap IPI Card

    The customer presents a wallet-bound authorization factor at the physical checkout.

  3. 03

    Approve in Wallet

    IPI Wallet shows the product, merchant, amount and resulting records before confirmation.

  4. 04

    Receive the proof bundle

    After approval, the integrated merchant can deliver the receipt, warranty context, authenticity and ownership records to the Wallet.

IPI Card system

A secure tap is a role—not a rectangle.

IPI is designed for cards, chips, stickers and embedded inlays that can live with a person or inside a product.

Choose the trust profile, physical format and purpose the operation actually needs.

01 / FOR PEOPLE

IPI Card

A wallet-bound authorization factor for payment and high-value operations. It is not a second wallet: it holds no independent balance and no recovery seed.

  • Tap to introduce the authorization factor
  • Review the complete operation in IPI Wallet
  • Freeze or replace the factor without moving the assets
02 / FOR PRODUCTS

IPI Product Chip

A physical identity and authentication layer embedded in an item, package or asset. It can identify the product and prove chip-level evidence, but cannot change ownership by itself.

  • Connect an item to its durable product record
  • Carry identity through production, sale and service
  • Separate product proof from human authorization
Security profile ADEVELOPMENT EVIDENCE

Symmetric verification

Efficient authentication using protected shared key material and a verifier-controlled lifecycle. The current physical development evidence uses NTAG 424 DNA with dynamic SDM/SUN proofs.

Designed forHigh-volume cards · labels · product inlays
Security profile BPLANNED

Asymmetric verification

A future profile where the chip proves possession of a private key that does not leave the secure hardware, enabling verification through the corresponding public key.

Designed forPremium goods · independent verification · long-lived assets
Hardware program

One protocol. Multiple physical forms.

Cards, chips, adhesive labels and embedded inlays are being prepared for future availability. Physical format does not decide the role: where the verified security profile and lifecycle permit it, a form can identify a product or act as an authorization factor. Final supported operations and sale dates will be published only after production verification.

CardsAuthorization or product credential ChipsEmbedded identity or secure factor StickersProduct label or tap factor InlaysCustom identity or authorization
Discuss a hardware integration
Interactive product demo

Watch an in-store IPI purchase reach the Wallet.

Follow a controlled interface simulation from the merchant’s counter to the customer’s proof bundle. It does not sign, broadcast or record a real transaction.

Front-end simulation · no real transaction
IPI FLOW SIMULATION Ready
  1. ▦
    Product identified and checkout createdWaiting to start
    1
  2. ⌁
    Customer taps IPI Card at the TerminalWaiting for checkout
    2
  3. ◫
    Customer reviews and approves in IPI WalletWaiting for card factor
    3
  4. ◇
    Receipt, warranty, authenticity and ownership deliveredWaiting for approval
    4
Simulation only 0%
After the approval

The payment is the start of the product relationship.

When a merchant or platform integrates the complete IPI flow, the Wallet can become the customer’s verifiable place for the records created around a purchase—not another disconnected loyalty app.

One approval. The relevant records arrive with the completed purchase.

IPIPublic testnet asset USDCNoble / IBC integration gated

The USDC path is implemented behind an evidence gate and remains disabled until the live channel, denomination trace, relayer and transfer path are independently verified.

IPI WALLETPURCHASE / 0184
Verified productProduct 0184Ownership accepted
✓
01
Receipt or invoice trailMerchant · amount · payment · timestamp
PROOF
02
Warranty contextTerm and service events selected by the issuer
POLICY
03
Authenticity and provenanceProduct identity and disclosed origin events
TRAIL
04
Transferable ownershipAccept, hold or initiate a future transfer
OWNER
05
Benefits and verified feedbackEligibility and reviews linked to purchase evidence
VALUE

Illustrative integrated experience. Availability depends on the participating issuer, merchant and application.

One system, four layers

Built as one system.

01

IPI Terminal

A clear checkout experience for products, payments, receipts and ownership operations.

In active development
02

Product Identity

NFC and cryptographic product identity connecting physical items with their digital records.

Physical testing underway
03

IPI Wallet

The human approval layer where the customer verifies exactly what is being signed.

Public testnet interface available
04

IPI Chain

The independent network layer for verification, settlement and ownership events.

Public testnet live
Engineering reality

More than a network. A product stack with visible boundaries.

IPI is being developed across protocol, physical identity, consumer approval and merchant infrastructure.

Every capability is labeled by evidence—not ambition.

Public now

Infrastructure you can inspect today.

Public interfaces backed by the running IPI testnet.

  • 01
    IPI ScanBlocks, transactions, accounts, validators and EVM lookup
  • 02
    Dual executionNative IPI state with EVM and CosmWasm execution paths
  • 03
    Open network interfacesRPC, REST, WebSocket and EVM JSON-RPC; gRPC tracked separately
  • 04
    Test infrastructureWallet interface, faucet, status and public monitoring
Active validation

Integrated source under real-world testing.

Implemented boundaries that are not being presented as production-ready.

  • 01
    IPI Wallet applicationsWeb/PWA plus separate Android and iOS consumer shells
  • 02
    IPI TerminalAndroid merchant shell for charge, products, Tap, sales and business
  • 03
    IPI Tap v1QR, deep link, NFC/HCE and Nearby transport boundaries
  • 04
    Commerce and identityProducts, acceptance, ownership, receipts and recoverable sale states
Verification gated

Explicitly blocked until evidence exists.

Controls stay unavailable instead of manufacturing a success state.

  • 01
    Production wallet custodyTrusted account and signing adapters remain a release gate
  • 02
    Merchant authenticationProtected Terminal operations require a real identity provider
  • 03
    Secure card provisioningProduction keys, attestation and shared replay state are pending
  • 04
    Live USDC over IBCDisabled until channel, trace, relayer and transfer evidence all pass
Source maturity and network availability are different claims. Review the public organization
Live network

Proof, not promises.

The IPI public testnet is available now.

Live dataConnecting…
Latest blockConnecting…CometBFT height
Average block timeConnecting…Latest 20 blocks
Total transactionsConnecting…Indexed native activity
Network statusConnecting…ipi-testnet-1
Active validatorsConnecting…Current validator set
Native supplyConnecting…IPI · Cosmos REST
EVM blockConnecting…Chain ID 42424
Public RPC statusConnecting…Read-only availability
Updating every 5 seconds

Latest finalized blocks

Open block history
  1. Connecting to IPI Scan data…
Open IPI Scan View Network Status Get Testnet IPI
Ecosystem possibilities

One proof layer. Many products the ecosystem can build.

The goal is not for IPI to manufacture every application below. The goal is open infrastructure and a credible direction for builders, merchants, manufacturers and communities.

These are potential development paths—not claims that every product is available today.

01THE CUSTOMER

Proofs that stay with the purchase.

  • Receipt and invoice trailDurable proof of what was bought, from whom and when.
  • Warranty and repair historyThe issuer decides which warranty terms and authorized service events are disclosed.
  • Authenticity and ownershipOriginality evidence, possession proof and transferable ownership records.
  • Verified reviewsProduct and service feedback backed by purchase or service evidence.
02COMMERCE

More context around every transaction.

  • Discounts and loyaltyEligibility based on products, purchases or disclosed customer groups.
  • E-commerce and P2P flowsConnect online checkout, wallet approval, acceptance and transfer.
  • Auctions and marketplacesApplications can combine listing, payment, provenance and delivery evidence.
  • Product and service exchangeTyped operations for sales, refunds, payouts and product-for-product exchange.
03SUPPLY CHAINS

Turn operational events into evidence.

  • Materials and origin trailsDisclosed provenance from raw materials through production and distribution.
  • Fraud detection signalsFind mismatches across identity, custody, inventory and declared movement.
  • Provable inventory and servicesAttest stock, custody or completed work without one shared private database.
  • Customs, excise and tax proofsOptional evidence issued by authorized participants and verified later.
04PHYSICAL INDUSTRY

Give long-lived assets a verifiable memory.

  • Digital Product PassportsRecords designed to outlive a manufacturer’s private application.
  • Vehicles and equipmentOdometer, ownership and authorized service events with accountable issuers.
  • Medical and industrial identificationNFC, RFID and embedded identities chosen for the risk profile.
  • Commodities and goods marketsFuture applications can combine asset evidence, custody and settlement.
Important

IPI provides verifiable primitives, not automatic truth. Every claim still needs an accountable issuer, appropriate hardware, a disclosure policy and evidence that can be checked. Private business or customer data should not be placed on a public chain by default.

Why IPI is different

Most chains begin with a transaction.
IPI begins with the complete operation.

A payment alone cannot prove what changed in the physical world. IPI is being designed so product identity, participant intent, settlement, receipt and ownership can be reviewed and verified as one connected event.

01

Product-aware primitives

Native models for products, chips, checkout, receipts, acceptance and ownership—not only generic token transfers.

02

Typed IPI Tap operations

Twenty-two versioned operations across Wallet and Terminal, independent of QR, NFC, nearby or deep-link transport.

03

Human-readable authorization

The exact product, amount, parties and action are bound to the summary the customer reviews before approval.

04

Multiple execution paths

Native IPI settlement alongside public EVM and CosmWasm execution, exposed through standard network interfaces.

05

Hardware with separate roles

A card authorizes, a product chip identifies, the account owns. No seed or independent card balance is required.

06

Fail-closed engineering

Unverified cards, identities, exchange rates and USDC routes stay unavailable instead of producing a manufactured success state.

Long-range protocol thesis

Portable execution. Message-first integration. Verification without gatekeepers.

Research directions include broader WebAssembly portability, language-neutral message schemas, parallel execution, modular protocol upgrades, wider validator participation and privacy-preserving proofs. These are not current testnet performance or consensus claims.

Independent Protocol Infrastructure

No gatekeeper.
No mandatory sales call.
Just evidence.

You do not need approval from IPI to inspect the public testnet, query its public interfaces, use the faucet, review the source or prototype against the available infrastructure. The design target is infrastructure that no single company—including IPI—can make the sole authority over verification.

Verify it yourself Start building
READPublic evidence

Blocks, transactions, accounts and network status can be checked independently.

BUILDOpen interfaces

Prototype with public RPC, REST, WebSocket, EVM JSON-RPC and published source.

CONTROLYour integration

Choose the application, hardware roles and data disclosure model appropriate to your product.

VERIFYNo private dashboard required

The landing page and IPI itself should never be the only source of network truth.

Current reality: the public testnet is presently operator-run and has a limited validator set. Broader independent operation and community-operated releases remain explicit roadmap gates.

Public roadmap

Progress is measured by evidence.

The IPI roadmap is a sequence of verification gates—not a promise of dates, token value or production readiness.

Read the complete roadmap
  1. 00
    Current focus

    Make the project legible

    Public ownership, maturity labels, licensing, architecture and decision records.

  2. 01
    Current focus

    Reproducible protocol baseline

    Builds, network identity, compatibility tests, release artifacts and independent verification.

  3. 02
    Verification gate

    Verifiable commerce primitives

    Product passports, chips, checkout, receipts, wallet signing and public/private data boundaries.

  4. 03
    Verification gate

    Independent operation

    Repeatable node, wallet, explorer, terminal, monitoring, recovery and degraded-mode operation.

  5. 04
    Planned

    Interoperability with explicit trust

    IBC and anchoring only with published custody, accounting, failure and exit models.

  6. 05
    Long-term

    Community-operated releases

    Independent reviewers, multiple operators, security reviews and durable public governance.

Why IPI

The physical and digital worlds should not be separate systems.

A product can be genuine while its receipt is lost.

A payment can be valid while the product information is incomplete.

A database can contain ownership records while remaining controlled by one company.

IPI is being built to connect these elements into one independently verifiable flow.

01Product identity. 02Human approval. 03Transaction receipt. 04Chain-backed ownership.
Build on IPI

Build, test and verify.

Connect to the public IPI testnet and explore the infrastructure currently available.

Developer documentation and integration tools are being expanded as the product moves through public testing.

Build with IPI

Make every product provable.

Tell us what you are building, what must be verified and where the physical and digital flow breaks today.

Explore the Testnet View public GitHub
Prefer email? [email protected]
  • 01Technical first responseIntegration, protocol and infrastructure conversations
  • 02Contact is optionalPublic testnet access does not require commercial approval
  • 03Privacy-aware intakeYour message is emailed to IPI and never written on-chain
Integration enquiryStart a conversation.
SECURE FORM

By sending this form, you ask IPI to reply to the email provided. See the privacy summary.