Goldfinch

Internal linkages

  • Named operator boundary for UID signing, Goldfinch Council representation, and core-development gravity: warbler-labs.
  • Keep the note on the strongest branch contrasts: wildcat, 3jane, and compound.
  • Wildcat is the borrower-authored-market contrast; 3Jane is the protocol-underwriter contrast; Compound is the clean pooled-money-market baseline.

Protocol / company boundary

  • Keep this note on the mechanism layer: borrower-specific pools, junior-versus-senior tranche subordination, Backer signaling, auditor checks, governance powers, and the broader trust through consensus design.
  • Use warbler-labs when the sharper question is who currently sits in the UID trusted-signer lane, occupies multiple seats on the Goldfinch Council, and carries the named core-development / token-allocation boundary the docs still surface explicitly.
  • That split matters because how does Goldfinch route credit risk? and which named organization still occupies identity and governance-adjacent defaults around that protocol? are related but not identical questions.

Control surface

  • Goldfinch’s formal control surfaces still include governance upgrades and parameters, approved identity-provider policy, offchain servicing, and the tranche design that routes loss and underwriting incentives.

  • But some practical leverage now points upward to warbler-labs because the current UID signer and part of the governance-execution shell are still organization-shaped rather than purely protocol-shaped.

  • Last reviewed: 2026-08-12 UTC