Opening IdentaFi…Opening IdentaFi…Opening IdentaFi…Know what is controlled, trusted and still unverified.
Private keys remain in the user’s wallet. IdentaFi does not request a seed phrase, export a private key or derive account keys on a server. Connecting requests only a public address and readable network information.
Drafts and sealed receipt previews live in browser storage. Anyone with access to that browser profile may access them. Clearing site data removes them. Downloaded receipts contain the information needed to inspect the local preview.
No completed audit or production contract deployment is claimed. An interface, parameter table or mathematical model does not prove that a future contract enforces its promises.
Production review must cover ownership, upgradeability, oracle trust, vault accounting, liquidation losses, batch settlement, operator limits and route permanence.
A frontend should never mark a transaction complete until it is confirmed on the intended network. A connection should never be presented as a deposit or permission to trade. Failed data requests should remain visible instead of being replaced with fabricated live metrics.