Multisig accounts API

Sep 19, 2014 • 已阅读 1 分钟

Today we’re announcing a new developer tool in beta: our multi-sig API.

We’re still working on a great consumer interface around this, but for today we’re releasing it to developers only.

Does this put me in control of my Bitcoin?

Yes. When you go and create a multisig account, you provide the extended (BIP32) public keys, which only enable us to create new receive addresses for your convenience. Only you have the extended private keys that can sign transactions and move bitcoin out of these addresses.

How to use

Learn how to use the new API in this tutorial.

Multisig accounts are considered an advanced feature and our API is currently in beta, so only use small amounts of bitcoin for the moment.

最新报道

Part 3/3 Owning Intelligence Series: How Coinbase Built, Evaluated, and Post-Trained a Fraud Agent

Yao Ma, Xuwei Tan, Akshit Trehan, Aman Choudhary, Anyscale Team: Eric Tang, Sumanth Hegde, Seiji Eicher, Jess Kong

Oct 8, 2026

TL;DR: Using SkyRL on Anyscale, we post-trained Qwen3.5-9B for Onramp fraud detection and served it with Ray Serve LLM and vLLM. On our benchmark, it exceeded Opus 4.5 across all four detection metrics, including 9.6% higher F1. In online inference, we reduced end to end latency by 55%.

Engineering

Part 2/3 Owning Intelligence Series: How Coinbase Built, Evaluated, and Post-Trained a Fraud Agent

Yao Ma, Xuwei Tan

Oct 7, 2026

TL;DR: Newer LLMs are not necessarily better at domain-specific tasks. On our fraud benchmark, newer Opus, Sonnet, and GPT versions all had lower recall, F1, and dollar-weighted recall—even when precision improved. The lesson: choose models using high-quality, domain-specific benchmarks, with reproducible evaluation and ideally deterministic scoring against verified outcomes. These findings also motivated our next step: post-training open-weight models for greater control over quality, cost, and deployment.

Engineering

Migrating 300+ namespaces from self-hosted Temporal to Temporal Cloud

Ian Yap

Oct 1, 2026

TL;DR: We moved more than 300 Temporal namespaces, across more than 300 services, from a cluster we ran ourselves onto Temporal Cloud. You cannot finish the move by repointing services at Temporal Cloud while workflows are still running on the old one. Where teams could pause new work, we waited for in-flight runs to finish and then switched; for trading, payments, and long-running work, we ran the old cluster and Temporal Cloud, and moved new workflows over in steps, with rollback as a config change. Private connectivity, per-namespace service allowlists, and encrypted payloads were in place before the first production namespace moved.

Engineering

免责声明：Coinbase Advanced 平台上的衍生品交易由 Coinbase Financial Services Europe Ltd.（CySEC 许可证 374/19）向符合条件的欧洲经济区（EEA）客户提供。要参与衍生品交易，客户须通过我们的标准评估，以确认其是否具备使用该产品的资格，以及该产品是否适合该客户。

Multisig accounts API

Does this put me in control of my Bitcoin?

How to use

最新报道

Part 3/3 Owning Intelligence Series: How Coinbase Built, Evaluated, and Post-Trained a Fraud Agent

Coinbase and Samsung Bring USDC to Samsung Wallet

Part 2/3 Owning Intelligence Series: How Coinbase Built, Evaluated, and Post-Trained a Fraud Agent

Coinbase 正在打造更全面的交易平台

Part 1/3 Owning Intelligence Series: How Coinbase Built, Evaluated, and Post-Trained a Fraud Agent

Migrating 300+ namespaces from self-hosted Temporal to Temporal Cloud