Opaque identity references

Identity anchors

Every deal reserves four bytes32 identity references—buyer, seller, verifier and arbitrator—and signs them into the seller acceptance.

What an anchor means

Sinetti consumes identity rather than issuing it. Each reference is an opaque bytes32 value recording what the parties agreed stood behind a role at deal time. The escrow stores and emits it and never checks it against the caller address.

The published source defines no derivation rule. How a reference is built from an external identity, and what assurance it carries, is a convention the integrator chooses and documents off-chain. An unresolved role uses bytes32(0).

What it does not prove

• It is a commitment, not a confidential value.
• It does not prove that the address using the role controls the referenced identity.
• ERC-8004 anchoring is deferred; no registration binding is implemented.
• It cannot populate itself; a deal-opening surface still needs to write it.