Questions about FinP2P, answered with sources.

No. finp2p.info is an independent community resource maintained by Alon Goren and the Draper Goren Blockchain venture studio. It is not operated, sponsored, reviewed or endorsed by Ownera or XCap Ecosystem Ltd, and Ownera has no editorial input. The official sources are ownera.io, Ownera's developer docs and the SuperApps store.

To help more people understand, connect to and build on the network. Ownera's store, docs and industry reports contain a lot of public information, spread across many places. This site puts it in one map with a source on every claim.

Yes, and it is disclosed on every page. Alon Goren is on the board of Ownera, and Draper Goren Holm, a fund he manages, is an Ownera investor. He is also on the board of LunarCrush, the data provider behind a proposed SuperApp. That is why every institution on the site needs a public source and anything without one is left off. See the about page.

The app and institution data is a snapshot taken on 2026-11-06, from the store's public API and the documents on the sources page. For an app's current status, check the store itself.

Email alon@dgb.vc, or open a pull request against data/graph.json in the public repository, with the correction and a public source. Corrections ship the same week.

FinP2P is Ownera's application-layer network for tokenized finance. Each institution runs its own Router; Routers coordinate transactions peer to peer, and assets and cash stay on whatever ledgers they already live on. Applications connected to Routers are called SuperApps. How it works has the diagrams.

No to the first: it is not a blockchain and has no shared ledger. It orchestrates transactions across existing blockchains and traditional ledgers. Ownera's public documentation describes no network token.

Per public sources: Ethereum and all EVM L1/L2, Hyperledger Besu, Canton, Corda, Hedera, XRP Ledger, Tezos, Stellar, Kadena, Solana, Polygon, 150+ chains via LayerZero. Each one, with its source, is on the network page.

The flagship is intraday repo between J.P. Morgan and HQLAx, in production since 2025 with $5 billion traded in its first month (HQLAx). On the store, 15 of 35 listings carry production status: Intraday Repo Hub, Asset Distribution & Access Hub, Collateral Mobility for Intraday Repo, Connector to Digital Custody Tech Providers, Custodian Service, Exberry Matching Engine, Institutional Real Estate Market, Investor SuperApp, Payment Provider Service, Prove Know Your Payee, Prove Pre-Fill for Business, ProveX, Universal Blockchain Connector, Universal Stablecoin Connector, plus the FinP2P Router License itself.

Ownera states that it is ISO 27001 (information security management) and ISO 27017 (cloud services) certified on its Trust page. Its October 2026 white paper adds SOC 2 Type II, and says the scope of each certificate is available from Ownera on request. We have not seen the certificates themselves.

Besides the Router, Ownera publishes its own applications on the store, and the Tokenized Treasury Manager: inventory and funding, collateral management and a treasury hub for minute-precision intraday repo with atomic delivery versus payment across chains. See the network page.

Not necessarily. A name means the institution is publicly connected to an app or to the network in the cited document, which might be a production deployment, a sandbox report or a vendor's partner page. Read the citation on the institutions page.

Ownera does not publish them. We derive them from each app's category, participant types and stated orchestration using ten explicit rules, listed on the map page. They are our reading, not an Ownera statement.

Decide whether you are building a business application (your product talks to a Router) or a utility or connector (the Router calls your adapter). Then follow the developer guide, which links each step to Ownera's official docs.

Usually not. Financial institutions run Routers, one per organisation. If you are a software vendor or fintech, your app connects to your clients' Routers, either as SaaS or deployed inside the institution.

From Ownera. You generate an RSA key pair, send Ownera the public key, and receive an API key, an organisation ID and a sandbox Router URL. The process is in the Authorization reference, and listing starts at superapps.ownera.io/onboarding-howto.

Anything that speaks HTTPS, signs RS256 JWTs and does GraphQL. Ownera publishes adapter skeletons in Node.js and Java and a reference adapter for EVM chains on GitHub.

Six steps, run by Ownera: portal sign-up, company profile, draft submission, review and agreements (including KYC due diligence), sandbox integration, then promotion to production. Summary in the developer guide.

Ownera does not publish listing fees. Ask Ownera.

Yes. Data providers implement the Data Provider adapter, and the Router routes asset identifiers to providers with data rules. Kaiko, Particula and ZeroBeta are examples on the store, and Draper Goren Blockchain open-sourced a reference data adapter.

Yes. /data/graph.json is CC BY 4.0: reuse it anywhere with attribution to finp2p.info.

For FinP2P itself, Ownera runs a public docs MCP server at https://finp2p-docs.ownera.io/mcp and the store has a public JSON API. This site is static: everything is in /llms.txt, /llms-full.txt and /data/index.json. Setup is on the agents page.

Ownera's docs list autonomous systems (automated trading, scheduled rebalancing, event-driven workflows) as a kind of business application. An agent goes through the same Router integration and credentials as any other app, and the institution's Router policies and approvals still apply.

Only the parties to a trade can see the trade. Everyone else on the network, and anyone reading the chain, sees nothing about it. It is how traditional markets already work: a repo between two banks is known to the two banks, their custodians and, when required, their regulator.

FinP2P has no central hub. Each institution runs its own Router, and Routers in a trade connect peer to peer. Ownera's white paper says Ownera supplies the Router as software, installed on-premises or run as a managed service, and is not a party to any trade: no Ownera system sits between the Routers, sees the data or holds the keys. See who sees what.

It depends on the chain used for settlement. Some hide amounts but not addresses; some hide everything from outsiders; some are not live yet. Some chains now hide metadata too; on public networks some transaction metadata may remain visible, as Ownera's own paper notes. See privacy by chain.

Each institution keeps a complete off-chain record of its own trades, with proofs signed by its counterparties, so it can hand a supervisor exactly the trades in scope. Need-to-know includes the supervisor.

It has happened: Solana paused confidential transfers for a year after a proof bug, and Besu removed built-in private transactions in 2025. On FinP2P each institution's signed record does not depend on any single chain, and adding or swapping a chain does not change who can see a trade.

Canton was the first network to build need-to-know privacy into its design, and it does it well, within one network. FinP2P applies the same model one layer above the chains and supports Canton as one of them, including delivery versus payment between Canton and other ledgers. See one chain or many.