Lighthouse Labs

Accelerating the adoption of onchain governance technology

[Lighthouse Labs @LighthouseGov]

The win isn't any one app, it's every governance tool reading the same records, so a delegate's reputation travels with them.

@AragonProject @ensdomains, worth converging while ENSIP-64 is open?

And delegates: what do you wish lived on your ENS name?

Spec + guide: https://t.co/K7CBmgm8cV

[Lighthouse Labs @LighthouseGov]

Your delegate statement shouldn't be trapped in one app's database.

@AragonProject just made sure it isn't, shipping delegate statements onto ENS. 👏

Here's how it snaps into the ENS standard already in review 🧵

[Aragon.eth 🦅 @AragonProject]

Introducing onchain profiles for council members, multisig signers, and delegates.

Publish profiles and statements in Aragon via @ensdomains, improving opsec hygiene and making approval flows easier to track.

Built on open infrastructure, so profiles stay portable across apps.

[Lighthouse Labs @LighthouseGov]

And it doesn't box you in — the bracket label is freeform, so contract- or token-level scoping still works if a DAO needs it.

The ENS name is just the human-readable default.

[Aragon.eth 🦅 @AragonProject]

Introducing onchain profiles for council members, multisig signers, and delegates.

Publish profiles and statements in Aragon via @ensdomains, improving opsec hygiene and making approval flows easier to track.

Built on open infrastructure, so profiles stay portable across apps.

[Lighthouse Labs @LighthouseGov]

Nice writeup on emerging ways to handle Agents on ENS.

We also wrote an early discovery piece in https://t.co/gEyXV9uAXr for those who want to unpack further on the forums.

[cap.eth @TheCapHimself]

https://t.co/Wp85hbIoRr

[ensdao.eth @ENS_DAO]

ENS names lacked a standard way to express structured metadata. Lighthouse’s ENS Schemas fixes that.

Live now → draft ENSIP + tooling (10 schemas, SDK, CLI, app/docs).

Review @ensdomains PR #64 and weigh in.

https://t.co/tuQLaWEmno

[Lighthouse Labs @LighthouseGov]

How-to guides now live for:

→ Representing an entire org on-chain
→ Publishing your delegate statement
→ Giving an AI agent identity

Try it → https://t.co/gyJja9kh6Y

What would you classify first?

[Lighthouse Labs @LighthouseGov]

ENS names are how people and orgs identify themselves on-chain, but until now there's been no standard way to describe what a name represents.

More details on our solution for @ensdomains:

https://t.co/cKFx3GbthF

[Lighthouse Labs @LighthouseGov]

Any ENS name can now declare its class (wallet, contract, agent, etc) and attach a JSON schema describing its attributes.

This enables DAOs to publish a verifiable org chart directly to their ENS name, including treasuries, contracts, and delegate info.

[Mark Beylin @Beylin]

Some greenfield areas where I hope to see more experimentation in 2026:
- agent DAOs
- zk games
- programmable markets
- onchain hardware locks
- dynamic token models

[Lighthouse Labs @LighthouseGov]

AI will allow us to create new tools for coordination.
https://t.co/NQ7bBmy7hK

[Snapshot.eth @SnapshotLabs]

"The combination of near-free software production and low-cost DAO structures creates the first meaningful economic advantage for pure DAOs since their inception."

[blockful.eth @blockful_io]

Moonwell on Moonriver is under an active governance attack.

$1,808. That's what it cost to buy enough tokens to pass a proposal that can drain $1.08M in user funds. A 597x profit.

Voting ends on March 27. There's still time to stop it. 👇

[vitalik.eth @VitalikButerin]

It's a good decision!

ENS names and records are a form of state that is central to the Ethereum ecosystem, the state is limited in size and there is high value in it being as accessible as possible from anywhere.

It's also a semi-financial application, in the sense that buying and holding ENS names has a cost, and ENS names can become very valuable objects.

With the expanded scaling roadmap, Ethereum L1 is the ideal place for these applications.

More generally, I expect that the optimal architecture for decentralized identity and social (the general space I see ENS being in) is to have this kind of per-user account and profile data on L1, and to have special-purpose L2s, likely much simpler than full EVMs, to handle user actions (eg. actions on social platforms).

[Lighthouse Labs @LighthouseGov]

Makes sense. Wen!?

[netto.eth (in SF, then NYC) @alextnetto]

ENS is still missing in some places on @safe.

Here is a PR to take one more step to better UX.

https://t.co/DV1nolEGXz

[Lighthouse Labs @LighthouseGov]

Read our submission: https://t.co/XOi4p2Him4

[Lighthouse Labs @LighthouseGov]

Submitted to @Designing_DeFi

Harbor Protocol unlocks secondary markets for vesting and staked positions, without breaking the lock.

Exit positions early. Buy someone else's at a discount. The original commitment stays intact.

[Fhenix @fhenix]

https://t.co/6Ysrw3rvwh