Optional On-Chain Operational Model Signal for Universal Profiles

[Iledesignia]

Context
This post is intended to open an exploratory discussion prior to drafting any formal LIP.
The objective is to evaluate whether introducing a minimal, optional signal that allows a Universal Profile to declare its operational model, readable directly on-chain, would provide meaningful value.
This is not related to identity verification.
It does not introduce compliance logic.
It does not modify base contract behavior.
It does not introduce enforcement mechanisms.
It is purely a semantic signal intended for programmatic interpretation.

---

Motivation
Universal Profiles may represent different operational realities, including:

• Self-sovereign individuals

• Custodial systems

• Autonomous agents

• Subagents

• DAOs

• Corporate entities

Currently, LSP3-ProfileMetadata allows semantic distinctions through tags and descriptive fields.
However, such metadata is often stored off-chain (e.g., on IPFS), meaning it is not directly readable on-chain without resolving external URIs.
In contexts where the following may be relevant:
Deterministic interpretation directly on-chain
Contract-to-contract automation logic
Signaling without reliance on off-chain resolution
there may be practical limitations.
This discussion explores whether storing a minimal signal directly via ERC725Y could complement (not replace) LSP3 in scenarios where direct on-chain readability is beneficial.

---

Proposed Minimal Scope
Built entirely on ERC725Y
Tentative data keys:

SupportedStandards:LSPXXEntityProfile

EntityModel (bytes32)

ControllingEntity (address, optional)

---

Default State
bytes32(0) = Undeclared

• No profile would be required to declare a model.

• Undeclared would remain the natural and fully valid state.

• Absence of declaration would carry no implications.

---

Illustrative Models (Non-Exhaustive)
IndividualSelfSovereign
CustodialAccount
Agent
SubAgent
DAO
CorporateEntity

The use of bytes32 aims to:

• Avoid rigid taxonomies

• Preserve extensibility

• Maintain minimal surface area

Interpretation would remain entirely at the application or protocol layer.

---

Principle

• Optional

• Neutral

• Non-enforcing

• Backward compatible

• Minimal surface area

• Complementary to LSP3

---

Open Questions

1. Is there a real need for a signal that is directly readable on-chain to distinguish operational models?

2. Is the use of tags within LSP3 sufficient in practice?

3. Could the absence of a minimal on-chain signal create friction in automation, integration, or adoption by applications, institutional users, or automated infrastructures?

---

Collaboration
This idea is being explored in collaboration with Antonio Arroyo
Before considering a formal LIP draft (tentatively titled Entity Profile Declaration), architectural and conceptual feedback would be greatly appreciated.