Game Assets
    Lords
    Governance
    Information

      BIP-86: Ecosystem Team 3-Month Extension & BA Devconnect Funding (Dual Biblio/RoyaltyDAO)

      Passed
      Proposed by 0x5b0a...7201•3 months ago

      Ecosystem Team — 3-Month Extension (Oct–Dec 2025)

      TL;DR

      • Extend the Ecosystem Team (Calc, Nejc & Squiddy) for 3 months with the same monthly budget and remit structure.

      • Add a one-off $12,500 USDC “Devconnect Argentina Pot” for lean, high-leverage event activations (unused funds return to the DAOs).

      • Focus this term on: Pirate Nation claim onboarding, Devconnect Argentina execution (Gaming District), weekly DAO updates, social media ops, EOY LLC compliance & 2026 planning, and execution of the Loot Treasury plan.

      • Funding split: We are asking that this funding come from BiblioDAO (58%) & RoyaltyDAO (42%).

      Note: Nejc is the volunteer lead curator of the Devconnect Gaming District, providing high visibility to Loot and its culture through spotlighting Realms and other Loot-native projects.

      Why a bridge term?

      This 3-month bridge keeps ops tight while we sprint into Devconnect Buenos Aires, finish EOY obligations, and wrap up three high-impact deliverables: the Pirate Nation claim, Devconnect execution (Gaming District), and the Loot Treasury plan. Assuming passage, we’ll return before year’s end with a 3–6 month proposal informed by outcomes from this term.

      Scope of Work (Oct–Dec 2025)

      1) Pirate Nation Claim — Plan, Coordinate, Execute

      Objective: Bring diamond-handed holders of Pirate Nation Founder Pirates (holder snapshot made before the NFT burn event) into the Realms ecosystem via a structured claim that drives new wallets, DAU, and cross-community engagement.

      • Organise “Realms Bag” claim of games in our ecosystem.

      • Finalise claim mechanics.

      • Tech coordination.

      • Comms & GTM.

      2) Devconnect Argentina — Plan & Execute (Gaming District)

      Objective: Maximise exposure and gameplay for ecosystem titles during Devconnect.

      • Curate and schedule all ecosystem game activations: demos, playtests, and talks.

      • Manage gaming district and asset operations: banners, merch, and shared materials.

      • Coordinate creator and press touchpoints: interview slots, hands-on sessions, and daily recap content.

      • Oversee onsite logistics: tournaments, playtests, speaker coordination, meetups, and partner engagement.

      • Produce and execute Loot Day: a flash, Loot-inspired cultural takeover of the Gaming District featuring art, CC0 poem readings, and game tournaments, recorded for inclusion in a Loot mini-documentary.

      • Conduct post-event debrief and collect actionable insights for future activations.

      • Lead BD efforts and partnership development throughout and after the event.

      3) DAO Updates (Now includes Socials)

      Objective: Provide a reliable, digestible heartbeat to the DAO across channels.

      • DAO Updates: ecosystem progress, links, next-week focus.

      • Media: ship 3–5 weekly posts across priority channels, amplifying ecosystem milestones, partner beats, Devconnect/Pirate Nation progress, and Realms.world-related articles (plus healthy “reply-guying”).

      • Interviews: a monthly Realms interview series covering ecosystem projects, contributors, personal journeys, and views on the space.

      4) Listings & Platform Stewardship (Hygiene)

      • Maintain CMC/CG/Dexscreener/DappRadar/Realms.world data parity.

      • Discord housekeeping, security, link hubs, OpenSea collections, basic site copy updates.

      • Serve as POC in Discord for tickets, enquiries, etc.

      5) EOY LLC Work (Fulfil Criteria) + 2026 LLC Plan

      Objective: Close 2025 cleanly and set 2026 structure/options.

      • EOY compliance checklist (filings, bookkeeping, resolutions, document pack).

      • Options review for 2026 (status quo vs. alternative jurisdictions/providers; cost, risk, ops burden).

      • Organise and execute the proposals needed for 2026.

      6) Loot Treasury Plan — Execute

      Mandate: The Ecosystem Team (authorised multisig signers) will operationalise the approved Lootverse Microstrategy over this 3-month term.

      What that means (concise):

      • We execute: source, approve, and sign treasury actions end-to-end (venue selection, OTC/TWAP execution, settlements) in line with the passed strategy and DAO approvals.

      • We document: maintain a public execution log (tx links, dates, sizes) and keep custody/compliance hygiene (multisig policies, 3/5 signer review).

      • We report: include progress in DAO updates and deliver an end-of-term treasury summary (positions, cost basis, cap usage, next-steps recommendation).

      7) Studio Alignment and Grantees POC & Support

      Mandate: Continue hands-on support for aligned studios and grantees; keep roadmaps on track; release funds against verified milestones; and amplify launches/playtests with clear comms.

      What we’ll do

      • POC per studio/grantee: maintain a POC for every aligned studio and active grantee.

      • Cadenced check-ins: light regular async check-ins + a monthly review to track progress, risks, and help needed.

      • Milestone gating & payments: verify deliverables against the approved plan; prepare vesting/payment packets; execute grants when due.

      • Launch & playtest support: slot teams into the content calendar; coordinate playtests; provide GTM boosts (socials, Discord, KOLs); ensure listings/link hubs are current.

      • Issue escalation: flag slippage/blocked items early; agree remediation or scope adjustments with teams and (if needed) the DAO.

      Budget

      1) Team funding (unchanged)

      • $7,300 USDC per month ($6,350 + 15% buffer) × 3 months = $21,900 USDC.

      • Unused funds return to the DAOs at term end.

      2) Devconnect Argentina Pot (one-off)

      • $12,500 USDC cap, used responsibly and sparingly for:

        • Team attendance light subsidies critical to delivery.

        • Event merch (stickers/tees/small materials/banners).

        • Lordly meetup/event (reasonable bar/venue cap).

        • Lightweight activations in/around the Gaming District throughout the week.

        • Loot Day commemorative event that will take over the Gaming District with a day’s worth of activities.

        • LATAM gaming-related charity contribution, planned to coincide with Devconnect Argentina and organised with local charities (to be refunded if it does not take place).

      • Reporting on spend and unused funds return to the DAOs.

      Total Ask (Term 1.5): $34,400 USDC ($21,900 funding + $12,500 Devconnect Pot).
      Rollover: There is $5,388 USDC remaining from Term 1; this offsets Term 1.5 requirements.

      Execution (unchanged mechanics)

      Funding structure: This proposal is submitted in equal form to BiblioDAO and RoyaltyDAO. Net of rollovers, BiblioDAO will cover ~58% of the total by applying leftover USDC from the prior term. Rationale: while all work advances the Loot ecosystem, the team’s day-to-day execution this term is primarily within Realms World.

      • The RealmsDAO L2 wallet will immediately sell $14,506 USD of EKUBO & ETH for USDC.

        • 50% from ETH tokens.

        • 50% from Ekubo tokens.

      • The RoyaltyDAO wallet will immediately sell $14,506 USD of ETH for USDC.

        • 100% from ETH tokens.

      • The Ecosystem Team may claim up to $21,900 USDC at 1:1 within the term; allocation at the team’s discretion until term end.

      Contingency & Dual-DAO Ratification

      Context: This funding term is being proposed to two DAOs. To avoid mismatch or unilateral execution, the following rules apply.

      Ratification condition (both or nothing):

      • Funding is only ratified—and any execution (token sales, disbursements, Devconnect Pot usage, etc.) may begin—once both DAOs have approved the proposal at the same total amount.

      • Until dual approval is achieved, the proposal is pending/void and no funds move.

      If one passes and the other doesn’t:

      • The passed side remains approved but unexecuted and will not trigger any actions alone.

      • We will make up to three (3) re-submission attempts per DAO to secure matching approval.

      • If one DAO requests edits, we will update only that DAO’s version provided the total amount does not change.

      • If an edit changes the total amount or materially alters scope, the already-approved DAO must re-ratify.

      Failed ratification (after attempts or deadline):

      • If matching approval is not achieved after the allowed attempts (or by the term start deadline, if earlier), the proposal lapses for this term.

      • We will return any remaining USDC from the prior term to BiblioDAO as previously committed. (This clarifies that leftover funds are not being held contingent on passage.)

      Operational holds until ratified:

      • No treasury conversions (e.g., ETH/EKUBO → USDC), disbursements, or Devconnect spending occur prior to dual-DAO approval.

      • Signers will publish a short confirmation once both approvals are in place and before execution begins.

      Governance & Conduct

      • Bound by the previously approved Binding Code of Conduct (welcoming, honest, anti-manipulation, pro-collab).

      • Weekly updates to keep the DAO informed; end-of-term report with outcomes and recommendations for the next 3–6 month proposal.

      Results
      Yes:1864
      No:0
      Abstain:0