CORELOTOpen dashboard →Private inputs. Visible resource costs.
Resource accounting and application content should be separate. The animations illustrate this design direction, not a deployed protocol.
01 · Workload boundary
Prompts, files, outputs and secrets belong to the application privacy boundary. A production design must define access permissions and storage lifetimes.
02 · Resource accounting
GPU time, energy and scheduling metrics could support billing without publishing application content. The interface generates synthetic values; it does not read real meters.
03 · Solana settlement
Solana and USDC are the planned coordination and payment layer. Ordinary on-chain payments are public. Confidential payments require an additional implemented and verified mechanism.
04 · Confidential execution
MPC, FHE and trusted execution environments are possible approaches, not existing CORELOT integrations. No cryptographic privacy guarantee is offered by the current interface.