This page documents production updates to Multi-party Compute. Check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.
You can see the latest product updates for all of Google Cloud on the Google Cloud page, browse and filter all release notes in the Google Cloud console, or programmatically access release notes in BigQuery.
October 15, 2026
Workforce Identity Federation (BYOID): You can now authenticate to the Multi-party Compute API with identities from your organization's external identity provider, such as Okta or Microsoft Entra ID, using Workforce Identity Federation and Workload Identity Federation. For setup steps, see Configure Workforce Identity Federation (BYOID).
Pagination for ListKeyRings and ListParticipants: KeyRingService.ListKeyRings and ParticipantService.ListParticipants now support pagination with page_size and page_token. Responses return up to 100 results by default, and you can set page_size to request up to 1,000. When more results are available, the response includes a next_page_token that you pass as page_token to get the next page.
October 01, 2026
Schnorr Signatures for Curve25519: Added support for generating distributed Schnorr signatures using Curve25519 keys with standard Ed25519 (RFC 8032) challenge hashing for multi-party transaction signing.
Extended Participant and Approver ID Limits: Increased character limits for external participant IDs (external_participant_id) and policy approver governance entity IDs (governance_entity_id) to 4,096 characters, enabling full Workforce Identity Federation and Workload Identity Federation principal URIs in API requests, Cedar policies, and JWS intent tokens.
Assent Signature Validation Error Code: Updated RecordParticipantDecision in ProposalService to return INVALID_ARGUMENT instead of PERMISSION_DENIED when a participant's cryptographic assent or dissent signature fails verification.
Bitcoin Policy Engine Rules: Enhanced Bitcoin policy evaluation in the Policy Engine. Cedar rules for Bitcoin transactions now support normalized spending amounts (spend_amount_scaled), automated change output detection, destination address classification (such as SegWit and Taproot), and OP_RETURN data transactions.
August 20, 2026
API Validations & Stability: Enhanced API request validation for AuthorizePayload, UpdatePolicyAuthorTrustBundle, and quorum thresholds. Resolved a cache synchronization bug during policy activation.
Dissent Signature Payload Update: Dissent signatures for the RecordParticipantDecision API must now be generated over the SHA-256 hash of the Proposal ID instead of the raw transaction digest. Assent signatures remain unchanged.
Curve25519 Support: Added support for the Curve25519 elliptic curve for distributed key generation and signing.
Ethereum V2 Schema: Introduced the ETHEREUM_TX_V2 schema for the Policy Engine to normalize EVM transaction data into a protocol-agnostic format.
Ethereum Wallet Address Exposure: The MPC API now automatically exposes the derived Ethereum wallet address for distributed keys generated with the ECDSA_SECP256K1 algorithm.
Policy Engine Bitcoin Support (Preview): You can now authorize Bitcoin payloads using the BITCOIN_TX_V2 schema. This includes parsing for Partially Signed Bitcoin Transactions (PSBT v0, BIP-174) and native Bitcoin address extraction.