Hosts

Host Creation

The DaylightHosts.sol contract implements the protocol's decentralized identity platform, providing a foundation for location verification and device association within the protocol. This fully decentralized system enables users to establish verifiable connections between their accounts, physical locations, and energy devices while maintaining privacy and security.

When creating a DayFi Host, users claim a specific location that becomes permanently associated with their account. Rather than storing the actual location data onchain, the system stores a cryptographic hash of the location, ensuring privacy while maintaining verifiability. This location claim serves as the anchor point for all subsequent device and meter associations within the protocol.

The account system implements a sophisticated linking mechanism for connecting energy devices and meters to user accounts. This linking process enforces a critical security requirement: the location associated with any device or meter must match the claimed location of the account. Location verification occurs through trusted third-party providers - Texture for device locations and Arcadia for meter locations - ensuring that physical presence at a location can be reliably verified without compromising user privacy. A Host can also specify a recipient address that Capacity Grants rewards must be directed to. The recipient can then claim any incoming rewards efficiently, independent of how many hosts direct their rewards to that recipient. Linking a recipient begins with an offchain signatures by the recipient acknowledging (and consenting) that a Host wants to designate them as their recipient. The Host can then submit this signature onchain to link the recipient to their onchain account.

Claiming Preexisting Locations

The protocol automatically associates a location with the most recent account that successfully linked a verified device or meter at that address. When new occupants move into a location, they can naturally claim the location by linking their own verified devices or meters, automatically updating the protocol's location associations without requiring manual intervention or complex ownership transfer processes.

We also tie H3 cell regions to accounts, which users can verify by providing a zkTLS proof of a previously linked device's coordinates (hashed) and a zk proof that the hash of the coordinates map to a H3 cell contained within the provided H3 cell. This gives us a sound protocol for privately mapping a user's real world location to a broader H3 cell for privacy.

Angry-Purple-Fusion

DayFi accounts follow a randomized naming convention for human legibility. This convention combines an adjective, a color, and an energy-related concept into one unique account name "Angry-Purple-Fusion".