#night $NIGHT In the Midnight application ecosystem, if a privacy-protecting DApp needs to acquire off-chain data, this request action is no longer publicly triggered by the smart contract on-chain. Instead, the responsibility for data acquisition is transferred to the user's local client-side or the enterprise's own trusted execution environment. The specific engineering implementation path is as follows: The enterprise's local application directly queries the off-chain trusted oracle network through an encrypted API channel. The oracle returns the result to the enterprise's local setup, accompanied by a cryptographically valid digital signature to ensure the authenticity of the data.

Next, the most critical dimensionality reduction strike occurred. The enterprise's local device calls Midnight's underlying compiler engine, using this set of 'data with oracle signatures' along with the enterprise's own 'secret business logic' as input parameters, sending them into the local zero-knowledge proof circuit for computation. After the computation is completed, the enterprise only submits the final generated ZK proof to the Midnight mainnet. The consensus nodes of the mainnet are only responsible for verifying one thing: 'The submitter did indeed obtain the legally issued data from the oracle, and based on its internal logical operations, the current on-chain state transition request is legitimate.