Frequently Asked Questions

Yes. Neti can integrate blockchain and digital asset infrastructure with an existing core banking system without requiring the institution to replace a platform that already supports critical financial operations. The existing core can remain the system of record, while new blockchain, settlement, custody, compliance, or payment components are connected around it. We begin by assessing the current architecture, APIs, data flows, transaction lifecycle, reporting requirements, and integration constraints. Based on this analysis, we define which responsibilities should remain in the core banking system and which should be handled by additional components. Integration may use APIs, event-driven communication, messaging infrastructure, or a dedicated orchestration layer. We also define how transaction states, balances, reconciliation, exceptions, and audit records remain synchronized across the connected systems. Where possible, Neti recommends a phased integration rather than a high-risk replacement of the entire infrastructure. The objective is to add new capabilities while preserving operational continuity, regulatory controls, and the systems that already work.

No. In many cases, blockchain can be introduced as an additional layer connected to existing systems rather than as a full replacement. Neti helps define which processes should remain in the current infrastructure, which can benefit from blockchain, and how both environments should exchange data and transaction states. Depending on the architecture, integration may use APIs, event-driven communication, or an orchestration layer. Where possible, we recommend a phased approach that adds new capabilities while preserving operational continuity and systems that already work.

Yes. Neti can integrate blockchain infrastructure with legacy, proprietary, and highly customized systems, provided their interfaces, dependencies, and operational constraints are understood first. We begin with a technical assessment of the existing architecture, available APIs, data flows, documentation, and business-critical processes. Where direct integration is not practical, we may recommend an adapter, event-driven integration, or dedicated orchestration layer. Our goal is to introduce new capabilities without disrupting systems that already support essential operations. When possible, we use a phased approach that limits risk and allows each integration stage to be tested before wider deployment.

Yes. Neti can modernize blockchain and backend infrastructure incrementally, without replacing the entire system at once. We can introduce new components alongside existing platforms, migrate selected workflows in stages, and use APIs, adapters, or interoperability layers to maintain continuity during the transition. This reduces operational risk, limits downtime, and allows each stage to be validated before the next one begins.

Yes. Neti can work with partially documented or undocumented systems. We begin by mapping the existing architecture, dependencies, data flows, integrations, and operational constraints through code review, stakeholder interviews, and system analysis. This allows us to identify risks, document the current state, and plan modernization or integration without relying on assumptions.

Yes. Blockchain infrastructure can be introduced as an additional layer around your existing core banking system rather than replacing it. Neti can connect blockchain-based settlement, asset, or verification components through APIs, adapters, and integration services while the core system continues to manage accounts, customer records, and internal operations. This supports phased implementation, limits disruption, and avoids a high-risk big-bang migration.

A standard ledger is transparent; anyone can see address balances and transaction paths. The Invisible Ledger uses shielded transactions where the data is transformed into cryptographic commitments. The "correctness" of the ledger is verified by math (ZK-proofs) rather than public inspection.

The nullifier acts as a unique fingerprint for a spent note. It allows the smart contract to prevent double-spending without ever knowing which specific commitment (note) in the Merkle tree was accessed. It provides a secure way to prove I have funds and have spent them, without revealing my account history.

No. As an L1 application, it runs directly on existing transparent chains (like Ethereum). It creates a "private room" within the public house, where institutional capital can move without surveillance while retaining the security of the underlying network.

In a shielded model, we don't delete data because that would reveal which note was used. Instead, we always add new commitments. This keeps the global state auditable at the root level without leaking the contents of the individual leaves.

We use a Secure Mint architecture with Chainlink PoR. The smart contract only mints tokens after the Oracle verifies the bar's metadata in the VMS.

1:1 stability = MiCA. Yield-bearing = MiFID II. Neti helps you choose the right technical standard (ERC-20 vs. ERC-3643) for either path.

ERC-20 lacks built-in compliance. ERC-3643 (T-REX) embeds an ONCHAINID layer, validating every transfer against KYC/AML rules in real-time.

Can I get physical gold back?

With our modular infrastructure, we can deploy a functional MVP in 3 to 5 months.