Co-signer

In cryptocurrency, a co-signer is a participant that contributes a cryptographic signature toward authorizing a transaction, commonly through a multisignature wallet. The wallet's authorization policy determines which signatures are accepted and how many are required. This meaning concerns transaction approval, not responsibility for another person's loan.

How Co-Signing Works

A multisignature arrangement recognizes several signing keys and applies a preset signature requirement, often called a threshold. A co-signer uses a private key to sign a proposed transaction. Others can verify the signature without seeing that private key, so participants do not need to reveal their private keys to one another. The transaction must meet the signing requirement and the underlying system's other validity rules before it can be accepted.

In a hypothetical 2-of-3 arrangement, signatures from any two of three authorized keys satisfy the signing policy. The third signature is unnecessary: approval does not imply unanimous consent. One signature alone cannot meet this threshold. Supported policies depend on the wallet and underlying system; not every setup permits every combination of signatures.

Signing Keys and Participants

Signing keys and people are not interchangeable. One co-signer may control several authorized keys across different devices, or each key may belong to a different participant. The policy counts signatures from authorized keys, not distinct people. If one owner controls enough keys to meet the threshold, that owner can authorize spending without anyone else's participation.

Distributing keys among participants so that no one holds enough to meet the threshold can instead require cooperation. A valid signature demonstrates authorization by a key; it does not by itself identify who operated that key or establish organizational accountability.

Security and Availability

Requiring multiple independently protected keys can prevent one compromised key from being sufficient to spend funds. This benefit depends on the threshold and whether an attacker can access enough other keys. Several keys exposed through the same vulnerable access path offer less separation than their number suggests. Adding a co-signer therefore does not guarantee protection against unauthorized spending.

The tradeoff is availability: too few usable keys or willing signers can block spending. In the hypothetical 2-of-3 arrangement, losing access to one key leaves two available, while losing access to two leaves the threshold unmet. A lost device does not necessarily mean a permanently lost key if a usable backup exists. Recovery depends on the remaining keys, backups, and any recovery arrangements supported by the setup; co-signing alone does not bypass an unmet signing requirement.

Personal and Organizational Uses

For a personal wallet, one owner may use separate devices to hold different keys. This can separate access paths without creating multiple independent decision-makers. An organization may instead assign keys to different participants so that a proposed payment requires cooperation. The wallet policy enforces the configured signature threshold, while internal procedures determine who should approve a payment and for what purpose.

Each signer still needs to understand the transaction being approved, including its destination and requested action. Several valid signatures on the same mistaken or deceptive transaction do not make its outcome safe. Shared control changes how authorization is obtained; it does not replace transaction review or establish that every stakeholder consented.