NFTeria is building the future of merchant-owned money.
A merchant’s till becomes a portfolio—and the portfolio still spends.
Live settlement on Ethereum Sepolia. Treasury automation and confidential execution are still being built.
One thing, done end to end.
We are building merchant-selected treasury holdings, spend-time conversion, confidential policy execution, human-readable merchant identity, and verifiable merchant ledgers. The settlement leg is live; the rest is in progress, and this page says which is which on every claim.
Merchant settlement on Uniswap v4.
Today
A barbershop creates an invoice for 40 settlement units. The customer pays with a supported asset. Uniswap performs the conversion, and the merchant receives the exact invoice asset and amount through the verified settlement path.
“Settlement units” is a demo denomination. The live deployment is a testnet, so nothing here is a real dollar amount.
UNICA does not take beneficial custody: the payer’s asset moves to the pool and the output moves to the merchant, and the contracts assert on real balances that neither leg was retained.
Next
After settlement, the merchant chooses a treasury policy:
- remain in the settlement asset;
- allocate into a supported portfolio asset;
- preserve a minimum operating balance;
- convert only the required amount when spending.
When the merchant buys clippers later, a future supported flow can convert the necessary amount at spend time. Spending can trigger bounded conversion without requiring a separate manual unwind.
Portfolio assets shown anywhere on this site are illustrative. No named equity is supported today.
Two people authorize. Nothing in between.
Settlement does not require discretionary approval once the merchant and the payer have authorized bounded terms. There is no admin pause, upgrade, dispute, refund or clawback in the settlement contracts.
The merchant authorizes
The merchant states the invoice: which asset, exactly how much, and to whom. On V1 that is an on-chain order; on V2 it is a signed, bounded quote.
The payer authorizes
The customer authorizes a bounded payment — a ceiling they will not exceed, in a token they chose, with a deadline. They are never asked to approve terms they did not see.
It executes atomically
Uniswap converts and the merchant is paid, or the whole transaction reverts. Whoever submits it cannot change a single term, and there is no third party who may approve, delay, reverse or seize it.
Your assets can work in public. Your strategy stays yours.
A real business should not have to publish its revenue patterns, allocation rules, minimum cash floor, or sell thresholds.
UNICA’s Chainlink CRE integration is designed so private policy values can be supplied through CRE secrets while public code exposes the permitted action schema. The workflow publishes a policy commitment intended to bind execution to a policy without publishing its private values.
Honestly: the policy model, adapter, secrets boundary and commitment behaviour are tested locally. UNICA has not run this workflow in a real CRE TEE or DON because Early Access remains pending. It is not TEE-attested today.
A commitment provides the integrity and binding property its scheme defines. It does not, by itself, prove that the hidden policy is safe, profitable, or correctly executed in a confidential environment.
Private strategy
Merchant policy values are designed to remain outside public code and public logs when executed through the intended confidential workflow. Real TEE/DON attestation remains pending.
Working capital
Merchant funds can be governed by an allocation policy rather than remaining indefinitely idle. Portfolio execution is currently being built.
Merchant control
The merchant selects the supported holding and risk policy. NFTeria does not select investments on the merchant's behalf.
Spendability
Supported holdings are intended to convert only as needed at purchase time, subject to liquidity, slippage, oracle, token and execution constraints.
Non-custodial design
NFTeria does not operate a custodial account for merchant funds. Smart-contract, wallet, token, oracle and protocol risks still exist.
Verifiable settlement
UNICA produces settlement evidence that can be independently recomputed from canonical payment data and chain records.
Autonomous treasury is not deployed, and it will not be until it is bounded
Settlement is safe to run without a supervisor because two parties already agreed to the exact terms. Treasury automation is different: it can act while the merchant is asleep. Before any of it goes live it needs per-action and rolling-period caps, a minimum reserve, an asset allowlist, fixed contract targets, oracle-freshness and slippage bounds, cooldowns, a policy expiry, a merchant revoke, a circuit breaker, and an emergency path that is narrower than the discretionary one.
That control model is being designed and tested now. Until it exists, nothing autonomous touches a merchant’s funds.
What is live, and what is not.
Every row carries the repository path or the command that proves it. If a row has no evidence you can re-run, it does not get a better badge.
V1 settlement
Hook and executor deployed and source-verified on Ethereum Sepolia, with a settlement receipted on chain.
Uniswap v4 settlement path
The conversion runs through Uniswap's official PoolManager and Universal Router. Tests run against the deployed bytecode, not a mock.
V2 release candidate (rc1)
V2 is written and frozen as rc1. It is not shipped. Release is blocked pending remediation and re-review of an internally identified Critical finding.
Receipt verifier
Recomputes a settlement from the quote rather than trusting the receipt's own fields. Runs with no endpoint at all.
Chainlink CRE policy + adapter
The risk policy, its adapter and the commitment/secrets boundary are implemented and tested locally. Never executed in a real CRE TEE or DON.
ENS merchant identity
A name resolves to a canonical merchant configuration, and the configuration binds into the quote. Offline fixtures and forks — no live registry.
The Graph merchant ledger
An indexer namespace with deterministic entity ids. Not deployed to Subgraph Studio.
Circle / Arc
Circle's Gateway batching was read from source and its guarantees written down. Nothing is wired, and no UNICA contract runs on Arc.
Robinhood / tokenized assets
The chain was probed for a Uniswap v4 stack. No integration exists, and no tokenized asset is supported today.
Cross-chain settlement (CCIP)
Designed, not started. There is no CCIP code in the repository yet — this row exists so the gap is visible rather than implied away.
no implementation in the repository at the commit above
Merchant treasury automation
Caps, reserves, asset restrictions, cooldowns, revocation and an emergency model are being specified before any autonomous execution is deployed.
Verified against the public UNICA repository at commit c20a17a.
Who we depend on, and what we still need.
Ordered by how much the product currently depends on them.
Uniswap
Role. The conversion itself — the merchant's asset out of whatever the customer paid, and later the spend-time conversion back.
What we built. A v4 hook and executor that bind an invoice to the swap that discharges it, live and source-verified on Sepolia.
Still needed. Guidance on binding a Permit2 witness to a counterparty-signed order — see our developer feedback.
Chainlink
Role. Confidential policy execution, price inputs, and automated protection for a merchant's treasury.
What we built. A deterministic risk policy, a workflow adapter, and a policy commitment that binds execution without publishing the policy.
Still needed. CRE Early Access, so the workflow can run in a real TEE/DON. It has never done so.
Circle / Arc
Role. The stable settlement asset a merchant falls back to, on a chain where the money and the gas are the same thing.
What we built. An independent verification of Circle Gateway's batching guarantees, written from its source.
Still needed. A Uniswap deployment on Arc. Until then UNICA cannot settle there.
Robinhood
Role. A venue for the tokenized assets a merchant might choose to hold.
What we built. A chain probe only. No integration.
Still needed. A citable, supported venue and an eligibility path. We claim no asset availability.
ENS
Role. A merchant is a name, not an address.
What we built. Name to canonical configuration to quote, with every failure shape classified and fail-closed.
Still needed. Nothing from ENS — this one is ours to deploy.
The Graph
Role. The merchant's own searchable record of what settled.
What we built. An indexer namespace with deterministic entity ids and mapping tests.
Still needed. Nothing from The Graph — a Studio deployment is an owner action.
The rest of what we have built.
UNICA is the current focus, not the whole history. These are earlier and parallel lines of work. Treat them as building or planned unless a status above says otherwise.
Payments and invoices
USD-priced onchain payments from a shareable link, settled through the NFTeria rail on testnets.
Read more →Bookings
Reservations, deposits and no-show fees settled onchain, with no platform holding the money.
Read more →Credentials and identity
Memberships and credentials as self-contained onchain SVG that cannot rot or be revoked from afar.
Read more →Agents
An agent paying per call within a budget the owner sets, via session grants and nanopayments.
Read more →The manifesto
Why we think a business should own its own money rail, written before any of this existed.
Read more →Deployed across 8 testnets
The NFTeria rail and contract stack, deployed on 8 EVM testnets and source-verified on 6. Every address reads from a committed broadcast. These are testnets — there is no mainnet deployment.
Credentials
Self-contained on-chain SVG — the same art the contract carries as its tokenURI.
Achievement badge
A medallion with a bronze / silver / gold tier ring. Earned, not bought.
Certificate
Name, accomplishment, issuer, and date — a verifiable record anyone can check.
Membership
A wallet-held member card. Tiered, transferable, revocable.
Loyalty stamp
A small perforated stamp for repeat-visit and collect-them-all programs.
The open stack
Every layer NFTeria runs on is open-source, gas-only, or pay-as-you-go.
Identity
- ENS
- World ID
- Dynamic
- MetaMask Snaps
- Ledger
Payments
- Chainlink
- Circle (USDC)
- Arc
- Coinbase
- Uniswap
- LI.FI
- Yellow
- Hedera
- Blink
Data
- The Graph
- 0G
- Walrus
- Google Cloud
Chains
- Base
- Arc
- Sui
- zkSync
What we will not claim.
- UNICA has not been audited by a third party. The security review published in the repository is internal, by the people who wrote the code.
- V2 is written and frozen as rc1. It is not shipped. Release is blocked pending remediation and re-review of an internally identified Critical finding.
- Everything deployed is on testnets. There is no mainnet deployment and no real value at risk.
- Merchant treasury automation is not deployed. Its control model — caps, reserves, asset restrictions, revocation, emergency behaviour and an optional notice period — is under active development.
- The Chainlink CRE workflow has never run in a real TEE or DON. Confidentiality claims describe a design that is tested locally, not an attested execution.
- No tokenized equity is supported. Named assets used to illustrate the treasury idea are illustrative only.
- Cross-chain settlement is designed, not implemented. There is no CCIP code in the repository yet.
- Arc is not running UNICA, and no Uniswap deployment there is available to us today.
- Merchant signers must be EOAs; smart-contract wallets cannot yet sign a merchant quote.
“Unica” is used as a name meaning “one of a kind”. That is name etymology, not a claim that the product is the first or only system of its kind.
Read the code, not the copy.
Everything above is checkable. The repository is public, the settlement contracts are source-verified on a public explorer, and the security review names its own open findings.