Summary

This proposal authorizes relocating the DAO treasury funds, 4,425,952,773.499635058009345650 LCAI, from the Ethereum-based Treasury (0x07A716a551E5f4CA7D6C71Da9dF1cb1429Dba826) to the Lightchain AI Mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389, chain ID 9200).

The treasury is transferred to the Lightchain AI Deployer (0xfbE810101064E326f871bf20576d8e42C75d5Dd7) and bridged to mainnet at a 1:1 rate: for every 1 LCAI bridged from Ethereum, 1 native LCAI is delivered to the mainnet DAO Treasury. This is a move, not a spend. The funds remain the DAO's treasury, nothing is spent or destroyed, and the total LCAI supply is unchanged. All transaction hashes are published for verification.

Motivation

The DAO treasury has been held as an ERC-20 balance on Ethereum since inception. With Lightchain AI Mainnet now live, the treasury's natural home is the protocol's own Layer 1, where the network and its governance run. Relocating it lets the DAO fund mainnet activity (staking and validator rewards, ecosystem grants, liquidity, operations) directly in native LCAI, instead of leaving the treasury on Ethereum.

This is a one-time relocation of existing DAO funds. It is not a new allocation, a distribution, or an expenditure. The previously approved treasury allocation framework carries over and continues to be executed from the mainnet Treasury through future governance proposals.

Strategic Significance

This migration is more than moving tokens between locations. It marks the ecosystem's transition from legacy ERC-20 infrastructure on Ethereum toward the native Lightchain mainnet economy and governance environment. As more ecosystem activity operates on native infrastructure, governance alignment improves, native ecosystem utility strengthens, operational fragmentation decreases, and long-term sustainability becomes easier to build around the L1 itself rather than external dependency layers.

It also reinforces something structurally important: a live, decentralized ecosystem ultimately depends on active governance participation from its own community. Wrapping, delegating, and voting are not only technical actions; they are part of the transition from community spectators toward active ecosystem participants. The community is encouraged to prepare early, understand the process clearly, and participate constructively once the proposal goes live. Healthy governance participation is itself a sign of ecosystem maturity.

How the Funds Move

1. The treasury is sent to the Deployer for bridging. The treasury's LCAI is transferred to the Lightchain AI Deployer (0xfbE810101064E326f871bf20576d8e42C75d5Dd7), the account the Lightchain DUNA team uses to operate the Lightchain bridge. The Lightchain bridge must be called by the account that holds the funds, which is why the transfer goes to the Deployer. This is the same mechanism the DAO approved in Proposal #862832.
2. The Deployer bridges the funds 1:1 to mainnet. The Lightchain DUNA team bridges the LCAI through the Lightchain bridge, with the mainnet DAO Treasury as the recipient. For every 1 LCAI bridged, 1 native LCAI is delivered on mainnet. The rate is one to one.
3. Native LCAI arrives in the governed mainnet treasury. Before delivery, the Lightchain DUNA team transfers ownership of the mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389) from the deployer EOA to the DAO multisig, on the path to the Timelock-controlled Governor, verified on-chain. The native LCAI is then delivered to the mainnet DAO Treasury, completing the relocation.
4. The funds remain the DAO's, and supply is unchanged. This is a 1:1 bridge of existing DAO funds across chains. Nothing is created, spent, or destroyed, and the total 10,000,000,000 LCAI supply is unchanged. The Deployer holds the funds only transiently to perform the bridge, and every transaction is published.

Proposal

Authorize the following:

1. Transfer the treasury to the Deployer for bridging. Transfer the full DAO treasury balance, 4,425,952,773.499635058009345650 LCAI, from the Treasury (0x07A716a551E5f4CA7D6C71Da9dF1cb1429Dba826) to the Lightchain AI Deployer (0xfbE810101064E326f871bf20576d8e42C75d5Dd7).
2. Bridge to mainnet at 1:1. The Lightchain DUNA team bridges the LCAI through the Lightchain bridge to the mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389), where it is received as native LCAI.
3. Governed destination (Lightchain DUNA team responsibility). Before any funds are delivered, the Lightchain DUNA (core) team transfers ownership of the mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389) away from the current deployer EOA (0x48C6570f000212E2Bfc1f38311Ca4b210987A160) to the DAO multisig, on the documented path to the Timelock-controlled Governor (Timelock 0x79e571420c5473Ca9b0FCd599B1b0062D7793c97, Governor 0x262E9f9232933E8565253918db703baD58DE93aB); this handover is the path documented on the official Lightchain mainnet contracts page (see References). The ownership-transfer transaction hash is published, and the new owner is verified on-chain, before the bridge delivery proceeds.
4. Publish proof. Publish the transaction hashes for the transfer to the Deployer and for the bridge delivery on mainnet.

Rationale

This relocates the entire treasury in a single governance action. The transfer is gated by this vote, and the Deployer is the protocol's operational bridging account, used here exactly as in Proposal #862832, holding the funds only transiently to perform the bridge. The bridge converts at 1:1, so the total supply is unchanged and the funds are neither created nor destroyed, only moved. The destination must be under DAO governance before the funds land, and every transaction is published and verifiable. All future spending from the mainnet Treasury continues to require separate DAO-approved proposals.

Note on the Destination Treasury

The mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389) is native-LCAI-only as currently deployed. It custodies and sends native LCAI (transfer, batchTransfer, and a pull-based claimWithdrawal fallback). Receiving this migration requires only native LCAI handling, which the contract supports today. If the DAO later wants the Treasury to also hold and pay out ERC-20 assets such as stablecoins, that would require a separate, governance-approved upgrade, proposed on its own.

Execution

1. The Lightchain DUNA team transfers ownership of the mainnet DAO Treasury (0x786eDe8C42Ca54E54c9dCECa9b30052CF4743389) from the deployer EOA (0x48C6570f000212E2Bfc1f38311Ca4b210987A160) to the DAO multisig (and onward to the Timelock-controlled Governor, Timelock 0x79e571420c5473Ca9b0FCd599B1b0062D7793c97, Governor 0x262E9f9232933E8565253918db703baD58DE93aB), and publishes the transfer hash. Confirm via the contract's owner that the new owner is the multisig or the Timelock-controlled Governor, not the deployer EOA, before proceeding.
2. Upon a successful vote, the Treasury (0x07A716a551E5f4CA7D6C71Da9dF1cb1429Dba826) transfers the full balance to the Deployer (0xfbE810101064E326f871bf20576d8e42C75d5Dd7).
3. The Lightchain DUNA team bridges the LCAI through the Lightchain bridge to the mainnet DAO Treasury, where 4,425,952,773.499635058009345650 native LCAI is received at 1:1. The community verifies the balance on mainnet.lightscan.app.
4. All transaction hashes are published. Net result: the DAO treasury now holds the full amount as native LCAI on mainnet, the total LCAI supply is unchanged, and the funds remain the DAO's.

Constraints

• The funds remain the DAO treasury. This proposal only relocates them to mainnet and does not authorize any other use.
• The Deployer holds the funds only transiently, solely to perform the bridge, and bridges them promptly to the mainnet DAO Treasury.
• The bridge delivery must not occur until the Lightchain DUNA team has transferred treasury ownership off the deployer EOA to the DAO multisig (or the Timelock-controlled Governor) and the new owner is verified on-chain. The ownership-transfer transaction hash must be published.
• All transactions, both the transfer to the Deployer and the bridge delivery, must be published and verifiable on-chain.
• The bridge converts at 1:1. The total LCAI supply is unchanged, and no tokens are created, spent, or destroyed.
• This proposal does not modify any existing contracts.

Voting Options

FOR: Approve relocating the DAO treasury to the mainnet DAO Treasury via the 1:1 bridge.

AGAINST: Do not authorize.

ABSTAIN: No opinion.

References

Precedent: Authorization to Establish a Treasury Stablecoin Operational Buffer (Proposal #862832), Executed. That proposal established the mechanism of a governance-authorized transfer from the Treasury to the Deployer, with the team performing the external step and publishing all hashes. This proposal uses the same mechanism, with the external step being the 1:1 bridge to the mainnet DAO Treasury.

Permalink: https://dao.lightchain.ai/proposal/0x6dfa413b5900a1a7947bc75e68abba093cb2492d/86283215617203156919667759950014439530977403806509669132200286285039830402482

Official Lightchain AI Mainnet contracts (Treasury, TimelockController, LightChainGovernor addresses, and the note that the upgradeable protocol contracts are owned by the deployer EOA pending handover to a multisig and ultimately the Timelock-controlled Governor): https://docs.lightchain.ai/docs/getting-started/mainnet/contracts