Home · Learn · Custody

The default key is not a user-held shard

How the default service key is split, who holds the shares today, and what is on the roadmap.

The threshold

The default service key is generated under a 2-of-3 threshold. All three shares are created and held server-side by JIL, and signing reconstructs the key in memory. JIL holds the key shares for the default key. A user does not hold a shard on that key. JIL can sign with that key. This is not self-custody in the "you hold the only key" sense.

Custody status

Live: the 2-of-3 default service key described above. Designed: threshold signing of the FROST or GG20 class, where the key is never reconstructed, and a hardware security module for validator keys. Until threshold signing ships, compromise of the signing host is compromise of that key. Who holds every other key in the system is on the control and custody page.

In practice

  • JIL holds the key shares for the default key. A user does not hold a shard on that key. JIL can sign with that key.
  • All three shares of the default key are held server-side by JIL today
  • Target 72-hour operational rotation in production configurations
  • Works alongside hardware wallets, does not replace them

Questions people actually ask

Is this self-custody?

No. JIL holds the key shares for the default key. A user does not hold a shard on that key. JIL can sign with that key.

What if one share is lost?

The key is recovered from the two remaining shares, which meet the threshold, and a new share set is issued. There is no 12-word backup string.

Keep reading

The white paper and a briefing are the next step if you are evaluating a domain.