Skip to content

Conversation

JoeZYXStateLabs
Copy link

This PR adds three vendor entries from State Labs to the Ethereum Foundation's Institutional Privacy Mapping.


1. Tx-Shield (Private Payments)

  • Tech: High Performance MPC; Audit-Key Protocol
  • Use case: Confidential settlement of stablecoins, RWAs, and bonds on-chain.
    Transactions are visible only to stakeholders, while regulators can access details through granted audit keys.
    Ensures institutional privacy and compliance with high-performance (~10k TPS) MPC execution.

2. OpenTMP LLM (Collaborative Private AI)

  • Tech: MPC-FL; Distributed Learning; Edge AI Acceleration; SFT; RLHF
  • Use case: Efficient, secure, and privacy-preserving large-model training and inference across distributed environments.
    Combines federated learning and MPC-FL to keep data local while performing encrypted aggregation and joint model updates.

3. Collab-Key (MPC-TSS Key Management)

  • Tech: MPC; TSS (ECDSA 2PC / multi-party); Threshold Signatures
  • Use case: Distributed ECDSA signing for institutional wallets and custody.
    Eliminates single-party key reconstruction and integrates with KMS for fast, production-grade signing.
    Built upon our team’s peer-reviewed research presented at USENIX Security 2025, combining academic rigor with real-world performance.

Each entry represents a key component of State Labs’ privacy-preserving infrastructure—covering payments (Private Payments), AI collaboration (Private Collaborative AI), and key management (Collab-Key) — aligned with IPTF’s institutional privacy domains.

Adds State Labs’ OpenTMP LLM to the vendor map under the Collaborative AI / Federated Learning privacy domain.
- Tech: MPC-FL with threshold-secure aggregation
- Scope: privacy-preserving training & inference with data locality
- Modules: Private / Efficient / Governable LLM
Adds State Labs’ Collab-Key to the vendor map under the Custody / Key Management domain.
- Tech: MPC-TSS for distributed ECDSA signing (2PC & multi-party)
- Problem: eliminates single-point key compromise
- Integrates with KMS; production-grade throughput
This PR adds State Labs to the vendor map under the Private Payments domain.

- Product: Tx Shield — regulator-auditable private payment layer
- Tech: MPC-based encryption + threshold key control (TSS)
- Use cases: confidential settlement for stablecoins, RWAs, bonds
- Performance: ~10k TPS via optimized MPC execution
@Meyanis95
Copy link
Collaborator

Hi @JoeZYXStateLabs
Thanks for your contribution! Could you please consolidate all three into a single vendor card? We try to keep one card per vendor for consistency.

@JoeZYXStateLabs
Copy link
Author

Hi @JoeZYXStateLabs Thanks for your contribution! Could you please consolidate all three into a single vendor card? We try to keep one card per vendor for consistency.

Thank you for your prompt reply!
Updated as requested — all three solutions (Tx-Shield, OpenTMP LLM, and Collab-Key) have now been consolidated into a single vendor card.

Copy link
Collaborator

@oskarth oskarth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution! Left some comments, but overall looks good as a first entry to me

# State Labs – Privacy-Preserving Infrastructure

State Labs develops regulared privacy-preserving infrastructure for institutional payments (Tx-Shields), Private AI collaboration (OpenTMP LLM), and MPC-TSS Key Management (Collab-Key).
Our three core solutions — **Tx-Shield**, **OpenTMP LLM**, and **Collab-Key** — address compliance, compute, and custody privacy challenges for regulated institutions.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we rewrite this in third person? E.g. State Labs having three core offerings etc

(Our is ambigous for most consumers)


## Fits with patterns (names only)

Tx-Shield:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you see some patterns in patterns folder that seems relevant, feel free to link to them from here :)

State Labs builds modular privacy layers/solutions for institutional finance and AI systems:
- **Tx Shield** — a regulated private payment layer/solution built on MPC-based encryption and threshold key control.
It enables confidential settlement for stablecoins, RWAs, and bonds while ensuring regulator-auditable transparency.
Transactions are visible only to stakeholders, while regulators can access details through granted audit keys.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in this part, can you pls clarify how an investor is KYCed? and how asset issuance is done?

It enables confidential settlement for stablecoins, RWAs, and bonds while ensuring regulator-auditable transparency.
Transactions are visible only to stakeholders, while regulators can access details through granted audit keys.

- **OpenTMP LLM** — is a distributed edge AI training and inference framework designed for privacy-preserving large-language model collaboration. It combines federated learning and multi-party computation (MPC-FL) to keep data local while enabling encrypted aggregation and joint model updates. It powers collaborative, effcient, secure, and governable AI training across distributed environments.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do we map this to institutional privacy? is this a new feature for institutions?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and how does this interact with Ethereum L1?


- **Collab-Key** — is a high-performance MPC-TSS framework supporting both two-party and multi-party ECDSA signing.
It ensures that no single participant ever reconstructs a full private key, providing cryptographic resilience and institutional-grade security.
The system integrates seamlessly with existing KMS and client applications for fast, production-grade signing.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this MPC-TSS for Bank, Investor, or for Regulator and how to incorporate it?

It ensures that no single participant ever reconstructs a full private key, providing cryptographic resilience and institutional-grade security.
The system integrates seamlessly with existing KMS and client applications for fast, production-grade signing.

Each module can operate independently or as part of a unified privacy-preserving stack across payments, compute, and custody.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you pls add an example of how do you stack them together?

- Custody / Key Management
- Threshold Signatures
- Distributed Signing Infrastructure

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section is a bit too general and does not add much information what has been in the introduction, can you pls elaborate?

## Not a substitute for

Tx-Shield:
- Non-compliant on-chain transfer systems
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what you mean here, but non-compliant on-chain system is not among the institutional usecases


## Architecture
### Tx-Shield
Implements a high performance MPC-based private payment layer with threshold key control and an audit-key protocol for regulator visibility.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this technically a network? or a centrally controlled 2-3 nodes cluster?


### OpenTMP LLM
Distributed AI architecture using federated learning and multi-party computation (MPC-FL) with threshold-secure aggregation.
Supports edge acceleration, model distillation, quantization, and joint model governance.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the concrete efficiency can we expect here?

Supports edge acceleration, model distillation, quantization, and joint model governance.

### Collab-Key
MPC-TSS signing system supporting both 2PC and multi-party ECDSA protocols.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the current scheme and library you are using here?

- Backed by peer-reviewed research from *USENIX Security 2025*
1. *Improved Secure Two-party Computation from a Geometric Perspective* (USENIX Security 2025)
2. *Achilles: A Formal Framework of Leaking Secrets from Signature Schemes via Rowhammer* (USENIX Security 2025, Honorable Mentions)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is quite repetitive to above sections as well

## Risks and open questions
Tx-Shield:
- Governance over regulator audit keys
- Integration complexity across different blockchain environments
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you pls be more specific with this intergration complexity?

---

## Links
Website: [https://statelabs.ai](https://statelabs.ai)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is your solution open-sourced? The GH https://github.com/StateLabs does not have a public repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants