Establishment of Lido Labs BORG Foundation as a Lido-DAO-Adjacent Foundation

Proposals
5

Absent sections to <new borg name> relative to Lido Alliance BORG

J. BORG Personnel / Eligibility to Serve

Lido Alliance: “2.1.2. Each BORG Personnel’s agreements with and duties to the BORG must not contravene, conflict with, or violate or constitute a breach or default under (or an event that with notice or lapse of time or both would become a violation or constitute a breach or default under) any applicable Legal Requirement or agreement to which such BORG Personnel is subject.”

<new borg name>: None

K. Alliance Multisig Members / Removal Of Alliance Multisig

Lido Alliance: “2.4.5.1. Removal of Director Alliance Multisig Members. Each person who is removed as a Director in accordance with these Bylaws shall also thereby automatically be deemed removed as a Director Alliance Multisig Member, and the Alliance Multisig Members shall take all action necessary or desirable to cause such person to be removed as a Multisig Member of the Alliance Multisig.”

<new borg name>: None

L. Emergency Supervisors / Disputes Regarding Emergency Supervisors Appointment

Lido Alliance: “2.6.6. Disputes Regarding Emergency Supervisor Appointment. Notwithstanding any other provision of these Bylaws, the existence, threat or pendency of any Dispute by a BORG Personnel (other than the Emergency Supervisor) regarding whether an Emergency Supervisor was duly appointed or regarding the scope of authorities of an Emergency Supervisor (including any Dispute regarding the existence of an Adverse Event forming the basis of a Community Module Approval of an Emergency Supervisor) shall not excuse any breach or non-performance of these Bylaws or any Governance Agreement by any BORG Personnel (other than the Emergency Supervisor) or any duty owed to the BORG by any BORG Personnel (other than the Emergency Supervisor), and all performance obligations and duties shall continue to apply to all such BORG Personnel during such Dispute.”

<new borg name>: None

M. Board Meetings:

Lido Alliance: “

  • 3.5. Board Meetings

  • 3.5.1. Place and Manner of Meetings

  • 3.5.1.1. The Board may hold meetings, both regular and special, in any place or in any manner (including remotely in accordance with Article 3.5.1.2 below) selected reasonably and in good faith by the Chair or agreed by any two Directors.

    • 3.5.1.2. Any or all Directors may participate in a meeting of the Board by means of internet conference, phone, or other communications equipment by means of which all persons participating in the meeting can hear each other, and such participation in a meeting shall constitute presence in person at the meeting.

  • 3.5.2. Regular Meetings

Regular meetings of the Board may be held without notice at such time and at such place as shall from time to time be determined by the Board.

  • 3.5.3. Special Meetings; Notice

  • 3.5.3.1. Special meetings of the Board for any purpose or purposes may be called at any time

by the Chair or any two Directors.

  • 3.5.3.2. Notice of the time and place of special meetings shall be delivered to each Director in the manner specified for giving notice to such Director recorded on the BORG’s records and shall be given at least 48 hours before the meeting is scheduled to occur. The notice need not specify the purpose of the meeting. Unless otherwise indicated in the notice thereof, any and all business may be transacted at a special meeting.

  • 3.5.4. Quorum

    • 3.5.4.1. At all meetings of the Board, a majority of the total number of Directors then in office shall constitute a quorum for the transaction of business and the act of a majority of the Directors present at any meeting at which there is a quorum shall be the act of the Board, except as may be otherwise specifically provided by statute or by the Constitution. If a quorum is not present at any meeting of the Board, then the Directors present thereat may adjourn the meeting from time to time, without notice other than announcement at the meeting, until a quorum is present.
    • 3.5.4.2. A meeting at which a quorum is initially present may continue to transact business notwithstanding the withdrawal of Directors, if any action taken is approved by at least a majority of the required quorum for that meeting.

  • 3.5.5. Waiver Of Notice: Whenever notice is required to be given under applicable Legal Requirement, these Bylaws, or any other Governance Agreement, a written waiver thereof, signed by the person entitled to notice, or waiver by electronic mail or other electronic transmission by such person, whether before or after the time stated therein, shall be deemed equivalent to notice. Attendance of a person at a meeting shall constitute a waiver of notice of such meeting, except when the person attends a meeting for the express purpose of objecting, at the beginning of the meeting, to the transaction of any business because the meeting is not lawfully called or convened. Neither the business to be transacted at, nor the purpose of, any regular or special meeting of the Directors, need be specified in any written waiver of notice unless so required by the Constitution or these Bylaws.

  • 3.5.6. Board Action By Written Consent Without A Meeting

    • 3.5.6.1. Unless otherwise restricted by the Constitution or these Bylaws, any action required or permitted to be taken at any meeting of the Board may be taken without a meeting if all members of the Board consent thereto in writing or by electronic transmission, and the writing or writings or electronic transmission or transmissions are filed with the minutes of proceedings of the Board. Such filing shall be in paper form if the minutes are maintained in paper form and shall be in electronic form if the minutes are maintained in electronic form.
    • 3.5.6.2. Any copy, facsimile or other reliable reproduction of a consent in writing may be substituted or used in lieu of the original writing for any and all purposes for which the original writing could be used, provided that such copy, facsimile or other reproduction shall be a complete reproduction of the entire original writing.

  • 3.5.7. Deadlocks

    • 3.5.7.1. “Deadlock” means:
    • (a) that, with respect to any proposal, resolution or action that has been submitted to a vote of the Board by a Director (including, if applicable, by Alliance Multisig Proposal):
      • (i) the full Board is evenly divided thereon such that there is neither a majority of the Board in favor of nor a majority of the Board against such proposal, resolution, or action and it cannot reasonably be expected that a majority of the Board will be voted in favor of or against such proposal, resolution, or action in the near future; or
      • (ii) a quorate meeting of the Board where such proposal, resolution, or action is scheduled to be voted upon has failed to be convened after three consecutive reasonable good faith attempts to do so in accordance with all applicable notice requirements and it cannot reasonably be expected that a quorum of the Board will convene for such a meeting in the near future. For purposes of this provision, a Director’s Signature Decision to intentionally refrain from signing an Alliance Multisig Proposal, indicated by any reasonable communication method of such Director signaling that such refrain is intentional, shall count as a vote against the relevant Alliance Multisig Proposal or other relevant proposal that is voted upon via Multisig; or
    • (b) as a result of circumstances described in the preceding clause ‘(a)’ or otherwise, a sustained vacancy in a position (such as Supervisor) that is required by these Bylaws to be occupied.
    • 3.5.7.2. During the existence of any Deadlock, any BORG Personnel may: (a) deliver written notice to the Board stating that in such person’s opinion a Deadlock has occurred and identifying the proposal, resolution or action giving rise to the Deadlock; and (b) submit a proposal to the Community Module to vote upon the proposal, resolution or action giving rise of the Deadlock. Following such a notice, notwithstanding any requirement for Board approval that would otherwise apply, a Community Module Approval on the proposal, resolution or action giving rise to the Deadlock shall determine the outcome of the Deadlock, and the Board and all other BORG Personnel shall be bound thereby and shall implement the resolution of the Deadlock approved by Community Module Approval.

  • 3.5.8. Minutes

The Board shall keep minutes of all meetings and record them in the BORG’s minute book.”

<new borg name>: None

N. Alliance Multisigs / Documentation and Updates to Schedule:

Lido Alliance: “

  • 3.6.3. Each Alliance Multisig shall be identified and described in reasonable detail on the Alliance Multisig Schedule including by identifying and describing in plain English, in reasonable detail:

    • 3.6.3.1. the Blockchain System to which the Alliance Multisig is deployed;
    • 3.6.3.2. the network address of the Alliance Multisig on such Blockchain System;
    • 3.6.3.3. the network addresses serving as the public keys corresponding to the Private Keys included in the Multisig Private Key Set for such Alliance Multisig (i.e., the network addresses used by the Alliance Multisig Members for purposes of interacting with the Alliance Multisig);
    • 3.6.3.4. the names (or public pseudonyms within the Community) of each Alliance Multisig Member and whether each such person is a Director Alliance Multisig Member or a Guardian Alliance Multisig Member;
    • 3.6.3.5. the minimum number of Multisig Private Keys required to execute transactions through the Alliance Multisig (broken down by transaction type, in the event that different transaction types have different approval thresholds);
    • 3.6.3.6. any and all abilities, powers, and rights such Alliance Multisig has with respect to any Community Autonomous Systems, including a technical and plain-English description of each function of a Community Autonomous System over which such Alliance Multisig has privileged, elevated or exclusive access, power or authority and the intended uses thereof;
    • 3.6.3.7. any and all abilities, powers, and rights the Community Module or any other Multisig, BORG, Blockchain System or Smart Contract has with respect to the Alliance Multisig;
    • 3.6.3.8. a copy of or persistent link to the source code for Alliance Multisig; and
    • 3.6.3.9. for each Alliance Multisig Member with respect to each Alliance Multisig, at least one public key address corresponding to the Private Key of such Alliance Multisig Member that belongs to the Private Key Set for such Alliance Multisig.”

<new borg name>: None

O. Multisig Private Key Management Practices:

Lido Alliance: “ 3.8. Multisig Private Key Management Practices

  • 3.8.1. Key Generation

    • 3.8.1.1. The Board or an Officer shall provide each person intended to be an Alliance Multisig Member (“Prospective Alliance Multisig Member”) with instructions for generating a Private Key intended for use in each Alliance Multisig, and such Prospective Alliance Multisig Member shall follow such instructions strictly.
    • 3.8.1.2. Each Private Key must be unique to one and only one Alliance Multisig Member and not shared with or accessible to the BORG or any other person.
    • 3.8.1.3. The Private Key generated by a Prospective Alliance Multisig Member in accordance with the aforementioned requirements may be deemed to be the Multisig Private Key of such Prospective Alliance Multisig Member for one or more Alliance Multisigs, and thus the Prospective Alliance Multisig Member become an Alliance Multisig Member for such Alliance Multisig(s).
    • 3.8.1.4. From time to time, the Board may require and direct that any Multisig Alliance Member replace or substitute any Multisig Private Key with a new Private Key generated in accordance with the aforementioned requirements.
    • 3.8.1.5. The Private Key shall be the property of the Alliance Multisig Member or Prospective Alliance Multisig Member and shall not constitute the property of the BORG. The Private Key of the Alliance Multisig Member or Prospective Alliance Multisig Member shall not represent any interest in any asset which is controlled by a Multisig.

  • 3.8.2. Private Key Security

    • 3.8.2.1. Each Alliance Multisig Member shall securely hold, custody and safeguard his or her Multisig Private Key(s) and immediately notify the BORG and the other Alliance Multisig Members if any of such Alliance Multisig Member’s Multisig Private Key(s) could reasonably be expected to have been stolen, published or otherwise accessed by, made available to or become known to any other person (including any other Alliance Multisig Member).
    • 3.8.2.2. Alliance Multisig Members shall not disclose or make available any Alliance Multisig Private Key to, or share any Alliance Multisig Private Key with, any other person, including other Alliance Multisig Members.

  • 3.8.3. Ownership of Multisig-Controlled Property

    • 3.8.3.1. Unless otherwise expressly agreed by the relevant Alliance Multisig Member and the BORG in writing, no Alliance Multisig Member shall be deemed to own any Community Tokens held in, by or through any Alliance Multisig or any other Blockchain Tokens, digital assets or other property held in, by or through, or received by an Alliance Multisig Member on account of such Alliance Multisig Member’s participation in any Alliance Multisig (including, without limitation, any “airdrops” or other distributions of Blockchain Tokens received or claimable by such Alliance Multisig Member’s externally owned account or blockchain address on account of such Alliance Multisig Member’s participation in the Alliance Multisig).
    • 3.8.3.2. In the event any such Community Tokens or other Blockchain Tokens, digital assets or other property is not owned by a third party, then such Community Tokens or other Blockchain Tokens or property shall automatically be deemed to be owned by, and constitute the sole property of, the BORG.
    • 3.8.3.3. In the event an Alliance Multisig Member receives any property of the BORG to such Alliance Multisig Member’s externally owned account or blockchain address, such Alliance Multisig Member shall promptly notify the BORG and remit such property to the BORG in the manner directed by the BORG (which may include depositing such property into an Alliance Multisig).
    • 3.8.3.4. In no event shall any Multisig, Alliance Multisig Member, or the BORG be deemed to own or control the Community Module, the Community Autonomous Systems, or any assets held therein or controlled thereby.

  • 3.8.4. Conduct of Alliance Multisig Members

    • 3.8.4.1. Coordination Among Alliance Multisig Members; Multisig Procedures
      • (a) Each Alliance Multisig Member shall undertake to maintain good relations with and engage in reasonably prompt, frequent and timely consultation and cooperation with the other Alliance Multisig Members on all other matters arising in connection with or relating to the BORG.
      • (b) The Director Alliance Multisig Members may from time to time establish various standard rules, practices, customs, protocols and procedures related to being an Alliance Multisig Member or participating in the Alliance Multisig, provided that the foregoing are only supplemental to these Bylaws and do not conflict with, amend, terminate, limit or waive any express provision of or right or duty existing under these Bylaws (the “Multisig Procedures”).
      • (c) Multisig Procedures may be established through course of conduct, informal agreement, or other reasonable means providing the Alliance Multisig Members with reasonable notice thereof.
      • (d) Each Alliance Multisig Member shall comply with any Multisig Procedures of which it is or reasonably should be aware.
    • 3.8.4.2. Proposals; Response to Proposals. Any Director Alliance Multisig Member may from time to time propose that a certain action be taken or transaction effected by the Alliance Multisig, pursuant to the Authorized Uses. A Director Alliance Multisig Member shall make such a proposal by signing with such Director Alliance Multisig Member’s Multisig Private Key a draft executable transaction message that, if such draft executable transaction message receives sufficient other such signatures from other Alliance Multisig Members, will be executed by the Alliance Multisig (each such proposal, a “Alliance Multisig Proposal”). A Director Alliance Multisig Member shall also follow any Multisig Procedures applicable to the making of an Alliance Multisig Proposal; provided, however, that any breach or non- observance of a Multisig Procedure in respect of an Alliance Multisig Proposal shall not in itself impair, void, or require any reversal or limitation of an Alliance Multisig Proposal that is executed by the Alliance Multisig pursuant to the Authorized Uses and otherwise in accordance with these Bylaws. Each Alliance Multisig Member shall promptly, reasonably, diligently, independently, and in good faith evaluate the merits of each Alliance Multisig Proposal solely in light of the Purposes, Authorized Uses and the Principles, and, based solely on such evaluation, and without regard to any personal or extrinsic interest or consideration, determine whether to vote in favor of such Alliance Multisig Proposal (i.e, to sign the relevant transaction message with such their respective Multisig Private Keys) or vote against such Alliance Multisig Proposal (i.e, intentionally refrain from so signing Alliance Multisig Proposal) (each, a “Signature Decision”). Upon an Alliance Multisig Member reaching an affirmative Signature Decision with respect to an Alliance Multisig Proposal, such Alliance Multisig Member shall promptly sign the relevant transaction message with such Alliance Multisig Member’s Key for potential execution by the Alliance Multisig. Once an Alliance Multisig Proposal has received sufficient signatures by the Alliance Multisig Members to be executed, the Alliance Multisig Members shall cause such Alliance Multisig Proposal to be executed by the Alliance Multisig as promptly as reasonably practicable in light of all applicable facts and circumstances, including security considerations relating to front-running and similar issues. For the avoidance of doubt, the Alliance Multisig Members and the BORG may make use of private mempools and other such confidentiality or transaction prioritization or transaction batching mechanisms in connection with the execution of Alliance Multisig Proposals, as determined in their reasonable good faith discretion in light of the Authorized Uses, Purposes, and Principles. The approval by a sufficient number of Alliance Multisig Members of an Alliance Multisig Proposal (to cause the Alliance Multisig to execute such Alliance Multisig Proposal onchain or as otherwise provided by these Bylaws) shall constitute the action of such Alliance Multisig as a body. Notwithstanding the foregoing, Guardian Multisig Members shall assess Alliance Multisig Proposals solely in accordance with the role of Guardians as set forth in Article 3.7.2, and shall only approve Alliance Multisig Proposals that have been approved by at least a majority of the Director Alliance Multisig Members (or in the event there are two or fewer Director Alliance Multisig Members, all of the Director Alliance Multisig Members).

  • 3.8.5. Navigating Conflicting Community Interests: In considering how to act in connection with a matter that, when considered in light of the Purposes and the Principles, involves any material conflict, competition or inconsistency among the interests of categories of Community members, each Alliance Multisig Member shall act in a manner intended to maximize benefits and minimize harms to the overall Community taking into account all relevant facts and circumstances then known to or reasonably discoverable by such Alliance Multisig Member.”

<new borg name>: None

P. NATURE OF BORG ACTIVITIES; NO GENERAL DUTIES TO COMMUNITY / Conflicts of Interest

Lido Alliance: “

  • 4.5.1. Each BORG Personnel shall use reasonable best efforts to continuously monitor and evaluate such BORG Personnel’s personal facts and circumstances (including such BORG Personnel’s direct and indirect investments and other economic interests in other blockchain-based companies, systems and communities) that could reasonably be expected to give rise to a material conflict of interest on the part of such BORG Personnel in connection with such BORG Personnel’s activities relating to the BORG.

  • 4.5.2. If a BORG Personnel becomes aware of an ongoing material conflict of interest with respect to such BORG Personnel’s participation in the BORG, such BORG Personnel shall resign from the BORG, unless such conflict of interest has been disclosed (along with all relevant material facts and circumstances) to the Board and the Community in reasonable detail and such BORG Personnel’s continued participation in the BORG has been approved by a majority of the disinterested Directors and by a Community Module Approval notwithstanding such conflict of interest (which consent may be conditioned on appropriate ongoing procedures, disclosures, limitations, or similar terms and conditions, which shall be observed by the applicable BORG Personnel from and thereafter).

  • 4.5.3. The holding, ownership or use of the Community Token or any right to receive or purchase any Community Token on the part of any BORG Personnel shall not in itself be deemed a conflict of interest,”

<new borg name>: None

Q. Indemnification

Lido Alliance: “ 7. INDEMNIFICATION

  • 7.1. Indemnification of Certain BORG Personnel. Each person who was or is made a party to, or is threatened to be made a party to, or is involved in any threatened or actual action, suit, claim, counterclaim, cross claim, arbitration, mediation, alternate dispute resolution mechanism, investigation, inquiry, administrative hearing or any other actual or threatened proceeding, including any appeal or action for enforcement, in each case, whether civil, criminal, administrative or investigative, brought by or on behalf of or to be determined or tried by or before a governmental body or legal mediator, arbitrator or panel of mediators or arbitrators, in each case, by reason of the fact that such person (or a person of whom such person is the legal representative), is or was a BORG Personnel (each, a “Proceeding” and each such person against whom a Proceeding is brought, an “Indemnitee”) shall be indemnified and held harmless by the BORG upon the terms and conditions set forth in this Article 7 against all expenses, liability and loss (including attorneys’ fees, judgments, fines, excise taxes and penalties and amounts paid or to be paid in settlement) reasonably incurred or suffered by such Indemnitee in connection therewith, provided such Indemnitee acted in good faith and in a manner that the Indemnitee reasonably believed to be in or not opposed to the best interests of the BORG, did not commit fraud, gross negligence, an intentional and knowing material breach of a material provision of these Bylaws or another Governance Agreement or legal agreement with the BORG, or a crime involving moral turpitude, and, with respect to any criminal action or Proceeding, had no reasonable cause to believe the Indemnitee’s conduct was unlawful. Such indemnification shall continue as to an Indemnitee who has ceased to be a director or officer and shall inure to the benefit of such Indemnitees’ heirs, executors and administrators. Notwithstanding the foregoing, the BORG shall indemnify any such Indemnitee seeking indemnity in connection with a Proceeding (or part thereof) initiated by such Indemnitee only if such Proceeding (or part thereof) was authorized by the Board or such indemnification is authorized by an agreement approved by the Board.

  • 7.2. Advance of Expenses. The BORG shall pay all expenses (including attorneys’ fees) incurred by such an Indemnitee in defending any such Proceeding as they are incurred in advance of its final disposition; provided, however, that (a) the payment of such expenses incurred by such an Indemnitee in advance of the final disposition of such Proceeding shall be made only upon delivery to the BORG of an undertaking, by or on behalf of such Indemnitee, to repay all amounts so advanced if it should be determined ultimately by final judicial decision from which there is no appeal that such Indemnitee is not entitled to be indemnified under these Bylaws; and (b) the BORG shall not be required to advance any expenses to a person against whom the BORG directly brings a claim, in a Proceeding, alleging that such person has breached such person’s duty of loyalty to the BORG, committed an act or omission not in good faith or that involves intentional misconduct or a knowing violation of applicable Legal Requirements, or derived an improper personal benefit from a transaction.

  • 7.3. Non-Exclusivity of Rights. The rights conferred on any person in this Article 7 shall not be exclusive of any other right that such person may have or hereafter acquire under any statute, Governance Agreement, or otherwise. Additionally, nothing in this Article 7 shall limit the ability of the BORG, in its discretion, to indemnify or advance expenses to persons whom the BORG is not obligated to indemnify or advance expenses pursuant to this Article 7.

  • 7.4. Right of Indemnitee to Bring Suit.

    • 7.4.1. Right to Bring Suit. If a claim under Article 7.1 or 7.2 is not paid in full by the BORG within sixty (60) days after a written claim has been received by the BORG, except in the case of a claim for an advancement of expenses, in which case the applicable period shall be twenty (20) days, the Indemnitee may at any time thereafter bring suit against the BORG to recover the unpaid amount of the claim. If successful in whole or in part in any such suit, or in a suit brought by the BORG to recover an advancement of expenses pursuant to the terms of an undertaking, the Indemnitee shall be entitled to be paid also the expense of prosecuting or defending such suit. In (a) any suit brought by the Indemnitee to enforce a right to indemnification hereunder (but not in a suit brought by the Indemnitee to enforce a right to an advancement of expenses) it shall be a defense that, and (b) in any suit brought by the BORG to recover an advancement of expenses pursuant to the terms of an undertaking, the BORG shall be entitled to recover such expenses upon a final adjudication that, the Indemnitee has not met any applicable standard for indemnification set forth in applicable Legal Requirements or these Bylaws.
    • 7.4.2. Effect of Determination. Neither the failure of the BORG to have made a determination prior to the commencement of such suit that indemnification of the Indemnitee is proper in the circumstances because the Indemnitee has met the applicable standard of conduct set forth in applicable Legal Requirements, nor an actual determination by the BORG that the Indemnitee has not met such applicable standard of conduct, shall create a presumption that the Indemnitee has not met the applicable standard of conduct or, in the case of such a suit brought by the Indemnitee, be a defense to such suit.
    • 7.4.3. Burden of Proof. In any suit brought by the Indemnitee to enforce a right to indemnification or to an advancement of expenses hereunder, or brought by the BORG to recover an advancement of expenses pursuant to the terms of an undertaking, the burden of proving that the Indemnitee is not entitled to be indemnified, or to such advancement of expenses, under this Article 7, or otherwise, shall be on the BORG.

  • 7.5. Nature of Rights. The rights conferred upon Indemnitees in this Article 7 shall be contract rights and such rights shall continue as to an Indemnitee who has ceased to be a BORG Personnel and shall inure to the benefit of the Indemnitee’s heirs, executors and administrators. Any amendment, repeal or modification of any provision of this Article 7 that adversely affects any right of an Indemnitee or an Indemnitee’s successors shall be prospective only, and shall not adversely affect any right or protection conferred on a person pursuant to this Article 7 and existing at the time of such amendment, repeal or modification.”

<new borg name>: None

R. General Provisions

Lido Alliance: “

  • 8.4. Severability. Any term or provision of these Bylaws that is found invalid or unenforceable in any situation in any jurisdiction shall not affect the validity or enforceability of the remaining terms and provisions hereof or the validity or enforceability of the offending term or provision in any other situation or in any other jurisdiction. If a final judgment of a court of competent jurisdiction declares that any term or provision hereof is invalid or unenforceable, the court making such determination shall have the power to limit such term or provision, to delete specific words or phrases, or to replace any invalid or unenforceable term or provision with a term or provision that is valid and enforceable and that comes closest to expressing the intention of the invalid or unenforceable term or provision, and these Bylaws shall be enforceable as so modified. In the event such court does not exercise the power granted to it in the prior sentence, such court or the Board shall be empowered to replace such invalid or unenforceable term or provision with a valid and enforceable term or provision that will achieve, to the extent possible, the economic, business and other purposes of such invalid or unenforceable term or provision.

  • 8.5. Entire Agreement. These Bylaws, the Governance Agreements and any other documents or agreements referred to herein or therein constitute the entire agreement and understanding with respect to the subject matter hereof and thereof, and supersedes any and all prior negotiations, correspondence, warrants, agreements, understandings duties or obligations with respect to the subject matter hereof and thereof.

  • 8.6. Further Assurances. The BORG Personnel shall execute and deliver any further instruments or documents and to take all such further actions as may be necessary or advisable in order to carry out the intent of these Bylaws.”

<new borg name>: None