Conversation
Deploying taceo-stage-docs with
|
| Latest commit: |
957f97b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d93ac3c1.taceo-stage-docs.pages.dev |
| Branch Preview URL: | https://network-docs.taceo-stage-docs.pages.dev |
| # coCircom | ||
|
|
||
| coCircom enables us perform [circom](../resources/circom)'s witness extension and proof generation with MPC. circom and coCircom and their artifacts may be used interchangeably, e.g. a proof generated by coCircom verifies using circom and vice-versa. coCircom also relies on artifacts generated by circom, e.g. the R1CS file, the zkey, and the vkey. | ||
| coCircom enables us perform [circom](https://docs.circom.io/)'s witness extension and proof generation with MPC. circom and coCircom and their artifacts may be used interchangeably, e.g. a proof generated by coCircom verifies using circom and vice-versa. coCircom also relies on artifacts generated by circom, e.g. the R1CS file, the zkey, and the vkey. |
There was a problem hiding this comment.
...MPC. Circom and coCircom....
|
|
||
| ## Which Service Do I Need? | ||
|
|
||
| <div style={{display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(300px, 1fr))', gap: '2rem', marginTop: '2rem'}}> |
There was a problem hiding this comment.
super nitpicky but it irks me a bit that the learn more buttons are not aligned :D
|
|
||
| The TACEO Network already powers privacy infrastructure for: | ||
|
|
||
| - **World** - Biometric identity verification at global scale |
There was a problem hiding this comment.
Just to be sure, we are happy with disclosing world and zkPassport? Also I thought biometric identity should not be in here for world?
Maybe better to highlight OPRF?
|
|
||
| <div className="getting-started-box"> | ||
|
|
||
| ### 🚀 **Ready to integrate?** |
There was a problem hiding this comment.
nit: blue ist not really our collor right?
generally we break a bit with the color scheme here dont know if it is fine just wanted to highlight that
|
|
||
| It encrypts and distributes sensitive computation across independent node operators so that no single party controls the data, the keys, or the outcome. | ||
|
|
||
| The cryptographic infrastructure behind the network has been deployed in production systems used in World ID, supporting identity verification for more than 18 million users. |
|
|
||
| The cryptographic infrastructure behind the network has been deployed in production systems used in World ID, supporting identity verification for more than 18 million users. | ||
|
|
||
| Applications integrate privacy services through APIs. Under the hood, those services route confidential requests to MPC node committees that compute over encrypted shares and return verifiable outputs. |
| Each request follows the same high-level flow: | ||
|
|
||
| 1. **Application request** | ||
| An application sends a request through a TACEO service API, for example proof generation, private verification, or private state updates. |
| The request is routed to a specific service instance. Each instance has its own cryptographic keys, committee configuration, and operational policy. | ||
|
|
||
| 3. **Distributed MPC execution** | ||
| The selected committee executes the protocol over encrypted or secret-shared inputs. No single node can reconstruct the full private input by itself. |
There was a problem hiding this comment.
over encrpyted ... inputs seems like we do FHE
|
|
||
| Only the requested result is revealed. The underlying inputs remain confidential throughout execution. | ||
|
|
||
| ## How the Network Works |
There was a problem hiding this comment.
I mean this is more a "How the Network might work in the future".
There was a problem hiding this comment.
but I don't know if that sounds as nice
No description provided.