-
Notifications
You must be signed in to change notification settings - Fork 5
docs revamp network #42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
474db04
f6817ef
f534971
0d25942
2339ecb
5576c4c
34266a8
c460708
2ab8a99
74ae567
046f976
957f97b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| # 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. | ||
|
|
||
| To get started with the coCircom workflow, we require some circuit alongside an input. Based on these files we can create a proof according the workflow depicted below. For more details the Circom setup have a look at the circom docs [extending the witness](https://docs.circom.io/getting-started/computing-the-witness/) and [generating a proof](https://docs.circom.io/getting-started/proving-circuits/). | ||
| To get started with the coCircom workflow, we require some circuit alongside an input. Based on these files we can create a proof according the workflow depicted below. For more details the Circom setup have a look at the circom docs [extending the witness](https://docs.circom.io/getting-started/computing-the-witness/) and [generating a proof](https://docs.circom.io/getting-started/proving-circuits/). | ||
|
|
||
| <img src={require("./figures/co-circom-workflow.png").default} alt="overview drawing"/> | ||
| <img src={require("./figures/co-circom-workflow.png").default} alt="overview drawing"/> | ||
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,143 @@ | ||
| --- | ||
| title: Privacy Services Overview | ||
| description: Choose the right privacy service for your application | ||
| --- | ||
|
|
||
| import Link from "@docusaurus/Link"; | ||
|
|
||
| # Privacy Services on TACEO Network | ||
|
|
||
| The TACEO Network provides production-ready privacy services that your application can integrate today. Each service handles different privacy-preserving computation needs. | ||
|
|
||
| ## Which Service Do I Need? | ||
|
|
||
| <div style={{display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(300px, 1fr))', gap: '2rem', marginTop: '2rem'}}> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. super nitpicky but it irks me a bit that the learn more buttons are not aligned :D |
||
|
|
||
| <div className="service-card-success"> | ||
|
|
||
| ### **TACEO\:OPRF** | ||
|
|
||
| _Oblivious Pseudorandom Function_ | ||
|
|
||
| **Use when you need:** | ||
|
|
||
| - Privacy-preserving uniqueness checks | ||
| - Generate nullifiers without revealing identity | ||
| - Private set membership checks (e.g. PSI-style protocols) | ||
| - Identity-based rate limiting or eligibility checks | ||
|
|
||
| **Perfect for:** | ||
|
|
||
| - Biometric identity and uniqueness verification | ||
| - Anonymous credentials and pseudonymous identities | ||
| - Builder codes and private access / eligibility systems | ||
| - Identity-based rate limiting | ||
|
|
||
| {/* prettier-ignore */} | ||
| <Link className="button button--success get-in-touch-btn" to="/docs/taceo-oprf/overview" style={{ marginTop: "1rem", width: "100%" }}>Learn More</Link> | ||
|
|
||
| </div> | ||
|
|
||
| <div className="service-card-primary"> | ||
|
|
||
| ### **TACEO\:Proof** | ||
|
|
||
| _Private Proof Delegation_ | ||
|
|
||
| **Use when you need:** | ||
|
|
||
| - Generate ZK proofs without revealing witness data | ||
| - Scale proof generation beyond client devices | ||
| - Mobile/web app proof generation | ||
| - Production-ready Groth16 proofs | ||
|
|
||
| **Perfect for:** | ||
|
|
||
| - DeFi applications with private transactions | ||
| - Identity systems requiring proof of credentials | ||
| - Gaming with hidden state verification | ||
| - Any app needing scalable ZK proofs | ||
|
|
||
| {/* prettier-ignore */} | ||
| <Link className="button button--primary get-in-touch-btn" to="/docs/taceo-proof/overview" style={{ marginTop: "1rem", width: "100%" }}>Learn More</Link> | ||
|
|
||
| </div> | ||
|
|
||
| </div> | ||
|
|
||
| ## Coming Soon | ||
|
|
||
| <div style={{display: 'grid', gridTemplateColumns: 'repeat(auto-fit, minmax(300px, 1fr))', gap: '2rem', marginTop: '2rem'}}> | ||
|
|
||
| <div className="service-card-muted"> | ||
|
|
||
| ### **TACEO\:OMap** | ||
|
|
||
| _Private Reads & Writes_ | ||
|
|
||
| **Deployed, onboarding first applications** | ||
|
|
||
| Private data structures and confidential shared state management across multiple parties. | ||
|
|
||
| </div> | ||
|
|
||
| <div style={{ | ||
| padding: '2rem', | ||
| border: '1px solid var(--ifm-color-emphasis-400)', | ||
| borderRadius: '12px', | ||
| backgroundColor: 'var(--ifm-color-emphasis-100)', | ||
| opacity: '0.8' | ||
| }}> | ||
|
|
||
| ### **TACEO\:Match** | ||
|
|
||
| _Distributed Biometric Uniqueness_ | ||
|
|
||
| **In active integration** | ||
|
|
||
| Privacy-preserving biometric matching and verification without centralized biometric storage. | ||
|
|
||
| </div> | ||
|
|
||
| </div> | ||
|
|
||
| ## Integration Patterns | ||
|
|
||
| ### **Direct API Integration** | ||
|
|
||
| TODO | ||
|
|
||
| ### **Smart Contract Integration** | ||
|
|
||
| TODO | ||
|
|
||
| ## Getting Started | ||
|
|
||
| <div className="getting-started-box"> | ||
|
|
||
| ### 🚀 **Ready to integrate?** | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: blue ist not really our collor right? |
||
|
|
||
| 1. **Choose your service** from the options above | ||
| 2. **Read the service documentation** for technical details | ||
| 3. **Try the quickstart** to see it in action | ||
| 4. **Contact us** for production access and support | ||
|
|
||
| {/* prettier-ignore */} | ||
| <div className="button-row"> | ||
| <Link className="button button--info button--lg get-in-touch-btn" to="mailto:hello@taceo.io">Get Production Access</Link> | ||
| <Link className="button button--outline button--info get-in-touch-btn" to="https://taceo.io/discord">Join Discord Community</Link> | ||
| </div> | ||
|
|
||
| </div> | ||
|
|
||
| ## Production Applications | ||
|
|
||
| The TACEO Network already powers privacy infrastructure for: | ||
|
|
||
| - **World** - Biometric identity verification at global scale | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just to be sure, we are happy with disclosing world and zkPassport? Also I thought biometric identity should not be in here for world? |
||
| - **zkPassport** - Privacy-preserving identity verification | ||
| - And growing ecosystem of privacy-focused applications | ||
|
|
||
| --- | ||
|
|
||
| Need help choosing the right service? [Join our Discord](https://taceo.io/discord) or [email our team](mailto:hello@taceo.io). | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...MPC. Circom and coCircom....