Connection And Addresses
The console opens on the published Sepolia deployment and lets reviewers override any address if they want to point at a local or replacement deployment.
This interface is built for judges and developers who want to see the full flow: employee onboarding, confidential payroll runs, equity attestations, and verifiable payslips, all without putting salary balances in public view.
The console opens on the published Sepolia deployment and lets reviewers override any address if they want to point at a local or replacement deployment.
Requests that depend on the Zama gateway move through the same four stages. Transactions settle first, then the encrypted proof waits for the asynchronous callback that reveals only the requested boolean or salary value.
{{ item.txHash }}{{ item.requestId }}The contract expects the salary handle and proof generated by `fhevm-js`. This keeps the UI production-aligned instead of sneaking plaintext into an admin form.
Trigger the encrypted payroll path directly from the UI. This keeps the demo simple for judges while still exercising the same contract entrypoint used by the scripts.
Request one of the expanded claim types, including department-average and gender-pay-gap checks, without exposing the employee's salary.
Generate a verifier-specific proof without disclosing the exact salary. This is the flow that tends to land well with banks, landlords, and compliance reviewers.
Enter a token ID and read the verifier-safe metadata returned by the payslip contract.