Goosie Open Source and Standard License Notices
This document separates the Goosie open source position from the Goosie standard and identity position, so that the code may remain open while the canonical Goosie standard remains clear.
1. Open Source Code Notice
The Goosie Protocol documentation and software are provided in open source form for inspection, use, modification, and improvement.
Any man or woman may inspect, copy, modify, and deploy the documentation and code.
The code and documentation are made available on the basis that:
Rather, the rules of The Goosie Private Club determine the conditions under which a deployment may represent itself as part of the canonical Goosie standard.
This keeps the code genuinely open while preserving a clear distinction between the standard and any fork or variation.
2. Goosie Standard Notice
The Goosie standard is the canonical form of the Protocol maintained by Nodes operating in agreement as The Goosie Private Club.
A deployment may represent itself as standard Goosie only where its Nodes operate under the canonical rules of the Protocol.
The canonical rules include, among other things:
Any deployment that materially changes these canonical rules may still operate, but should not present itself as standard Goosie.
The strength of Goosie arises from consistent adherence to its canonical design, not from the prohibition of building software.
3. Name and Identity Notice
The Goosie Private Club is the collection of Nodes operating in agreement under the canonical rules of the Protocol.
A deployment becomes part of The Goosie Private Club when its Nodes:
Such notice should make clear the difference between:
This protects the identity of Goosie by truth of notice and clarity of representation, rather than by trying to prevent others from building.
4. Statement of Principle
We of mankind, acting within The Goosie Private Club, do not claim that others may not inspect, modify, or build upon the Protocol.
Rather, we claim that the Goosie name and standard should be used truthfully, so that users, partners, and counterparties may know whether a deployment is operating:
1. Open Source Code Notice
The Goosie Protocol documentation and software are provided in open source form for inspection, use, modification, and improvement.
Any man or woman may inspect, copy, modify, and deploy the documentation and code.
The code and documentation are made available on the basis that:
- the software may be freely studied and improved;
- modified or forked deployments are permitted;
- the right to inspect and develop the code is not dependent on membership of The Goosie Private Club.
Rather, the rules of The Goosie Private Club determine the conditions under which a deployment may represent itself as part of the canonical Goosie standard.
This keeps the code genuinely open while preserving a clear distinction between the standard and any fork or variation.
2. Goosie Standard Notice
The Goosie standard is the canonical form of the Protocol maintained by Nodes operating in agreement as The Goosie Private Club.
A deployment may represent itself as standard Goosie only where its Nodes operate under the canonical rules of the Protocol.
The canonical rules include, among other things:
- 1,000 Goosie = 1 ounce of gold;
- minting at 51% of gold value;
- Bitcoin-only collateral unless changed by formal standard fork;
- individually attributable and non-pooled BTC backing;
- no forced liquidation;
- the canonical 1% fee structure.
Any deployment that materially changes these canonical rules may still operate, but should not present itself as standard Goosie.
The strength of Goosie arises from consistent adherence to its canonical design, not from the prohibition of building software.
3. Name and Identity Notice
The Goosie Private Club is the collection of Nodes operating in agreement under the canonical rules of the Protocol.
A deployment becomes part of The Goosie Private Club when its Nodes:
- synchronize a common blockchain ledger;
- share a threshold-signing set;
- maintain the same canonical economic rules;
- operate in good faith as standard Goosie.
Such notice should make clear the difference between:
- standard Goosie operating under the canonical rules; and
- any fork, variation, or derived deployment operating outside those rules.
This protects the identity of Goosie by truth of notice and clarity of representation, rather than by trying to prevent others from building.
4. Statement of Principle
We of mankind, acting within The Goosie Private Club, do not claim that others may not inspect, modify, or build upon the Protocol.
Rather, we claim that the Goosie name and standard should be used truthfully, so that users, partners, and counterparties may know whether a deployment is operating:
- within the canonical rules of Goosie; or
- outside them as a fork, variation, or derived deployment.
- openness of code;
- clarity of notice;
- consistency of standards.
Blockchain time stamp verifications:
| notice_time_stamp_verification.png |
| screenshot_goosie_rules_8_time_stamp_verification.png |
| screenshot_notice_update_3_june_22.png |
| screenshot_goosie_rules_9_time_stamp_verification.png |
| screenshot_goosie_rules_10_time_stamp_verification.png |
| screenshot_paper_time_stamp_verification.png |
| screenshot_goosie_rules_12_time_stamp_verification.png |
| verification_of_goosie_rules_14_on_25_nov_22.png |
| verification_of_goosie_rules_15_april_2024.png |
| verification_of_goosie_rules_18_june_2024.png |
| verification_of_goosie_rules_18_spreadsheet_june_2024.png |
| verification_of_goosie_rules_20_july_2024.png |
| verification_of_goosie_rules_20_spreadsheet_july_2024.png |
| screenshot_goosie_rules_22_time_stamp.png |
| verification_of_goosie_rules_22_spreadsheet_april_26.png |
| screenshot_open_source_license_verification_may_26.png |
| screenshot_goosie_build_rules_may_26_verification.png |
| screenshot_goosie_build_rules_spreadsheet_may_26_verification.png |