diff --git a/Archive/B2B/Inbound SOP.md b/Archive/B2B/Inbound SOP.md
deleted file mode 100644
index f465b80e..00000000
--- a/Archive/B2B/Inbound SOP.md	
+++ /dev/null
@@ -1,27 +0,0 @@
----
-tags: docs/b2b, archive
----
-1. **Initial Contact**:
-	- Respond promptly and professionally to all inbound sales inquiries.
-	- Gather relevant information about the potential customer's needs and requirements.
-	- Provide a brief overview of our DAO's mission, projects, and goals.
-2. **Product/Service Presentation**:
-	- Tailor the presentation to the specific needs and interests of the potential customer.
-	- Highlight the unique features and benefits of our projects, such as sending DNA to the moon and offering Zero G flights.
-	- Emphasize the decentralized nature of our organization and the opportunities for collaboration and community involvement.
-3. **Addressing Concerns**:
-	- Listen actively to any concerns or questions raised by the potential customer.
-	- Provide clear and accurate information to address their concerns.
-	- Offer examples and case studies to showcase the success and impact of our projects.
-4. **Pricing and Payment**:
-	- Clearly explain the pricing structure for our products or services.
-	- Provide transparency regarding any associated costs or fees.
-	- Offer flexible payment options, including the use of our decentralized governance token ($MOONEY) if applicable.
-5. **Closing the Sale**:
-	- Summarize the key points discussed during the conversation.
-	- Confirm the customer's understanding of the product/service and its value.
-	- Provide clear instructions for the next steps, such as signing up for our projects or making a purchase.
-6. **Follow-up and Relationship Building**:
-	- Send a follow-up email or message to express gratitude for the customer's interest.
-	- Provide additional resources or information if requested.
-	- Maintain regular communication to nurture the relationship and keep the customer updated on our latest developments.
\ No newline at end of file
diff --git a/Archive/B2B/Outbound SOP.md b/Archive/B2B/Outbound SOP.md
deleted file mode 100644
index 8732cd22..00000000
--- a/Archive/B2B/Outbound SOP.md	
+++ /dev/null
@@ -1,14 +0,0 @@
----
-tags:
-  - docs/b2b
-  - archive
-aliases:
----
-1. **Identify Target Market**: Research and identify businesses and organizations that align with our mission and could benefit from our space exploration projects. This includes companies involved in aerospace, research institutions, educational institutions, and other relevant industries.
-2. **Develop Sales Pitch**: Create a compelling sales pitch that highlights the unique value proposition of our projects and how they can benefit potential partners. Emphasize the decentralized nature of our organization, the open science and open hardware development principles, and the collaborative opportunities available.
-3. **Build Relationships**: Establish connections with key decision-makers within the target organizations. This can be done through networking events, conferences, online communities, and introductions from existing contacts. Cultivate relationships based on mutual interests and shared goals.
-4. **Customize Outreach**: Tailor outreach messages to each potential partner, highlighting specific aspects of our projects that align with their interests and objectives. Personalize the communication to show that we have done our research and understand their needs.
-5. **Demonstrate Value**: Provide clear and concise information about the benefits and potential impact of partnering with our organization. Highlight the opportunities for academic partnerships, engineering collaborations, and the potential for groundbreaking research and development in the lunar settlement.
-6. **Follow-up and Persistence**: Follow up with potential partners regularly to maintain engagement and address any questions or concerns they may have. Be persistent but respectful, understanding that decision-making processes may take time.
-7. **Track and Analyze**: Keep detailed records of all interactions and outcomes. Analyze the effectiveness of different outreach strategies, messaging, and follow-up approaches. Use this data to continuously improve the outbound sales process.
-8. **Collaborate with Internal Teams**: Work closely with the Space Science and Engineering working groups to gather relevant information, updates, and insights about ongoing projects. Collaborate with these teams to ensure accurate and up-to-date information is shared with potential partners.
diff --git a/Archive/Citizen NFT Owner Agreement.md b/Archive/Citizen NFT Owner Agreement.md
deleted file mode 100644
index efc31143..00000000
--- a/Archive/Citizen NFT Owner Agreement.md	
+++ /dev/null
@@ -1,84 +0,0 @@
----
-tags: docs/ticket-to-space, nft, docs/legal
-id: tts-nft-owner-agreement
-title: NFT Owner Agreement
-description: Agreements regarding ownership of the MoonDAO Ticket to Space NFT
-keywords: [NFT, Ticket-to-Space, MoonDAO, Space Travel]
-sidebar_label: NFT Owner Agreement
-sidebar_position: 3
-slug: /tts-nft-owner-agreement
----
-
-**NFT OWNER AGREEMENT**
-
-This NFT Owner Agreement (“Owner Agreement”) is entered into by and between MoonDAO DAO LLC d/b/a MoonDAO (“Licensor”) and the individual or entity that obtains a limited license in and to a MoonDAO Citizen NFT as defined below (the “Owner”), and is effective as of the date that the limited license rights in and to the MoonDAO Citizen NFT are transferred to the Owner (the “Effective Date”). This Owner Agreement shall be deemed incorporated into the MoonDAO Website Terms and Conditions (“Site Terms,” and together with this Owner Agreement, the “Agreement”), as made available on the Licensor website located at [www.moondao.com](http://www.moondao.com) (the “Site”); _provided, however,_ to the extent that anything in this Owner Agreement is inconsistent with the Site Terms, this Owner Agreement shall take precedence.
-
-OWNER ACKNOWLEDGES RECEIPT AND UNDERSTANDING OF THE AGREEMENT, AND AGREES TO BE BOUND BY ITS TERMS, IN THEIR ENTIRETY. **OWNER’S ACCEPTANCE OF A MOONDAO CITIZEN NFT SHALL BE DEEMED OWNER’S ACCEPTANCE OF, AND CONSENT TO BE GOVERNED BY, THE TERMS OF THE AGREEMENT. IF OWNER DOES NOT AGREE TO BE BOUND BY THE TERMS OF THE AGREEMENT IN THEIR ENTIRETY, THE LICENSE CONTEMPLATED HEREUNDER SHALL AUTOMATICALLY TERMINATE.**
-
-In consideration of the premises and the mutual covenants set forth below and for other good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, and intending to be bound, the parties hereto agree as follows:
-
-1. **Purchase, Licenses & Restrictions**.
-
-   1. MoonDAO Citizen NFTs. The “MoonDAO Citizen NFTs” sold or otherwise transferred to Owner pursuant to the Agreement are non-fungible tokens, the ownership of which are registered on a blockchain. Each MoonDAO Citizen NFT is associated with a single instance of a digital art file (“Digital Object”) and/or other entitlements. As detailed below, Owner may own a token, but shall have only a limited license to the Digital Object, subject to the terms and conditions of the Agreement. Owner must ensure that she/he/it obtains and maintains a functioning Coinbase®, MetaMask®, and/or WalletConnect® wallet (each, a “Wallet”) capable of accessing the MoonDAO Citizen NFTs, as well as any cryptocurrencies used to purchase and/or sell the MoonDAO Citizen NFT including, where applicable, Ether (“ETH”).
-   1. Digital Object. The Digital Object is subject to copyright and other intellectual property protections, which rights are and shall remain owned by Licensor and/or third parties.
-   1. Purchase; Payment Terms. Where a user wishes to purchase a MoonDAO Citizen NFT, that user MUST first connect her/his/its Wallet to the designated area of the Site then, upon clicking the applicable purchase button, that user’s Wallet will be charged the applicable purchase fee (the “NFT Fees”) for the MoonDAO Citizen NFT. All NFT Fees are payable in ETH. By making a purchase of a MoonDAO Citizen NFT, Owner: (a) represents that she/he/it is authorized to use the Wallet utilized in connection therewith and that any Wallet information provided is true and accurate; and (b) authorizes Licensor to charge the Fees to the applicable Wallet. Any attempt to defraud Licensor through the use of any Wallet, regardless of the outcome, or any failure by Owner to honor legitimate charges or requests for payment, will result in immediate termination of Owner’s right in and to the subject MoonDAO Citizen NFT. **ALL NFT FEES ARE FINAL AND NON-REFUNDABLE.**
-
-1. **License**.
-
-Upon a valid transfer of a MoonDAO Citizen NFT to Owner, Licensor grants Owner a limited, non-sublicensable, license to use, publish, and display the Digital Object during the Term, subject to Owner’s compliance with the terms and conditions of the Agreement including, without limitation, the restrictions in Section 1.5 below, solely for the following purposes: (a) for her/his/its own personal, non-commercial use; (b) to, after the conclusion of the Member Sweepstakes (as defined below), list the Digital Object for resale or trade as part of a marketplace that permits the purchase and sale of the MoonDAO Citizen NFTs; _provided, that_ the marketplace cryptographically verifies each MoonDAO Citizen NFT owner’s rights to display the Digital Object associated with the MoonDAO Citizen NFT to ensure that only the actual owner can display the Digital Object; and/or (c) as part of a third party website or application that permits the inclusion, involvement, or participation of MoonDAO Citizen NFTs; _provided, that_ the website/application cryptographically verifies each MoonDAO Citizen NFT owner’s rights to display the Digital Object associated with the subject MoonDAO Citizen NFT to ensure that only the actual owner can display the Digital Object; and _provided, further, that_ the Digital Object is no longer visible once the owner of the subject MoonDAO Citizen NFT leaves the website/application (the “Owner License”). The Owner license is non-transferable, except that it will automatically transfer in connection with a Permitted Transfer (defined below) of the subject MoonDAO Citizen NFT. Upon expiration of the Term (as defined below) or breach of any condition of the Agreement by Owner, all license rights shall immediately terminate.
-
-1. **License Restrictions**.
-
-The Digital Objects provided pursuant to the Agreement are licensed, not sold, and Owner receives no title to or ownership of the Digital Object(s) or any associated intellectual property rights thereto. Without limiting the foregoing, the license to the Digital Object does not grant Owner any right, title or interest in or to the individual layered files, traits or digital works associated with same (collectively, the “Layered Files”). Except for the express license granted to Owner by the Owner License, no other rights (express or implied) to the Digital Object are granted and all rights that are not specifically granted to Owner are reserved by Licensor. These reserved rights include, but are not limited to, the intellectual property rights, and publicity rights, associated with the images, names, logos, Layered Files, trademarks, copyrights, the ability to mint 3D, voxel or other versions of the MoonDAO Citizen NFTs, the smart contract code, or anything else not specifically granted by the Owner License. Without limiting the generality of the foregoing, Owner shall not, nor authorize, permit, or assist any third party to, do or attempt to do any of the following: (a) transfer a MoonDAO Citizen NFT prior to the conclusion of the Member Sweepstakes; (b) copy, modify, create derivative works from, or distribute the Digital Object or a MoonDAO Citizen NFT; (c) display the Digital Object other than as expressly licensed in Section 1.4; (d) use a MoonDAO Citizen NFT or Digital Object to advertise, market or sell a product and/or service; (e) incorporate a MoonDAO Citizen NFT or Digital Object in any videos or other media; (f) sell merchandise incorporating a MoonDAO Citizen NFT or Digital Object; (g) attempt to register any trademark, copyright, or otherwise acquire additional intellectual property rights in or to a Digital Object; (h) impose a fee or require other consideration for another to view a Digital Object; (i) use a Digital Object for its or any third party’s commercial benefit; (j) use a Digital Object to create, sell or attempt to create or sell any new cryptographic token; or (k) fractionalize, pool, rent or stake a MoonDAO Citizen NFT or Digital Object, unless done so in compliance with all applicable jurisdictional laws, rules or regulations. Moreover, Owner agrees not to remove any copyright or other legal notices associated with a MoonDAO Citizen NFT or Digital Object. Failure to comply with the conditions set forth in Sections 1.4 and 1.5 hereof constitutes a material breach of the Agreement.
-
-1. **Membership and Entitlements**.
-
-   1. Membership Description. Subject to the disclaimers, restrictions and conditions set forth herein and elsewhere in the Agreement, the acquisition of a MoonDAO Citizen NFT shall entitle the current Owner thereof to become a MoonDAO community member (“Member”). MoonDAO community Membership provides each Member with: (a) access to certain Members-only or MoonDAO Citizen's Discord® channel (“Member Discord Channel”); (b) access to the promotional offers made available exclusively to Members (“Member Promotions”), pursuant to the rules applicable to each such Member Promotion; (c) access to certain merchandise, products and/or services made available exclusively to Members (“Member Product Offers”); (d) access to live events made available exclusively to Members (“Member Live Events”); and (e) any other entitlement(s) as may be offered by the Licensor, in its sole discretion, from time-to-time (“Other Member Entitlement(s)”), each subject to availability and the restrictions set forth in Subsection 2.2 below and as otherwise communicated by Licensor from time-to-time. As used herein, the Member Discord Channel, Member Promotions, Member Product Offers, Member Live Events and Other Member Entitlements, are each an “Entitlement,” and collectively, the “Entitlements.”
-   1. Restrictions.
-      1. _Redemption_. Certain Entitlements may be limited to one (1) redemption (such as entry in the Member Sweepstakes). In such circumstances, and notwithstanding a valid transfer of ownership of a MoonDAO Citizen NFT, once such an Entitlement has been redeemed by an Owner of the subject MoonDAO Citizen NFT, no subsequent Owner of that same NFT shall have the right to redeem such Entitlement.
-      1. _Disclaimers and Restrictions_. The Entitlements shall at all times remain subject to the disclaimers, terms and conditions set forth in the Terms, and other parts of the Agreement, as well as any terms and conditions set forth on the Site, or as otherwise communicated to Owner by Licensor.
-      1. _Other Member Entitlement(s)_. Licensor reserves the right to offer Other Member Entitlements associated with MoonDAO Citizen NFTs, the redemption terms and restrictions for which will be published on the Site or otherwise communicated to Owner by Licensor.
-      1. _General_. No Entitlement may be licensed, sold, transferred, rented or assigned, separate and apart from a Permitted Transfer of ownership of a MoonDAO Citizen NFT. The Entitlements have no cash value. Redemption of the Entitlement(s) are subject to availability, and Licensor reserves the right to modify, reschedule and/or cancel each Entitlement, in its sole discretion, including for circumstances beyond Licensor’s control. For purposes of clarity, Owner is not required to exchange the MoonDAO Citizen NFT(s) in order to redeem any Entitlement, and redemption of an Entitlement shall have no bearing on Owner’s ownership of any MoonDAO Citizen NFT.
-   1. Procedure: Owner may claim the Entitlement(s) by following the procedures detailed on the Site, or as otherwise communicated to Owner by Licensor.
-
-1. **Warranty; Disclaimers and Assumption of Risk**.
-   1. Owner Warranty. Owner represents and warrants that Owner: (a) is at least the age of majority in Owner’s state of residence (which is typically eighteen (18) in most U.S. states), is a United States citizen, and has the legal capacity to enter into the Agreement; (b) will use each MoonDAO Citizen NFT, including the Digital Object associated therewith, only for lawful purposes and in accordance with the Agreement and all applicable laws, rules and regulations; and (c) will not use the MoonDAO Citizen NFT, including the Digital Object associated therewith, to violate any law, regulation or ordinance or any right of Licensor or any third party, including, without limitation, any right of privacy, publicity, copyright, trademark and/or patent.
-   1. DISCLAIMER; ASSUMPTION OF RISK. THE MOONDAO CITIZEN NFTS, ASSOCIATED DIGITAL OBJECTS AND ENTITLEMENTS ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS, WITHOUT WARRANTY OR SUPPORT OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR AND ITS MEMBERS, OFFICERS, EMPLOYEES, DIRECTORS, SHAREHOLDERS, PARENTS, SUBSIDIARIES, AFFILIATES, AGENTS, AND LICENSORS (COLLECTIVELY, “COVERED PARTIES”) DISCLAIM ANY AND ALL WARRANTIES, CONDITIONS, AND REPRESENTATIONS OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING THOSE RELATED TO MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, QUIET ENJOYMENT AND NON-INFRINGEMENT AND ANY WARRANTIES ARISING OUT OF COURSE OF DEALING OR USAGE OF TRADE.
-
-WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR MAKES NO WARRANTY THAT A MOONDAO CITIZEN NFT, THE ASSOCIATED DIGITAL OBJECT AND/OR ANY ENTITLEMENT WILL MEET OWNER’S REQUIREMENTS OR BE AVAILABLE ON AN UNINTERRUPTED, SECURE, OR ERROR-FREE BASIS. FURTHER, LICENSOR PROVIDES NO WARRANTY REGARDING, AND WILL HAVE NO RESPONSIBILITY FOR, ANY CLAIM ARISING OUT OF: (a) A MODIFICATION OF A MoonDAO CITIZEN NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT MADE BY ANYONE OTHER THAN LICENSOR, UNLESS LICENSOR APPROVES SUCH MODIFICATION IN WRITING, IN ADVANCE; (b) OWNER’S MISUSE OF, OR MISREPRESENTATION REGARDING, A MOONDAO CITIZEN NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT; (c) THE FLUCTUATION IN VALUE OF A MOONDAO CITIZEN NFT; AND/OR (d) ANY TECHNOLOGY THAT FAILS TO PERFORM OR CEASES TO EXIST.
-
-FURTHER, OWNER UNDERSTANDS AND AGREES THAT OWNERSHIP OF, AND TRANSACTIONS INVOLVING, A MOONDAO CITIZEN NFT AND/OR ENTITLEMENT MAY REQUIRE OR RELY ON: (i) THIRD-PARTY TECHNOLOGY AND/OR PLATFORMS INCLUDING, WITHOUT LIMITATION, DIGITAL WALLETS, BLOCKCHAINS OR RELATED TECHNOLOGY, SMART CONTRACTS, INTERNET SERVICE PROVIDERS, MARKETPLACES, EQUIPMENT OR OTHER INFRASTRUCTURE (COLLECTIVELY, “THIRD PARTY TECHNOLOGY”); AND/OR (ii) THIRD-PARTY SERVICE PROVIDERS, SUCH AS BLUE ORIGIN TEXAS, LLC (“BLUE ORIGIN”), AS WELL AS ITS SPACECRAFT, TECHNOLOGY AND TRANSPORTATION SERVICES (COLLECTIVELY, “THIRD PARTY SERVICES,” AND TOGETHER WITH THE THIRD PARTY TECHNOLOGY, THE “THIRD PARTY OFFERINGS”). OWNER UNDERSTANDS AND AGREES THAT THE EXISTENCE AND PERFORMANCE OF THIRD PARTY OFFERINGS ARE OUTSIDE OF LICENSOR’S CONTROL. TO THE MAXIMUM EXTENT PERMISSIBLE UNDER APPLICABLE LAW, LICENSOR DISCLAIMS ALL LIABILITY FOR THE USE, UNAVAILABILITY AND/OR FAILURE OF ANY THIRD PARTY OFFERINGS.
-
-**The MoonDAO Citizen NFTs are not intended as investment vehicles. Licensor makes absolutely no promise or guarantee that the MoonDAO Citizen NFTs will increase in value, or maintain the same value as the amount Owner paid to purchase same. Owner understands and agrees that the MoonDAO Citizen NFTs have no inherent monetary value (other than with respect to Membership benefits and Entitlements). Please be aware that the prices of MoonDAO Citizen NFTs are extremely volatile, and price fluctuations in ETH could impact the value of MoonDAO Citizen NFTs, both positively and negatively. Given this volatility, MoonDAO Citizen NFTs should not be considered investments. Owner assumes all risks in connection therewith. No information and/or content made available by and/or through the Site or otherwise by Licensor is or should be considered advice or an invitation to enter into an agreement for any investment purpose. Further, no element of the MoonDAO Citizen NFTs qualifies or is intended to be an offering of securities in any jurisdiction, nor does it constitute an offer or an invitation to purchase shares, securities or other financial products. Owner is solely and exclusively responsible for assuring that the purchase and sale of MoonDAO Citizen NFTs, and the use of cryptocurrencies, complies the with laws and regulations in Owner’s jurisdiction. Owner assumes all risks associated with using an Internet-based cryptocurrency including, but not limited to, the risk of hardware, software and Internet connections, the risk of malicious software introduction, and the risk that third parties may obtain unauthorized access to information stored within Owner’s Wallet. NFTs, cryptocurrencies and blockchain technology are relatively new and the regulatory landscape is unsettled. New regulations could negatively impact such technologies which may, in turn, impact the value of Owner's MoonDAO Citizen NFTs. Owner understands and accepts all risk in that regard. Without limiting the foregoing, Owner assumes all responsibility for any adverse effects of disruptions or other issues impacting ETH or the Ethereum platform.**
-
-1. **Limitation of Liability**.
-   1. Liability Cap. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE COVERED PARTIES’ CUMULATIVE LIABILITY UNDER THE AGREEMENT, FOR ALL CAUSES OF ACTION AND ALL THEORIES OF LIABILITY, WILL BE LIMITED TO AND WILL NOT EXCEED THE GREATER OF: (a) THE AMOUNT PAID TO LICENSOR FOR THE INITIAL SALE OF THE SUBJECT MOONDAO CITIZEN NFT(S); OR (b) ONE HUNDRED DOLLARS ($100).
-   1. Excluded Damages. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL THE COVERED PARTIES BE LIABLE UNDER ANY CLAIM ARISING OUT OF OR RELATED TO THE AGREEMENT FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR OTHER NONDIRECT DAMAGES OF ANY KIND OR FOR ANY SPECIAL, PUNITIVE OR SIMILAR DAMAGES OR EXPENSES (INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR OTHER ECONOMIC LOSS, LOST REIMBURSEMENTS, LOST DATA, OR LOST SAVINGS), EVEN IF THE APPLICABLE COVERED PARTY(IES) WAS/WERE ADVISED OF THE POSSIBILITY OF THE OCCURRENCE OF SUCH DAMAGES.
-   1. Additional Terms. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LIABILITIES LIMITED BY THIS SECTION 4 APPLY: (a) TO LIABILITY FOR NEGLIGENCE; (b) REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, STRICT PRODUCT LIABILITY, OR OTHERWISE; (c) EVEN IF THE APPLICABLE COVERED PARTY(IES) IS/ARE ADVISED IN ADVANCE OF THE POSSIBILITY OF THE DAMAGES IN QUESTION AND EVEN IF SUCH DAMAGES WERE FORESEEABLE; AND (d) EVEN IF OWNER’S REMEDIES FAIL OF THEIR ESSENTIAL PURPOSE. WITHOUT LIMITING THE FOREGOING, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE COVERED PARTIES WILL NOT BE LIABLE TO OWNER FOR ANY USE OF A MOONDAO CITIZEN NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT INCLUDING, BUT NOT LIMITED TO, ANY LOSSES, DAMAGES OR CLAIMS ARISING FROM: (i) USER ERROR, SUCH AS FORGOTTEN PASSWORDS, INCORRECTLY CONSTRUCTED TRANSACTIONS, OR MISTYPED WALLET ADDRESSES; (ii) SERVER FAILURE OR DATA LOSS; (iii) CORRUPTED CRYPTOCURRENCY WALLET FILES; (iv) UNAUTHORIZED ACCESS TO A MOONDAO CITIZEN NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT; (v) ANY UNAUTHORIZED THIRD PARTY ACTIVITIES INCLUDING, WITHOUT LIMITATION, THE USE OF VIRUSES, PHISHING, BRUTE FORCING OR OTHER MEANS OF ATTACK AGAINST A BLOCKCHAIN NETWORK UNDERLYING A MOONDAO CITIZEN NFT AND/OR ASSOCIATED DIGITAL OBJECT; (vi) OWNER’S FAILURE TO MAINTAIN THE SECURITY OF HER/HIS/ITS WALLET’S PRIVATE KEY; (vii) ANY UNINTENDED TRANSFER OR LOSS OF A MOONDAO CITIZEN NFT, ENTITLEMENT AND/OR ASSOCIATED DIGITAL OBJECT; (viii) THE FAILURE TO REALIZE ANY SPECIFIC INVESTMENT INCOME, REVENUE OR OTHER FINANCIAL OUTCOME; (ix) THE FAILURE TO OBTAIN ACCESS TO ANY ENTITLEMENT; (x) THE USE, UNAVAILABILITY AND/OR FAILURE OF ANY THIRD PARTY OFFERINGS INCLUDING, WITHOUT LIMITATION, ANY BLUE ORIGIN OFFERING; AND/OR (xi) OWNER’S INABILITY TO DEMONSTRATE OWNERSHIP AND/OR CONTROL OF A MOONDAO CITIZEN NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT. If applicable law limits the application of the provisions of this Section 4, Licensor’s liability will be limited to the maximum extent permissible.
-1. **Indemnity**.
-
-   Owner shall indemnify, defend and hold harmless the Covered Parties from and against any and all claims, demands, causes of action, liabilities, damages, penalties, losses, fines, costs and expenses (including reasonable attorneys' fees, legal costs and court costs, which shall be reimbursed as incurred) arising out of, related to, or in connection with, or alleging: (a) Owner’s breach of any provision contained in the Agreement, including, but not limited to, Owner’s failure to comply with the licensing conditions set forth in Section 1 hereof; (b) Owner’s use of a MoonDAO Citizen NFT, associated Digital Object and/or Entitlement in any way that violates any applicable laws, rules or regulations; (c) Owner’s unauthorized transfer, or purported transfer, of a MoonDAO Citizen NFT, associated Digital Object and/or Entitlement; or (d) Owner’s improper and/or unauthorized exercise of any license rights in and/or to a MoonDAO Citizen NFT, associated Digital Object and/or Entitlement.
-
-1. **Term & Termination**.
-   1. Term. This Owner Agreement shall continue until terminated pursuant to the terms of this Owner Agreement (the “Term”).
-   1. Termination for Transfer*.* The Owner License applies only to the extent that Owner continues to own the subject NFT. If, at any time, the Owner sells, trades, donates, gives away, transfers, purports to transfer, or otherwise disposes of the subject MoonDAO Citizen NFT for any reason, this Owner Agreement, including, without limitation, the Owner License granted to Owner hereunder, will immediately terminate without the requirement of notice, and Owner will have no further rights in or to the subject MoonDAO Citizen NFT, Digital Object, or any Entitlement(s).
-   1. Termination for Cause. Licensor may terminate this Owner Agreement for Owner’s material breach of any term of the Agreement by written notice specifying in detail the nature of the breach, effective in fifteen (15) days unless the Owner first cures such breach, or effective immediately if the breach is not subject to cure.
-   1. Effects of Termination. Upon termination of this Owner Agreement, Owner shall cease all use of the Digital Object and delete, destroy, or return all copies of the Digital Object in its possession or control. Owner acknowledges that any use of the Digital Object upon termination of the Owner License shall be deemed intellectual property infringement. Any provision of this Owner Agreement that must survive to fulfill its essential purpose will survive termination or expiration.
-1. **Miscellaneous**.
-   1. Independent Contractors. The parties are independent contractors and shall so represent themselves in all respects. Neither party is the agent of the other, and neither may make commitments on the other’s behalf.
-   1. Force Majeure. No delay, failure, or default, other than a failure to pay fees when due, will constitute a breach of the Agreement to the extent caused by acts of war, terrorism, hurricanes, earthquakes, epidemics, other acts of God or of nature, strikes or other labor disputes, riots or other acts of civil disorder, embargoes, COVID-19 or any similar virus, disease and/or pandemic, as well as any private sector or governmental responses to any of the foregoing, or other causes beyond the performing party’s reasonable control.
-   1. Assignment & Successors. This Owner Agreement is not assignable or transferable by Owner, except pursuant to a Permitted Transfer of ownership of a MoonDAO Citizen NFT to a Secondary Acquirer, in which case the terms and conditions hereof will transfer and be binding upon and will inure to the benefit of the parties and their permitted successors and assigns. Any purported assignment or transfer by Owner in violation of this Section 7.3 is null and void.
-   1. Severability. To the extent permitted by applicable law, the parties waive any provision of law that would render any clause of the Agreement invalid or otherwise unenforceable in any respect. If any provision of the Agreement is held to be invalid or otherwise unenforceable, such provision will be interpreted to fulfill its intended purpose to the maximum extent permitted by applicable law, and the remaining provisions of the Agreement will continue in full force and effect.
-   1. No Waiver. Neither party will be deemed to have waived any of its rights under the Agreement by lapse of time or by any statement or representation other than by an authorized representative in an explicit written waiver. No waiver of a breach of the Agreement will constitute a waiver of any other breach of the Agreement.
-
-1. **Dispute Resolution Provisions**:
-The Agreement shall be treated as though it were executed and performed in New York, NY and shall be governed by and construed in accordance with the laws of the State of New York (without regard to conflict of law principles). **The parties (and Covered Parties) hereby agree to arbitrate all claims that may arise under and/or relate to the MoonDAO Citizen NFTs, Entitlements, Digital Objects and/or the Agreement. Without limiting the foregoing, should a dispute arise between the parties/any Covered Parties including, without limitation, any matter concerning the MoonDAO Citizen NFTs, Entitlements, Digital Objects, the terms and conditions of the Agreement or the breach of same by any party hereto: (a) the parties/Covered Parties agree to submit their dispute for resolution by arbitration before the American Arbitration Association (“AAA”) in New York, NY, in accordance with the then current Commercial Arbitration rules of the AAA; and (b) Owner agrees to first commence a formal dispute proceeding by completing and submitting an Initial Dispute Notice which can be found [here](/tts-dispute-notice). The Covered Party(ies) named in Owner’s Initial Dispute Notice (collectively, the “Named Parties”) may choose to provide Owner with a final written settlement offer after receiving Owner’s Initial Dispute Notice (“Final Settlement Offer”). If the applicable Named Party(ies) provide(s) Owner with a Final Settlement Offer and Owner does not accept it, or such Named Party(ies) cannot otherwise satisfactorily resolve Owner's dispute and Owner wishes to proceed, Owner must submit Owner’s dispute for resolution by arbitration before the AAA, in Owner’s county of residence, by filing a separate Demand for Arbitration, which is available [here](https://adr.org/sites/default/files/Consumer_Demand_for_Arbitration_Form_1.pdf). For claims of Ten Thousand Dollars ($10,000.00) or less, Owner can choose whether the arbitration proceeds in person, by telephone or based only on submissions. If the arbitrator awards Owner relief that is greater than the applicable Final Settlement Offer, then the Named Party(ies) will pay all filing, administration and arbitrator fees associated with the arbitration and, if Owner retained an attorney to represent Owner in connection with the arbitration, the Named Party(ies) will reimburse any reasonable attorneys’ fees that Owner’s attorney accrued for investigating, preparing and pursuing the claim in arbitration. Any award rendered shall be final and conclusive to the parties and a judgment thereon may be entered in any court of competent jurisdiction. Although the Named Party(ies) may have a right to an award of attorneys’ fees and expenses if Named Party(ies) prevail(s) in arbitration, the Named Party(ies) will not seek such an award from Owner unless the arbitrator determines that Owner's claim was frivolous.**
-
-**To the extent permitted by law, Owner agrees that Owner will not bring, join or participate in any class action lawsuit as to any claim, dispute or controversy that Owner may have against any of the Covered Parties. Owner agrees to the entry of injunctive relief to stop such a lawsuit or to remove Owner as a participant in the suit. Owner agrees to pay the attorney's fees and court costs that any Covered Party incurs in seeking such relief. This provision preventing Owner from bringing, joining or participating in class action lawsuits: (i) does not constitute a waiver of any of Owner's rights or remedies to pursue a claim individually and not as a class action in binding arbitration as provided above; and (ii) is an independent agreement. Owner may opt-out of these dispute resolution provisions by providing written notice of Owner's decision within thirty (30) days of the date that Owner first purchases a MoonDAO Citizen NFT.**
-
-1. Entire Agreement. This Owner Agreement, together with the Site Terms and the documents referenced therein, sets forth the entire agreement of the parties and supersedes all prior or contemporaneous writings, negotiations, and discussions with respect to its subject matter. Neither party has relied upon any such prior or contemporaneous communications.
-2. Amendment. The Agreement may not be amended in any way except through a written agreement by authorized representatives of the Licensor and the MoonDAO Citizen NFT Owner.
-3. Headings. All section headings and captions have been inserted for convenience only and shall not affect the interpretation of the Agreement.
-
-4. Drafting. Each party providing Electronic Acceptance (as defined below) to the terms of the Agreement agrees that it has fully participated in the drafting of the Agreement and that no party shall be deemed to be the drafting party of the Agreement.
-5. Electronic Signatures. Owner acknowledges and agrees that Owner accepts the Agreement via electronic means rather than via traditional handwritten signature (“Electronic Acceptance”). Owner acknowledges and agrees that by clicking on the “submit” button, or taking such other action as may be designated by Licensor as a means of accepting the Agreement, Owner is submitting a legally binding electronic signature and is entering into a legally binding contract. Owner acknowledges that Owner’s electronic submission constitutes Owner’s agreement and intent to be bound by the Agreement. Pursuant to any and all applicable statutes, regulations, rules, ordinances or other laws including, without limitation, the United States Electronic Signatures in Global and National Commerce Act, P.L. 106-229 (the “E-Sign Act”) and other similar state and federal statutes, OWNER HEREBY AGREES TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS AND OTHER RECORDS AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED THROUGH THE SITE AND/OR ANY OTHER ONLINE PLATFORMS AND/OR SERVICES OPERATED BY LICENSOR. Further, Owner hereby waives any rights and/or requirements under any statutes, regulations, rules, ordinances or other law in any jurisdiction which requires an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by other than electronic means. Owner acknowledges and agrees that it has the ability to print information delivered to Owner electronically, or otherwise knows how to store that information in a way that ensures that it remains accessible to Owner in unchanged form. {00136579;1}
diff --git a/Archive/Docs Quickstart.md b/Archive/Docs Quickstart.md
deleted file mode 100644
index 21459271..00000000
--- a/Archive/Docs Quickstart.md	
+++ /dev/null
@@ -1,38 +0,0 @@
----
-tags:
-  - docs/onboarding
----
-MoonDAO's documentation, planning, project notes, and other reference material is organized in an [Obsidian vault](https://help.obsidian.md/Home). This vault is the source data for [docs.moondao.com](https://docs.moondao.com) through [Obsidian Publish](https://obsidian.md/publish). As an Obsidian vault, all documentation is saved as plain-text files styled with [a flavor of Markdown syntax](https://help.obsidian.md/Editing+and+formatting/Obsidian+Flavored+Markdown).
-
-The source files for [docs.moondao.com](https://docs.moondao.com) and other archived documentation are publicly available at [github.com/Official-MoonDao/moondao-vault](https://github.com/Official-MoonDao/moondao-vault).
-# Using the vault
-The vault is best experienced locally with the Obsidian app.
-1. Clone or fork this repository `git clone git@github.com:Official-MoonDao/moondao-vault.git`
-2. [Download and install Obsidian](https://help.obsidian.md/Getting+started/Download+and+install+Obsidian)
-3. Start Obsidian, choose `Open folder as vault` and select the `moondao-vault` directory from step 1.
-## Recommended Plugins
-For the best experience, enable the recommended plugins.
-### Core Plugins
-The following [core plugins](https://help.obsidian.md/Plugins/Core+plugins) are recommended:
-- [Backlinks](https://help.obsidian.md/Plugins/Backlinks)
-- [Bookmarks](https://help.obsidian.md/Plugins/Bookmarks)
-- [Graph view](https://help.obsidian.md/Plugins/Graph+view)
-- [Outgoing links](https://help.obsidian.md/Plugins/Outgoing+links)
-- [Sync](https://help.obsidian.md/Obsidian+Sync/Introduction+to+Obsidian+Sync)
-- [Templates](https://help.obsidian.md/Plugins/Templates)
-### Community Plugins
-The following [community plugins](https://obsidian.md/plugins) are recommended:
-- [Dataview](https://obsidian.md/plugins?id=dataview)
-- [Obsidian Git](https://obsidian.md/plugins?id=obsidian-git)
-- [Plugin Update Tracker](https://obsidian.md/plugins?id=obsidian-plugin-update-tracker)
-
-Be sure to [turn on community plugins](https://help.obsidian.md/Extending+Obsidian/Community+plugins) in your main settings.
-## Keeping your vault up to date
-The [Obsidian Git](https://github.com/denolehov/obsidian-git) plugin streamlines automatic commits and syncing to the remote branch.
-The vault must be set up as a git repository to use this plugin. If you cloned or forked the repo from GitHub, you're all set.
-
-Nearly all the regular git practices have corresponding commands in Obsidian from the plugin. Pull changes from the main branch with Command Palette → `Obsidian Git: Pull`.
-# Contributing to the docs
-The documentation vault and website are decoupled. Changes to the vault's source files only propagate to the site through a manual Publish step.
-## Submitting changes to the vault
-The `main` branch is protected. All changes must be submitted as [Pull Requests](https://github.com/Official-MoonDao/moondao-vault/pulls) into `main`.
diff --git a/Archive/Entity NFT Owner Agreement.md b/Archive/Entity NFT Owner Agreement.md
deleted file mode 100644
index 9f986280..00000000
--- a/Archive/Entity NFT Owner Agreement.md	
+++ /dev/null
@@ -1,84 +0,0 @@
----
-tags: docs/ticket-to-space, nft, docs/legal
-id: tts-nft-owner-agreement
-title: NFT Owner Agreement
-description: Agreements regarding ownership of the MoonDAO Ticket to Space NFT
-keywords: [NFT, Ticket-to-Space, MoonDAO, Space Travel]
-sidebar_label: NFT Owner Agreement
-sidebar_position: 3
-slug: /tts-nft-owner-agreement
----
-
-**NFT OWNER AGREEMENT**
-
-This NFT Owner Agreement (“Owner Agreement”) is entered into by and between MoonDAO DAO LLC d/b/a MoonDAO (“Licensor”) and the individual or entity that obtains a limited license in and to a MoonDAO Entity NFT as defined below (the “Owner”), and is effective as of the date that the limited license rights in and to the MoonDAO Entity NFT are transferred to the Owner (the “Effective Date”). This Owner Agreement shall be deemed incorporated into the MoonDAO Website Terms and Conditions (“Site Terms,” and together with this Owner Agreement, the “Agreement”), as made available on the Licensor website located at [www.moondao.com](http://www.moondao.com) (the “Site”); _provided, however,_ to the extent that anything in this Owner Agreement is inconsistent with the Site Terms, this Owner Agreement shall take precedence.
-
-OWNER ACKNOWLEDGES RECEIPT AND UNDERSTANDING OF THE AGREEMENT, AND AGREES TO BE BOUND BY ITS TERMS, IN THEIR ENTIRETY. **OWNER’S ACCEPTANCE OF A MOONDAO ENTITY NFT SHALL BE DEEMED OWNER’S ACCEPTANCE OF, AND CONSENT TO BE GOVERNED BY, THE TERMS OF THE AGREEMENT. IF OWNER DOES NOT AGREE TO BE BOUND BY THE TERMS OF THE AGREEMENT IN THEIR ENTIRETY, THE LICENSE CONTEMPLATED HEREUNDER SHALL AUTOMATICALLY TERMINATE.**
-
-In consideration of the premises and the mutual covenants set forth below and for other good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, and intending to be bound, the parties hereto agree as follows:
-
-1. **Purchase, Licenses & Restrictions**.
-
-   1. MoonDAO Entity NFTs. The “MoonDAO Entity NFTs” sold or otherwise transferred to Owner pursuant to the Agreement are non-fungible tokens, the ownership of which are registered on a blockchain. Each MoonDAO Entity NFT is associated with a single instance of a digital art file (“Digital Object”) and/or other entitlements. As detailed below, Owner may own a token, but shall have only a limited license to the Digital Object, subject to the terms and conditions of the Agreement. Owner must ensure that she/he/it obtains and maintains a functioning Coinbase®, MetaMask®, and/or WalletConnect® wallet (each, a “Wallet”) capable of accessing the MoonDAO Entity NFTs, as well as any cryptocurrencies used to purchase and/or sell the MoonDAO Entity NFT including, where applicable, Ether (“ETH”).
-   1. Digital Object. The Digital Object is subject to copyright and other intellectual property protections, which rights are and shall remain owned by Licensor and/or third parties.
-   1. Purchase; Payment Terms. Where a user wishes to purchase a MoonDAO Entity NFT, that user MUST first connect her/his/its Wallet to the designated area of the Site then, upon clicking the applicable purchase button, that user’s Wallet will be charged the applicable purchase fee (the “NFT Fees”) for the MoonDAO Entity NFT. All NFT Fees are payable in ETH. By making a purchase of a MoonDAO Entity NFT, Owner: (a) represents that she/he/it is authorized to use the Wallet utilized in connection therewith and that any Wallet information provided is true and accurate; and (b) authorizes Licensor to charge the Fees to the applicable Wallet. Any attempt to defraud Licensor through the use of any Wallet, regardless of the outcome, or any failure by Owner to honor legitimate charges or requests for payment, will result in immediate termination of Owner’s right in and to the subject MoonDAO Entity NFT. **ALL NFT FEES ARE FINAL AND NON-REFUNDABLE.**
-
-1. **License**.
-
-Upon a valid transfer of a MoonDAO Entity NFT to Owner, Licensor grants Owner a limited, non-sublicensable, license to use, publish, and display the Digital Object during the Term, subject to Owner’s compliance with the terms and conditions of the Agreement including, without limitation, the restrictions in Section 1.5 below, solely for the following purposes: (a) for her/his/its own personal, non-commercial use; (b) to, after the conclusion of the Member Sweepstakes (as defined below), list the Digital Object for resale or trade as part of a marketplace that permits the purchase and sale of the MoonDAO Entity NFTs; _provided, that_ the marketplace cryptographically verifies each MoonDAO Entity NFT owner’s rights to display the Digital Object associated with the MoonDAO Entity NFT to ensure that only the actual owner can display the Digital Object; and/or (c) as part of a third party website or application that permits the inclusion, involvement, or participation of MoonDAO Entity NFTs; _provided, that_ the website/application cryptographically verifies each MoonDAO Entity NFT owner’s rights to display the Digital Object associated with the subject MoonDAO Entity NFT to ensure that only the actual owner can display the Digital Object; and _provided, further, that_ the Digital Object is no longer visible once the owner of the subject MoonDAO Entity NFT leaves the website/application (the “Owner License”). The Owner license is non-transferable, except that it will automatically transfer in connection with a Permitted Transfer (defined below) of the subject MoonDAO Entity NFT. Upon expiration of the Term (as defined below) or breach of any condition of the Agreement by Owner, all license rights shall immediately terminate.
-
-1. **License Restrictions**.
-
-The Digital Objects provided pursuant to the Agreement are licensed, not sold, and Owner receives no title to or ownership of the Digital Object(s) or any associated intellectual property rights thereto. Without limiting the foregoing, the license to the Digital Object does not grant Owner any right, title or interest in or to the individual layered files, traits or digital works associated with same (collectively, the “Layered Files”). Except for the express license granted to Owner by the Owner License, no other rights (express or implied) to the Digital Object are granted and all rights that are not specifically granted to Owner are reserved by Licensor. These reserved rights include, but are not limited to, the intellectual property rights, and publicity rights, associated with the images, names, logos, Layered Files, trademarks, copyrights, the ability to mint 3D, voxel or other versions of the MoonDAO Entity NFTs, the smart contract code, or anything else not specifically granted by the Owner License. Without limiting the generality of the foregoing, Owner shall not, nor authorize, permit, or assist any third party to, do or attempt to do any of the following: (a) transfer a MoonDAO Entity NFT prior to the conclusion of the Member Sweepstakes; (b) copy, modify, create derivative works from, or distribute the Digital Object or a MoonDAO Entity NFT; (c) display the Digital Object other than as expressly licensed in Section 1.4; (d) use a MoonDAO Entity NFT or Digital Object to advertise, market or sell a product and/or service; (e) incorporate a MoonDAO Entity NFT or Digital Object in any videos or other media; (f) sell merchandise incorporating a MoonDAO Entity NFT or Digital Object; (g) attempt to register any trademark, copyright, or otherwise acquire additional intellectual property rights in or to a Digital Object; (h) impose a fee or require other consideration for another to view a Digital Object; (i) use a Digital Object for its or any third party’s commercial benefit; (j) use a Digital Object to create, sell or attempt to create or sell any new cryptographic token; or (k) fractionalize, pool, rent or stake a MoonDAO Entity NFT or Digital Object, unless done so in compliance with all applicable jurisdictional laws, rules or regulations. Moreover, Owner agrees not to remove any copyright or other legal notices associated with a MoonDAO Entity NFT or Digital Object. Failure to comply with the conditions set forth in Sections 1.4 and 1.5 hereof constitutes a material breach of the Agreement.
-
-1. **Membership and Entitlements**.
-
-   1. Membership Description. Subject to the disclaimers, restrictions and conditions set forth herein and elsewhere in the Agreement, the acquisition of a MoonDAO Entity NFT shall entitle the current Owner thereof to become a MoonDAO community member (“Member”). MoonDAO community Membership provides each Member with: (a) access to certain Members-only or MoonDAO Entity's Discord® channel (“Member Discord Channel”); (b) access to the promotional offers made available exclusively to Members (“Member Promotions”), pursuant to the rules applicable to each such Member Promotion; (c) access to certain merchandise, products and/or services made available exclusively to Members (“Member Product Offers”); (d) access to live events made available exclusively to Members (“Member Live Events”); and (e) any other entitlement(s) as may be offered by the Licensor, in its sole discretion, from time-to-time (“Other Member Entitlement(s)”), each subject to availability and the restrictions set forth in Subsection 2.2 below and as otherwise communicated by Licensor from time-to-time. As used herein, the Member Discord Channel, Member Promotions, Member Product Offers, Member Live Events and Other Member Entitlements, are each an “Entitlement,” and collectively, the “Entitlements.”
-   1. Restrictions.
-      1. _Redemption_. Certain Entitlements may be limited to one (1) redemption (such as entry in the Member Sweepstakes). In such circumstances, and notwithstanding a valid transfer of ownership of a MoonDAO Entity NFT, once such an Entitlement has been redeemed by an Owner of the subject MoonDAO Entity NFT, no subsequent Owner of that same NFT shall have the right to redeem such Entitlement.
-      1. _Disclaimers and Restrictions_. The Entitlements shall at all times remain subject to the disclaimers, terms and conditions set forth in the Terms, and other parts of the Agreement, as well as any terms and conditions set forth on the Site, or as otherwise communicated to Owner by Licensor.
-      1. _Other Member Entitlement(s)_. Licensor reserves the right to offer Other Member Entitlements associated with MoonDAO Entity NFTs, the redemption terms and restrictions for which will be published on the Site or otherwise communicated to Owner by Licensor.
-      1. _General_. No Entitlement may be licensed, sold, transferred, rented or assigned, separate and apart from a Permitted Transfer of ownership of a MoonDAO Entity NFT. The Entitlements have no cash value. Redemption of the Entitlement(s) are subject to availability, and Licensor reserves the right to modify, reschedule and/or cancel each Entitlement, in its sole discretion, including for circumstances beyond Licensor’s control. For purposes of clarity, Owner is not required to exchange the MoonDAO Entity NFT(s) in order to redeem any Entitlement, and redemption of an Entitlement shall have no bearing on Owner’s ownership of any MoonDAO Entity NFT.
-   1. Procedure: Owner may claim the Entitlement(s) by following the procedures detailed on the Site, or as otherwise communicated to Owner by Licensor.
-
-1. **Warranty; Disclaimers and Assumption of Risk**.
-   1. Owner Warranty. Owner represents and warrants that Owner: (a) is at least the age of majority in Owner’s state of residence (which is typically eighteen (18) in most U.S. states), is a United States citizen, and has the legal capacity to enter into the Agreement; (b) will use each MoonDAO Entity NFT, including the Digital Object associated therewith, only for lawful purposes and in accordance with the Agreement and all applicable laws, rules and regulations; and (c) will not use the MoonDAO Entity NFT, including the Digital Object associated therewith, to violate any law, regulation or ordinance or any right of Licensor or any third party, including, without limitation, any right of privacy, publicity, copyright, trademark and/or patent.
-   1. DISCLAIMER; ASSUMPTION OF RISK. THE MOONDAO ENTITY NFTS, ASSOCIATED DIGITAL OBJECTS AND ENTITLEMENTS ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS, WITHOUT WARRANTY OR SUPPORT OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR AND ITS MEMBERS, OFFICERS, EMPLOYEES, DIRECTORS, SHAREHOLDERS, PARENTS, SUBSIDIARIES, AFFILIATES, AGENTS, AND LICENSORS (COLLECTIVELY, “COVERED PARTIES”) DISCLAIM ANY AND ALL WARRANTIES, CONDITIONS, AND REPRESENTATIONS OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING THOSE RELATED TO MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, QUIET ENJOYMENT AND NON-INFRINGEMENT AND ANY WARRANTIES ARISING OUT OF COURSE OF DEALING OR USAGE OF TRADE.
-
-WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR MAKES NO WARRANTY THAT A MOONDAO ENTITY NFT, THE ASSOCIATED DIGITAL OBJECT AND/OR ANY ENTITLEMENT WILL MEET OWNER’S REQUIREMENTS OR BE AVAILABLE ON AN UNINTERRUPTED, SECURE, OR ERROR-FREE BASIS. FURTHER, LICENSOR PROVIDES NO WARRANTY REGARDING, AND WILL HAVE NO RESPONSIBILITY FOR, ANY CLAIM ARISING OUT OF: (a) A MODIFICATION OF A MoonDAO Entity NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT MADE BY ANYONE OTHER THAN LICENSOR, UNLESS LICENSOR APPROVES SUCH MODIFICATION IN WRITING, IN ADVANCE; (b) OWNER’S MISUSE OF, OR MISREPRESENTATION REGARDING, A MOONDAO ENTITY NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT; (c) THE FLUCTUATION IN VALUE OF A MOONDAO ENTITY NFT; AND/OR (d) ANY TECHNOLOGY THAT FAILS TO PERFORM OR CEASES TO EXIST.
-
-FURTHER, OWNER UNDERSTANDS AND AGREES THAT OWNERSHIP OF, AND TRANSACTIONS INVOLVING, A MOONDAO ENTITY NFT AND/OR ENTITLEMENT MAY REQUIRE OR RELY ON: (i) THIRD-PARTY TECHNOLOGY AND/OR PLATFORMS INCLUDING, WITHOUT LIMITATION, DIGITAL WALLETS, BLOCKCHAINS OR RELATED TECHNOLOGY, SMART CONTRACTS, INTERNET SERVICE PROVIDERS, MARKETPLACES, EQUIPMENT OR OTHER INFRASTRUCTURE (COLLECTIVELY, “THIRD PARTY TECHNOLOGY”); AND/OR (ii) THIRD-PARTY SERVICE PROVIDERS, SUCH AS BLUE ORIGIN TEXAS, LLC (“BLUE ORIGIN”), AS WELL AS ITS SPACECRAFT, TECHNOLOGY AND TRANSPORTATION SERVICES (COLLECTIVELY, “THIRD PARTY SERVICES,” AND TOGETHER WITH THE THIRD PARTY TECHNOLOGY, THE “THIRD PARTY OFFERINGS”). OWNER UNDERSTANDS AND AGREES THAT THE EXISTENCE AND PERFORMANCE OF THIRD PARTY OFFERINGS ARE OUTSIDE OF LICENSOR’S CONTROL. TO THE MAXIMUM EXTENT PERMISSIBLE UNDER APPLICABLE LAW, LICENSOR DISCLAIMS ALL LIABILITY FOR THE USE, UNAVAILABILITY AND/OR FAILURE OF ANY THIRD PARTY OFFERINGS.
-
-**The MoonDAO Entity NFTs are not intended as investment vehicles. Licensor makes absolutely no promise or guarantee that the MoonDAO Entity NFTs will increase in value, or maintain the same value as the amount Owner paid to purchase same. Owner understands and agrees that the MoonDAO Entity NFTs have no inherent monetary value (other than with respect to Membership benefits and Entitlements). Please be aware that the prices of MoonDAO Entity NFTs are extremely volatile, and price fluctuations in ETH could impact the value of MoonDAO Entity NFTs, both positively and negatively. Given this volatility, MoonDAO Entity NFTs should not be considered investments. Owner assumes all risks in connection therewith. No information and/or content made available by and/or through the Site or otherwise by Licensor is or should be considered advice or an invitation to enter into an agreement for any investment purpose. Further, no element of the MoonDAO Entity NFTs qualifies or is intended to be an offering of securities in any jurisdiction, nor does it constitute an offer or an invitation to purchase shares, securities or other financial products. Owner is solely and exclusively responsible for assuring that the purchase and sale of MoonDAO Entity NFTs, and the use of cryptocurrencies, complies the with laws and regulations in Owner’s jurisdiction. Owner assumes all risks associated with using an Internet-based cryptocurrency including, but not limited to, the risk of hardware, software and Internet connections, the risk of malicious software introduction, and the risk that third parties may obtain unauthorized access to information stored within Owner’s Wallet. NFTs, cryptocurrencies and blockchain technology are relatively new and the regulatory landscape is unsettled. New regulations could negatively impact such technologies which may, in turn, impact the value of Owner's MoonDAO Entity NFTs. Owner understands and accepts all risk in that regard. Without limiting the foregoing, Owner assumes all responsibility for any adverse effects of disruptions or other issues impacting ETH or the Ethereum platform.**
-
-1. **Limitation of Liability**.
-   1. Liability Cap. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE COVERED PARTIES’ CUMULATIVE LIABILITY UNDER THE AGREEMENT, FOR ALL CAUSES OF ACTION AND ALL THEORIES OF LIABILITY, WILL BE LIMITED TO AND WILL NOT EXCEED THE GREATER OF: (a) THE AMOUNT PAID TO LICENSOR FOR THE INITIAL SALE OF THE SUBJECT MOONDAO ENTITY NFT(S); OR (b) ONE HUNDRED DOLLARS ($100).
-   1. Excluded Damages. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL THE COVERED PARTIES BE LIABLE UNDER ANY CLAIM ARISING OUT OF OR RELATED TO THE AGREEMENT FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR OTHER NONDIRECT DAMAGES OF ANY KIND OR FOR ANY SPECIAL, PUNITIVE OR SIMILAR DAMAGES OR EXPENSES (INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR OTHER ECONOMIC LOSS, LOST REIMBURSEMENTS, LOST DATA, OR LOST SAVINGS), EVEN IF THE APPLICABLE COVERED PARTY(IES) WAS/WERE ADVISED OF THE POSSIBILITY OF THE OCCURRENCE OF SUCH DAMAGES.
-   1. Additional Terms. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE LIABILITIES LIMITED BY THIS SECTION 4 APPLY: (a) TO LIABILITY FOR NEGLIGENCE; (b) REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT, TORT, STRICT PRODUCT LIABILITY, OR OTHERWISE; (c) EVEN IF THE APPLICABLE COVERED PARTY(IES) IS/ARE ADVISED IN ADVANCE OF THE POSSIBILITY OF THE DAMAGES IN QUESTION AND EVEN IF SUCH DAMAGES WERE FORESEEABLE; AND (d) EVEN IF OWNER’S REMEDIES FAIL OF THEIR ESSENTIAL PURPOSE. WITHOUT LIMITING THE FOREGOING, TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE COVERED PARTIES WILL NOT BE LIABLE TO OWNER FOR ANY USE OF A MOONDAO ENTITY NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT INCLUDING, BUT NOT LIMITED TO, ANY LOSSES, DAMAGES OR CLAIMS ARISING FROM: (i) USER ERROR, SUCH AS FORGOTTEN PASSWORDS, INCORRECTLY CONSTRUCTED TRANSACTIONS, OR MISTYPED WALLET ADDRESSES; (ii) SERVER FAILURE OR DATA LOSS; (iii) CORRUPTED CRYPTOCURRENCY WALLET FILES; (iv) UNAUTHORIZED ACCESS TO A MOONDAO ENTITY NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT; (v) ANY UNAUTHORIZED THIRD PARTY ACTIVITIES INCLUDING, WITHOUT LIMITATION, THE USE OF VIRUSES, PHISHING, BRUTE FORCING OR OTHER MEANS OF ATTACK AGAINST A BLOCKCHAIN NETWORK UNDERLYING A MOONDAO ENTITY NFT AND/OR ASSOCIATED DIGITAL OBJECT; (vi) OWNER’S FAILURE TO MAINTAIN THE SECURITY OF HER/HIS/ITS WALLET’S PRIVATE KEY; (vii) ANY UNINTENDED TRANSFER OR LOSS OF A MOONDAO ENTITY NFT, ENTITLEMENT AND/OR ASSOCIATED DIGITAL OBJECT; (viii) THE FAILURE TO REALIZE ANY SPECIFIC INVESTMENT INCOME, REVENUE OR OTHER FINANCIAL OUTCOME; (ix) THE FAILURE TO OBTAIN ACCESS TO ANY ENTITLEMENT; (x) THE USE, UNAVAILABILITY AND/OR FAILURE OF ANY THIRD PARTY OFFERINGS INCLUDING, WITHOUT LIMITATION, ANY BLUE ORIGIN OFFERING; AND/OR (xi) OWNER’S INABILITY TO DEMONSTRATE OWNERSHIP AND/OR CONTROL OF A MOONDAO ENTITY NFT, ASSOCIATED DIGITAL OBJECT AND/OR ENTITLEMENT. If applicable law limits the application of the provisions of this Section 4, Licensor’s liability will be limited to the maximum extent permissible.
-1. **Indemnity**.
-
-   Owner shall indemnify, defend and hold harmless the Covered Parties from and against any and all claims, demands, causes of action, liabilities, damages, penalties, losses, fines, costs and expenses (including reasonable attorneys' fees, legal costs and court costs, which shall be reimbursed as incurred) arising out of, related to, or in connection with, or alleging: (a) Owner’s breach of any provision contained in the Agreement, including, but not limited to, Owner’s failure to comply with the licensing conditions set forth in Section 1 hereof; (b) Owner’s use of a MoonDAO Entity NFT, associated Digital Object and/or Entitlement in any way that violates any applicable laws, rules or regulations; (c) Owner’s unauthorized transfer, or purported transfer, of a MoonDAO Entity NFT, associated Digital Object and/or Entitlement; or (d) Owner’s improper and/or unauthorized exercise of any license rights in and/or to a MoonDAO Entity NFT, associated Digital Object and/or Entitlement.
-
-1. **Term & Termination**.
-   1. Term. This Owner Agreement shall continue until terminated pursuant to the terms of this Owner Agreement (the “Term”).
-   1. Termination for Transfer*.* The Owner License applies only to the extent that Owner continues to own the subject NFT. If, at any time, the Owner sells, trades, donates, gives away, transfers, purports to transfer, or otherwise disposes of the subject MoonDAO Entity NFT for any reason, this Owner Agreement, including, without limitation, the Owner License granted to Owner hereunder, will immediately terminate without the requirement of notice, and Owner will have no further rights in or to the subject MoonDAO Entity NFT, Digital Object, or any Entitlement(s).
-   1. Termination for Cause. Licensor may terminate this Owner Agreement for Owner’s material breach of any term of the Agreement by written notice specifying in detail the nature of the breach, effective in fifteen (15) days unless the Owner first cures such breach, or effective immediately if the breach is not subject to cure.
-   1. Effects of Termination. Upon termination of this Owner Agreement, Owner shall cease all use of the Digital Object and delete, destroy, or return all copies of the Digital Object in its possession or control. Owner acknowledges that any use of the Digital Object upon termination of the Owner License shall be deemed intellectual property infringement. Any provision of this Owner Agreement that must survive to fulfill its essential purpose will survive termination or expiration.
-1. **Miscellaneous**.
-   1. Independent Contractors. The parties are independent contractors and shall so represent themselves in all respects. Neither party is the agent of the other, and neither may make commitments on the other’s behalf.
-   1. Force Majeure. No delay, failure, or default, other than a failure to pay fees when due, will constitute a breach of the Agreement to the extent caused by acts of war, terrorism, hurricanes, earthquakes, epidemics, other acts of God or of nature, strikes or other labor disputes, riots or other acts of civil disorder, embargoes, COVID-19 or any similar virus, disease and/or pandemic, as well as any private sector or governmental responses to any of the foregoing, or other causes beyond the performing party’s reasonable control.
-   1. Assignment & Successors. This Owner Agreement is not assignable or transferable by Owner, except pursuant to a Permitted Transfer of ownership of a MoonDAO Entity NFT to a Secondary Acquirer, in which case the terms and conditions hereof will transfer and be binding upon and will inure to the benefit of the parties and their permitted successors and assigns. Any purported assignment or transfer by Owner in violation of this Section 7.3 is null and void.
-   1. Severability. To the extent permitted by applicable law, the parties waive any provision of law that would render any clause of the Agreement invalid or otherwise unenforceable in any respect. If any provision of the Agreement is held to be invalid or otherwise unenforceable, such provision will be interpreted to fulfill its intended purpose to the maximum extent permitted by applicable law, and the remaining provisions of the Agreement will continue in full force and effect.
-   1. No Waiver. Neither party will be deemed to have waived any of its rights under the Agreement by lapse of time or by any statement or representation other than by an authorized representative in an explicit written waiver. No waiver of a breach of the Agreement will constitute a waiver of any other breach of the Agreement.
-
-1. **Dispute Resolution Provisions**:
-The Agreement shall be treated as though it were executed and performed in New York, NY and shall be governed by and construed in accordance with the laws of the State of New York (without regard to conflict of law principles). **The parties (and Covered Parties) hereby agree to arbitrate all claims that may arise under and/or relate to the MoonDAO Entity NFTs, Entitlements, Digital Objects and/or the Agreement. Without limiting the foregoing, should a dispute arise between the parties/any Covered Parties including, without limitation, any matter concerning the MoonDAO Entity NFTs, Entitlements, Digital Objects, the terms and conditions of the Agreement or the breach of same by any party hereto: (a) the parties/Covered Parties agree to submit their dispute for resolution by arbitration before the American Arbitration Association (“AAA”) in New York, NY, in accordance with the then current Commercial Arbitration rules of the AAA; and (b) Owner agrees to first commence a formal dispute proceeding by completing and submitting an Initial Dispute Notice which can be found [here](/tts-dispute-notice). The Covered Party(ies) named in Owner’s Initial Dispute Notice (collectively, the “Named Parties”) may choose to provide Owner with a final written settlement offer after receiving Owner’s Initial Dispute Notice (“Final Settlement Offer”). If the applicable Named Party(ies) provide(s) Owner with a Final Settlement Offer and Owner does not accept it, or such Named Party(ies) cannot otherwise satisfactorily resolve Owner's dispute and Owner wishes to proceed, Owner must submit Owner’s dispute for resolution by arbitration before the AAA, in Owner’s county of residence, by filing a separate Demand for Arbitration, which is available [here](https://adr.org/sites/default/files/Consumer_Demand_for_Arbitration_Form_1.pdf). For claims of Ten Thousand Dollars ($10,000.00) or less, Owner can choose whether the arbitration proceeds in person, by telephone or based only on submissions. If the arbitrator awards Owner relief that is greater than the applicable Final Settlement Offer, then the Named Party(ies) will pay all filing, administration and arbitrator fees associated with the arbitration and, if Owner retained an attorney to represent Owner in connection with the arbitration, the Named Party(ies) will reimburse any reasonable attorneys’ fees that Owner’s attorney accrued for investigating, preparing and pursuing the claim in arbitration. Any award rendered shall be final and conclusive to the parties and a judgment thereon may be entered in any court of competent jurisdiction. Although the Named Party(ies) may have a right to an award of attorneys’ fees and expenses if Named Party(ies) prevail(s) in arbitration, the Named Party(ies) will not seek such an award from Owner unless the arbitrator determines that Owner's claim was frivolous.**
-
-**To the extent permitted by law, Owner agrees that Owner will not bring, join or participate in any class action lawsuit as to any claim, dispute or controversy that Owner may have against any of the Covered Parties. Owner agrees to the entry of injunctive relief to stop such a lawsuit or to remove Owner as a participant in the suit. Owner agrees to pay the attorney's fees and court costs that any Covered Party incurs in seeking such relief. This provision preventing Owner from bringing, joining or participating in class action lawsuits: (i) does not constitute a waiver of any of Owner's rights or remedies to pursue a claim individually and not as a class action in binding arbitration as provided above; and (ii) is an independent agreement. Owner may opt-out of these dispute resolution provisions by providing written notice of Owner's decision within thirty (30) days of the date that Owner first purchases a MoonDAO Entity NFT.**
-
-1. Entire Agreement. This Owner Agreement, together with the Site Terms and the documents referenced therein, sets forth the entire agreement of the parties and supersedes all prior or contemporaneous writings, negotiations, and discussions with respect to its subject matter. Neither party has relied upon any such prior or contemporaneous communications.
-2. Amendment. The Agreement may not be amended in any way except through a written agreement by authorized representatives of the Licensor and the MoonDAO Entity NFT Owner.
-3. Headings. All section headings and captions have been inserted for convenience only and shall not affect the interpretation of the Agreement.
-
-4. Drafting. Each party providing Electronic Acceptance (as defined below) to the terms of the Agreement agrees that it has fully participated in the drafting of the Agreement and that no party shall be deemed to be the drafting party of the Agreement.
-5. Electronic Signatures. Owner acknowledges and agrees that Owner accepts the Agreement via electronic means rather than via traditional handwritten signature (“Electronic Acceptance”). Owner acknowledges and agrees that by clicking on the “submit” button, or taking such other action as may be designated by Licensor as a means of accepting the Agreement, Owner is submitting a legally binding electronic signature and is entering into a legally binding contract. Owner acknowledges that Owner’s electronic submission constitutes Owner’s agreement and intent to be bound by the Agreement. Pursuant to any and all applicable statutes, regulations, rules, ordinances or other laws including, without limitation, the United States Electronic Signatures in Global and National Commerce Act, P.L. 106-229 (the “E-Sign Act”) and other similar state and federal statutes, OWNER HEREBY AGREES TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS AND OTHER RECORDS AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED THROUGH THE SITE AND/OR ANY OTHER ONLINE PLATFORMS AND/OR SERVICES OPERATED BY LICENSOR. Further, Owner hereby waives any rights and/or requirements under any statutes, regulations, rules, ordinances or other law in any jurisdiction which requires an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by other than electronic means. Owner acknowledges and agrees that it has the ability to print information delivered to Owner electronically, or otherwise knows how to store that information in a way that ensures that it remains accessible to Owner in unchanged form. {00136579;1}
diff --git a/Archive/guilds.md b/Archive/guilds.md
deleted file mode 100644
index 80ce26c6..00000000
--- a/Archive/guilds.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-tags: archive, docs/guilds
-id: guild-guidelines
-title: MoonDAO Guild Guidelines
-description: Learn more about how MoonDAO Guilds work
-keywords: [Proposal, Guilds, MoonDAO, Space Travel]
-sidebar_label: MoonDAO Guilds
-sidebar_position: 6
----
-
-
-MoonDAO Guilds are talent pools to onboard, orient, and train members to complete bounties for MoonDAO projects. Guilds are operated by Guild Stewards who are responsible for:
-Onboarding and orienting new members
-Ensuring the quality of their guild members which includes but not limited to: Interviewing their new members to ensure they have all necessary skills relevant to the guild, and provision of regular training and educational opportunities to their guild members
-Supporting MoonDAO projects to find the right resource and help their guild members get started on MoonDAO bounties and projects
-
-This document includes how a guild is established and intended to work in a transparent and auditable way, guild scope of works, and how compensation will work for those guild members.
-
-## How is a MoonDAO Guild created?
-
-
-### 1. Build an initial team. 
-
-Any MoonDAO member that meets the following requirements can steward a guild:
-Obtain and hold a role of Rocketeer or MoonSettler for at least one month. Proof of work is required before someone can start a Guild.
-Possess good knowledge and experience in their field.
-Successfully recruit at least 3 initial members for their guild.
-Be sufficiently differentiated from any existing guilds, this is subjective and other DAO members can weigh in.
-
-Guild stewards are responsible for onboarding, orienting and training their guild members. They should act as the point of contact for the guild and manage the guild related activities. 
-
-There is only one guild steward on any given guild at the beginning. The number of guild steward may be increased overtime as the guild grows. Adding new guild stewards shall follow the guild steward selection process.  
-
-If the guild proposal gets passed, each person on the initial team will become guild members. They will be eligible for taking project bounties as well as having early access to new MoonDAO projects.
-
-### 2. Find a sponsor.
-
-A Sponsor is found from our DAO, either an Astronaut or Rocketeer. The Sponsor cannot be the same person as the steward. 
-
-Sponsors are responsible for making sure the proposal meets all the requirements needed for a guild to be properly put together. The sponsor could pull their support at any point in the process if they do not think the guild proposal is meeting the requirements. This pull of support will be recorded on the guild proposal with their reasoning, but the guild steward can always find another sponsor if he or she wishes to continue. 
-
-
-### 3. Fill out a Guild proposal template. 
-
-A google doc template is filled out (below) and with the help of the Sponsor to workshop the project and make sure it fits all the requirements. Once the proposal meets all the requirements to be put up, then the sponsor will put it up under a special channel in the Discord that only the Astronauts or Rocketeers (sponsors) can post in.
-
-### 4. Present Guild Proposal to DAO leadership. 
-
-On a weekly basis the Rocketeers and Astronauts go on a call to evaluate the new
-guild proposals and talk about it together. The people who put up the proposal need to be on that call to discuss the guild proposal and explain it for people to get feedback. The Guild Stewards have to post the proposal at least 24 hours before the DAO Leadership meeting. 
-
-
-### 5. Get feedback from DAO leadership. 
-
-The proposal must have an in-depth review from at least three Astronauts or Rocketeers. 
-Iterate on the proposal. 
-
-Guild Stewards can change their proposal based on feedback from the reviews. If the proposal is changed, they should notify the reviewers and they can update their scores based on the feedback. Proposals may be workshopped in this way with weekly reviews until the proposal feels good enough to move on to the next phase of review (at this point it is static and cannot change).
-DAO Discord vote by the senate members. 
-
-An announcement will be made by the sponsor on the Discord with the document to a special channel where only senate members can react with a Yes or No. A 70% majority in the Senate is required for the proposal to go forward to vote from the MoonDAO Member House, with a quorum of 80% required. Senate votes are one vote per member.
-
-### 6. Present at Town hall. 
-
-If the proposal passes the requirement from Step #7. The guild steward will talk about the proposal at the weekly town hall and pitch the proposal to the DAO and take questions from people in the DAO 
-
-At this point the proposal is also translated into other languages and communicated to the rest of the DAO.
-
-### 7. Vote on Snapshot. 
-
-After the proposal is pitched, it’s included in that batch’s weekly snapshot for approval by the DAO and the DAO can vote on the snapshot for it to be passed with 80% approval.
-
-### 8. Update role and setup the guild channel on discord
-
-Once passed, the guild steward will officially have the Guild Steward role in discord, and the initial team will be guild members.
-
-The guild stewards then do the following:
-Create new guild channel for their guild, including but not limited to the following:
-
-1. Start here: 
-2. Welcome message and induction of the guild 
-3. Instructions on how to get started (sign up, introduce yourself, attend regular meetings, etc.) 
-4. Official links of the guild 
-5. Contact points (normally guild stewards) 
-6. `#Announcement` (bounties can be announced here)  
-7. `#General` Chat (for daily discussion and sharing knowledge) 
-8. Setup the tests or method to ensure the quality of new guild members
-9. Schedule regular guild meetings with guild members for knowledge sharing, on-boarding new members, helping guild members to get involved in projects and bounties. 
-
-
-### 9. Progress updates.
-Every month guild stewards have to report what their guild has done in the past month and what is the plan for the next month to the senate. The monthly guild report should be written with facts and figures, and posted on the guild discord channel to ensure transparency.
-
-
-
-
-
-## Guild member expectations
-
-Everyone can apply to be a guild member as long as they have knowledge and experience in their field. They will be interviewed or put on a test by guild steward to ensure that they qualify as a member of the guild. 
-
-Guild members are expected to join and contribute to the guild related activities such as on-boarding new members, helping guild steward training new members.
-
-Guild members have the right to get involved in bounties and projects. Once they take a bounty, they are responsible to complete the bounty on time and ensure the quality of their works.
-
-Failure to deliver taken bounties may result in a ban from applying next bounties or even removal from the guild. 
-
-
-## Guild steward Expectations
-
-Guild stewards are responsible for onboarding, orienting and training their guild members. They should act as the point of contact for the guild and manage the guild related activities. 
-
-Guild stewards must provide monthly updates to the DAO on their guild’s activities at the town halls, where the community can share their thoughts, comments, or concerns with the team. The update should be written down and shared in the Discord in their own guild channel. 
-
-Guild stewards must ensure the quality of their guild members by setting up the entry test, interviewing applicants, organizing regular training and knowledge sharing between guild members.
-
-Guild stewards should work closely with Rocketeers to have an overview of on-going projects as well as coming projects so that they can introduce or allocate the right resource to project teams. Besides, guild stewards are expected to help guild members to get involved in bounties and make sure that their members complete the bounties on time. 
-
-Guild stewards are responsible for on-boarding new members, registering the addition or removal of members. Guild stewards should consider ramping up their team whenever appropriate to meet the demands from the projects. 
-
-Guild stewards are expected to have MoonDAO be a commitment in their life. They are expected to act as a point of contact for the guild and be active and responsive to make sure things move along and goals are achieved.
-
-Guild stewards have the right to individually propose a salary. The salary shall be put in the guild proposal and get approved by the community. The salary will be reviewed every quarter, it can be increased or decreased based on the performance and workloads of the guild steward. 
-
-## What are the term limits of guild stewards?
-
-Guild stewards initially serve for one quarter, and then the Senate will vote on extending the Guild. After that, Guild Stewards will serve on a one year term. After one year, the DAO must conduct an election to find out the guild steward for the next term. Guild stewards can remain their position for multiple terms if they win the election. 
-
-## How to run for a guild steward election?
-
-Everyone who meets the following criteria can run for the guild steward election. 
-Having the role of Rocketeer or Moonsettler for at least a month. Proof of work is required before someone can steward a Guild.
-Possess good knowledge and experience in their field  
-Being an active member of the guild and having a good track record of completing bounties.
-
-The guild steward candidates have to submit their application including their bios, proposed master plan for the guild in next term, and why they should be selected.
-
-The Senate will vote to select the new guild steward. Each senate member will vote for one candidate only, the one who receives the highest votes will be selected as guild steward for the next term.
-
-
-## Do Guild members receive rewards for work?
-Guild members receive rewards by taking and completing bounties or they can join the project team to get the project rewards.
-
-Guild stewards can propose a payment and get it approved by the community.
-
-
-## Do guilds have their own budget?
-
-Guilds do not have their own budget. If a guild thinks that they need a budget to run their activities they have to come up with a proposal and go through the project proposal process. If the proposal gets passed, the budget will be managed under the project team which may consist of guild members and guild steward. 
-
-
-## Can a guild be shut down?
-
-If the community loses faith in a guild’s ability to execute for whatever reason, the DAO can pass a Snapshot vote to disband the guild with a 50% token weighted vote. The guild stewards will no longer receive their salary. Guild members working on bounties can still receive their bounties as long as they complete the bounties on time. 
-
-Once the guild is shut down, the guild stewards are responsible to handover all guild asset, documents and on-going works to the DAO. 
-
-
-
-## Can a Guild have more than one guild steward?
-
-Yes, a guild can have more than one guild steward, however, adding 2nd guild stewards or more shall go through the proposal process with justification why the guild needs more than one guild stewards and what are the OKRs of each guild stewards. Once the proposal passes, the selection of new guild stewards shall follow the above selection process. 
-
-
-## How to monitor and measure the performance of a guild? 
-
-Every month, guild stewards must provide updates to the DAO on their guild’s activities at the town halls, where the community can share their thoughts, comments, or concerns with the team. The update should be written down and shared in the Discord in their own guild channel. 
-
-Every quarter, the senate will assess the performance of both the guilds and guild stewards. The assessment shall be based on fact and figures (e.g., monthly guild report). If the senate thinks that a guild is no longer necessary, it will be shut down. Similarly, if a guild steward fails to deliver his promises, then he must step down. 
-
-Every year, at the end of the term, the DAO must conduct an election to find out the guild steward for the next term.
-
-
-
-
-
-
-=====================================================================
-
-# MoonDAO Guild Proposal Template
-
-
-**Guild Title:** e.g. MoonDAO Community guild
-
-**Abstract:** This is a top level description about the idea. Please use ELI5 wording and summarize things for anyone to understand what you want to achieve.
-
-**Motivation:** Describe the motivation behind the proposal, the problem(s) it solves and the value it adds. This is your chance to show why this guild is necessary, and how the it would benefit the DAO if established. 
-
-**Guild Master Plan:** Provides a conceptual layout to guide future growth and development of the guild. Go into deep detail around the work that needs to be done in the short -term (e.g., first and second quarter), and future direction. The more detail, the better.
-
-
-**Benefits:** Point out core benefits of the guild establishment and how it will affect the DAO.
- 
- 
-## Guild Objectives:
-
-You can write as many OKRs as you think are needed. One OKR is fine if that captures the full extent of what you want to achieve. One focused goal is preferred instead of many.
-
-**Objective #1:** e.g., Translation guild may have the following objective: To create high quality translation for all MoonDAO document and project proposals 
-
-Team Table 
-There is one guild steward and he/she must play the role of Rocketeer for at least a month. Initial guild team must have at least 3 members and they must have knowledge in their field. 
-
-| Guild Steward                                   | e.g. @Larrotiz#8888                      |
-| ----------------------------------------------- | ---------------------------------------- |
-| **Initial Team**                                | e.g. @enroggo @bay @kori @pablo @richard |
-| **Sponsors**                                    | 1 Rocketeer or Astronaut                 |
-| **Foreign Language Representatives (optional)** | e.g. @carol, luffy                       |
-| **Multi-sig Signers (if Budget is needed)**     | e.g @kori @pablo @enroggo @Larrotiz @bay |
-
-## Guild Steward Bio:
-
-### Guild Steward OKRs:
-
-**Objective #1:** e.g. Lorem ipsum
-
-**Key Results for Objective #1:**
-- Lorem ipsum
-- Lorem ipsum
-
-
-**Guild Steward Minimum Viable Payment (optional):**
-
-
-## Guild members Bio:
-
-**Member #1:** e.g., @username. I’m a professional translator with 5-year experience.
-
-**Member #2:** etc.
-
-Guild members OKRs are not required. 
-
-
-
-
-
-
diff --git a/Archive/join.md b/Archive/join.md
deleted file mode 100644
index 1dd7cf94..00000000
--- a/Archive/join.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-tags: archive, docs/roles
-id: join-moondao
-title: How to Join to MoonDAO
-description: Learn how to contribute to MoonDAO, understand Progressive Governance, and Titles and their Subject Roles.
-keywords:
-  [
-    Contribute,
-    Progressive Governance,
-    Titles,
-    Astronauts,
-    Cosmonauts,
-    Rocketeers,
-    Moon Settlers,
-    Earthlings,
-    Subject Roles,
-    Decentralization,
-  ]
-sidebar_label: How To Join
-sidebar_position: 3
----
-
-The best way to get involved would be to attend our Town Hall meetings at **8am PST every Monday** on our [Twitter](https://twitter.com/OfficialMoonDAO) and introduce yourself. Our town halls are on Twitter Spaces and they’re open to anyone.
-
-If you're new to DAOs, [sign up for our email newsletter](https://www.moondao.com/explore). This will walk you through how to join MoonDAO step-by-step, providing you with all the tools you need to contribute!
-
-If you just can't wait, and you're familiar with DAO tools already, you'll simply need to complete the following four steps. They can be done in under five minutes by following the links provided:
-
-## Join now
-1. Jump in our [Discord](https://discord.gg/RpDEtQHcPw)
-2. Apply to a [MoonDAO Guild](https://moondao.com/contribute). You don't necessarily need to be part of a Guild to be in MoonDAO, but this is the first step to contributing towards a project or bounty.
-3. [Purchase our governance token $MOONEY](https://app.uniswap.org/#/swap?inputCurrency=ETH&outputCurrency=0x20d4DB1946859E2Adb0e5ACC2eac58047aD41395&chain=mainnet). There is no expectation of profit with the $MOONEY token, please check our $MOONEY token documentation for more information. This is optional, you may also complete tasks to receive $MOONEY.
-4. [Stake your $MOONEY tokens for voting power.](https://www.moondao.com/lock) Important note: this does not consume the tokens, your $MOONEY can be unlocked after the time period ends. Connect your wallet in the “verify-wallet” channel to start contributing to MoonDAO
-
-We also host onboarding meetings for new members, so stay tuned and find our event calendar on Discord to see all the events going on at MoonDAO.
-
-Now as a full MoonDAO member you can:
-1. Vote on our [Snapshot](https://snapshot.org/#/tomoondao.eth).
-2. Submit proposals to MoonDAO on [Discord](https://discord.gg/RpDEtQHcPw).
-3. Join [MoonDAO Projects](https://docs.moondao.com/projects).
-4. Complete [MoonDAO Bounties](https://app.dework.xyz/moondao) for $MOONEY.
-
diff --git a/MoonDAO/docs/Projects/Active Projects/deprize/DAO Structure.canvas b/MoonDAO/docs/Projects/Active Projects/deprize/DAO Structure.canvas
deleted file mode 100644
index 202959d2..00000000
--- a/MoonDAO/docs/Projects/Active Projects/deprize/DAO Structure.canvas	
+++ /dev/null
@@ -1,28 +0,0 @@
-{
-	"nodes":[
-		{"id":"237e8140a92df411","x":-780,"y":-35,"width":250,"height":60,"type":"text","text":"Executive Branch"},
-		{"id":"25b46b2b5db600a2","x":-780,"y":40,"width":670,"height":60,"type":"text","text":"Tripartite Governance, Checks and Balances on Each Institution"},
-		{"id":"eb7913134acb2d3b","x":-570,"y":-140,"width":250,"height":60,"type":"text","text":"Senate"},
-		{"id":"40497143eb1a2113","x":-20,"y":-110,"width":250,"height":60,"type":"text","text":"DePrize 1"},
-		{"id":"0813cbbcc1021e41","x":-20,"y":-35,"width":250,"height":60,"type":"text","text":"Deprize 2"},
-		{"id":"656372296389cac2","x":-20,"y":40,"width":250,"height":60,"type":"text","text":"Deprize 3"},
-		{"id":"3e904a9ba1c5f15f","x":-360,"y":-35,"width":250,"height":60,"type":"text","text":"Member House"},
-		{"id":"8decce1d3f00d4bb","x":387,"y":-38,"width":250,"height":60,"type":"text","text":"Team 3"},
-		{"id":"89e33d731632c4ad","x":387,"y":-110,"width":250,"height":60,"type":"text","text":"Team 2"},
-		{"id":"6f0b81ec4f418c93","x":387,"y":-182,"width":250,"height":60,"type":"text","text":"Team 1"}
-	],
-	"edges":[
-		{"id":"b938e048e0cb2b88","fromNode":"3e904a9ba1c5f15f","fromSide":"right","toNode":"40497143eb1a2113","toSide":"left"},
-		{"id":"c3e7b4789329d037","fromNode":"3e904a9ba1c5f15f","fromSide":"right","toNode":"0813cbbcc1021e41","toSide":"left"},
-		{"id":"b23db6d829c5003a","fromNode":"3e904a9ba1c5f15f","fromSide":"right","toNode":"656372296389cac2","toSide":"left"},
-		{"id":"6835c614b2ab0c9d","fromNode":"237e8140a92df411","fromSide":"right","toNode":"3e904a9ba1c5f15f","toSide":"left"},
-		{"id":"bc3f197a08dd22e8","fromNode":"3e904a9ba1c5f15f","fromSide":"left","toNode":"237e8140a92df411","toSide":"right"},
-		{"id":"d4ea5ecfb35f30e4","fromNode":"237e8140a92df411","fromSide":"top","toNode":"eb7913134acb2d3b","toSide":"left"},
-		{"id":"f455371d5de9c5ff","fromNode":"eb7913134acb2d3b","fromSide":"left","toNode":"237e8140a92df411","toSide":"top"},
-		{"id":"cd8f37138231a560","fromNode":"3e904a9ba1c5f15f","fromSide":"top","toNode":"eb7913134acb2d3b","toSide":"right"},
-		{"id":"3fafbda8325d2f73","fromNode":"eb7913134acb2d3b","fromSide":"right","toNode":"3e904a9ba1c5f15f","toSide":"top"},
-		{"id":"452986c3ba8a7481","fromNode":"40497143eb1a2113","fromSide":"right","toNode":"6f0b81ec4f418c93","toSide":"left"},
-		{"id":"e5ec59a5bfac7007","fromNode":"40497143eb1a2113","fromSide":"right","toNode":"89e33d731632c4ad","toSide":"left"},
-		{"id":"6d932c07dbf4a6c1","fromNode":"40497143eb1a2113","fromSide":"right","toNode":"8decce1d3f00d4bb","toSide":"left"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/deprize/DePrize Musings (greg).md b/MoonDAO/docs/Projects/Active Projects/deprize/DePrize Musings (greg).md
deleted file mode 100644
index c3ce3a58..00000000
--- a/MoonDAO/docs/Projects/Active Projects/deprize/DePrize Musings (greg).md	
+++ /dev/null
@@ -1,17 +0,0 @@
----
-tags:
-  - notes
-  - project/deprize
----
-
-Overall, this is an excellent construct for Moon DAO. Wouldn't recommend implementing anything below until the DePrize model has been "trained" with a case study (lunar comms). These ideas are for inspiring future Moon DAO thoughts/dreams!
-
-Ideation extension: 
-Think if the lunar comms incubation period is successful, MoonDAO could experiment with opening the ideation phase to a much larger audience. I'm envisioning something akin to the One immediate concern one may have is: "how would we process all of the 1000s of ideas each day by randos." But MoonDAO members wouldn't need to, necessarily. [Unanimous AI](Unanimous%20AI.md) provides a "swarm voting" mechanism. My hypothesis is that you wouldn't even need to pay folks to vote, they would do it based on curiosity alone. Maybe make a group of 5 ideas and have votes on the best, then keep repeating until the law of large numbers tells us what the best ideas graduate to the Moon DAO ideation. 
-
-Secondary impact: Imagining the vibe akin to the App revolution of the early 2000s but with space hardware. About 95% of the ideas will not make it, but there are bound to be some winners. And even if it isn't marketable, it opens up space opportunities to folks that may not be exposed to it normally: see 13 year olds that made thousands of $'s from Apps back in the day. 
-
-Machine/Human judge: The judge of the winner could be either a machine or a judge. A machine is preferred for traditional acquisition requirements that have objective metrics (NASA style). But DePrize winners may have achieved a capability through a means that does not lend itself to objective criteria. [DARPA](DARPA.md) bases their success/fail criteria on capabilities, rather than requirements. A goal such as: "enable GPS receivers small enough to embed in myriad consumer devices." This would probably need a human judge. 
-
-Post DePrize rewards: Depending on how the DePrize is written, there could be a potential for high value within the losing teams at later time. Imagine Team A achieves the required data rate of 10Mb/s from the moon to earth and wins the DePrize in October. In the following January, Team B finishes their project that can deliver 10Gb/s. Or more abstractly, Team B finds a way to push comms via graphine coating (or something novel) that can't hack it short term, but has game changing impacts down the road. Guessing the blockchain could be used to store lessons learned for the future. If nothing else: it helps decrease redoing projects from the past and saves time. This is a key feature of [DARPA](DARPA.md) innovations: lots of them are shelfed until the limiting technology has been improved to make it a possibility. Best way to implement this I can think is to still give the losers IP rights to developments that are unique to their project. These IP are tracked for the future and give an ROI if they're picked up by a funder in the future. Eventually, instead of scouring the patent office to see if your idea has been done: some future Obsidian-like program could smartly direct you through the IP environment to find one that fits your needs. 
-
diff --git a/MoonDAO/docs/Projects/Active Projects/deprize/DePrize.canvas b/MoonDAO/docs/Projects/Active Projects/deprize/DePrize.canvas
deleted file mode 100644
index c7db468a..00000000
--- a/MoonDAO/docs/Projects/Active Projects/deprize/DePrize.canvas	
+++ /dev/null
@@ -1,77 +0,0 @@
-{
-	"nodes":[
-		{"type":"text","text":"Funder 1","id":"e49cad8dabc4bc4a","x":-1720,"y":-730,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Funder ...","id":"de58c6d40c5225fe","x":-1720,"y":-640,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Funder X","id":"ca5a46dedfd58fae","x":-1720,"y":-550,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Request For Proposal Phase. Project teams submit to get support from funders who can allocate funding to teams directly with their tokens.","id":"d0f58fe1d22ba751","x":-1720,"y":-920,"width":765,"height":80,"color":"6"},
-		{"type":"text","text":"Proposal 1","id":"3b37ba5a2c9bcb6b","x":-1205,"y":-730,"width":250,"height":60,"color":"5"},
-		{"type":"text","text":"Proposal  ...","id":"45eedd37ac96c802","x":-1205,"y":-640,"width":250,"height":60,"color":"5"},
-		{"type":"text","text":"Proposal Y","id":"c49e93cc6bdd015f","x":-1205,"y":-550,"width":250,"height":60,"color":"5"},
-		{"type":"text","text":"The teams work on IP and submit to get judged to make sure it meets all the criteria for the fund. If it does, then it is accepted and the team wins the prize pool.","id":"1f4da868194a9be1","x":-875,"y":-920,"width":660,"height":80,"color":"6"},
-		{"type":"text","text":"IP Submission ...","id":"3cf78f36fd683fe4","x":-635,"y":-640,"width":250,"height":60},
-		{"type":"text","text":"A portion of the revenue generated from the Revenue from the created  IP will flow to the original funders of the initiative proportional to the amount of tokens they put into the project.","id":"d96d46335f72a519","x":-155,"y":-920,"width":440,"height":80,"color":"6"},
-		{"type":"text","text":"Funder 1","id":"9b1e41b37d07060c","x":35,"y":-730,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"MoonDAO Treasury ","id":"6685d16741c66bee","x":35,"y":-450,"width":250,"height":60,"color":"1"},
-		{"type":"text","text":"Funding Phase. Each Member puts ETH into a Juicebox blunt to raise a certain amount towards a specific funding objective. In return members receive tokens proportioanal to the amount they put into the fund.","id":"0ac2800e22820b2b","x":-2760,"y":-920,"width":1020,"height":80,"color":"6"},
-		{"type":"text","text":"Funder 1","id":"acb96efc2817dc8e","x":-2760,"y":-730,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Funder ...","id":"c3f1f52be39ab5ef","x":-2760,"y":-640,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Blunt","id":"f106ebe881ad9f5c","x":-2280,"y":-640,"width":250,"height":60,"color":"6"},
-		{"type":"text","text":"Funder X","id":"b4afefe446346061","x":-2760,"y":-550,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Winning IP Submission Z","id":"b5c4a52f199ef544","x":-760,"y":-550,"width":250,"height":60,"color":"3"},
-		{"type":"text","text":"IP Submission 1","id":"8bb679db9905171c","x":-720,"y":-730,"width":250,"height":60},
-		{"type":"text","text":"Funder X","id":"3ea7c58179253bc7","x":35,"y":-550,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Funder ...","id":"da5ef34bfb30182d","x":35,"y":-640,"width":250,"height":60,"color":"4"},
-		{"type":"text","text":"Credibly Neutral Judges w/ Objective Criteria Met","id":"c9a938b76dc6ba52","x":-385,"y":-240,"width":250,"height":90,"color":"2"},
-		{"type":"text","text":"Prize Pool","id":"ecc39a6b6b7a5f96","x":-385,"y":-50,"width":250,"height":60,"color":"6"},
-		{"type":"text","text":"Winning Team","id":"9e6046f7d6c1f2eb","x":35,"y":-50,"width":250,"height":60,"color":"5"},
-		{"type":"text","text":"Quadratic Funding Voted By Funders","id":"b1fa3bba9bfbefd5","x":-1330,"y":-195,"width":250,"height":90,"color":"6"},
-		{"type":"text","text":"Gnosis of Judges","id":"12b0d7dfce8924a9","x":-2280,"y":-50,"width":250,"height":60,"color":"6"}
-	],
-	"edges":[
-		{"id":"7a085c892e9d8a46","fromNode":"12b0d7dfce8924a9","fromSide":"right","toNode":"b1fa3bba9bfbefd5","toSide":"left","label":"50% ETH"},
-		{"id":"975cc7a5422dd619","fromNode":"45eedd37ac96c802","fromSide":"right","toNode":"3cf78f36fd683fe4","toSide":"left","label":"Creates"},
-		{"id":"167cd36696792d6e","fromNode":"c49e93cc6bdd015f","fromSide":"right","toNode":"b5c4a52f199ef544","toSide":"left","label":"Creates"},
-		{"id":"d09f82dc36624696","fromNode":"3b37ba5a2c9bcb6b","fromSide":"right","toNode":"8bb679db9905171c","toSide":"left","label":"Creates"},
-		{"id":"8230118729b50041","fromNode":"e49cad8dabc4bc4a","fromSide":"right","toNode":"3b37ba5a2c9bcb6b","toSide":"left","label":"Votes"},
-		{"id":"6d8ab55a2a49ddc8","fromNode":"ca5a46dedfd58fae","fromSide":"right","toNode":"c49e93cc6bdd015f","toSide":"left","label":"Votes"},
-		{"id":"b9797e1d86694790","fromNode":"f106ebe881ad9f5c","fromSide":"right","toNode":"ca5a46dedfd58fae","toSide":"left","label":"Tokens"},
-		{"id":"3220f20efc59bfe3","fromNode":"f106ebe881ad9f5c","fromSide":"right","toNode":"de58c6d40c5225fe","toSide":"left","label":"Tokens"},
-		{"id":"e8e1abc190351b50","fromNode":"f106ebe881ad9f5c","fromSide":"right","toNode":"e49cad8dabc4bc4a","toSide":"left","label":"Tokens"},
-		{"id":"6b49a1b43dfce703","fromNode":"de58c6d40c5225fe","fromSide":"right","toNode":"45eedd37ac96c802","toSide":"left","label":"Votes"},
-		{"id":"8915ca8c934dec06","fromNode":"f106ebe881ad9f5c","fromSide":"bottom","toNode":"12b0d7dfce8924a9","toSide":"top","label":"ETH"},
-		{"id":"a95f61a4a4e7a2f5","fromNode":"acb96efc2817dc8e","fromSide":"right","toNode":"f106ebe881ad9f5c","toSide":"left","label":"ETH"},
-		{"id":"65b4dff5c1dc1952","fromNode":"c3f1f52be39ab5ef","fromSide":"right","toNode":"f106ebe881ad9f5c","toSide":"left","label":"ETH"},
-		{"id":"36797ed33dc9d7fb","fromNode":"b4afefe446346061","fromSide":"right","toNode":"f106ebe881ad9f5c","toSide":"left","label":"ETH"},
-		{"id":"7fc12643ea128d5e","fromNode":"e49cad8dabc4bc4a","fromSide":"right","toNode":"c49e93cc6bdd015f","toSide":"left"},
-		{"id":"bd52b4194d829be9","fromNode":"e49cad8dabc4bc4a","fromSide":"right","toNode":"45eedd37ac96c802","toSide":"left"},
-		{"id":"f0c29b39e171bbbd","fromNode":"de58c6d40c5225fe","fromSide":"right","toNode":"3b37ba5a2c9bcb6b","toSide":"left"},
-		{"id":"168917a917e5ca2c","fromNode":"de58c6d40c5225fe","fromSide":"right","toNode":"c49e93cc6bdd015f","toSide":"left"},
-		{"id":"c1e33c42fc11173d","fromNode":"ca5a46dedfd58fae","fromSide":"right","toNode":"3b37ba5a2c9bcb6b","toSide":"left"},
-		{"id":"49671d6c62cf13ed","fromNode":"ca5a46dedfd58fae","fromSide":"right","toNode":"45eedd37ac96c802","toSide":"left"},
-		{"id":"29440d1e24374d65","fromNode":"ca5a46dedfd58fae","fromSide":"right","toNode":"c49e93cc6bdd015f","toSide":"left"},
-		{"id":"c904ce9fd515e200","fromNode":"b1fa3bba9bfbefd5","fromSide":"top","toNode":"45eedd37ac96c802","toSide":"bottom"},
-		{"id":"9cbc229a1a15ab6a","fromNode":"b1fa3bba9bfbefd5","fromSide":"top","toNode":"3b37ba5a2c9bcb6b","toSide":"bottom"},
-		{"id":"06da18e136204702","fromNode":"b5c4a52f199ef544","fromSide":"right","toNode":"9b1e41b37d07060c","toSide":"left","label":"Revenue"},
-		{"id":"b39d089aef709c7b","fromNode":"b5c4a52f199ef544","fromSide":"right","toNode":"da5ef34bfb30182d","toSide":"left","label":"Revenue"},
-		{"id":"5446918ca6a726e2","fromNode":"b5c4a52f199ef544","fromSide":"right","toNode":"3ea7c58179253bc7","toSide":"left","label":"Revenue"},
-		{"id":"929a63005ef8e907","fromNode":"b5c4a52f199ef544","fromSide":"right","toNode":"6685d16741c66bee","toSide":"left","label":"Revenue"},
-		{"id":"b9e11718a0114b14","fromNode":"b5c4a52f199ef544","fromSide":"right","toNode":"c9a938b76dc6ba52","toSide":"left"},
-		{"id":"b9a44d6bb35582d8","fromNode":"3cf78f36fd683fe4","fromSide":"right","toNode":"c9a938b76dc6ba52","toSide":"left"},
-		{"id":"0971170e06eed421","fromNode":"8bb679db9905171c","fromSide":"right","toNode":"c9a938b76dc6ba52","toSide":"left"},
-		{"id":"547923a25008a253","fromNode":"ecc39a6b6b7a5f96","fromSide":"right","toNode":"9e6046f7d6c1f2eb","toSide":"left","label":"ETH"},
-		{"id":"c014d078e9355402","fromNode":"c9a938b76dc6ba52","fromSide":"bottom","toNode":"ecc39a6b6b7a5f96","toSide":"top","label":"Confirm Winner"},
-		{"id":"905c7c670ef82821","fromNode":"b1fa3bba9bfbefd5","fromSide":"right","toNode":"b5c4a52f199ef544","toSide":"bottom","label":"50% ETH when submiited"},
-		{"id":"4498b710d1fada43","fromNode":"b1fa3bba9bfbefd5","fromSide":"right","toNode":"3cf78f36fd683fe4","toSide":"bottom"},
-		{"id":"defec4bb0c903e95","fromNode":"b1fa3bba9bfbefd5","fromSide":"top","toNode":"c49e93cc6bdd015f","toSide":"bottom","label":"50% ETH up front Proportional To Votes"},
-		{"id":"5bfa977fa53b5775","fromNode":"8bb679db9905171c","fromSide":"right","toNode":"9b1e41b37d07060c","toSide":"left","label":"Revenue"},
-		{"id":"20d700fe28ed4f1d","fromNode":"8bb679db9905171c","fromSide":"right","toNode":"da5ef34bfb30182d","toSide":"left","label":"Revenue"},
-		{"id":"01f13ac5ebfc302d","fromNode":"8bb679db9905171c","fromSide":"right","toNode":"3ea7c58179253bc7","toSide":"left"},
-		{"id":"5e2afa08289cd043","fromNode":"8bb679db9905171c","fromSide":"right","toNode":"6685d16741c66bee","toSide":"left"},
-		{"id":"b9c9c946386622fd","fromNode":"3cf78f36fd683fe4","fromSide":"right","toNode":"9b1e41b37d07060c","toSide":"left"},
-		{"id":"8f6bb0a3ffb517f2","fromNode":"3cf78f36fd683fe4","fromSide":"right","toNode":"da5ef34bfb30182d","toSide":"left"},
-		{"id":"1671594c2c903788","fromNode":"3cf78f36fd683fe4","fromSide":"right","toNode":"3ea7c58179253bc7","toSide":"left"},
-		{"id":"5a1b2db324643f6c","fromNode":"3cf78f36fd683fe4","fromSide":"right","toNode":"6685d16741c66bee","toSide":"left"},
-		{"id":"f4254a31bc7a822e","fromNode":"b1fa3bba9bfbefd5","fromSide":"right","toNode":"8bb679db9905171c","toSide":"bottom"},
-		{"id":"d0f225b851a77a52","fromNode":"12b0d7dfce8924a9","fromSide":"right","toNode":"ecc39a6b6b7a5f96","toSide":"left","label":"50% ETH"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/deprize/Economic Flywheel.canvas b/MoonDAO/docs/Projects/Active Projects/deprize/Economic Flywheel.canvas
deleted file mode 100644
index dba28e19..00000000
--- a/MoonDAO/docs/Projects/Active Projects/deprize/Economic Flywheel.canvas	
+++ /dev/null
@@ -1,25 +0,0 @@
-{
-	"nodes":[
-		{"id":"98556c475181b21a","type":"text","text":"DePrize 1","x":-540,"y":-420,"width":250,"height":60,"color":"3"},
-		{"id":"657ba44acbb5f93f","type":"text","text":"Fees from MarketPlace","x":-540,"y":-340,"width":250,"height":60,"color":"4"},
-		{"id":"9fec9f934c4e7db0","type":"text","text":"DePrize 2","x":-540,"y":-260,"width":250,"height":60,"color":"3"},
-		{"id":"e8ad9be8cd097c97","type":"text","text":"Fees from Marketplace","x":-540,"y":-180,"width":250,"height":60,"color":"4"},
-		{"id":"ef973dadccd387f3","type":"text","text":"DePrize 3","x":-540,"y":-100,"width":250,"height":60,"color":"3"},
-		{"id":"527ea194b72c31a7","type":"text","text":"Data / Real World Assets","x":-200,"y":-420,"width":250,"height":60,"color":"2"},
-		{"id":"bb2929be0aed597a","type":"text","text":"Marketplace Product / Service","x":-200,"y":-340,"width":250,"height":60,"color":"6"},
-		{"id":"d48c7f3ed9b506e3","type":"text","text":"Data / Real World Assets","x":-200,"y":-260,"width":250,"height":60,"color":"2"},
-		{"id":"ca02c06c0833df81","type":"text","text":"Marketplace Product / Service","x":-200,"y":-180,"width":250,"height":60,"color":"6"},
-		{"id":"b65df65b9247fba0","type":"text","text":"Etc.","x":-200,"y":-100,"width":250,"height":60}
-	],
-	"edges":[
-		{"id":"137518ccd9ee31d2","fromNode":"9fec9f934c4e7db0","fromSide":"right","toNode":"d48c7f3ed9b506e3","toSide":"left"},
-		{"id":"5d822bf83ac0f841","fromNode":"98556c475181b21a","fromSide":"right","toNode":"527ea194b72c31a7","toSide":"left"},
-		{"id":"cd46f820e39dc916","fromNode":"d48c7f3ed9b506e3","fromSide":"right","toNode":"ca02c06c0833df81","toSide":"right","label":"Creates"},
-		{"id":"11d706bfe67adb4c","fromNode":"527ea194b72c31a7","fromSide":"right","toNode":"bb2929be0aed597a","toSide":"right","label":"Creates"},
-		{"id":"9e66b0c8ddc002cc","fromNode":"bb2929be0aed597a","fromSide":"left","toNode":"657ba44acbb5f93f","toSide":"right"},
-		{"id":"2bf8c44aab21ca47","fromNode":"657ba44acbb5f93f","fromSide":"left","toNode":"9fec9f934c4e7db0","toSide":"left","label":"Funds"},
-		{"id":"4594eb9d05659ae4","fromNode":"ca02c06c0833df81","fromSide":"left","toNode":"e8ad9be8cd097c97","toSide":"right"},
-		{"id":"f74d3dec3f911eb8","fromNode":"e8ad9be8cd097c97","fromSide":"left","toNode":"ef973dadccd387f3","toSide":"left","label":"Funds"},
-		{"id":"1ac9e1db36cb5b05","fromNode":"ef973dadccd387f3","fromSide":"right","toNode":"b65df65b9247fba0","toSide":"left"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/deprize/Layered Mental Model.canvas b/MoonDAO/docs/Projects/Active Projects/deprize/Layered Mental Model.canvas
deleted file mode 100644
index b0b1311d..00000000
--- a/MoonDAO/docs/Projects/Active Projects/deprize/Layered Mental Model.canvas	
+++ /dev/null
@@ -1,24 +0,0 @@
-{
-	"nodes":[
-		{"id":"bc9cfdbbab234a2e","type":"text","text":"Capital Allocation","x":560,"y":40,"width":250,"height":60,"color":"4"},
-		{"id":"62c6920f48e3dec9","type":"text","text":"Governance","x":560,"y":120,"width":250,"height":60,"color":"4"},
-		{"id":"afbbe21b5aa759ab","type":"text","text":"Control","x":820,"y":40,"width":250,"height":60,"color":"5"},
-		{"id":"46704b252a941b89","type":"text","text":"Command","x":820,"y":120,"width":250,"height":60,"color":"5"},
-		{"id":"fab68448a378da5d","type":"text","text":"Labor","x":560,"y":-40,"width":250,"height":60,"color":"4"},
-		{"id":"42d36cc3af1b4ac8","type":"text","text":"Execution","x":820,"y":-40,"width":250,"height":60,"color":"5"},
-		{"id":"1a58a5ebc8a15838","type":"text","text":"User","x":300,"y":-40,"width":250,"height":60,"color":"3"},
-		{"id":"4136bb1f6bba44cd","type":"text","text":"Application Layer","x":300,"y":40,"width":250,"height":60,"color":"3"},
-		{"id":"82a38e0319c5d77d","type":"text","text":"Operating System","x":300,"y":120,"width":250,"height":60,"color":"3"},
-		{"id":"7adf822b36ed45cf","type":"text","text":"Team 6","x":155,"y":-40,"width":125,"height":60,"color":"6"},
-		{"id":"73ba5244cd6d7b91","type":"text","text":"DePrize 1","x":-500,"y":40,"width":250,"height":60,"color":"6"},
-		{"id":"9fa076fac1cb17d3","type":"text","text":"Governance / Constitution: The Senate, Executive Branch, Member House","x":-500,"y":120,"width":780,"height":60,"color":"6"},
-		{"id":"0ba19a99e2d616ab","type":"text","text":"Team 2","x":-370,"y":-40,"width":120,"height":60,"color":"6"},
-		{"id":"7000c1bfd8c8de8a","type":"text","text":"Team 4","x":-115,"y":-40,"width":125,"height":60,"color":"6"},
-		{"id":"158ad932dc91bb27","type":"text","text":"Team 5","x":20,"y":-40,"width":125,"height":60,"color":"6"},
-		{"id":"32e3001789468069","type":"text","text":"DePrize 3","x":20,"y":40,"width":260,"height":60,"color":"6"},
-		{"id":"2efa94c5b3cc1651","type":"text","text":"Team 3","x":-245,"y":-40,"width":125,"height":60,"color":"6"},
-		{"id":"3adae70d071564da","type":"text","text":"DePrize 2","x":-245,"y":40,"width":255,"height":60,"color":"6"},
-		{"id":"f03a90f0418f6d2d","type":"text","text":"Team 1","x":-500,"y":-40,"width":125,"height":60,"color":"6"}
-	],
-	"edges":[]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/desci-journal/MoU DeSci Labs x MoonDAO.md b/MoonDAO/docs/Projects/Active Projects/desci-journal/MoU DeSci Labs x MoonDAO.md
deleted file mode 100644
index 48e0d524..00000000
--- a/MoonDAO/docs/Projects/Active Projects/desci-journal/MoU DeSci Labs x MoonDAO.md	
+++ /dev/null
@@ -1,48 +0,0 @@
-Date: July 15th, 2023  
-Author: [@manuelolariu](@manuelolariu.md)
-
-[Manuel Olariu](@manuelolariu.md)
-MoonDAO
-
-[Erik van Winkle](Erik%20van%20Winkle.md)
-[DeSci Labs](DeSci%20Labs.md)
-
-
-# Memorandum of Understanding ([MOU](MOU.md)) for Partnership
-
-## 1. Purpose
-1.1. The purpose of this partnership is to foster collaboration and innovation in space science and engineering, with a particular focus on decentralized science initiatives and web3 tooling. The aim is to leverage the expertise and resources of both organizations to advance the frontiers of space exploration and further our shared mission.
-
-## 2. Scope of Collaboration
-2.1. Academic Partnerships: MoonDAO and DeSci Labs will explore academic collaborations to promote scientific research, knowledge sharing, and technology transfer in the field of space exploration.
-
-This will include joint research projects, exchange programs, and academic publications.
-
-2.2. Scientific & Engineering Tasks for Lunar Settlement: Both parties will work together to provide members with the tools to work on science & engineering tasks necessary for the development of a lunar settlement.
-
-This may involve designing infrastructure, systems, and technologies to support scientific discoveries for a sustainable human presence on the Moon.
-## 3. Specific Projects
-3.1. Open/ Decentralized Science: Community Utilization of DeSci Nodes and other present and future products of DeSci Labs.
-- What DeSci Labs offers
-	- Access to DeSci Nodes publishing tools for MoonDAO members 
-- Benefits for MoonDAO
-	- Integrate scientific publishing tools like a Decentralized Journal 
-	- Implement a peer-review process for papers
-	- Early adopters for DeSci tools
-## 4. Intellectual Property
-4.1. Both parties acknowledge that any intellectual property resulting from joint research or collaborative projects will be shared in accordance with mutually agreed terms, ensuring fair and equitable distribution of rights and benefits.
-## 5. Governance and Partnership Onboarding
-5.1. Both parties will actively participate in the governance process of the partnership. This includes regular meetings, joint decision-making, and the establishment of a point of contact to ensure continuous mutual benefits and project selection, evaluation, and implementation together with the community and governance systems in place.
-
-## 6. Duration and Termination
-6.1. This MOU shall be effective from the date of signature and remain in force for a period of 1 year, unless terminated earlier by mutual agreement or due to exceptional circumstances.
-
-6.2. Either party may terminate this agreement by providing 30 days' written notice to the other party, detailing the reasons for termination.
-
-This MOU is not legally binding and does not create any financial obligations or liabilities between the parties. It serves as a preliminary document for expressing the parties' intent to collaborate and establishes a framework for further negotiations and agreements.
-
-Additional Resources:
-- DeSci Labs base links: [Website](https://www.desci.com/), [Twitter](https://twitter.com/DeSciLabs), [Discord](https://discord.gg/juwrV6RvfZ), [Nodes Application](https://nodes.desci.com/)
-- DeSci Foundation base links: [Website](https://descifoundation.org/), [Twitter](https://twitter.com/DesciFoundation), [dPID](https://www.dpid.org/), [Future of Science Seminars](https://www.youtube.com/playlist?list=PLrER0V_Xme6NjO8d3z4luIEd8yP7kwOfV)
-- [NASA Reproducible Demo Node](https://beta.dpid.org/46)
-- Longevist (VitaDAO) collaboration: [Announcement Tweet](https://twitter.com/longevist_xyz/status/1645440648890204160), [DAO Governance](https://gov.vitadao.com/t/vdp-75-the-longevist-a-collection-of-the-top-longevity-research/1028) Proposal
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/desci-journal/Publish a reproducible work on DeSci Labs.md b/MoonDAO/docs/Projects/Active Projects/desci-journal/Publish a reproducible work on DeSci Labs.md
deleted file mode 100644
index 1dec5dc8..00000000
--- a/MoonDAO/docs/Projects/Active Projects/desci-journal/Publish a reproducible work on DeSci Labs.md	
+++ /dev/null
@@ -1,15 +0,0 @@
----
-tags:
-  - task
-  - project/desci-journal
----
-https://nodes.desci.com/
-
-_reproducibility_ is not _replication_
-- link the code and data and reproduce the results
-- _not_ replicating the experiments
-
-1. find a paper with code and data
-	1. https://www.zenodo.org/record/6025377
-2. remake the figures with the code and data
-3. publish the work on a desci node
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Home.canvas b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Home.canvas
deleted file mode 100644
index 3f691e1a..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Home.canvas	
+++ /dev/null
@@ -1,17 +0,0 @@
-{
-	"nodes":[
-		{"type":"file","file":"MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Network Topology Proposal.md","id":"92a28bab80128405","x":-1099,"y":-900,"width":679,"height":108,"color":"6"},
-		{"type":"file","file":"MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms Project Home.md","id":"decba5f4bab53e93","x":-800,"y":-700,"width":760,"height":240},
-		{"type":"file","file":"projects/lunar-comms/journal/Reading List.md","id":"d110a7b7f5e38d96","x":100,"y":-800,"width":700,"height":420},
-		{"type":"file","file":"projects/lunar-comms/journal/captain's log.md","id":"8c2a67d4ba2ab0c0","x":-340,"y":-380,"width":400,"height":120,"color":"4"},
-		{"type":"file","file":"MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure.md","id":"927473345dee1583","x":-800,"y":-180,"width":748,"height":400,"color":"3"},
-		{"type":"file","file":"MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Research Notes.md","id":"8d6fd98f7cbb193a","x":-1060,"y":-387,"width":441,"height":127,"color":"5"},
-		{"id":"ed888377ae9ad0bb","x":133,"y":-55,"width":267,"height":75,"type":"text","text":"#project/lunar-comms, "}
-	],
-	"edges":[
-		{"id":"dcb4c82388b9aa3b","fromNode":"92a28bab80128405","fromSide":"bottom","toNode":"decba5f4bab53e93","toSide":"top"},
-		{"id":"07ab4d8f401cc660","fromNode":"decba5f4bab53e93","fromSide":"right","toNode":"d110a7b7f5e38d96","toSide":"left"},
-		{"id":"55f761492f3aa94c","fromNode":"decba5f4bab53e93","fromSide":"bottom","toNode":"8c2a67d4ba2ab0c0","toSide":"left"},
-		{"id":"a5f363e69680e428","fromNode":"decba5f4bab53e93","fromSide":"bottom","toNode":"8d6fd98f7cbb193a","toSide":"right"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms Project Home.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms Project Home.md
deleted file mode 100644
index 68c8a080..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms Project Home.md	
+++ /dev/null
@@ -1,9 +0,0 @@
----
-tags: project/lunar-comms
----
-Proposal:: [[Network Topology Proposal]]
-GitHub:: https://github.com/Official-MoonDao/lunar-comms
-Dework:: https://app.dework.xyz/moondao/lunar-comms/view/board-ll7f6s8x 
-Coordinape:: https://app.coordinape.com/circles/16935 
-Google Drive:: https://drive.google.com/drive/folders/1ShhRGmpVNglUcu3RsECko_I97Xcm1yW_?usp=drive_link
-
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms.canvas b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms.canvas
deleted file mode 100644
index 48d10375..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Lunar Comms.canvas	
+++ /dev/null
@@ -1,31 +0,0 @@
-{
-	"nodes":[
-		{"type":"text","text":"","id":"5579554bc9a58ecf","x":-920,"y":-270,"width":250,"height":60},
-		{"type":"text","text":"","id":"9d4f381da60c634a","x":-900,"y":-240,"width":250,"height":60},
-		{"type":"text","text":"Lunar Sat Array","id":"fa7c0b1deae1281e","x":-880,"y":-210,"width":250,"height":60},
-		{"type":"text","text":"Lunar South Pole Ground Station","id":"08398c89466f9990","x":-880,"y":-90,"width":250,"height":60},
-		{"type":"text","text":"End Bot / Person Address","id":"7c43a886e9ac7578","x":-880,"y":30,"width":250,"height":60},
-		{"type":"file","file":"philiplinden/captain's log/attachments/Pasted image 20230819155232.png","id":"2d5c94818d095706","x":-480,"y":-700,"width":484,"height":251},
-		{"type":"file","file":"philiplinden/captain's log/attachments/Pasted image 20230819155013.png","id":"869c4fb167693f9a","x":-180,"y":-60,"width":989,"height":413},
-		{"type":"text","text":"Earth-Based Lunar Sats","id":"f53787c2caf99e4d","x":-480,"y":-275,"width":250,"height":60},
-		{"type":"text","text":"Ground Station","id":"a960914efecf7211","x":-100,"y":-275,"width":250,"height":60},
-		{"type":"text","text":"End User Address","id":"c5ca263aa5ec7f7f","x":240,"y":-270,"width":250,"height":50},
-		{"type":"text","text":"#project/lunar-comms","id":"1fd335806f800633","x":304,"y":-789,"width":250,"height":60}
-	],
-	"edges":[
-		{"id":"6c1249e0671adf94","fromNode":"fa7c0b1deae1281e","fromSide":"bottom","toNode":"08398c89466f9990","toSide":"top"},
-		{"id":"e6d0f63862fa39cd","fromNode":"08398c89466f9990","fromSide":"bottom","toNode":"7c43a886e9ac7578","toSide":"top"},
-		{"id":"caac56cc032bd863","fromNode":"08398c89466f9990","fromSide":"top","toNode":"fa7c0b1deae1281e","toSide":"bottom"},
-		{"id":"2219eca6caeff767","fromNode":"7c43a886e9ac7578","fromSide":"top","toNode":"08398c89466f9990","toSide":"bottom"},
-		{"id":"aa056aa891e56797","fromNode":"a960914efecf7211","fromSide":"right","toNode":"c5ca263aa5ec7f7f","toSide":"left"},
-		{"id":"2a8d33a771dcbaa4","fromNode":"a960914efecf7211","fromSide":"left","toNode":"f53787c2caf99e4d","toSide":"right"},
-		{"id":"7cf4964b84e8712a","fromNode":"f53787c2caf99e4d","fromSide":"left","toNode":"5579554bc9a58ecf","toSide":"right"},
-		{"id":"d9165bb6484ba87c","fromNode":"f53787c2caf99e4d","fromSide":"left","toNode":"9d4f381da60c634a","toSide":"right"},
-		{"id":"f57d0b0febafd748","fromNode":"f53787c2caf99e4d","fromSide":"left","toNode":"fa7c0b1deae1281e","toSide":"right"},
-		{"id":"dfe198ffbc4834e3","fromNode":"f53787c2caf99e4d","fromSide":"left","toNode":"08398c89466f9990","toSide":"right"},
-		{"id":"07fa9ca5b4434d2b","fromNode":"a960914efecf7211","fromSide":"left","toNode":"fa7c0b1deae1281e","toSide":"right"},
-		{"id":"e3050226703c1f18","fromNode":"a960914efecf7211","fromSide":"left","toNode":"08398c89466f9990","toSide":"right"},
-		{"id":"d7eff75dd8ecd751","fromNode":"a960914efecf7211","fromSide":"left","toNode":"7c43a886e9ac7578","toSide":"right"},
-		{"id":"314b89f3d9ca4814","fromNode":"f53787c2caf99e4d","fromSide":"left","toNode":"7c43a886e9ac7578","toSide":"right"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Primer on Lunar Communications.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Primer on Lunar Communications.md
deleted file mode 100644
index a9a709e6..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/Primer on Lunar Communications.md	
+++ /dev/null
@@ -1,136 +0,0 @@
----
-tags: notes
----
-> [!warning]
-> This document was originally authored as part of the Space Engineering Guild project in April 2023, not the Lunar Comms project.
-# A Primer on Future Lunar Communications Infrastructures & Related Challenges
-
-Author:: [[@philiplinden|Philip Linden]]
-Space Engineering Guild, [[MoonDAO]]
-Apr 4, 2023
-
-link:: https://docs.google.com/document/d/1Wj4L7IGK1iwLjSjg0FwqYjgjxByOaWxGbJ5iSWf9pE8/edit
-
-> [!note] Abstract
-> There is a lot of interest and necessity for lunar communications infrastructure, but so far most endeavors are experimental, expensive, or difficult to access. There is lots of new technology and a ton of potential for developing new business and governance models. This topic is still nascent and is growing rapidly―there are no clear answers, and that means there's still a lot we can explore.
-
-# It's a solved problem―but that's not the problem
-
-## It's not easy, but it can be done
-
-First, the Moon is very far away from Earth. The average distance between the Earth and the Moon is about 384,400 kilometers―nearly ten times further than the distance from Earth to GPS satellites. This means that radio signals take about two and a half seconds to travel from the Earth to the Moon and back. When a communication signal is sent through cislunar space, the beam spreads out and the intensity of the signal becomes weaker [proportionally to the square of the distance traveled](https://en.wikipedia.org/wiki/Inverse-square_law). Because the Moon is so far away, the transmitted signals must either be very powerful or must be aimed with very good accuracy to be received at the other end.
-
-Second, the Moon has no atmosphere. This means that there is nothing to block or absorb radio signals. As a result, radio signals from the Earth can be easily scattered by the Moon's surface, unlike on Earth where radio signals can bounce around in the atmosphere to the other side of the globe.[^1] Moreover, the Moon has no magnetic field. This means that the Moon is not protected from the solar wind. The solar wind is a stream of charged particles from the Sun. The solar wind can interfere with radio signals.
-
-All of these factors make telecommunications difficult at and around the Moon. However, there are a number of technologies that can be used to overcome these challenges. For example, high-gain antennas or lasers can be used to focus signals and improve reception.[^2][^3] Delay- and disruption-tolerant networking protocols can be used to make connections more resilient. [^4][^5] And much more. [^6][^7][^8][^9][^10]
-
-## Restricted to the privileged few
-
-While the technology capable of overcoming these challenges has been used for decades to command and control spacecraft in cislunar space, one aspect remains relatively unchanged: *access* (or lack thereof).
-
-Today, NASA's Deep Space Network (DSN) and other state-owned equivalents are the primary resources used to transmit and receive data from cislunar spacecraft. DSN is limited in bandwidth and schedule, which are already heavily oversubscribed,[^11][^12][^13] and must compete with all other deep space missions served by the DSN. Not to mention using a government-operated resource has a multitude of ever-evolving geopolitical and regulatory implications in its own right.
-
-Even with a network to use, the technology needed to interface with it is still relatively expensive and/or nascent.[^9][^14][^15][^16] Looking at the landscape of low Earth-orbit (LEO) satellite missions before and after the introduction of the CubeSat standard, it is clear that the barrier to entry for space missions is, well, the barrier itself! An accessible platform for conducting missions in space―such as open reference designs, commodity components, and standardized interfaces―can bootstrap an entire thriving industry that would be otherwise infeasible for all but the largest institutions.[^17][^18]
-
-The number of missions that plan to operate on and around the Moon is large and growing every day [^19]. It is clear that more communications infrastructure is needed in order to sustain a diverse, multi-national ecosystem of public and private/commercial lunar activities. 
-
-# Governance & policy is unproven and untested
-
-The whole business of lunar communications infrastructure is still not really figured out (pun intended). While there has been discussion about the implications of different paradigms of shared infrastructure,[^10][^20][^21][^22][^23] many of the governance and economic gray areas remain nebulous. For example, here is a non-exhaustive list of open questions:
-
-- Communications links are literally a life-and-death resource for spacecraft and crewed missions alike. What if a spacecraft/astronaut dies because a network operator did not allow them to send/receive data over a link that was available?
-- Is the network operator at fault? Is this fair play?
-- Does the ethical situation change if the two parties are nations in conflict?
-- Does the ethical situation change if one or both parties are private businesses?
-- What is the business model of a communications relay service?
-- Do users pay per bit of data? Some bits take more work to transmit than others.
-- If data is lost at an endpoint, but the network operator still did work to relay data between the endpoints, does the user still owe the network operator for the transmission?
-- Do users pay a fee for access to the network? A connection is not always guaranteed due to the dynamic and chaotic nature of a cislunar communications network. What if a user pays for the service but the service cannot serve that user due to coverage or line-of-sight issues?
-- If two paying users request services but the network can only support one user at a time, which user gets priority?
-- Does the ethical situation change if the content of the data contains life-or-death information? 
-- What if the requests are coming from government actors?
-    
-
-# Interesting examples
-
-There are many, many organizations looking into lunar communications infrastructures. I've picked out a few that were interesting to me.
-
-## A non-exhaustive list of relevant missions
-
-State-sponsored missions: [^5], [^7], [^8], [^24], [^25]
-
-Private & Commercial missions: [^26][^27][^28]
-
-## Selected relevant technologies
-
-- Modular, commoditized optical terminals that don't need a priori knowledge of where the origin of the signal is coming from: [^16]
-	- The spacecraft is divided into many small, steerable optical terminals facing out in many directions. Once the terminal determines where the signal is coming from, it can form a two-way link by selecting the module most closely aligned to the signal's origin, then using a steering mirror for fine pointing to maintain the link. The spacecraft bus remains still and does not need to perform a rotational slew to establish or maintain a link.
-	- The terminals have many diodes that figure out on-the-fly where a signal is coming from, just like how an HTC Vive determines its location in a room from being illuminated. The terminal does not need to know any information about where the transmission originated in order to establish a link.
-	- Since there are modules with transmitters in every direction, the terminal can establish a link with another spacecraft in any arbitrary direction. Theoretically, it could also maintain a link even if the other craft moves across the terminal's local sky.
-- Terrestrial dishes capable of communicating with cislunar spacecraft are entering the commercial sector of the industry: [^28]
-	- When services are provided by commercial entities, the ecosystem is ripe for competition and innovation.
-	- More service providers mean more access.
-- New network protocols allow intermediate links in a network to attach "ephemeral" information to packets as they move through the network, without reading the entire contents of the packet: [^29][^30][^31][^32]
-	- For example, consider a situation where two intermediate nodes encrypt a packet and the terminal nodes (separately) encrypt the data. In this example, the transmission between two nodes may be encrypted and decrypted along the way in order to securely send a packet, while keeping the contents of the packet only readable to the end user.
-	- This opens the door for third-party relay systems to intelligently and securely hold-and-pass data around in a delay/disruption-tolerant network.
-
-## What about a near-side lunar surface installation?
-
-Question: The Moon is tidally locked so there is a whole hemisphere of the Moon that always has line-of-sight to the Earth. Would it be feasible to set up a large antenna on the near side of the Moon for a communications relay?
-
-(Author's note: this is not an "answer" per se, since a whole thesis could probably explore this topic. What follows are my technical and personal opinions.)
-
-Of course, a system installed on the surface of the near side of the Moon would have a constant view of the Earth―but that's not the whole story. Finding a location on the lunar surface with continuous line-of-sight to terrestrial communication systems is easy in central latitudes, but those locations are usually undesirable for long-term lunar missions.
-
-Publications discussing continuous communication to lunar poles: [^33][^34][^35]
-
-Below is a list of considerations that we'd need to look into before a mission like this could be declared feasible with confidence:
-
-- Lunar night. The Moon is tidally locked to the Earth, but it still rotates with respect to the Sun. The "dark side" of the Moon is only actually dark half the time, the other half of the time it is lit by the Sun just not visible from Earth (new Moon, remember?). A lunar night lasts for about 23.5 Earth days. The poles are so desirable as a location for lunar activity because if you're at the pole it doesn't take much to get back in the sunlight―if a spacecraft is located at the lunar equator it has to wait out the whole lunar night.
-- The lunar night is a really harsh environment for spacecraft―23.5 Earth days of perpetual darkness with temperatures as low as -130C the whole time. Typical operating temperatures for most electronics are between -30 and 90C, so a heater would have to be working overtime to keep the system alive through the night, and the power system would have to support that kind of load without solar energy.[^36][^37]
-- Even if the spacecraft was equipped with a bangin' heater, that heat doesn't come for free. 
-- Electric resistive heaters have a typical power efficiency of 80% (0.8W of heat is generated for every 1W of energy consumed) so the spacecraft would have to store enormous amounts of charge to last the whole night. That energy would be able to be used by other systems in daylight periods, but more than likely the system would have to spend all its power on heaters during the night. This situation has killed a number of lunar missions over the years.
-- Radioisotope thermal generators (RTGs) produce heat on their own through radioactive decay, and the heat is converted to electric charge and spread around the thermal control system.[^38] This would enable nighttime operations from both a thermal and a power perspective. Sounds like a great idea, but RTGs are super expensive and not easy to get. 
-- Visibility to other actors. Establishing a link to Earth is one objective for a lunar communications relay, but another objective is to link to other lunar actors. Here's a discussion on the topic of visibility and link access for various orbits and latitudes of the lunar surface: [^39]
-
-# References
-
-[^1]: [[@RadioHistory]] "Radio's First Message -- Fessenden and Marconi." https://ewh.ieee.org/reg/7/millennium/radio/radio_differences.html (accessed Apr. 04, 2023).
-[^2]: [[@Araki2021]] T. Araki, “A trade-off study of lunar-earth optical communication links,” in International Conference on Space Optics — ICSO 2020, SPIE, Jun. 2021, pp. 811–819. doi: 10.1117/12.2599331.
-[^3]: [[@RazaEtAl2022]] W. Raza et al., “Toward a Hybrid RF/Optical Lunar Communication System (LunarComm),” IEEE Network, vol. 36, no. 6, pp. 76–83, Nov. 2022, doi: 10.1109/MNET.103.2100419.
-[^4]: [[@CainiFiore2012]] C. Caini and V. Fiore, “Moon to earth DTN communications through lunar relay satellites,” in 2012 6th Advanced Satellite Multimedia Systems Conference (ASMS) and 12th Signal Processing for Space Communications Workshop (SPSC), Sep. 2012, pp. 89–95. doi: 10.1109/ASMS-SPSC.2012.6333112.
-[^5]: [[@IsraelEtAl2020]] D. J. Israel et al., “LunaNet: a Flexible and Extensible Lunar Exploration Communications and Navigation Infrastructure,” in 2020 IEEE Aerospace Conference, Big Sky, MT, USA: IEEE, Mar. 2020, pp. 1–14. doi: 10.1109/AERO47225.2020.9172509.
-[^6]: [[@Nokia4G]] “Nokia aims for the Moon with LTE/4G,” Nokia. https://www.nokia.com/about-us/newsroom/articles/nokia-aims-for-the-moon-with-lte4g/ (accessed Apr. 04, 2023).
-[^7]: [[@Brown2020]] K. Brown, “NASA Announces Partners to Advance 2020 ‘Tipping Point’ Technologies,” NASA, Oct. 14, 2020. http://www.nasa.gov/press-release/nasa-announces-partners-to-advance-tipping-point-technologies-for-the-moon-mars (accessed Apr. 04, 2023).
-[^8]: [[@HarleEtAl]] N. O. Harle et al., “Lunar comms and nav infrastructure – first data relay orbiter Lunar Pathfinder, operational in 2024, paves the way for full constellation by 2030s,” in ASCEND 2021, American Institute of Aeronautics and Astronautics. doi: 10.2514/6.2021-4132.
-[^9]: [[@PasqualeEtAl2022]] A. Pasquale, G. Zanotti, J. Prinetto, M. Ceresoli, and M. Lavagna, “Cislunar distributed architectures for communication and navigation services of lunar assets,” Acta Astronautica, vol. 199, pp. 345–354, Oct. 2022, doi: 10.1016/j.actaastro.2022.06.004.
-[^10]: [[@Naseem2022]] M. Naseem, “Last-mile Analogies for a Lunar Communications Network - Open Lunar Foundation,” Open Lunar Foundation, Jan. 26, 2022. https://www.openlunar.org/library/last-mile (accessed Feb. 11, 2023).
-[^11]: [[@CarruthEtAl2010]] B. Carruth, M. Johnston, A. Coffman, M. Wallace, B. Arroyo, and S. Malhotra, “A Collaborative Scheduling Environment for NASA’s Deep Space Network,” in SpaceOps 2010 Conference, Huntsville, Alabama: American Institute of Aeronautics and Astronautics, Apr. 2010. doi: 10.2514/6.2010-2284.
-[^12]: [[@ClementJohnston]] B. J. Clement and M. D. Johnston, “The Deep Space Network Scheduling Problem”.
-[^13]: [[@ShourabouraEtAl]] C. Shouraboura, M. D. Johnston, and D. Tran, “Prioritization and Oversubscribed Scheduling for NASA’s Deep Space Network”.
-[^14]: [[@Cheetham2021]] B. Cheetham, “Cislunar Autonomous Positioning System Technology Operations and Navigation Experiment (CAPSTONE),” in ASCEND 2021, Las Vegas, Nevada & Virtual: American Institute of Aeronautics and Astronautics, Nov. 2021. doi: 10.2514/6.2021-4128.
-[^15]: [[@KellerEtAl2016]] J. W. Keller, N. E. Petro, and R. R. Vondrak, “The Lunar Reconnaissance Orbiter Mission – Six years of science and exploration at the Moon,” Icarus, vol. 273, pp. 2–24, Jul. 2016, doi: 10.1016/j.icarus.2015.11.024.
-[^16]: [[@VelazcoEtAl]] J. E. Velazco, A. C. Aguilar, A. R. Klaib, U. S. Escobar, S. E. Cornish, and J. C. Griffin, “Development of Omnidirectional Optical Terminals for Swarm Communications and Navigation”.
-[^17]:  [[@ChinEtAl2008]] A. Chin, R. Coelho, L. Brooks, G. Student, R. Nugent, and J. P. Suari, “Standardization Promotes Flexibility: A Review of CubeSats’ Success,” 2008. Accessed: Feb. 11, 2023. [Online]. Available: https://www.semanticscholar.org/paper/Standardization-Promotes-Flexibility%3A-A-Review-of-Chin-Coelho/2ccd7bcb1f253432bc60dcebd2a4dc2736c3f514#references
-[^18]: [[@VillelaEtAl2019]] T. Villela, C. A. Costa, A. M. Brandão, F. T. Bueno, and R. Leonardi, “Towards the Thousandth CubeSat: A Statistical Overview,” International Journal of Aerospace Engineering, vol. 2019, pp. 1–13, Jan. 2019, doi: 10.1155/2019/5063145.
-[^19]: [[@Al-EkabiRobinson2021]] C. Al-Ekabi and C. Robinson, “Recent Lunar Activity, Stakeholders and Incentives – A Backgrounder,” Open Lunar Foundation, May 2021. Accessed: Feb. 11, 2023. [Online]. Available: https://www.openlunar.org/library/recent-lunar-activity-stakeholders-and-incentives-a-backgrounder
-[^20]: [[@Jardine2022b]] S. Jardine, “Building Lunar Security and Cooperation Through an Astropolitcal Lens- how to construct normative behaviours on the moon- enter the registry,” Open Lunar Foundation, Dec. 16, 2022. https://www.openlunar.org/library/open-lunar-registry-project-blog-post-series-blog-4 (accessed Feb. 11, 2023).
-[^21]: [[@Schingler2020]] J. K. Schingler, “Space Tenure: The Policies of Sustained Lunar Presence - Open Lunar Foundation,” Open Lunar Foundation. https://www.openlunar.org/library/space-tenure-the-policies-of-sustained-lunar-presence (accessed Feb. 11, 2023).
-[^22]: S. Jardine, “Building Lunar Security and Cooperation Through an Astropolitical Lens- Why Normative Behaviours are Needed for Lunar Activity,” Open Lunar Foundation, Dec. 14, 2022. https://www.openlunar.org/library/open-lunar-registry-blog-post-series-blog-3 (accessed Feb. 11, 2023).
-[^23]: [[@Jardine2022a]] S. Jardine, “Building Lunar Security and Cooperation Through an Astropolitical Lens- the role of normative behaviours in creating stability,” Open Lunar Foundation, Nov. 10, 2022. https://www.openlunar.org/library/open-lunar-registry-project-blog-post-series-blog-1 (accessed Feb. 11, 2023).
-[^24]: [[@GiordanoEtAl2022]] P. Giordano, F. Malman, R. Swinden, P. Zoccarato, and J. Ventura-Traveset, “The Lunar Pathfinder PNT Experiment and Moonlight Navigation Service: The Future of Lunar Position, Navigation and Timing,” presented at the 2022 International Technical Meeting of The Institute of Navigation, Long Beach, California, Long Beach, California, Feb. 2022, pp. 632–642. doi: 10.33012/2022.18225.
-[^25]: [[@CosbyTai2022]] M. Cosby and W. Tai, “Report of the Interagency Operations Advisory Group Lunar Communications Architecture Working Group,” Lunar Communications Architecture Working Group, Jan. 2022.
-[^26]: [[@Foust2022]] J. Foust, “Quantum Space raises $15 million for cislunar spacecraft,” SpaceNews, Dec. 13, 2022. https://spacenews.com/quantum-space-raises-15-million-for-cislunar-spacecraft/ (accessed Apr. 04, 2023).
-[^27]: [[@CrescentSpace2023]] “ParsecTM Service from Lockheed Martin,” Lockheed Martin, Mar. 28, 2023. https://www.lockheedmartin.com/en-us/news/features/2021/lunar-communication-and-navigation-network.html (accessed Apr. 04, 2023).
-[^28]:  [[@KongsbergSatelliteServices]] Kongsberg Satellite Services, “KSAT to invest in a dedicated antenna network for lunar missions.” https://www.ksat.no/news/news-archive/2022/ksat-to-invest-in-antenna-network-for-lunar-missions/ (accessed Feb. 03, 2023).
-[^29]: [[@BurleighEtAl2022]] S. Burleigh, K. Fall, and E. J. Birrane, “Bundle Protocol Version 7,” Internet Engineering Task Force, Request for Comments RFC 9171, Jan. 2022. doi: 10.17487/RFC9171.
-[^30]: [[@DTN7]] “DTN7,” DTN7. https://dtn7.github.io/ (accessed Apr. 04, 2023).
-[^31]: E. J. Birrane and K. McKeever, “Bundle Protocol Security (BPSec),” Internet Engineering Task Force, Request for Comments RFC 9172, Jan. 2022. doi: 10.17487/RFC9172.
-[^32]: [[@awesomeDTN]] “dtn7/awesome-dtn: A curated list of awesome delay- and disruption-tolerant networking.” https://github.com/dtn7/awesome-dtn (accessed Apr. 04, 2023).
-[^33]: [[@MalmstromEtAl2006]] R. Malmström, A. Lo, N. Brown, and G. Haney, “Continuous Communications to the Moon’s South Pole,” in Space 2006, in AIAA SPACE Forum. American Institute of Aeronautics and Astronautics, 2006. doi: 10.2514/6.2006-7453.
-[^34]: [[@DivsalarEtAl2019]] D. Divsalar, M. S. Net, and K.-M. Cheung, “Acquisition and tracking for communications between Lunar South Pole and Earth,” in 2019 IEEE Aerospace Conference, Mar. 2019, pp. 1–14. doi: 10.1109/AERO.2019.8742112.
-[^35]: [[@Reinhold1990]] A. Reinhold, A Solar Powered Station at a Lunar Pole. 1990.
-[^36]:  [[@BiswasEtAl2021]] J. Biswas, P. Q. Malzone, and F. Rößler, “Energy storage selection and operation for night-time survival of small lunar surface systems,” Acta Astronautica, vol. 185, pp. 308–318, Aug. 2021, doi: 10.1016/j.actaastro.2021.04.042.
-[^37]: [[@Petro2020]] A. Petro, “Surviving and Operating Through the Lunar Night,” in 2020 IEEE Aerospace Conference, Mar. 2020, pp. 1–6. doi: 10.1109/AERO47225.2020.9172730.
-[^38]: [[@NasaRps]] “Light-Weight Radioisotope Heater Unit | Thermal Systems,” NASA RPS: Radioisotope Power Systems. https://rps.nasa.gov/power-and-thermal-systems/thermal-systems/light-weight-radioisotope-heater-unit (accessed Apr. 04, 2023).
-[^39]: [[@CheungLee2018]] K.-M. Cheung and C. Lee, “Lunar Relay Coverage Analysis for RF and Optical Links,” in 2018 SpaceOps Conference, Marseille, France: American Institute of Aeronautics and Astronautics, May 2018. doi: 10.2514/6.2018-2612.
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS) 3 page abstract.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS) 3 page abstract.md
deleted file mode 100644
index de0c9d0b..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS) 3 page abstract.md	
+++ /dev/null
@@ -1,55 +0,0 @@
----
-tags:
-  - project/luna-10
-  - notes
----
-## Summary of Proposed Approach
-
-Recent advancements in space technologies have prompted a surge in lunar missions, both crewed and uncrewed. Such an influx demands scalable, commercially-accessible Positioning, Navigation, and Timing (PNT) frameworks for the development of a cislunar economy. In order to bring PNT infrastructure to the lunar ecosystem and have it be as ubiquitous and useful as GNSS is terrestrially, there needs to be accurate, traceable and accessible timing and ranging infrastructure that is also resilient, reliable and flexible.
-
-Existing technology can be used to leverage the carrier signal of communications links to obtain sub-nanosecond timing and millimeter ranging. With terrestrial systems as a benchmark, our focus is to craft a comprehensive system tailored to the lunar ecosystem's challenges and the constraints of cislunar operations. Wireless 2-Way Interferometry (Wi-Wi) uses existing COTS RF chips to achieve phase-lock between precision clocks to achieve time synchronization and ranging. This approach does not require complex new technology development. The addition of a single component (Time Card, standardized by IEEE P3335) can be used to integrate a LEO platform with the cislunar PNT utility over its own pre-existing communications channels.
-
-In this study we will analyze Wi-Wi as an alternative method of implementing a PNT service to traditional GNSS constellations, and will compare the proposed method with metrics known from the current PNT solution, such as precision, availability, reliability, and throughput, in addition to costs, timeline and technology development requirements of implementing each system in a cislunar context. The goal is to develop the proposed solution to a level mature enough to predict the system’s performance relative to the number and distribution of interconnected assets, and quantitatively demonstrate that our approach becomes more robust and performant as it scales to service the anticipated demands of a thriving lunar ecosystem. The study will also consider specific lunar PNT user needs and infrastructure combination opportunities, as well as requirements for Earth / Earth Orbit systems to be usable with minimum changes for lunar applications. These metrics will be used to evaluate opportunities to improve PNT offerings for the cislunar ecosystem. As a result, it is expected that the study will demonstrate that the proposed alternative PNT infrastructure solution is superior to existing GNSS technology in scalability, cost of service, resilience, composability, and versatility.
-
-## Current State of the Art
-
-Currently, governmental agencies and the commercial sector are spearheading PNT-focused missions: 1) The European Space Agency's Lunar Pathfinder aims to address the unique communication demands of the moon's far side, bridging the gap for both commercial and institutional missions; 2) [NASA](NASA.md)'s Lunar GNSS Receiver Experiment (LuGRE) and Lunar Reconnaissance Orbiter (LRO) are delving into the intricacies of lunar GNSS constellations and polar mapping, respectively; and 3) the CAPSTONE program, currently in orbit, seeks to gather operational data ahead of the upcoming Artemis missions.
-
-Commercial endeavors like Lockheed’s Parsec and Spatiam's DTN service are paving the way for a cislunar communication link. Amidst these pioneering projects, technologies like the Time Card and Wireless Two-Way Interferometry (Wi-Wi) offer promising frameworks to build upon.
-
-## Proposed Design
-
-Traditional communication avenues can be revamped to serve dual purposes. Through the use of established links, achieving sub-nanosecond timing and millimeter-range precision becomes feasible. By equipping two distinct entities in cislunar space with stable clocks and a shared communication bandwidth, synchronization becomes a streamlined process. This synchronized environment then facilitates accurate relative ranging using wireless two-way interferometry (Wi-Wi) with the communication link's carrier signal. Essentially, all Wi-Wi demands is a standardized bandwidth and a precision clock.
-
-![](https://lh6.googleusercontent.com/YYBSpcOOOepswQKDhZRAd7jw75s8Y_m7T-bJIfJhFJk9w7hmKM90coCbBe-iJMGs7AtBW1N-CfNCYsl3YunQVUBgmaChWSPqbIkH9ER1652mVr9GEEbKqjGZgoUJDT9Y1wuoRgOK0N2YGljyFHHUblc)![](https://lh4.googleusercontent.com/VPdK8Wp2WTf_Q0Oky1LhQ0IUuFC9dI55Q5dSlLo4DnJFiqPNzpZ1xw57bvLOfTXgA3SyOfshgxKqnoId4_j9Og_YRGITz5lf80o3PiDRfXvkWCL_g6YyQ1LfqH2QjMqrJNDNbJQsQkS6NV8nLeleCB4)
-
-Figure 1: Experimental setup of Wi-Wi (left) and its clock variation and propagation delay (right)
-
-To democratize access to precision timekeeping in space, the introduction of an open reference design for a space-rated time card is proposed. This design, compatible with the latest spacecraft buses, seeks to offer a cost-effective solution (under $5,000). The system would be anchored to trusted Stratum 1 nodes that synchronize with terrestrial Universal Time Coordinated (UTC).
-
-![](https://lh4.googleusercontent.com/LxEqi7EjqgvoB4QYDvFUFUTOo6Ch-EnyX0vgOsOXypgRet7l5fCly5UXzSJP22Qei6EoWwLwgxwxhyIbIVk13n4YgtcUr2fAHcTF5pRkYOzN_wAaukLWba-vL5CqsK0CQBis2s-P5WVLktct8XLo3jk)
-
-Figure 2: Time Card with an integrated Chip-Scale Atomic Clock (CSAC)
-
-A fundamental characteristic of the proposed design is its peer-to-peer topology, ensuring resilience against centralized points of failure. The structure stands robust against interference, adversarial or accidental. The decentralized nature of the design further augments its flexibility, permitting in-flight mission adaptations and potential as a backup for lunar missions, reducing their dependence on individualized PNT structures. In essence, this philosophy aims to nurture a PNT ecosystem accommodating both public and private ventures.
-
-## Unique Insights
-
-The utilization of Wireless 2-Way Interferometry is a novel approach that maximizes the utility of existing communication modules. By deploying software-defined radios, Wi-Wi can establish time synchronization and ranging between lunar entities so long as the signal can be decoded. Our approach of cooperation and incentivization borrows insights from the success of the CubeSat. The system champions open standards, minimal entry barriers, and amplifies its resilience with every new participant. While entities remain free to deploy their proprietary PNT systems, the inclusion within this proposed structure augments their native capabilities.
-
-Further, the potential economic implications are profound. The proposed PNT infrastructure, when juxtaposed with the GNSS market, suggests abundant opportunities for token-based exchanges or premium PNT services following a similar model to terrestrial GNSS. SatNav/PNT for Earth & Space currently represents around 50% of the space industry yearly revenue, indicating the foreseeable downstream market could be valued also at billions for this cislunar service. Making it available, low cost, and secure has the potential of transforming the way we perceive and engage with lunar economies.
-
-## Technology Challenges
-
-Our proposition isn't intended to dethrone GNSS but to complement it. In anticipation of cislunar space becoming an adversarial domain, any PNT service must be robust to interference. When considering topologies for lunar PNT, a central reference node would become a single point of failure and could be targeted to disrupt PNT. By distributing time reference and synchronization between many nodes, the system can make guarantees of security and robustness to adversaries using secure decentralized data transfer. With this vision comes the challenge of crafting autonomous network clusters while ensuring data security in an open network.
-
-## Team and Teaming
-
-Spearheading this initiative is a consortium of companies and experts from diverse backgrounds, working on state-of-the-art (SoA) commercial space and SoA non-space technology companies with demonstrated skills in full life cycle engineering, hardware, software and network development, and space systems. The core team brings over 60 years of collective experience in the space industries at esteemed institutions such as Planet Labs, [SpaceX](SpaceX.md), Lockheed Martin, GoogleX, Waymo, Thales Alenia Space, and more.
-
-Key individual contributors are: [Ahmad Byagowi](Ahmad%20Byagowi.md) (50%) from [OCP-TAP](OCP-TAP.md), currently leading the Precision Time Division at Meta; [Philip Linden](@philiplinden.md) (50%) from [MoonDAO](MoonDAO.md), with space R&D experiences at [SpaceX](SpaceX.md), Lockheed Martin and Planet Labs; [Pablo Moncada-Larrotiz](@pmoncada.md) (50%) from MoonDAO, with experience at Waymo, GoogleX, and Decentralized Autonomous Organizations (DAOs). [Jacob Malthouse](Jacob%20Malthouse.md) (30%, Non US / Canadian) from [Open Lunar Foundation](Open%20Lunar%20Foundation.md), with a background in Economics and Entrepreneurship, including working for United Nations; and [Ramon Blanco Maceiras](Ramon%20Blanco%20Maceiras.md) (30%, Non-US / Spanish E2 US Visa Holder) from Added Value Solutions (AVS), with R&D and Management experiences at Thales Alenia Space for $50-500M programs.
-
-## Budget
-
-An estimated budget of $597,895.00 is projected over the 7-month contract period, this allocation encompasses personnel salaries in engineering and project management domains, and caters to the expenses affiliated with the development of simulation tools, both hardware and software.
-
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).md
deleted file mode 100644
index 4d08a8f2..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).md	
+++ /dev/null
@@ -1,27 +0,0 @@
----
-tags:
-  - project/luna-10
-  - notes
-aliases:
-  - CLOCSS
----
-Authors
-- MoonDAO
-	- [Philip Linden](@philiplinden.md)
-	- [Pablo Moncada-Larrotiz](@pmoncada.md)
-	- [Greg Search](@gregsearch.md)
-- [Open Lunar Foundation](Open%20Lunar%20Foundation.md)
-	- [Rachel Williams](Rachel%20Williams.md)
-	- [Jacob Malthouse](Jacob%20Malthouse.md)
-- [NICT](National%20Institute%20of%20Information%20and%20Communications%20Technology%20(Japan).md)
-	- [Nobuyasu Shiga](Nobuyasu%20Shiga.md)
-- [AVS](Added%20Value%20Systems.md)
-	- [Ramon Blanco Maceiras](Ramon%20Blanco%20Maceiras.md)
-	- [[Filipe Pereira]]
-- [OCP-TAP](OCP-TAP.md)
-	- [Ahmad Byagowi](Ahmad%20Byagowi.md)
-
-<iframe title="How to Build Decentralized Lunar Infrastructure on Time" src="https://www.youtube.com/embed/cd8hiubLy48?feature=oembed" height="113" width="200" allowfullscreen="" allow="fullscreen" style="aspect-ratio: 1.76991 / 1; width: 100%; height: 100%;"></iframe>
-
-![](Cislunar%20Open%20Clock%20Synchronization%20System%20(CLOCSS).pdf)
-![](LunA-10%20Soliciation%20Response_%20Lunar%20PNT%2010-pager%20.pdf)
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).pdf b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).pdf
deleted file mode 100644
index a0814fed..00000000
Binary files a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Cislunar Open Clock Synchronization System (CLOCSS).pdf and /dev/null differ
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/DARPA-EA-23-02.pdf b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/DARPA-EA-23-02.pdf
deleted file mode 100644
index efe75246..00000000
Binary files a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/DARPA-EA-23-02.pdf and /dev/null differ
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure.md
deleted file mode 100644
index 3f5f9db4..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure.md	
+++ /dev/null
@@ -1,13 +0,0 @@
----
-tags:
-  - project/lunar-comms
-  - darpa
-  - project/luna-10
----
-link:: https://www.darpa.mil/news-events/2023-08-15
-
-
-> Anticipating a burgeoning cislunar and lunar economy of scientific research and commercial development in the coming decade, [DARPA](DARPA.md) is soliciting innovative and revolutionary technical approaches to chart a vision and path toward an optimized and integrated lunar infrastructure for peaceful U.S. and international use.
-> The study’s thrust areas, derived from a subset of key sectors identified in a market analysis of the future lunar economy, include the following (with more details in the solicitation): transit/mobility; energy; communications; and other revolutionary orbital or surface infrastructure concepts. LunA-10 aims to facilitate the fusing and co-optimization of as many infrastructure sectors as possible, into key nodes that can be scaled up in the future.
-
-[[@philiplinden|@phil]] was notified of this by a colleague from AVS Space who is interested in a collab. Let's do it!!!
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10 Soliciation Response_ Lunar PNT 10-pager .pdf b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10 Soliciation Response_ Lunar PNT 10-pager .pdf
deleted file mode 100644
index a7a4bb7b..00000000
Binary files a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/LunA-10 Soliciation Response_ Lunar PNT 10-pager .pdf and /dev/null differ
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Network Topology Proposal.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Network Topology Proposal.md
deleted file mode 100644
index 53d7619a..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/luna-10/Network Topology Proposal.md	
+++ /dev/null
@@ -1,165 +0,0 @@
----
-tags:
-  - project/lunar-comms
-  - proposal
----
-# Lunar Communications Network Topology Analysis (Internal Research Study) Proposal
-
-**Author:** [@philiplinden](@philiplinden.md)
-**Date:** 2023-08-07
-[Link to proposal on Google Docs](https://docs.google.com/document/d/13OKGTcY7E_8SW2YD9gcRXCAEBr1VexCsowVhaheWaVg/edit)
-## Abstract
-
-Write a proposal for [[NASA]]'s NextSTEP-2 solicitation and submit it by August 7, 2023 with the goal of receiving funding to research Mesh, Star, Unstructured, and Hybrid network topologies for lunar communications.
-
-> [!info] Revisions
-> 
-> |Date|Summary of Changes|Reason for Revision|
-> |---|---|---|
-> |2023-08-02||First draft.|
-> |2023-08-07|- Removed NextSTEP-2 proposal submission from OKRs.<br>    <br>- Restructured objective to be an internal technical study.<br>    <br>- Added "unstructured" networks to the list of topologies to be analyzed.|NextSTEP-2 proposal submission deadline has passed.|
-
-## Problem Statement
-[[NASA]] is offering up to $800k to fund industry-led studies of, among a couple of other topics, "Constellation Topology Analysis" to inform future communication and navigation activities. The solicitation asks for a proposed approach to analyze Mesh, Star, and Hybrid network topologies.
-
-See Enclosure A, Study Area 3: [https://sam.gov/opp/afe50c193c8140a7a1a64878b3d69df4/view](https://sam.gov/opp/afe50c193c8140a7a1a64878b3d69df4/view)
-
-[MoonDAO](MoonDAO.md) has an interest in understanding network topologies for lunar operations, with special interest in decentralized paradigms.
-
-## Solution
-**Create an outline** of the effort and tools needed to complete an analysis of the impact Mesh, Star, Unstructured, and Hybrid network topologies have on decentralized and open access lunar services.
-
-The outline should include the following:
-- A description of the three network topologies (Mesh, Star, Unstructured, Hybrid) and network protocols for each 
-- A description of the decentralized and open access lunar services that will be analyzed
-- A description of the methods that will be used to analyze the impact of the network topologies on the services
-- CONOPS and operational considerations
-- Security considerations and encryption methodologies
-- Implications for existing network architectures and prime actors (LunaNet, Moonlight, Surrey Pathfinder, Crescent, US, China, …)
-- Test plan and methodology 
-- Opportunities for future research
-- Opportunities for funding (applicable grants, proposals, partnerships, etc)
-
-**Complete an internal study** of the absolute and relative performance of Mesh, Star, Unstructured, and Hybrid network topologies in the context of lunar communications, with a special focus on decentralized infrastructure. The work related to this study may include but is not limited to
-- Creating scripts, models, or simulations of communications network topologies
-- Creating data-driven metrics to evaluate each topology
-- Documenting research and development actions: actions taken, obstacles and their resolutions, missteps and mistakes, successes and surprises, and lessons learned.
-- Preparing a document that discusses analysis methods and results.
-
-## Benefits
-Understanding the benefits and drawbacks to different arrangements of connections between network nodes (ie, network topologies) is central to the ability to architect a sustainable, usable Lunar communications network.
-
-[MoonDAO](MoonDAO.md) has an interest in stewarding the lunar "commons" in order to achieve a sustainable framework for decentralized governance on the Moon. If [MoonDAO](MoonDAO.md) wishes to contribute to lunar communications architectures, we should understand the interaction between network topology, communication & navigation, and governance.
-
-Performing analysis and research strengthens [MoonDAO](MoonDAO.md)'s capacity to engage with the industry, builds a repository of knowledge, and potentially leads to the creation of engineering tools that could be used for future projects. This is especially true if the conclusions are based on open data and code, and publishing on [DeSci](DeSci%20Labs.md) to demonstrate reproducibility.
-
-The [Open Lunar Foundation](Open%20Lunar%20Foundation.md) has verbally expressed support for this analysis, but has made no commitments as of yet. The [Open Lunar Foundation](Open%20Lunar%20Foundation.md) is a non-profit organization that is dedicated to the development of the Moon. [MoonDAO](MoonDAO.md) is a community-based organization that is also dedicated to the development of the Moon. It will be valuable to establish how the [MoonDAO](MoonDAO.md) community and [Open Lunar](Open%20Lunar%20Foundation.md) could work together to receive [[NASA]] funding. This will be especially important as [MoonDAO](MoonDAO.md) continues into stage 3 of the [roadmap](Roadmap.md).
-
-If [[NASA]] awards our proposal funding, we could potentially receive funding to compensate contributors' efforts rather than spending from the DAO's treasury. Receiving an award from [[NASA]] would strengthen [MoonDAO](MoonDAO.md)'s reputation as a credible member of the space community.
-
-## Risks
-
-1. We don't submit time, or we don't receive an award. The consequence of this is that we miss out on an opportunity to bring funding to the DAO, and would not be able to compensate contributors for their engineering effort. All the materials generated from this proposal could be reused in future work.
-   > [!failure] Missed deadline
-   > This risk was realized―[MoonDAO](MoonDAO.md) did not submit a proposal.
-
-1. There are insurmountable legal roadblocks that prevent [MoonDAO](MoonDAO.md) from being awarded [[NASA]] funds. It would be helpful to understand what obstacles lie in the way for [MoonDAO](MoonDAO.md) to receive [[NASA]] funding. For example, an acceptable outcome would be to learn for certain whether [MoonDAO](MoonDAO.md) can be awarded funds directly,  and if it is necessary to use another entity (such as [Open Lunar Foundation](Open%20Lunar%20Foundation.md) or another partner) as a legal proxy. The MIDAO status is not complete, so [MoonDAO](MoonDAO.md) doesn't currently have an official entity in real life that can receive funds directly.
-## Objectives and Key Results:
-
-You can write as many OKRs as you think are needed. One OKR is fine if that captures the full extent of what you want to achieve. One focused goal is preferred instead of many. Objectives should use SMART principles (Specific, Measurable, Achievable, Relevant, and Time-Bound).
-
-~~**Objective #1:** Complete a proposal for this NextSTEP-2 solicitation (Study Area #3 only).~~ 
-
-> [!failure] Removed
-> This objective has been removed since the deadline has passed and we did not submit a proposal to [[NASA]].
-
-Key Results for Objective #1: 
-- Create an outline of the effort and tools needed to complete a network topology analysis.
-- Determine how much funding to ask from [[NASA]] as part of this project.
-- Create a proposal from the outline that meets the NextSTEP-2 submission requirements.
-- Submit the proposal before August 7, 2023.
-
-Member(s) responsible for OKR and their role:
-- [Philip Linden](@philiplinden.md) (Primary Author)
-- Pablo Moncada (Contributing Author)
-- [[@gregsearch|Greg Search]] (Contributing Author)
-- [Gonçalo Esteves](@gforce2050.md) (Advisor, Editor) 
-
-**Objective #2:** Set up an internal study based on this [[NASA]] NextSTEP-2 solicitation (Study Area #3 only).
-
-Key Results for Objective #2: 
-- Create an outline of the effort and tools needed to complete a network topology analysis.
-- Identify and define the nature of each topology under analysis.
-- Identify data-driven metrics that can be used to evaluate relative performance/utility of each topology based on these metrics.
-
-Member(s) responsible for OKR and their role:
-- [Philip Linden](@philiplinden.md) (Primary Author)
-- Pablo Moncada (Contributing Author)
-- [[@gregsearch|Greg Search]] (Contributing Author)
-
-**Objective #3:** Complete an internal study analyzing relative performance of several network topologies in the context of lunar operations.
-
-Key Results for Objective #3: 
-- Create code models or simulations of each network topology.
-- Document the results of the models and simulations with data-driven metrics from Objective #1.
-- Discuss the results in the context of other lunar communication technologies and missions.
-- Identify areas of future research.
-
-Member(s) responsible for OKR and their role:
-- [[@philiplinden|Philip Linden]] (Principal Author)
-- [[@pmoncada|Pablo Moncada]] (Contributing Author)
-- [[@gregsearch|Greg Search]] (Contributing Author)
-  
-## Team Table (Table A)
-
-Project teams may not need an initial team. It can just be an individual submitting a proposal. As a general rule of thumb, try to keep teams small and focused in the beginning, with clear deliverables and OKRs for each member. 
-
-|   |   |
-|---|---|
-|Team Rocketeer|[Philip Linden](@philiplinden.md) (@phil)|
-|Initial Team|[[Philip Linden](@philiplinden.md)](mailto:lindenphilipj@gmail.com)(@phil aka [[@philiplinden]])  <br>Pablo Moncada (@pmoncada)  <br>[[@greg|Greg Search]] ([[@gregsearch]] aka @gregsearch)<br><br>Rod Mamin (@ionrod)|
-|Delegate|[[@pmoncada]]|
-|Multi Language Representative (optional)|N/A|
-|Multisig signers|N/A|
-|Revenue Split Agreement Address|N/A|
-
-### Team Member: Philip Linden (@phil aka [[@philiplinden]])
-
-Bio: I'm a spacecraft engineer, writer, and all around space nerd. My core values are: Do Good, Be Collaborative, Dream Big, Strive for Openness, and Take Pride in Every Task. My professional experience includes R&D engineering for SpaceX (Mechanical/Reusability Engineering for Dragon Capsule), R&D engineering for Lockheed Martin Space (Electro-Optical engineer), Mission Operations for Planet Labs (Space Systems Engineer), and research for [Open Lunar Foundation](Open%20Lunar%20Foundation.md) (Fellow).
-### Team Member: Rod Mamin (@ionrod @difint)
-
-Bio: Rod Mamin is a systems engineer, with commercial experience building and sending robots for the Moon, Founder of LunCo.Space, Grantee on [DeSci](DeSci%20Labs.md) & OSS Gitcoin GR15, Alpha, Beta rounds, exSpace Engineering Guild Steward
-### Team Member: Pablo Moncada ([[@pmoncada]])
-
-Bio: Pablo is the founder of [MoonDAO](MoonDAO.md). Academic background in Computer Science, Mechanical Engineering, Business. Previously worked as a Software Engineer at YouTube (VR/TV), Waymo (ML Perception), Meta (Distributed Systems for Ads Infra), and research/startups in the biotech industry (Tissue Engineering, Bioreactors).
-
-### Team Member: Greg Search ([[@gregsearch]])
-
-Bio: Greg holds a Bachelor’s degree in Mathematics and Aeronautical Engineering, and a Master’s in Electrical Engineering. He helped early research in the Low Cost Attritable Aircraft Technology (LCAAT) program which became Skyborg. His research focuses mainly in aerospace, including: magnetic navigation, laser air data systems, and more. 
-
-## Estimated Project Timeline (Table B)
-
-|Date|Description|
-|---|---|
-|2023-08-07|Begin collecting literature and tools.|
-|2023-08-14|Share the planned objectives, methods, and hypotheses with the [MoonDAO](MoonDAO.md) community for review and feedback. Begin analysis.|
-|2023-08-31|Freeze scope of analysis. Note unexplored areas of research as potential future work.|
-|2023-09-30|Share summary of analysis so far. What has been done, what was learned, results if any.|
-|2023-10-31|Publish a manuscript, code, and data on [DeSci](DeSci%20Labs.md) discussing the analysis and results.|
-
-**Deadline for the project: End of Q3**
-  
-## Budget Justifications (Table C)
-
-Retroactive rewards only.
-
-|Description|Amount|Justification|
-|---|---|---|
-||||
-|Total|0 ETH||
-
-## In-Depth Approval Senate Signature
-
-This is only required if your project requires up-front funding from [MoonDAO](MoonDAO.md) or it is going to crowd-raise with support from [MoonDAO](MoonDAO.md).
-  
-Senate Member Signature #1:: [[@pmoncada]]
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-08-31 - LunA-10 dream team meet&greet.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-08-31 - LunA-10 dream team meet&greet.md
deleted file mode 100644
index e9fb1ac7..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-08-31 - LunA-10 dream team meet&greet.md	
+++ /dev/null
@@ -1,40 +0,0 @@
----
-tags:
-  - notes/meeting
-  - project/luna-10
----
-
-[Chris Rabotin](Chris%20Rabotin.md) -- blue ghost, capstone
-[Ramon Blanco Maceiras](Ramon%20Blanco%20Maceiras.md) -- avs. missions that are exploratory, fusion, space, lunar etc
-[Ahmad Byagowi](Ahmad%20Byagowi.md) (ah-med) -- time sync in data centers
-[Rachel Williams](Rachel%20Williams.md), [Jacob Malthouse](Jacob%20Malthouse.md) 
-[greg](@gregsearch.md), [phil](@philiplinden.md), [@pmoncada](@pmoncada.md) 
-
-need a SAM account → open lunar has one (we think!), avs does too
-if 3-pager is accepted, need to execute 10 pager within 30 days
-
-combination of providers and users -> would be useful to bring in reps for direct users to bring insights ([intuitive machines](Intuitive%20Machines.md)? capstone? firefly?)
-
-chris:
-> On Ramon's point, we should look into the payloads that are flying on the CLPS missions. I believe that almost all are scientific payloads, with the exception of the LuGRE payloads that try to do GPS at the Moon
-
-jacob:
-> fwiw my 2c are apply and if you get selected it's a good problem. :D my sense is that this is a fundamentally enabling technology that is aligned with what they're looking for and whatever OL can do to support we're behind you!
-
-
-how can we make lunar systems feel like they're in leo? how can we enable satellites to work at the moon with minimal modification
-- we have all these things in leo, can we make it a smooth transition to make those work on moon?
-- can we actually make satellites think they're in leo?
-	- like sat to phone -- phones thinking theyre talking to a tower but actually talking to a sat
-
-what do you get when yo uhave precise time
-- _reduces_ need for information to go around. reduce handshakes and get consensus 
-- consistency, availability, latency -- pick two.
-	- earth to moon, latency is ~seconds
-	- every element involved requires thesse handshakes, etc. increases quadratically
-
-we can identify the real problem -- if i have a clock, how can i do things better
-encourage people to think about assuming _have_ time end to end
-
-action: 
-- make a planning doc (copy from rachel's) as google doc → 
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-09-01 - Wi Wi for lunar timing.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-09-01 - Wi Wi for lunar timing.md
deleted file mode 100644
index 35e2c1ba..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/2023-09-01 - Wi Wi for lunar timing.md	
+++ /dev/null
@@ -1,31 +0,0 @@
----
-tags:
-  - project/lunar-comms
-  - project/luna-10
-  - notes/meeting
----
-[@ShigaEtAl2017](@ShigaEtAl2017.md)
-[@YasudaEtAl2018](@YasudaEtAl2018.md)
-[@YasudaEtAl2019](@YasudaEtAl2019.md)
-[@PantaEtAl2019](@PantaEtAl2019.md)
-[@KoyamaEtAl2021](@KoyamaEtAl2021.md)
-[@YamasakiEtAl2021](@YamasakiEtAl2021.md)
-[@TanakaEtAl2022](@TanakaEtAl2022.md)
-
-transport/dissemination -- wiwi
-timekeeping -- open time card as reference
-
-wiwi -> communication device becomes the sync+ranging device if both ends have a stable&precise clock
-
-if you can talk to someone, you can sync and find distance to them as long as both sides have a stable clock and using wiwi
-	this leads to decentralization... you don't need to have a-priori knowledge or intent to coop but you can anyway
-
-apply stratum concept here
-
-maintain a channel of communication to make pseudo entanglement
-
-stratum 0 is always UTC stratum 0 (on earth)
-stratum 1 is less precise than stratum 0
-gps is stratum 2
-
-![](MoonDAO/media-files/20221123_SpaceTimeSynchronization.pdf)
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-15.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-15.md
deleted file mode 100644
index d781aa5d..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-15.md	
+++ /dev/null
@@ -1,37 +0,0 @@
----
-tags: project/lunar-comms, notes/meeting
----
-# attendees
-- [[@philiplinden]]
-- [[@pmoncada]]
-- [[@name.get]] (lurking)
-- [[@justinpark01]] (lurking)
-# notes
-## [[Reading List]] catch up
-- [[@PasqualeEtAl2022]] 
-	- Used interesting optimization techniques to solve for optimal constellation configurations
-		- "optimal" meaning the least number of satellites
-		- tuned parameters being number of satellites, orbit (semi major axis, eccentricity, inclination, pericenter anomaly the same for all elements in the constellation)
-		- RAAN and true anomaly for every _i_ constellation elements
-		- Considered surface and orbital users, each wanting to maximize time of visibility and minimize dilution of precision
-	- The analysis found three optimal configurations, each with slightly different goals.
-		1. One serving south pole
-		2. One serving equator and north pole
-		3. One for whole-surface coverage
-	- [[@philiplinden|@phil]]: Let's focus our analysis using these orbits as our baseline constellation configurations.
-		- For each constellation (1, 2, and 3)
-			- How would network traffic actually look with a bunch of orbital and surface users?
-			- How would network traffic change if some nodes had different capabilities (range, signal integrity, etc)?
-			- How would network traffic change if every node had decentralized access, and service could not be refused?
-		- What if some nodes were "servers" and others were "consumers"? How would that affect all of these questions?
-- [[@Naseem2022]] 
-
-## objectives/interests for our special sauce
-- credible neutrality among adversarial actors
-- open and permissionless - can't refuse service. what happens?
-- how does the assumptions of decentralized actors impacts the effectiveness of different topologies
-- take inspiration from spam mitigation
-	- use fees as an inhibitor
-	- web3 gas auctions?
-	- have servers earn tokens, and use gas to send and receive (in [[MOONEY]])
-		- larger servers have more influence in [[MOONEY]] because they have more influence in the system governed by it!
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-19.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-19.md
deleted file mode 100644
index ebbf9d6f..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/meeting-notes/Meeting - 2023-08-19.md	
+++ /dev/null
@@ -1,76 +0,0 @@
----
-tags: project/lunar-comms, notes/meeting
----
-## attendees
-- [[@philiplinden]]
-- [[@pmoncada]]
-- [[@gregsearch]]
-
-# Notes
-### catch up
-[[@pmoncada]]
-- published a "master plan"
-- playing with obsidian canvases thinking through logical flows, mind maps, etc
-[[@gregsearch]]
-- read some papers, made some notes on dework
-- some ideation and notes and "musings"
--  _need to put things in obsidian!_
-[[@philiplinden]]
-- Made notes from [[Meeting - 2023-08-15]]
-- Added pdfs to [[Reading List]] items
-- "evangelizing"
-	- [[LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure]]
-	- [[../../../../philiplinden/captain's log/captain's log#2023-08-18]] 
-
-### today
-- [[NASA NextSTEP-2 BAA]] opp is gone and [[LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure|DARPA]] one is here – even if we don't _actually_ apply, these help us structure our deliverables and organize our research
-	- our research goals stay the same here
-	- note that [darpa](DARPA.md) and nasa's goals are usually not the same!
-		- [darpa](DARPA.md) seeks to fail fast, iterate, learn. if things "fail", they are usually shelved and saved later
-		- nasa seeks a durable, working system
-- [[DePrize.canvas|DePrize]] overview from [[@pmoncada]]
-	- tries to make economic incentive to work fast and productively, while still retaining decentralized ethos. also hopes to sustain moondao long term
-	- lunar comms is a great candidate for deprize, so is lunar settlement, isru etc
-	- This could also be the start of having crypto outpace govt grants, especially for historically underfunded areas.
-	- Lunar comms is poised to be a guinea pig for the first deprize while the structure is being refined
-	- Adapt existing, proven mechanisms (that have integrity and lessons baked in) to crypto
-	- Failed/losing projects – can they live on chain to support later work?
-		- with up front funding (half now, half winner) the research is still rewarded
-		- do funders still retain a stake in the submissions they voted for?
-	- The "credibly neutral judge" could (should) be a smart contract or program that determines the winner based on pass/fail criteria
-		- Whether the judge is a committee of humans or a program depends on the prize
-		- [darpa](DARPA.md)-like to catalyze capabilities — nebulous, not easily quantifiable or boiled down to pass/fail criteria
-		- nasa-like to meet mission requirements — easily converted to pass/fail criteria
-- [[@greg]] Lots of new people, new ideas, new systems, etc… how do we bridge the gap?
-	1. do the [darpa](DARPA.md) proposal
-	2. go back and pretend we submitted it to deprize first and see how things play out
-	3. use the [darpa](DARPA.md) thing as a baseline/reference to tune the deprize process
-
-What are our deliverables?
-- A report, some artifact that displays command of the subject matter
-	- submit to proposals?
-	- or pitch the ideas to people that are better positioned to execute?
-- Something compatible with [[DePrize.canvas|DePrize]]
-
-What is MoonDAO's contribution to the field?
-- Feels like the research papers are way deeper…
-- What can moondao bring to the industry, especially things that govt doesn't do well?
-- Be a hub for connecting ideas and people?
-	- DeSci overlay journals
-	- Obsidian docs for ideas
-- What can we do _uniquely_ to bring something _new_?
-	- short term we could basically be a quick startup wtih web3 flavor
-	- we'd miss out on more impactful things if we were taking our time
-
-[[How to leverage industry players]]
-
-what role do we play
-- it's a _feature_ not a _bug_ to come up with the open questions and find the problems
-- the audience for _us_ that we could help is the layperson or industry person, not the research community
-	- take the complexity and the issues and translate it to be easier to understood by the decision makers.
-	- don't invent, innovate/integrate and translate it to be understood by all
-# Actions
-- [ ] [[@philiplinden]] get interested parties (us, Ramon, Ahmad, Ramon's phd student from cornell, jacob from open lunar, [chris rabotin](Chris%20Rabotin.md)) in the same room to talk about [[LunA-10  - A Framework for Optimized, Integrated Lunar Infrastructure]] 
-	- When we connect, they don't have to "join the team" – not everyone needs to be in everything
-	- The core value is to bring these professional people into the MoonDAO orbit
-- [ ] [[@gregsearch]] boil down the main concepts/problems into an elevator pitch?
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/How to leverage industry players.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/How to leverage industry players.md
deleted file mode 100644
index a6fd8f3e..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/How to leverage industry players.md	
+++ /dev/null
@@ -1,7 +0,0 @@
----
-tags: project/lunar-comms, notes
----
-How to leverage industry players
-- Money talks. If we put up funds for deprize, the Ramons of the world will take interest
-- Build relationships with all of the most interested people in lunar space exploration
-- Be the crucible/melting pot for new ideas with the chaos of the internet
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Reading List.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Reading List.md
deleted file mode 100644
index a0ad8682..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Reading List.md	
+++ /dev/null
@@ -1,30 +0,0 @@
----
-tags: project/lunar-comms, notes
----
-
-# Architectures
- - [x] [[@PasqualeEtAl2022]] A. Pasquale, G. Zanotti, J. Prinetto, M. Ceresoli, and M. Lavagna, “Cislunar distributed architectures for communication and navigation services of lunar assets,” Acta Astronautica, vol. 199, pp. 345–354, Oct. 2022, doi: 10.1016/j.actaastro.2022.06.004.
-- [x] [[@Naseem2022]] M. Naseem, “Last-mile Analogies for a Lunar Communications Network - Open Lunar Foundation,” Open Lunar Foundation, Jan. 26, 2022. https://www.openlunar.org/library/last-mile (accessed Feb. 11, 2023).
-
-## Architecture x Policy
-- [x] [[@Schingler2020]] J. K. Schingler, “Space Tenure: The Policies of Sustained Lunar Presence - Open Lunar Foundation,” Open Lunar Foundation. https://www.openlunar.org/library/space-tenure-the-policies-of-sustained-lunar-presence (accessed Feb. 11, 2023).
-- [ ] [[@CosbyTai2022]] M. Cosby and W. Tai, “Report of the Interagency Operations Advisory Group Lunar Communications Architecture Working Group,” Lunar Communications Architecture Working Group, Jan. 2022.
-# Lunar South Pole
-- [ ] [[@DivsalarEtAl2019]] D. Divsalar, M. S. Net, and K.-M. Cheung, “Acquisition and tracking for communications between Lunar South Pole and Earth,” in 2019 IEEE Aerospace Conference, Mar. 2019, pp. 1–14. doi: 10.1109/AERO.2019.8742112.
-- [ ] [[@MalmstromEtAl2006]] R. Malmström, A. Lo, N. Brown, and G. Haney, “Continuous Communications to the Moon’s South Pole,” in Space 2006, in AIAA SPACE Forum. American Institute of Aeronautics and Astronautics, 2006. doi: 10.2514/6.2006-7453.
-# Existing Relays
-- [ ] [[@CainiFiore2012]] C. Caini and V. Fiore, “Moon to earth DTN communications through lunar relay satellites,” in 2012 6th Advanced Satellite Multimedia Systems Conference (ASMS) and 12th Signal Processing for Space Communications Workshop (SPSC), Sep. 2012, pp. 89–95. doi: 10.1109/ASMS-SPSC.2012.6333112.
-- [ ] [[@KellerEtAl2016]] J. W. Keller, N. E. Petro, and R. R. Vondrak, “The Lunar Reconnaissance Orbiter Mission – Six years of science and exploration at the Moon,” Icarus, vol. 273, pp. 2–24, Jul. 2016, doi: 10.1016/j.icarus.2015.11.024.
-
-# Future Relays
-- [ ] [[@Foust2022]] J. Foust, “Quantum Space raises $15 million for cislunar spacecraft,” SpaceNews, Dec. 13, 2022. https://spacenews.com/quantum-space-raises-15-million-for-cislunar-spacecraft/ (accessed Apr. 04, 2023).
-- [ ] [[@CrescentSpace2023]] “ParsecTM Service from Lockheed Martin,” Lockheed Martin, Mar. 28, 2023. https://www.lockheedmartin.com/en-us/news/features/2021/lunar-communication-and-navigation-network.html (accessed Apr. 04, 2023).
-# Deep Space Network
-- [ ] [[@CarruthEtAl2010]] B. Carruth, M. Johnston, A. Coffman, M. Wallace, B. Arroyo, and S. Malhotra, “A Collaborative Scheduling Environment for NASA’s Deep Space Network,” in SpaceOps 2010 Conference, Huntsville, Alabama: American Institute of Aeronautics and Astronautics, Apr. 2010. doi: 10.2514/6.2010-2284.
-- [ ] [[@ClementJohnston]] B. J. Clement and M. D. Johnston, “The Deep Space Network Scheduling Problem”.
-- [ ] [[@ShourabouraEtAl]] C. Shouraboura, M. D. Johnston, and D. Tran, “Prioritization and Oversubscribed Scheduling for NASA’s Deep Space Network”.
-# Optical Links
-- [ ] [[@CheungLee2018]] K.-M. Cheung and C. Lee, “Lunar Relay Coverage Analysis for RF and Optical Links,” in 2018 SpaceOps Conference, Marseille, France: American Institute of Aeronautics and Astronautics, May 2018. doi: 10.2514/6.2018-2612.
-- [ ] [[@Araki2021]] T. Araki, “A trade-off study of lunar-earth optical communication links,” in International Conference on Space Optics — ICSO 2020, SPIE, Jun. 2021, pp. 811–819. doi: 10.1117/12.2599331.
-- [ ] [[@RazaEtAl2022]] W. Raza et al., “Toward a Hybrid RF/Optical Lunar Communication System (LunarComm),” IEEE Network, vol. 36, no. 6, pp. 76–83, Nov. 2022, doi: 10.1109/MNET.103.2100419.
-- [ ] [[@VelazcoEtAl]] J. E. Velazco, A. C. Aguilar, A. R. Klaib, U. S. Escobar, S. E. Cornish, and J. C. Griffin, “Development of Omnidirectional Optical Terminals for Swarm Communications and Navigation”.
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Research Notes.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Research Notes.md
deleted file mode 100644
index 9ab67440..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Research Notes.md	
+++ /dev/null
@@ -1,65 +0,0 @@
----
-tags: project/lunar-comms, notes
----
-# Research Goal
-
-This study will analyze the relative benefits and drawbacks of network topologies for lunar communications: mesh networks, star networks, hybrid, and unstructured topologies.
-
-Mesh networks are decentralized and provide redundancy, which means that if one node fails, the other nodes can still communicate. This is important for lunar communications because there is a high risk of equipment failure due to the harsh environment. However, mesh networks can be complex to manage because each node needs to be able to communicate with all of the other nodes in the network.
-
-Star networks are simpler to manage than mesh networks because each node only needs to communicate with a single central node. However, star networks are more vulnerable to single point failures because if the central node fails, the entire network fails.
-
-Hybrid topologies combine the benefits of both mesh and star networks. In a hybrid topology, some nodes are connected to a central node, while other nodes are connected to each other. This provides redundancy and makes the network more resilient to failures.
-
-The study will include a discussion of the trade-offs between the different topologies and recommends that the choice of topology be based on the specific needs of the lunar mission. For example, a mission that requires a high level of redundancy would be better suited for a mesh network, while a mission that requires simplicity would be better suited for a star network.
-
-This study will include the models of each type of network. The models are examined through several performance metrics that are transferable to real-world systems, plus additional metrics that provide insight into the behavior of each agent.
-
-Here are some additional details on how different network topologies could be used by networks of agents in the cislunar ecosystem:
-
-- A star topology could be used to create a decentralized network of satellites that would provide internet access to the moon. In this topology, each satellite would be connected to a central hub. This would allow for communication between the satellites and the hub, as well as between the satellites themselves. This would be a reliable and efficient way to provide internet access to the moon.
-    
-- A mesh topology could be used to create a network of robots that would be able to work together to build infrastructure on the moon. In this topology, each robot would be connected to its neighbors. This would allow the robots to communicate with each other and coordinate their efforts. This would be a flexible and scalable way to build infrastructure on the moon.
-    
-- A ring topology could be used to create a network of sensors that would monitor the moon's environment. In this topology, each sensor would be connected to the two sensors next to it. This would allow the sensors to communicate with each other and share data. This would be a reliable and efficient way to monitor the moon's environment.
-    
-- Unstructured topologies may emerge from the chaos of lunar activities. This term is a catch-all for network topologies that may not be consistent or deliberate with respect to the arrangement of connections between nodes. Unstructured topologies will likely emerge naturally as lunar actors interact.
-    
-
-## Focus on Decentralized Network Architectures
-
-Decentralized networks are difficult to operate because there is no central authority to coordinate the activities of the network. This can lead to problems such as coordination failure, security risks, and scalability issues.
-
-Coordination failure can occur when different nodes in the network have different goals or objectives. This can make it difficult to reach consensus on how to operate the network.
-
-Security risks can arise when malicious actors are able to take control of a significant number of nodes in the network. This can allow them to disrupt the network or even take it over.
-
-Scalability issues can occur when the network becomes too large or complex to manage. This can lead to performance problems and make it difficult to add new features or functionality.
-
-The willingness of members of a decentralized network to cooperate with each other can also be a challenge. If members are not willing to share information or resources, it can be difficult to operate the network effectively.
-
-Despite these challenges, decentralized networks offer a number of advantages over centralized networks. They are more resilient to attack, they are more transparent, and they offer greater user privacy.
-
-  
-
-Objectives:
-
-  
-
-Methods:
-
-- Celestial is a tool helps lunar mission planning by providing 3d maps of lunar surfaces to high specificity and fidelity: [https://celestial.arc.nasa.gov/](https://celestial.arc.nasa.gov/) [[@Agrawal]]
-    
-- Trek is a [NASA](NASA.md) web-based portal for exploration of Moon. This portal showcases data collected by [NASA](NASA.md) at various landing sites and features an easy-to-use browsing tool that provides layering and viewing of high resolution data: [https://trek.nasa.gov/moon/#v=0.1&x=0&y=0&z=1&p=urn%3Aogc%3Adef%3Acrs%3AIAU2000%3A%3A30120&d=&locale=&b=moon&e=-834790.4296874987%2C-1434127.148437498%2C834790.4296874987%2C1434127.148437498&sfz=&w=](https://trek.nasa.gov/moon/#v=0.1&x=0&y=0&z=1&p=urn%3Aogc%3Adef%3Acrs%3AIAU2000%3A%3A30120&d=&locale=&b=moon&e=-834790.4296874987%2C-1434127.148437498%2C834790.4296874987%2C1434127.148437498&sfz=&w=) 
-    
-- LOS Analysis searches for windows of communication or a "line of sight" between any two entities: [[@LawEtAl2021]]
-    
-
-Hypotheses:
-
-  
-
-Sources::
-
-- NASA’s Lunar Communication and Navigation Structure: [[@FlaneganEtAl2008]]
-- Slime Mold Grows Network Just Like Tokyo Rail System: [[@Sanders2010]]
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Time Synchronization via LEO Satellites.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Time Synchronization via LEO Satellites.md
deleted file mode 100644
index 9765493b..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Time Synchronization via LEO Satellites.md	
+++ /dev/null
@@ -1,79 +0,0 @@
----
-tags: project/cloc, notes
----
-# Time Synchronization via LEO Satellites
-https://www.linkedin.com/events/timesynchronizationvialeosatell7099098080062423040/
-## Abstract  
-LEO satellites are being used as a resilient complement or alternative to GPS/GNSS to provide telecom, data centers, and other critical infrastructure with precise UTC time synchronization.  
-LEO PNT from Satelles (called STL), is an authenticated signal that is stronger than GPS/GNSS signals, and able to penetrate buildings to indoor antennas. This allows for more secure and lower cost installations where outdoor GPS/GNSS antennas or remote NTP or PTP time services are unavailable, not secure, not feasible, not desirable, or too expensive. The STL signal is also highly resilient to multi-path, jamming  
-and spoofing, and it’s available worldwide now.  
-Speaker  
-Charlie Meyer is a Senior Technical Director at Satelles Inc., where he develops LEO satellite timing solutions for critical infrastructure users.  
-Previously he was a Distinguished Member of the Technical Staff at Alcatel-Lucent/Nokia/Bell Labs where he worked for 25 years. He was a Principal Architect and SME for Wireless 3G/4G/5G RAN timing and synchronization systems. He has designed numerous GPS, GNSS, PTP, and OCXO solutions and has worked with multiple US government agencies regarding the dependence of telecommunications on GPS. He is a member of ATIS SYNC, IEEE-1952, [OCP-TAP](OCP-TAP.md), a senior member of the IEEE and holds four US patents.
-
-## Notes
-_Zero-trust authentication_
-
-GNSS is the most accurate method to get timing right now.
-- Needs a wide sky view. Urban canyons make it unusable!
-- Doesn't work well indoors
-- Prone to jamming/spoofing
-
-Remote NTP and PTP services
-- Time _distribution_ only
-- May not be UTC traceable, available, secure, feasible, or cost-effective
-
-Satelles STL service is a LEO PNT 
-- alternative to GPS/GNSS for network time and sync
-- Resilient to gps jamming/spoofing
-- works indoors
-
-STL == satellite time and location
-
-Uses Iridium LEO constellation, L-band
-- Higher power (closer to earth) up to 30dB stronger than MEO GNSS
-- GPS is an overlay of multiple systems transmitting on the same freq, so rx have to decorrelate them to use it. STL isn't sharing, so doesn't have this problem
-- Since LEO orbits are high velocity, multipath signal cancellations only last for minutes (not hours like MEO)
-
-![[Screenshot 2023-08-30 at 2.13.47 PM.png]]
-![[Screenshot 2023-08-30 at 2.15.37 PM.png]]
-![[Screenshot 2023-08-30 at 2.17.57 PM.png]]
-![[Screenshot 2023-08-30 at 2.20.48 PM.png]]
-![[Screenshot 2023-08-30 at 2.24.51 PM.png]]
-![[Screenshot 2023-08-30 at 2.31.18 PM.png]]
-![[Screenshot 2023-08-30 at 2.33.00 PM.png]]
-![[Screenshot 2023-08-30 at 2.35.21 PM.png]]
-
-## questions
-- Is STL using Iridium's system clock for holdover? What are the performance requirements for a clock to serve STL transmitter?
-	- Iridium have "good enough" clocks onboard, not quite as good as GPS but more available
-	- Observations show that accuracy can be maintained to nanoseconds → this depends on satellite system clock accuracy
-	- https://www.gpsworld.com/pnt-by-other-means-satelles/
-- Is the STL transmitter specific to Iridium platform or could it be adapted to other satellite busses?
-	- Exclusive use of one of the iridium channels for PNT
-	- Might be possible to put on another bus depending on SDR capabilities
-	- Requires at least an OCXO or Rubidium oscillator
-- Is STL using GPS/GNSS to sync itself to UTC?
-	- Can use GPS or NIST to correct, error is monitored by ground sys
-	- Corrections are commanded to satellite
-	- Satellite bus does not correct onboard from GPS
-- What does time transfer uplink look like?
-	- Iridium manages this, and also transfers time from ground to space, and that flows to transmitter
-	- Correct like with GPS
-- Do faster orbital speeds in LEO degrade timing accuracy?
-	- There's a lot of Doppler...
-	- Bursts have to manage doppler offsets along with ranging data
-	- Uses a specialized Kalman filter designed for this situation (proprietary)
-	- The filters are built in to the receivers
-- Proprietary receiver? What does compatibility look like compared to GPS rx?
-	- Deployed ground systems use a proprietary antenna (3x6in or so) to receive Lband signal
-	- Interface to downstream systems is the same as a GPS receiver, so compatible with existing systems that accept GPS signal
-- What's the delay spread of the signal? How many satellites can receive at once?
-	- Compensate for doppler and space-related params, but doppler is the biggest contributor
-	- More signals == better performance
-- The STL isn't a physical component, it's a software application that uses Iridium hardware
-- Could this be adapted to Starlink?
-	- didn't say it, but yes. Starlink is an SDR -- if they can accomodate the L-band freq, yeah
-	- X-band is a different discussion.... maybe?
-- Is this a subscription service?
-	- Yes. Can only get this signal if you pay
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Unanimous AI.md b/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Unanimous AI.md
deleted file mode 100644
index d91c7622..00000000
--- a/MoonDAO/docs/Projects/Active Projects/lunar-comms-pnt/research-notes/Unanimous AI.md	
+++ /dev/null
@@ -1,6 +0,0 @@
----
-tags:
-  - ai
-  - project/lunar-comms
----
-[Unanimous AI](https://youtu.be/xODlyNdxuEY?t=105)
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/midao/MoonDAO Legal Entity as a Marshall Island DAO LLC.md b/MoonDAO/docs/Projects/Active Projects/midao/MoonDAO Legal Entity as a Marshall Island DAO LLC.md
deleted file mode 100644
index f3f01987..00000000
--- a/MoonDAO/docs/Projects/Active Projects/midao/MoonDAO Legal Entity as a Marshall Island DAO LLC.md	
+++ /dev/null
@@ -1,89 +0,0 @@
----
-tags:
-  - project/midao
-  - proposal
----
-**Abstract**: *MoonDAO as an entity has rights and can take actions as an entity. It can own land, hire contractors and own IP. However, to exercise most of these rights, it needs to be legally recognized as a legal entity and have a bank account. This proposal would formally establish MoonDAO as a legal entity based in the Republic of Marshall Islands (RMI) as a Nonprofit DAO LLC. The RMI entity would also simplify MoonDAO’s tax obligations as outlined below.* 
-
-For context on what a nonprofit is, the IRS defines nonprofits as “organized and operated exclusively for religious, charitable, scientific, testing for public safety, literary, educational or other specified purposes.” The IRS also provides favorable tax treatment for “social welfare organizations, civic leagues, social clubs, labor organizations and business leagues.” 
-
-Motivation: The reason why RMI is the best option for MoonDAO is because this legal entity is compatible with tracking our members and our votes on the blockchain. Considering that our token is a [governance token](Governance%20Tokens.md) and we do not issue any returns or dividends to members, the nonprofit entity is the most ideal structure (See this article for more in depth analysis of the benefits of RMI legal entity). MoonDAO needs to have a proper legal entity if we plan on taking on bigger projects that may require us to make big purchases, enter into formal contracts and acquire a physical headquarters/working space. 
-
-Specification: The main goal is to go through [MIDAO](MIDAO.md) to establish this entity. It will require [@pmoncada](@pmoncada.md) to do KYC. The legal documents that establish us as a RMI Nonprofit DAO Llc will be similar to these and we will be able to adjust it as necessary: 
-
-https://docsend.com/view/caik9475xu5g9zqp 
-
-Once the final governing documents are finalized, MoonDAO will vote once more for final approval. 
-
-Benefits: Legal recognition for our community among the international community. This legal entity will further establish us as a professional organization that is here to stay. It will also provide legal protection to our members from legal liability issues. This will also allow our community to legally own assets as decided by the community. 
-
-Risks: There are minimal risks. The application could be denied (albeit unlikely), in which case we’d receive a full refund from [MIDAO](MIDAO.md).
-
-Objectives and Key Results: 
-
-Objective #1: Have our application to become a legal entity be approved. Key Results for Objective #1: 
-
-- Submit the application through [MIDAO](MIDAO.md).org and provide the requisite paperwork - Have three members submit the requisite applications to go through KYC process. - Follow up with [MIDAO](MIDAO.md) on finalizing application. 
-
-# Team
-
-|   |   |
-|---|---|
-|Team Leads|Favian|
-|Initial Team|Favian, Pablo|
-|Sponsors|Pablo|
-|Multi-sig Signers (if Budget is needed)|Favian|
-|Foreign Language Representatives (optional)|Spanish - Favian, Pablo|
-
-Team Leader(s) Bio: Favian#8760 is an attorney and key contributor for MoonDAO. He is focused on our long-term vision for MoonDAO. His legal background provides him a solid foundation in public speaking and networking in person and in writing, which will come in handy to establish a good reputation for MoonDAO amongst the space travel community. Favian has already established his own DAO (VanlifeDAO as a RMI LLC), so he is familiar with the process. He can also get a 5% discount from MIDAO.org (full disclosure: Favian has professional relationship with MIDAO.org and gets a 10% referral fee for recommending DAOs to MIDAO.org). 
-
-Role: Project leader 
-
-OKR within the project: 
-
-Objective #1: Oversee the application process and submit necessary information. Key Results for Objective #1: 
-
-- Review, edit and submit the application for MoonDAO 
-
-- Coordinate with MIDAO to process the application. 
-
-- Oversee the process of having members go through KYC process
-
-Team Steward Minimum Viable Payment: $2,000 
-
-Assuming that we do not have any members that own more than 10% of our token, we would just need one of ou[^2]r leaders to KYC, and Pablo has agreed to go through this process. 
-
-pmoncada#0261 Cofounder and fearless leader of MoonDAO. 
-
-Role: Application KYC process applicant 
-
-OKR within the project: 
-
-Objective #1: submit to KYC and background check. 
-
-Key Results for Objective #1: 
-
-- submit KYC and sign the required paperwork. 
-
-Team Stewards Minimum Viable Payment: $250 
-
-# Budget Justifications 
-
-|Description|Amount|
-|---|---|
-|Registration fee paid up-front|$9,025|
-|Annual fees each January|$5,000|
-
-Total Budget (including guaranteed payments to team members): $11,275 worth of Dai 
-
-0 $MOONEY 
-
-# Estimated Project Timeline (Table C)
-
-|Date|Description|
-|---|---|
-|October 15, 2022|Submit application|
-|October 15, 2022|Pablo submit KYC process through MIDAO.org|
-|November 15, 2022|Receive charter (obtain entity status)|
-
-# Deadline for the project: November 15, 2022
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/moondao-app/App Expansion.canvas b/MoonDAO/docs/Projects/Active Projects/moondao-app/App Expansion.canvas
deleted file mode 100644
index cbaac2c5..00000000
--- a/MoonDAO/docs/Projects/Active Projects/moondao-app/App Expansion.canvas	
+++ /dev/null
@@ -1,81 +0,0 @@
-{
-	"nodes":[
-		{"type":"text","text":"News","id":"f312c9c8f4964256","x":-760,"y":-66,"width":250,"height":60},
-		{"type":"text","text":"Discord Announcements","id":"6424806373e573df","x":-400,"y":-155,"width":250,"height":60},
-		{"type":"text","text":"Recent Blog Posts","id":"fccc1d1c1cc5afce","x":-400,"y":20,"width":250,"height":60},
-		{"type":"text","text":"Newsletter Link","id":"4307248d8196d05e","x":-400,"y":-66,"width":250,"height":60},
-		{"type":"text","text":"Connect","id":"199b5955e3107042","x":-400,"y":-390,"width":250,"height":60},
-		{"type":"text","text":"Join MoonDAO","id":"67ed8e510e903ceb","x":-760,"y":-450,"width":250,"height":60},
-		{"type":"text","text":"Landing Page","id":"f54b2997587c7b4c","x":-760,"y":-700,"width":250,"height":60},
-		{"type":"text","text":"Launch App","id":"7b20f7c4eca59c9c","x":-400,"y":-700,"width":250,"height":60},
-		{"type":"text","text":"View Current Projects","id":"5dcc1d621e70be31","x":-402,"y":600,"width":250,"height":60},
-		{"type":"text","text":"Apply to a current Project","id":"a6adca2b94401b3b","x":-400,"y":690,"width":250,"height":60},
-		{"type":"text","text":"Create a Project (no MVP)","id":"90164b07903e834c","x":-400,"y":780,"width":250,"height":60},
-		{"type":"text","text":"Contribute","id":"3d03a7d59501de95","x":-760,"y":690,"width":250,"height":60},
-		{"type":"text","text":"Treasury Statistics","id":"e61c476e24380ae8","x":-410,"y":914,"width":250,"height":60},
-		{"type":"text","text":"Voter Distribution","id":"511b7e6cb0641363","x":-408,"y":985,"width":250,"height":60},
-		{"type":"text","text":"Contributor Payouts","id":"f412e112a5717e4c","x":-408,"y":1060,"width":250,"height":60},
-		{"type":"text","text":"Govern","id":"33789da3282aba5a","x":-758,"y":180,"width":250,"height":60},
-		{"type":"text","text":"Project Page","id":"2dee87eb29ac21be","x":-40,"y":600,"width":250,"height":60},
-		{"type":"text","text":"Send to ideation to start a proposal","id":"bde7e09cf1a3b169","x":300,"y":150,"width":250,"height":60},
-		{"type":"text","text":"Select Template for voting","id":"0f5e482757550c3f","x":300,"y":228,"width":250,"height":60},
-		{"type":"text","text":"Obsidian Docs","id":"67844c1bf85122ed","x":-408,"y":1120,"width":250,"height":60},
-		{"type":"text","text":"Documentation and Analytics","id":"06084b7103481d08","x":-758,"y":1015,"width":250,"height":60},
-		{"id":"b2f5dce4b699dc2d","type":"text","text":"Marketplace","x":-758,"y":1280,"width":250,"height":60},
-		{"type":"text","text":"Explain voting @ MoonDAO","id":"125a171623c8a191","x":25,"y":-450,"width":250,"height":60},
-		{"type":"text","text":"Buy MOONEY interface","id":"67b577a933ae3026","x":25,"y":-390,"width":250,"height":60},
-		{"type":"text","text":"No Wallet Video / We create a wallet for them?","id":"bba75dbe5249e1c5","x":25,"y":-330,"width":250,"height":60},
-		{"type":"text","text":"Stake for vMOONEY","id":"5651ff75c791d812","x":425,"y":-360,"width":250,"height":60},
-		{"id":"3881c022f6dd61be","type":"text","text":"Explain Pledging / Stakeholder / Soul-bound","x":425,"y":-450,"width":250,"height":90},
-		{"type":"text","text":"Gitcoin Stamps","id":"cbbc9eb3e59df954","x":800,"y":-323,"width":250,"height":60},
-		{"type":"text","text":"Pitch on \"Why MoonDAO\"","id":"375242bedf9f12b1","x":-400,"y":-480,"width":250,"height":60},
-		{"id":"e969acfa8eb6b758","type":"text","text":"Onboarding Meeting / POAPs","x":1154,"y":-322,"width":250,"height":60},
-		{"id":"89b61fde89b97b71","type":"text","text":"Default / Quick Start","x":25,"y":-510,"width":250,"height":60},
-		{"id":"514228d6fa86e239","type":"text","text":"Super Supporter 250k vMOONEY","x":425,"y":-670,"width":250,"height":60},
-		{"id":"22480ceb83db31bf","type":"text","text":"Whale","x":425,"y":-610,"width":250,"height":60},
-		{"id":"89d1789efa5699d6","type":"text","text":"Sweepstakes - 50k MOONEY, stake half","x":425,"y":-730,"width":250,"height":60},
-		{"type":"text","text":"Review Proposals","id":"cfb53b6551e4d48d","x":-400,"y":228,"width":250,"height":60},
-		{"type":"text","text":"Submit a Proposal","id":"4f659c1bc0d8a1ea","x":-398,"y":150,"width":250,"height":60},
-		{"type":"text","text":"Vote on Proposals","id":"34fcef963ab5786e","x":-398,"y":310,"width":250,"height":60},
-		{"type":"text","text":"Increase Voting Power","id":"0a03735cc12d755c","x":-398,"y":390,"width":250,"height":60},
-		{"id":"7f89a363f1c70950","x":-398,"y":450,"width":250,"height":60,"type":"text","text":"Delegate Voting Power"},
-		{"id":"01fd763a3fb1dcb3","type":"text","text":"Explain Gitcoin Stamps","x":800,"y":-390,"width":250,"height":60}
-	],
-	"edges":[
-		{"id":"bcc1a7d5a3d05f36","fromNode":"f312c9c8f4964256","fromSide":"right","toNode":"6424806373e573df","toSide":"left"},
-		{"id":"8eea590d750b9b20","fromNode":"f312c9c8f4964256","fromSide":"right","toNode":"4307248d8196d05e","toSide":"left"},
-		{"id":"47b31a68b5355b17","fromNode":"f312c9c8f4964256","fromSide":"right","toNode":"fccc1d1c1cc5afce","toSide":"left"},
-		{"id":"795f53480e8d217f","fromNode":"67ed8e510e903ceb","fromSide":"right","toNode":"375242bedf9f12b1","toSide":"left"},
-		{"id":"1ccfc9a420f51c34","fromNode":"67ed8e510e903ceb","fromSide":"right","toNode":"199b5955e3107042","toSide":"left"},
-		{"id":"31d123729451b6ce","fromNode":"199b5955e3107042","fromSide":"right","toNode":"bba75dbe5249e1c5","toSide":"left"},
-		{"id":"4168d4e019da6ffe","fromNode":"199b5955e3107042","fromSide":"right","toNode":"67b577a933ae3026","toSide":"left"},
-		{"id":"dc53a1846b4a4489","fromNode":"f54b2997587c7b4c","fromSide":"right","toNode":"7b20f7c4eca59c9c","toSide":"left"},
-		{"id":"0d0c2f9f57cac846","fromNode":"33789da3282aba5a","fromSide":"right","toNode":"4f659c1bc0d8a1ea","toSide":"left"},
-		{"id":"d98c07c1d9274dc0","fromNode":"33789da3282aba5a","fromSide":"right","toNode":"cfb53b6551e4d48d","toSide":"left"},
-		{"id":"be2bcb580c3c04e2","fromNode":"33789da3282aba5a","fromSide":"right","toNode":"34fcef963ab5786e","toSide":"left"},
-		{"id":"33a71bdf498aab82","fromNode":"33789da3282aba5a","fromSide":"right","toNode":"0a03735cc12d755c","toSide":"left"},
-		{"id":"fd7871abad15cf51","fromNode":"199b5955e3107042","fromSide":"right","toNode":"125a171623c8a191","toSide":"left"},
-		{"id":"2f248c4fa3be69fe","fromNode":"67b577a933ae3026","fromSide":"right","toNode":"5651ff75c791d812","toSide":"left"},
-		{"id":"cbd047f8587c6ed7","fromNode":"5651ff75c791d812","fromSide":"right","toNode":"cbbc9eb3e59df954","toSide":"left"},
-		{"id":"c6864dc1c25158d7","fromNode":"3d03a7d59501de95","fromSide":"right","toNode":"5dcc1d621e70be31","toSide":"left"},
-		{"id":"f51c12ed8087e0a4","fromNode":"3d03a7d59501de95","fromSide":"right","toNode":"a6adca2b94401b3b","toSide":"left"},
-		{"id":"3245e719cd7a5c9a","fromNode":"3d03a7d59501de95","fromSide":"right","toNode":"90164b07903e834c","toSide":"left"},
-		{"id":"f8514c0b55e04b4e","fromNode":"06084b7103481d08","fromSide":"right","toNode":"e61c476e24380ae8","toSide":"left"},
-		{"id":"6c920508a59499fa","fromNode":"06084b7103481d08","fromSide":"right","toNode":"511b7e6cb0641363","toSide":"left"},
-		{"id":"3125191ce3597012","fromNode":"06084b7103481d08","fromSide":"right","toNode":"f412e112a5717e4c","toSide":"left"},
-		{"id":"a261945e2f7b731c","fromNode":"06084b7103481d08","fromSide":"right","toNode":"67844c1bf85122ed","toSide":"left"},
-		{"id":"06dcebf866d9fccf","fromNode":"0a03735cc12d755c","fromSide":"right","toNode":"67b577a933ae3026","toSide":"left"},
-		{"id":"ee66e5c45ae07e55","fromNode":"4f659c1bc0d8a1ea","fromSide":"right","toNode":"bde7e09cf1a3b169","toSide":"left"},
-		{"id":"94eb8893a0505dcb","fromNode":"4f659c1bc0d8a1ea","fromSide":"right","toNode":"0f5e482757550c3f","toSide":"left"},
-		{"id":"6060dfab84005127","fromNode":"5dcc1d621e70be31","fromSide":"right","toNode":"2dee87eb29ac21be","toSide":"left"},
-		{"id":"0df019596cb44c4f","fromNode":"90164b07903e834c","fromSide":"right","toNode":"0f5e482757550c3f","toSide":"left"},
-		{"id":"f330815dab1be2a0","fromNode":"67b577a933ae3026","fromSide":"right","toNode":"3881c022f6dd61be","toSide":"left"},
-		{"id":"91e3d70016f5c6e3","fromNode":"5651ff75c791d812","fromSide":"right","toNode":"01fd763a3fb1dcb3","toSide":"left"},
-		{"id":"9b7ae63dd91039fe","fromNode":"cbbc9eb3e59df954","fromSide":"right","toNode":"e969acfa8eb6b758","toSide":"left"},
-		{"id":"10f7c8ade945210d","fromNode":"199b5955e3107042","fromSide":"right","toNode":"89b61fde89b97b71","toSide":"left"},
-		{"id":"dfaef97143f4b018","fromNode":"89b61fde89b97b71","fromSide":"right","toNode":"89d1789efa5699d6","toSide":"left"},
-		{"id":"a761375387b192e9","fromNode":"89b61fde89b97b71","fromSide":"right","toNode":"514228d6fa86e239","toSide":"left"},
-		{"id":"17a83e13e6249e17","fromNode":"89b61fde89b97b71","fromSide":"right","toNode":"22480ceb83db31bf","toSide":"left"},
-		{"id":"d540c5993df2c0ec","fromNode":"33789da3282aba5a","fromSide":"right","toNode":"7f89a363f1c70950","toSide":"left"}
-	]
-}
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/moondao-entities/MoonDAO Entities.md b/MoonDAO/docs/Projects/Active Projects/moondao-entities/MoonDAO Entities.md
deleted file mode 100644
index 47d89c30..00000000
--- a/MoonDAO/docs/Projects/Active Projects/moondao-entities/MoonDAO Entities.md	
+++ /dev/null
@@ -1,50 +0,0 @@
-MoonDAO Entities are the easiest way for you to create an onchain organization and start contributing towards a lunar settlement.
-
-Are you...  
-*A new startup that wants to receive funding from MoonDAO?*
-*Or an existing company that wants to hire from MoonDAO?*
-*Or a nonprofit that is seeking support from MoonDAO?*
-*Or a small project you want to start for fun with other people with support from MoonDAO?*
-*Or a group of existing MoonDAO members that want to organize onchain?*
-
-Do you want to...
-*Receive discounts for the most used DAO tools?*
-*Operate with the most sophisticated and secure DAO tools?*
-*Manage your treasury and funds in a decentralized and secure way?*
-*Manage your organization onchain?*
-*Easily receive funding from MoonDAO and participate in its construction?*
-
-Then look no further! MoonDAO Entities can help you today!
-
-# What is a MoonDAO Entity?
-
-MoonDAO Entities are a yearly subscription service that gives you:
-
-- Control over a self-custodied Treasury that you can add other people onto.
-- Administration of permissions within your organization:
-- Create roles for your members. You can get creative and make your organization however you’d like.
-- Discounts on onchain legal incorporation within the Marshall Islands. If you don't have an existing legal incorporation, this allows you to know you are running your organization within the laws of a sovereign nation.
-
-# How do I create an Entity?
-
-Creating a MoonDAO Entity is simple. Simply go [here](https://www.moondao.com/join) and click “Register an Entity” to get started.
-
-All you need to do is fill out your Entity’s information in a quick questionnaire, and then design your registration image using our image generator.
-
-The image generator creates an imprint of the night sky at the moment you create your Entity and gives you a deed to your onchain organization within MoonDAO.
-
-# How does it work?
-
-MoonDAO has created a smart contract that helps you organize with others using Ethereum. It can store and send funds easily, it can have custom organization trees, and it plugs in simply with the rest of MoonDAO’s smart contracts so you can get the most out of MoonDAO by getting funding for your work, participating in governance, or competing in prizes.
-
-# How are funds handled onchain?
-
-Each Entity has an onchain multisig using a [Gnosis Safe](https://safe.global/), the onchain gold standard for self-custodied multisigs. A multisig is simply a treasury that has a minimum number of signers to execute a transaction. You can have as many signers on the multisig as you’d like, and you can set a signing threshold to execute a transaction. To start, the Entity creator’s wallet is the only signer on the multisig, and they can add more signers and change the threshold to manage funds using their Entity management page.
-
-# How are permissions handled?
-
-MoonDAO Entities uses [Hats Protocol](https://www.hatsprotocol.xyz/) to handle onchain permissions. Hats creates an organization tree that is customizable. To begin the Entity’s “root” hat will be stored in the multisig, and the administrator hat will be in the Entity creator’s wallet. These permissions can be changed using the Entity management page. Administrators can change the Entity’s onchain data (like the name of the organization, bio, or adding and removing members within the org.
-
-# How long is the membership?
-
-Membership lasts one year and can be renewed or extended on your Entity Management page by clicking Extend.
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Clock Drift.md b/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Clock Drift.md
deleted file mode 100644
index cd2c3277..00000000
--- a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Clock Drift.md	
+++ /dev/null
@@ -1,3 +0,0 @@
-# Introduction to Clocks
-![clock drift video](https://www.youtube.com/watch?v=4IzQe5PS8NM)
-A **clock** at a process $p_i$ is a monotonically increasing function $C_i$ from a *real time* to some real value. Real time is the clock's **Proper Time**.
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Entity-Component-System (ECS) Architecture.md b/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Entity-Component-System (ECS) Architecture.md
deleted file mode 100644
index 33b8b38f..00000000
--- a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Entity-Component-System (ECS) Architecture.md	
+++ /dev/null
@@ -1,55 +0,0 @@
----
-tags:
-  - project/lunar-comms
-  - notes
----
-This page describes a potential model for networked clocks in space.
-
-The model is built around an Entity-Component-System (ECS) architecture to make the most of the tools and ethos behind Rust and core crates like Bevy. This approach also aligns well with the intent of the model.
-
-An ECS architecture allows for a modular and scalable design, making it easier to manage the simulation's complexity. Components store data, and systems operate on that data, while resources hold shared data needed across systems. This separation of concerns and data-driven approach is a key characteristic of ECS.
-
-1. **Components:**
-    - **Clock Component (`Clock`):**
-        - Represents individual clocks in the simulation.
-        - Contains parameters such as speed, local gravity, clock time, and PTP clock information.
-        - Includes a `Radio` component for radio communication parameters.
-    - **Quartz Oscillator Component (`QuartzOscillator`):**
-        - Represents properties of a quartz oscillator associated with a clock.
-        - Includes parameters like frequency offset, aging rate, and temperature sensitivity.
-    - **Time Resource (`TimeResource`):**
-        - A resource to keep track of the time elapsed between frames.
-    - **TUI Stats Component (`TuiStats`):**
-        - Holds information related to TUI (Text-based User Interface) stats for display.
-    - **PtpClock Component (`PtpClock`):**
-        - Represents PTP-related information, including offset and delay.
-    - **PtpMessage Component (`PtpMessage`):**
-        - Placeholder component for PTP message.
-    - **Radio Component (`Radio`):**
-        - Represents radio communication parameters such as transmitter power, receiver sensitivity, and field of view.
-2. **Systems:**
-    - **Time Dilation System (`TimeDilationSystem`):**
-        - Calculates the time dilation factor for each clock based on speed, local gravity, and oscillator parameters.
-        - Updates the clock time accordingly.
-    - **Simulate Clock System (`SimulateClockSystem`):**
-        - Simulates the behavior of each clock, updating parameters like speed, local gravity, and aging.
-        - Handles the aging of quartz oscillators.
-    - **PtpSyncSystem (`PtpSyncSystem`):**
-        - Handles PTP synchronization logic, updating clock offset and delay based on PTP messages.
-    - **Radio Communication System (`RadioCommunicationSystem`):**
-        - Simulates radio communication logic, determining entities within the field of view and sending messages.
-    - **Update TUI System (`UpdateTuiSystem`):**
-        - Updates TUI stats based on simulation data.
-        - Prints the stats to the terminal for visualization.
-    - **PtpSyncSenderSystem (`PtpSyncSenderSystem`):**
-        - Sends PTP messages to synchronize clocks.
-    - **Radio Communication Sender System (`RadioCommunicationSenderSystem`):**
-        - Simulates sending radio messages to entities within the field of view.
-3. **Initialization:**
-    - In the Bevy app, entities are created with the relevant components, such as `Clock`, `QuartzOscillator`, `PtpClock`, and `Radio`.
-    - The ECS systems are added to the app to process and update entities during each frame.
-4. **Interaction:**
-    - Components hold the state of entities (e.g., clock parameters, oscillator properties, PTP information, radio communication parameters).
-    - Systems process and update entities based on their components and the logic defined in each system.
-
-This ECS architecture allows for a modular and scalable design, making it easier to manage the simulation's complexity, including PTP synchronization and radio communication. Components store data, and systems operate on that data, while resources hold shared data needed across systems.
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Simulating network load and watching it evolve.md b/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Simulating network load and watching it evolve.md
deleted file mode 100644
index 2aba2c69..00000000
--- a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Simulating network load and watching it evolve.md	
+++ /dev/null
@@ -1,163 +0,0 @@
----
-tags: project/lunar-comms
----
-# clocss-abm: an Agent-Based Model of Heterogeneous Lunar Networks for the Cislunar Open Clock Synchronization System (CLOCSS)
-https://github.com/philiplinden/clocss-abm
-
-## Abstract
-This project aims to use agent-based modeling and simulations to explore how
-network topology and time synchronization evolve in a growing lunar ecosystem.
-Modeling how the approach may be used in practice and at scale informs decisions
-about how to architect a robust cislunar PNT system that scales with the
-population.
-
-## Approach
-This project aims to use agent-based modeling and simulations to explore how
-centralized and decentralized PNT service network topologies evolve in a growing
-lunar ecosystem. Modeling network topologies representative of near-term lunar
-missions and large future populations of cislunar actors will predict the
-relative performance, “critical mass” of assets required for service, and
-coverage of decentralized PNT services and/or GNSS-like beacons providing PNT to
-lunar missions. There is an abundance of prior art describing optimal orbit
-configurations for such systems that can also be evaluated in this way.
-
-The model will feature a population of agents, where each agent has a Stratum, a
-location and velocity, a clock with drift, and a communications system with a
-spectral band and radiation power. Agents belong to one of three groups based on
-their behavior: Transmitters, Receivers, and Peers. Transmitter agents radiate
-signals but do not listen for incoming signals. Receivers listen for incoming
-signals but do not radiate. Peers are capable of listening for and radiating
-signals. Agents move in space independently along orbits or surface routes
-around a sphere in the simulation space representing the Moon. Terrestrial
-communications systems are modeled as a Stratum 0 Transmitter. Every node
-reports measurements of each metric described in the subsequent Metrics section
-at every step of the simulation period.
-
-Over the simulation period, each agent’s clock encounters simulated drift that
-accumulates over time. The agents record their perceived position by integrating
-instantaneous velocity observations over time, where the observed time is based
-on the local clock’s epoch. At the end of the simulation period, the observed
-position is compared to the true position. Agents may interact with one another
-over the simulation period using modeled communications links for PNT
-measurements and time synchronization. Links are only established between two
-agents if both 1) share a common spectral band; 2) have line-of-sight to each
-other; 3) have sufficient radiation power to transmit across the distance
-between them; and 4) at least one agent is a Transmitter. When a link is
-established, the Receiver agent’s clock is synchronized to the Transmitter’s
-epoch. If both agents are Peers, the agents synchronize to the epoch of the
-agent with a lower Stratum, or the mean epoch between them. Each time an agent
-synchronizes to another agent, it becomes Stratum n+1 where Stratum n belongs to
-the agent with the lower number. Agent A syncs to UTC and becomes Stratum 1,
-then Agent B syncs to A and so Agent B becomes Stratum 2, and so on.
-
-This model framework permits rapid simulation of heterogeneous nodes acting as
-PNT servers, clients, or both. The proposed study seeks to evaluate Wi-Wi based
-decentralized networks as alternatives to GNSS-like services for cislunar PNT.
-The described model allows each network topology to be tested and instrumented
-while subject to realistic client population densities in near-term (tens of
-agents) and future scenarios (hundreds, thousands of agents). The described
-model also permits the simulation of multiple PNT services coexisting,  such as
-Parsec, weak-GPS, and the proposed decentralized network. The model also
-accounts for the evolution of competing providers as the populations of servers
-and clients grow. 
-
-Insights obtained from models will then be applied to create an optimal mission
-profile for a constellation of cislunar spacecraft equipped with space-rated
-Time Cards that enable the proposed capability of a publicly available minimum
-viable PNT service. With relevant prediction of cislunar PNT users for each PNT
-service configuration over the next 5 to 15 years, and also computing the
-equivalent cost per user for terrestrial GNSS, data-driven investment decisions
-related to deploying new PNT fleets in cislunar space are possible.
-
-### Metrics
-The following metrics and quantitative evaluation criteria will be used to
-evaluate PNT service characteristics.
-
-**Accuracy**
-- *Sync precision* - Standard deviation absolute time across the node population
-- *Holdover* - Average clock drift from true time before syncing
-- *Latency (jitter)* - Round trip time, packet delay variation
-
-**Availability**
-- *Capacity* - % bandwidth used, peak bandwidth used, sqkm of coverage
-- *Throughput* - Total available bandwidth, # concurrent links
-
-**Continuity**
-- *Roaming ability* - # available links, time between links
-- *Failure & recovery rate* - Mean time between failures, mean time to restore
-
-**Interoperability**
-- *Standards compatibility* - Meets LunaNet and Moonlight requirements
-- *Technology compatibility* - # comms spectral bands, clients served per band
-
-**Cost**
-- *Nodes required for service* - # service nodes, # clients per provider node
-- *Hardware required* - $ per clock, # clocks, $ invested per client served
-
-**Signal Integrity**
-- *Packet integrity* - packet loss rate, packet delivery ratio, % duplicate
-  packets
-- *Channel dominance* - signal-to-noise ratio, jam-to-signal ratio
-
-## Motivation
-Recent advancements in space technologies have prompted a surge in lunar
-missions, both crewed and uncrewed. Such an influx demands scalable,
-commercially-accessible Positioning, Navigation, and Timing (PNT) frameworks for
-the development of a cislunar economy. In order to bring PNT infrastructure to
-the lunar ecosystem and have it be as ubiquitous and as useful as Global
-Navigation Satellite Systems (GNSS) are in the interoperable Space Service
-Volume (SSV), there needs to be accurate, traceable and accessible timing and
-ranging infrastructure that is also resilient, reliable and flexible. NASA’s
-LunaNet and ESA’s Moonlight are two major initiatives to promote
-interoperability and connectivity in cislunar space by providing a common
-communications framework and standards. Lunar constellations equivalent to
-terrestrial GNSS are one approach to delivering a cislunar PNT but it is not the
-only solution. Peer-to-peer networks of satellites with precision timekeeping
-may serve as an alternative method of implementing a PNT service to traditional
-GNSS constellations.
-
-This project will use agent-based modeling to compare satellite network
-topologies using metrics known from the current PNT solution such as accuracy,
-availability, continuity and integrity, in addition to costs, timeline and
-technology development requirements of implementing each system in a cislunar
-context. The goal is to develop the proposed solution to a level mature enough
-to predict the system’s performance relative to the number and distribution of
-interconnected assets, and quantitatively demonstrate that our approach becomes
-more robust and performant as it scales to service the anticipated demands of a
-thriving lunar ecosystem. The study will also consider specific lunar PNT user
-needs and infrastructure combination opportunities, as well as requirements for
-Earth / Earth Orbit systems to be usable with minimum changes for lunar
-applications.
-
-### Diverse Cislunar Ecosystems of PNT and Communications Infrastructures are Inevitable
-
-A fundamental characteristic of the this proposed design is its peer-to-peer
-topology, ensuring resilience against centralized points of failure. The
-structure stands robust against interference, adversarial or accidental. The
-decentralized nature of the design further augments its flexibility, permitting
-in-flight mission adaptations and potential as a backup for lunar missions,
-reducing their dependence on individualized PNT structures. Since Wi-Wi is a
-protocol that works with any radio band, it is likely that several independent
-PNT services could emerge on different parts of the spectrum. This allows actors
-to maintain closed PNT utilities or to offer services for a self-sustaining,
-monetizable, commercially owned-and-operated lunar infrastructure. Critically,
-public and private PNT utilities may coexist under this paradigm, like how a
-single transponder can access both terrestrial open-air radio and encrypted
-radio channels. In essence, this philosophy aims to nurture a resilient PNT
-ecosystem that accommodates both public and private ventures. Through a credibly
-neutral protocol for timekeeping, bad actors would not only have difficulty
-manipulating the service, but they may use this infrastructure themselves and
-even work to support its canonization.
-
-### Interoperability with Other Missions
-
-In the design of a lunar PNT system one important consideration is the
-definition of a reference frame to allow for absolute position. This time
-transfer and relative position concept could be used to define a network of
-realization points (fixed points for the reference frame) to assist in the
-realization of a Lunar Reference Frame. These lunar realization points would be
-located on the near side of the Moon and equipped with e.g., laser
-retroreflectors for accurate ranging from Earth by the existing Lunar Laser
-Ranging (LLR) stations. Like GNSS, passive receivers can obtain the time and
-position in reference to the PNT node’s position by observing the transmitted
-signal so long as the receiver’s clock is synchronized to the node.
\ No newline at end of file
diff --git a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Time and Relativity.md b/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Time and Relativity.md
deleted file mode 100644
index 8cc1d3a7..00000000
--- a/MoonDAO/docs/Projects/Active Projects/spacetime-protocol/Time and Relativity.md	
+++ /dev/null
@@ -1,96 +0,0 @@
----
-tags:
-  - project/lunar-comms
-  - notes
----
-I've been learning a lot about timekeeping lately. The most confusing thing for me has been [Allan Variance](https://en.wikipedia.org/wiki/Allan_variance). The second most confusing aspects of timekeeping for me is how to measure time if it is relative. The following video inspired me to dive a bit deeper.
-![time and relativity](https://www.youtube.com/watch?v=ZdrZf4lQTSg)
-# Frames of Reference
-## Coordinate Time
-The time as observed by the coordinate frame itself. This is a "god's-eye view" of the time in the system we are analyzing. Basically, it represents a perfect clock held by the world/universe/simulation coordinate frame's observer. Usually Earth-centric systems use UTC or TAI as the Coordinate Time.
-
-Formally, the coordinate time is the time that would be read on a hypothetical "coordinate clock" situated infinitely far from all gravitational masses, and stationary in the system of coordinates.
-## Proper Time
-The time as observed by a perfect clock attached to an object's local body frame. The body frame is a coordinate frame rigidly attached to the object. Whenever the object observes the time, it observes the local Proper Time.
-
-In most situations, Proper Time and Coordinate Time are the same. The distinction between Proper Time and Coordinate Time is only relevant when objects are subjected to large accelerations or move across lumpy spacetime (like going from sea-level on Earth to standing on the Moon), and the effects of General Relativity become significant.
-
-## System Time
-So far we've only talked about the hypothetical, perfect clocks that describe the physics. But we actually want to observe these times ourselves with real clocks. Unfortunately, no clock is perfect or ideal. The _System Time_ is the real clock's observation of the local Proper Time. We'll explore System Time later when we learn more about [[Allan Variance]].
-# Time Dilation
-> Time dilation is the lengthening of the time interval between two events for an observer in an inertial frame that is moving with respect to the rest frame of the events (in which the events occur at the same location). ([Source](https://openstax.org/books/university-physics-volume-3/pages/5-3-time-dilation))
-
-Consider a coordinate frame with a space axis, $x$, and a time axis, $t$. We also have two _events_, $a$ and $b$. Events are points in this coordinate frame with a time coordinate and a space coordinate. The length of a vector in this coordinate system, or the _spacetime interval_ between two events, represents the proper time measured with an inertial clock between the events.
-
-```plaintext
-    t
-    ▲     
-    │    .e(x,t)
-time│
-    │
-    └──────────►x
-       space
-```
-- $\Delta x$ is the distance traversed by a local observer of $e$.
-- $\Delta t$ is the elapsed coordinate time to event $e$.
-- $\Delta x / \Delta t$ is the speed of the moving observer relative to the coordinate frame, $v$.
-- $\Delta s$, the length of a vector from the origin to $e$, is equal to the elapsed proper time according a local observer's inertial clock. This is also called the _spacetime interval_.
-
-Unlike linear spatial coordinates where the "grid" is square, spacetime coordinates are not linear. The "grid" on the spacetime plot is made up of hyperbolas rather than lines.
-
-![](Pasted%20image%2020240101164720.png)
-
-## Time Dilation from Velocity
-The _Metric Equation_ lets us find a spacetime interval between events. ([Derivation](https://physics.unm.edu/Courses/Fields/Phys2310/Lectures/lecture27.pdf))
-$$\Delta s^2 = \Delta t^2 - \Delta x^2$$
-We want to relate the elapsed proper time $\Delta s$ to the elapsed coordinate time $\Delta t$. Special Relativity tells us that the speed of light, $c$, is constant in all inertial frames—this is the key to our solution.
-
-> [!note]
-> The Metric Equation comes from Special Relativity, which is to say we are assuming that this coordinate frame is far from any gravity wells for now. The consequences of General Relativity and being in the presence of gravitational potential field, or gravity well, are explored later.
-
-If we substitute our terms with equivalent definitions related to a pulse of light moving at $c$, we get
-$$
-\Big(c \frac{\Delta s}{2}\Big)^2 = \Big(c \frac{\Delta t}{2} \Big)^2 - \Big(v \frac{\Delta t}{2} \Big)^2, \quad v = \frac {\Delta x} {\Delta t}
-$$
-Now we can solve for elapsed coordinate time using the locally observed proper time $\Delta s$ and the observer's speed in the coordinate frame. ([Derivation](https://openstax.org/books/university-physics-volume-3/pages/5-3-time-dilation))
-$$
-\Delta t = \frac {\Delta s} {\sqrt{1 - (v/c)^2}}
-$$
-We can refer to the relationship between proper time and coordinate time that depends on the relative speed between observers as the _Relativistic Factor_, $\gamma$. This is syntactic sugar and sometimes called the _Lorentz Factor_.
-$$
-\Delta t = \gamma \Delta s, \quad \gamma = \frac {1}{\sqrt{1 - v^2/c^2}}
-$$
-The [**clock hypothesis**](https://en.wikipedia.org/wiki/Time_dilation#Clock_hypothesis) is the assumption that the **rate at which a clock is affected by time dilation does not depend on its acceleration but only on its instantaneous velocity.** We see this manifest above in our definition of $\gamma$ only depending on $v$ and universal constants. [Wikipedia's derivation](https://en.wikipedia.org/wiki/Time_dilation) is quite good here.
-
-> [!tip]
-> Velocity is not absolute, so the observer can't measure it without a reference to something else. Acceleration _is_ absolute, though, so a local observer can measure its own accelerations without an external frame of reference. Then again, if not for an external reference, coordinate time and proper time lose their meaning. An observer can't measure their own coordinate time because their proper time _is_ their coordinate time! My brain hurts…
-## Time Dilation from Acceleration
-It's time to bring gravity into the mix. General Relativity tells us that mass warps spacetime, and we describe this phenomenon with a _gravitational potential field_, or gravity well. In simple terms, a massive object close to another massive object will feel an acceleration just from being nearby.
-
-Gravity-induced accelerations also cause time dilation as described by the [Schwarzschild solution](https://en.wikipedia.org/wiki/Schwarzschild_solution) to Einstein's equations. This is way harder to derive than the equations from special relativity, but it has been experimentally proven time and again: **a clock close to the center of a gravity well will tick more slowly than one far away.**
-
-Unlike dilation from velocity, the dilation from potential is not symmetric. This means that both observers can agree about the dilation without encountering a paradox.
-
-# Let's Try It Ourselves
-
-Consider the Earth-centered Inertial frame (ECI), an inertial frame centered at Earth's center with three spatial axes, $(x,y,z)$. We place our perfect reference clock at the center of Earth and use it to track the Coordinate Time, $t$.
-
-Now imagine 4 points in this coordinate frame. How does time dilation affect each one?
-1. ⭕ - an imaginary, static point in inertial space 100 km above Beijing.
-2. 📡 - a ground station at sea-level in Canada rotating along with the Earth's surface.
-3. ✈️ - a plane flying 10 km due east above the ocean at 900 km/h ground speed.
-4. 🛰 - a satellite orbiting in a [geosynchronous equatorial orbit](https://en.wikipedia.org/wiki/Geostationary_orbit) around Earth. 
-
-![](ECI%20vs%20time%20dilation.png)
-Point ⭕ has zero velocity, but is still in the presence of Earth's gravity well and feels gravitational potential. Is its proper time faster or slower than coordinate time? _Faster!_
-
-Now let's consider some real objects, 📡 and ✈️. Both are pretty close to each other in terms of altitude, astronomically speaking, so they share about the same amount of gravitational dilation. Unlike ⭕, both are in motion with the Earth's surface as it rotates. And that means they're moving pretty dang fast with respect to the center of Earth. The dilation from velocity dominates over the dilation from being far from the center of Earth, so both clocks are _slower_ than the coordinate time in total.
-
-But how do 📡 and ✈️ compare to each other? ✈️ is moving 900 km/h ground speed, and 📡 is at rest on the surface. Since ✈️ is moving faster than 📡, its clock appears slower than 📡.
-
-Finally, let's consider 🛰… It's not so simple anymore. Let's check [the answers](https://en.wikipedia.org/wiki/Time_dilation).
-
-![](Pasted%20image%2020240101223031.png)
-
-Okay, we're on the right track! Now to do the math ourselves…
-