Sunsetting Implementation for the $TEC Token

Executive Summary

This proposal operationalizes the TEC wind-down with clear roles, deadlines, and safeguards. It establishes the consolidation of all assets to the Common Pool, mandates the conversion of all recovered assets to rETH, and funds a minimal claims mechanism for $TEC holders.

Legacy, deprecated contracts (Reserve and Common Pool) are upgraded by Guardians to freeze the Commons in a recoverable state and enable direct flows from the Common Pool to the claim contract. All other TEC-related multisigs/EOAs have 14 days to return funds to the Common Pool. Any $TEC held by participating multisigs will be burned through the ABC to avoid circular accounting. OP RPGF funds vesting via Superfluid will, upon vesting, be routed by default to the Common Pool and converted to rETH, unless governance directs otherwise between passage and execution.

There will be a four-week process for the community to verifiably raise any hacked addresses so those assets can be frozen and credited back to verified owners.

Closure logic: The claim period is indefinite by default; a future proposal (e.g., a the Severance and Postmortem Proposal) may define an end date and the treatment of unclaimed funds.

**Validity: ** This proposal, after going through the proper review process, will only be valid if a successful Tao Vote is reached.


Purpose & Principles

  • Stewardship of a Common-Pool Resource: Preserve value and reduce leakage by consolidating fragmented control into a single, accountable executor.
  • Clear Collective-Choice Arrangements: Named actors, timelines, and bounded mandates replace ambiguity with explicit, monitorable instructions.
  • Monitoring & Transparency: Upgrades and transfers are on-chain; progress updates will be posted at each major state change.
  • Graduated Sanctions (Minimal): A time-bound path (14-day remit window) followed by default routing prevents indefinite drift without adversarial posture.
  • Proportionality & Finality: Minimal technical scope (rationalized contracts, single claims flow) to limit operational and contract risk; no new programs.

Scope

This proposal covers:

  1. Asset recovery from legacy Aragon contracts and other TEC-related multisigs/EOAs into the Common Pool.
  2. Mandatory rETH conversion in the Common Pool prior to claims funding (executed by Guardians or via authorized adaptor).
  3. Build and deployment of a minimal claim contract + UI for $TEC holders (quoted at $5,000 USD).
  4. Handling of OP RPGF assets vesting via Superfluid (default β†’ Common Pool β†’ rETH).
  5. Token handling rules (burn TEC held by participating multisigs).
  6. Claims eligibility & disputes, including a four-week hacked-wallet intake window.
  7. Closure logic (indefinite by default; future proposal may define end and unclaimed handling).

Severance and post-mortem budgets are not in scope of this proposal, but stipulations are made in the case that they do or do not pass in a future proposal in order to maintain proposal independence.


Governance & Roles

Guardians

  • Mandate:
    • Pass upgrades to legacy Aragon contracts (Reserve and Common Pool) to freeze the Commons in a recoverable state (MiniMe and ABC as needed).
    • Enable Reserve β†’ Common Pool and Common Pool β†’ Claim Contract transfers per the Implementation Partner’s technical design.
    • Execute rETH conversions for inbound assets in the Common Pool.
    • Pay the $5,000 USD claim build to the Implementation Partner.
    • Execute contingencies described below and administer the hacked-wallet dispute process per this proposal.

Multisig Signers (other TEC-related units)

  • Pre-Step: Withdraw TEC-OP liquidity prior to any transfer.
  • Also: Burn any $TEC held (preferably via the bonding curve) before or at remittance to avoid circulars.

Implementation Partner

  • Mandate: Build and deploy a lightweight claim contract + UI.
  • Budget: $5,000 USD (fixed).

Asset Recovery Plan

A) Reserve & Common Pool (Legacy Aragon)

  • Action: Guardians execute upgrades that (i) freeze the system in a recoverable state (MiniMe and ABC as required) and (ii) enable direct transfers from Reserve to Common Pool and from Common Pool to the Claim Contract per Implementation Partner design.
  • Pre-Step: Withdraw TEC-OP liquidity before moving principal to avoid value leakage.

B) Other TEC-Related Multisigs/EOAs

  • Notice: Each unit is formally requested to remit remaining balances to the Common Pool within 14 days of notification.
  • If no action by Day 14: The unit is marked dormant and documented publicly; recovery efforts may continue, and any later-recovered funds will be returned pro-rata to tokenholders by topping up the Claim Contract (see β€œTop-ups” below).
  • Conversion Policy: All inbound assets to the Common Pool must be converted to rETH on receipt (hard requirement, executed by Guardians).

C) OP RPGF (Superfluid Vesting)

  • Status: Vests over time via Superfluid.
  • Rule: On each vesting withdrawal, route to the Common Pool by default and convert to rETH at that day’s rate, unless governance specifies otherwise between passage and execution.

Token Handling (Avoiding Circulars)

  • Any TEC held by participating multisigs/EOAs must be burned (preferably via the ABC bonding curve; otherwise to the zero address) prior to or at the time of remittance.
  • Rationale: Prevent circular accounting and supply feedback.

Claims Mechanism (Implementation Partner)

  • Budget: $5,000 USD from the Common Pool (fixed).
  • Mechanics:
    1. Confirm MiniMe and ABC are frozen or parameterized as required for claims.
    2. Snapshot balances via balanceOf at the frozen block.
    3. Maintain a claimed[address] mapping.
    4. Publish a TEC→rETH rate derived from total rETH committed to claims.
    5. Provide a simple web UI for wallet claims.
    6. Addresses under active hacked-wallet dispute are temporarily frozen until resolution.
  • Funding Flow:
    Common Pool converts assets to rETH β†’ pays USD 5,000 for the build β†’
    If Proposal Three passes: deduct approved severance and postmortem budgets β†’
    send the remainder to the Claim Contract.

Top-ups from Late Recoveries (Dormant Units)

  • If funds from dormant units are recovered after the Claim Contract is funded, they will be:
    • converted to rETH by Guardians and
    • deposited as a new tranche into the Claim Contract.
  • The contract should credit all snapshot addresses pro-rata for each top-up; addresses that already claimed become entitled to a second (delta) claim equal to their pro-rata share of the new tranche.

Claims Eligibility & Hacked Wallets Dispute Process

  • Four-week intake window (pre-claims): For the first 4 weeks after passage, the community may raise hacked cases; addresses reported during this window are temporarily held from claiming pending review.
  • Intake details: The holder opens a forum thread using the Hacked Wallet Case template with tx evidence, incident description, Seal911 due-process proof, and prior-ownership proof.
  • Review Panel: 3 reviewers β€” 1 Guardian, 1 independent steward, 1 additional reviewer designated by Guardians. Standard: preponderance of evidence. Decision and rationale published with PII redacted. SLA ≀14 days (one 7-day extension allowed).
  • Remedies:
    • Approved: blocklist compromised address; allowlist a new address for the same amount.
    • Denied or no decision: hold expires; original address may claim.
  • Appeal: One time to a broader panel designated by Guardians; majority decision is final.
  • Ongoing reports: After the initial four-week window, no further hacked cases may be filed.

Timelines & Service Levels

  • Day 0: Proposal passes.
  • Days 0–2: Guardians queue/execute Aragon upgrades; issue formal notices to all other multisigs/EOAs.
  • Day 14: Deadline for remittance to Common Pool; non-remitting units are marked dormant; process continues with available assets.
  • Weeks 0–4: Hacked-wallet intake window open; reported addresses held from claiming pending review.
  • Rolling: Convert each inbound asset to rETH on receipt.
  • Within 2 weeks of funding the build: Implementation Partner deploys Claim Contract + UI, and Guardians fund it from the Common Pool.

Closure Logic

  • Default: The claim period is indefinite and funds remain claimable by tokenholders.
  • Change by governance: A future proposal (including, but not limited to, Proposal Three) may set an end date and define unclaimed handling.

Risk Management & Operational Hygiene

  • Minimize legacy surface area: One-time Aragon upgrades; avoid bespoke extensions on deprecated contracts.
  • Credential hygiene: All signers follow the multisig credential guidelines (key security, rotation discipline).
  • Transparency: Public updates at each state change (upgrades executed, transfers received, conversions completed, claims live).

Decisions Requested (Snapshot Items)

  1. Authorize Guardians to execute Aragon upgrades that (a) freeze MiniMe and ABC as needed and (b) enable Reserve β†’ Common Pool and Common Pool β†’ Claim Contract transfers.
  2. Mandate a 14-day remittance window for all TEC-related multisigs/EOAs to the Common Pool; non-remitting units are marked dormant and disclosed, and any late recoveries will be returned pro-rata via top-ups.
  3. Require rETH conversion for all inbound assets to the Common Pool prior to claims funding (executed by Guardians).
  4. Fund the USD 5,000 claim contract and UI build from the Common Pool.
  5. Set OP RPGF default routing: on vesting, to Common Pool and convert to rETH, unless governance specifies otherwise.
  6. Adopt the TEC burn policy for any TEC held by participating multisigs/EOAs prior to remittance.
  7. Adopt the four-week hacked-wallet intake and the ongoing dispute process described above.
  8. Confirm closure logic: indefinite claim period by default; any change requires a future governance decision.

Appendix 1: Multisig Actions Table

Unit Primary Action Deadline If No Action Notes
Reserve (Aragon) Guardians upgrade β†’ Reserve β†’ Common Pool ASAP β€” Withdraw TEC-OP LP first
Common Pool (Aragon) Guardians enable Common Pool β†’ Claims Contract ASAP β€” Conversion to rETH enforced
Coordination Team No Action Required N/A N/A N/A
TECAN Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
TE Grants Program Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
Lasertag Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
TEC GG Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
TEC Giveth Donations EOA Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
Transaction Team Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
ABC EOA Transfer β†’ Common Pool 14 days Mark dormant Convert to rETH on receipt
OP RPGF Superfluid On each vest route β†’ Common Pool, convert Rolling β€” Default unless governance reroutes