# Amendment 1 to The Bridgit DAO Structure & Relationships Act of April 2025  
**Proposer:** @Shiftshapr  
**Purpose:** Apply name, stake, and service-fee clarifications before the upcoming vote.

---

## 1. Organization Name  
1.1 References to “Bridgit DAO” in this Act are hereby replaced with “Bridgit,” acknowledging that the entity remains a decentralized autonomous network of projects—hereafter styled simply as **Bridgit**, a network and collective. The names **Bridgit** and **Bridgit DAO** may be used interchangeably in social, informal, or promotional settings.

1.1.1 **Exception for Formal Contexts**  
> In formal legal, technical, academic, governance, or voting contexts—such as regulatory filings, scholarly publications, protocol specifications, or on-chain ballots—the term **“Bridgit DAO”** may be used to clarify the organization’s on-chain, decentralized structure.  

---

## 2. Financial Stake Clause  
2.1 Amend Section 6.1 (formerly “Bridgit DAO Stake & Investment”) to read:  
> **6.1 Stake Model**  
> 6.1.1 Bridgit may—but is not required to—hold a direct financial stake in any project.  
> 6.1.2 In lieu of equity, projects may instead:  
>   a) Provide services to Bridgit and/or other member projects at no cost or on favorable terms;  
>   b) Play a significant strategic role advancing Bridgit’s mission and/or the success of its constituent projects.  
>   c) The Council, as the voting body for onboarding projects, will determine whether contributions in lieu of equity meet an acceptable level.

---

## 3. Service-Fee Distinctions  
3.1 Insert new Section 6.4 as follows:  
> **6.4 Service Fee Structure**  
> 6.4.1 If Bridgit holds a financial stake in a project, the project’s service fees for Bridgit-provided resources may be adjusted to reflect that equity relationship.  
> 6.4.2 Projects without a financial stake will receive Bridgit services under standard community-rate schedules, as defined in Bridgit’s Service Catalog.  
> 6.4.3 All fee schedules and catalog updates require Project Guild approval (50% vote, 50% quorum) and inscription via DAO Satplication.

---

## 4. Effect & Ratification  
4.1 **Submission**  
> Any Amendment must be submitted via the DAO Satplication in full text.

4.2 **Amendment Ratification (Standalone)**  
> To ratify a single Amendment on its own, the Council must vote on-chain achieving **60% approval**, citing the Amendment’s inscription ID. Upon passage, that Amendment takes effect immediately.

4.3 **Combined Act + Amendment Vote**  
> Rather than separate ballots, the Council may bundle an Act together with one or more pre-inscribed Amendments into a single on-chain vote. That vote must reference the inscription ID of the most recently inscribed Amendment, which itself must explicitly cite the Act and any additional Amendments by their inscription IDs. A **60% approval** vote on this combined package ratifies **both** the Act and **all** referenced Amendment(s) in one step.

4.4 **Scope**  
> This vote includes this Amendment and The Bridgit DAO Structure & Relationships Act of April 2025, with the associated inscription ID:  
> `c6ad541d5fbaf5ddc0ee054c9832b8eafe676a954a21277f23cf330d15cbb363i0`.