FAQ
Frequently asked questions about Torq behavior, written for first-time non-technical readers.
Basics
What is Torq?
Torq is the credit facility operating system for tokenized assets. It combines vault commitments, market execution components, roles, permissions, NAV and Live-Feed valuation, indexing, projectors, APIs, and role-specific workspaces.
Is Torq just another lending pool?
No. A pool is one useful mental model for DeFi lending, but Torq is organized around governed credit facilities. A vault defines a controlled commitment, markets let borrowers draw under rules, and post-write verification confirms that the application truth updated.
Is Torq just a yield vault?
No. Torq has vaults, but the vault is not only a yield-routing container. It is the capital boundary for a facility with authority, capacity, fees, tranches, redemption, market attachment, and operating state.
How is Torq different from Aave or Morpho?
Aave's official introduction explains supplying assets into liquidity pools and borrowing against collateral. Morpho Vault V2 docs explain curated vault strategies, adapters, caps, and role separation. Torq is documented as a governed credit facility operating model with role action paths and post-write verification.
Users
Who uses Torq?
Torq has surfaces for lenders, borrowers, protocol managers, asset managers, asset issuers, NAV reporters, liquidators, partners, partners, guardians, council roles, vault owners, allocators, and indexer/projector operators.
What does a lender do?
A lender reviews vaults, deposits where supported, reviews Senior/Junior tranche exposure where active, monitors positions, and requests or claims redemption according to vault state.
What does a borrower do?
A borrower opens facility or market detail, manages collateral, draws through a prepared borrower route, repays debt, and waits for projected state to confirm the result.
What does an asset manager do?
An asset manager operates vault programs, assets, oracles, markets, IRMs, partners, roles, public profile, price adapters, and AI allocator support where surfaced.
What does an asset issuer do?
An asset issuer submits asset metadata and tracks controlled assets, submissions, NAV reports, messages, roles, and incidents. Submission is a review action path, not automatic protocol listing.
What does a NAV reporter do?
A NAV reporter submits or signs valuation reports where configured. Reporting authority is not the same as global governance authority.
Actions
When is an action complete?
An action is complete when the affected state can be read through the persisted product truth path: write or metadata update, indexing, projection, API refresh, and workspace reread.
Completion rule
A wallet confirmation is only one step in a completed Torq workflow
User sees what will change and what authority is required.
The required transaction or metadata write is executed.
The affected chain or persisted event is refreshed.
Postgres current-state rows are recomputed.
The workspace rereads persisted truth before showing complete.
Why did my wallet show success but Torq still says pending?
The transaction may be mined while the indexer or projector has not finished. Torq keeps that distinction visible so users do not confuse transaction submission with product-state completion.
Why is a button disabled?
Common reasons include missing permission, wrong wallet, wrong entity, missing allowance, insufficient balance, stale oracle, stale NAV, vault capacity, unsafe collateral health, active freeze, timelock delay, unsupported route, or pending indexing.
Why can a borrower not draw?
Borrowing can be blocked by missing collateral, invalid borrower route, stale oracle, expired risk epoch, insufficient vault partition liquidity, market emergency state, missing allowance, or missing wallet permission.
Why can a lender not redeem instantly?
Redemption depends on vault state, queue state, liquidity, tranche restrictions, and projected position state. A request can be accepted before a claim is available.
Why does Torq care about NAV?
Some assets need controlled valuation evidence. NAV reports and adapters help define what the system believes the asset value is, who reported it, whether it is fresh, and whether actions can proceed.
Why does Torq care about Live-Feed data?
Live-Feed data helps keep fast-changing market or price state current. If a feed is stale or unsafe, risk-increasing actions can be blocked.
Operators
What is Protocol Manager?
Protocol Manager is the control-plane workspace for global protocol inventory, roles, assets, asset issuers, NAV reporters, oracles, IRMs, markets, economics, risk, loss recovery, operations, audit, faucet, and incidents.
What is Asset Manager?
Asset Manager is the workspace for operating credit programs and related entity-scoped settings. It does not automatically mean global protocol power.
What is Incident Protection?
Incident Protection is a guided workspace for degraded, stale, emergency, or recovery states.
What is a timelock?
A timelock is a required delay before a sensitive operation can execute. It makes important changes observable before execution.
What does metadata-only mean?
Metadata-only means the action path updates persisted application data without requiring a wallet transaction by itself. It still needs permissions and post-write refresh.
Security and accounting
Why does Torq use a canonical read model?
Because valuation-sensitive credit action paths cannot depend on each screen reconstructing state in a different way. The product uses Chain -> Indexer -> Projector -> Postgres -> API -> Frontend.
Does the frontend read contracts directly?
For shared protocol truth, no. Live RPC is restricted to approved scopes such as balances, allowances, gas, simulation, pending transaction status, execution-time checks, and bounded preflight probes.
What is partition-local recovery?
It means a stressed borrower or market slice should be resolved inside its own accounting boundary instead of silently pushing losses into unrelated markets or vaults.
What happens if the indexer is down?
Product truth can become stale. Torq should show stale, pending, blocked, or degraded state instead of replacing it with a local guess.
What is the main accounting rule?
Value movements should reconcile through contracts, projectors, Postgres, API, and workspace state. The frontend should not invent accounting truth.
For reviewers
FAQ answers are backed by the route map, page surface registry, action registry, role catalogs, active V2 contract inventory, accounting inventory, and governance contract.