F22-I2: No
Rationale
An ordinary LeaseSet advertises tunnel entry points for one Destination. Meta LeaseSets go further: they can refer to several Destinations or nested Meta LeaseSets for a common service. However, the list is signed by the root Destination signing key or its authorized transient key. Independent participants cannot add themselves under that reference without its signing authority. Thus even this closer mechanism fails the nonexclusive-reference requirement of F22. The distributed floodfill database does not remove control of the signed record. The structure specification marks MetaLeaseSet preliminary and not fully supported; this decision does not assert deployed availability.
Assessment method
Primary netDb and MetaLeaseSet signature analysis; no execution
Source context
I2P network database: LeaseSets and Meta LeaseSets