0x7160357e7160…71603581
Midnight Moves Zero-Knowledge Proofs to Google Cloud TEE
Midnight Foundation and BCW LLC moved zero-knowledge proof generation into Google Cloud Confidential Space in two months, clearing the way for Lace wallet integration.

Outputs
The Midnight Foundation and BCW LLC moved proof generation to Google Cloud Confidential Space; the service went live in two months.
Local proof generation can take tens of seconds and drain a user's battery, according to a Google Cloud case study.
The proof service runs in a trusted execution environment designed so the operator cannot see the underlying data.
Lace's only currently supported proof-server option is local, with setup guides instructing users to install Docker.
The live Google Cloud service cleared the way for Lace wallet integration.
The Midnight Foundation and BCW LLC moved zero-knowledge proof generation into Google Cloud Confidential Space in a service that went live in two months, according to a Google Cloud case study. Proof computation now runs inside a trusted execution environment, or TEE, in Google's cloud.
Private transactions on the Midnight Network ($NIGHT) rely on zero-knowledge proofs. Generating one on a user's own device can take tens of seconds and drain the battery, according to the case study. The deployment moves that compute task from the user's device into Google's cloud.
What problem did Lace users face?
Before the move, Lace users typically had to run a proof server themselves. Midnight's developer documentation says: “a proof server is required to generate zero-knowledge proofs for transactions.” The same documentation describes the local proof server as “currently the only option supported within Lace.”
Setup guides instruct users to install Docker to run that server. Midnight characterizes the work as manageable for developers but a barrier for ordinary users, especially on phones. The supported configuration therefore required a local software stack even though Midnight's private transactions depend on proof generation.
How does the Google Cloud deployment work?
Google Cloud Confidential Space gives the project a remote location for proof generation while retaining the stated data-visibility boundary. The TEE is “designed so the operator cannot see the underlying data.” This separates Google's infrastructure role from access to the information used in the computation.
The deployment went live in two months and cleared the way for the Lace wallet integration. If Lace makes the service available to users, proof generation remains required while the customer-facing setup changes from running a local server to relying on a cloud-backed service. The case study does not provide a broader rollout date.
What changed in the operating model?
The two-month build is the clearest delivery metric in the source. It covers work by Midnight Foundation and BCW LLC to move the proof workload from a user-operated model into a TEE within Google's cloud. The former model left Lace users responsible for hosting the proof server; the new service places that function in the deployed environment.
That change targets the device burden recorded in the Google Cloud study. A proof that previously consumed tens of seconds and battery power on a user's device can run in the remote TEE instead. The source does not report post-deployment proof-generation times, costs, service levels, or supported-device requirements, so those operating figures remain unquantified.
The implementation separates Midnight's proof requirement from Lace's delivery mechanism. The former remains in place. The latter gains a possible cloud option after the two-month build, with the wallet's supported configuration still described as local-only in the cited documentation.
Confidential Space's role is narrower than the wallet integration itself. The case study names Google Cloud as the cloud provider, while the implementation involved Midnight Foundation and BCW LLC. The disclosed outcome is a live proof-generation service and a path to Lace integration; the source describes no change to Midnight's proof protocol or $NIGHT token.
The next structural checkpoint is whether Lace can add the Google Cloud TEE service as a supported alternative to its Docker-based local proof server. Until users receive that integration, the source supports a completed cloud deployment, not a completed end-user migration.
via cryptonews.net (Source)
More from Tom Whitfield
Show full bio
News editor covering technology and product news in crypto and web3 industry at Mempool Brief.
1,374 articles