@the_library/canonical-schemas 0.0.0-stage → 1.1.0

package/LICENSE

@@ -0,0 +1,684 @@
+# D-Open Code Sovereign Licence — Version 1.1 (unified edition)
+
+**Proprietary public source · non-commercial · conditional grant · D-SAFE compliant**
+
+| | |
+|---|---|
+| SPDX identifier | `LicenseRef-DOCSL-1.1` |
+| Year | 2026 |
+| In force | From its first publication at the Licence URL |
+| Full text | https://registry.worldbibliotech.com/licence (the "Licence URL") |
+| Copyright | © 2026 Antoine LUCAS ("Data Pond") |
+| Licensor | Antoine LUCAS, author and copyright owner, identified as in section 1.3 |
+| Certifier | Pond Enterprise Pty Ltd (ACN 694 747 987), operator of https://dsafe.us |
+| Contact | admin@pondenterprise.com |
+
+---
+
+## Read this first: key terms
+
+By downloading, installing, copying, using, running or distributing the Software, **you accept
+this Licence** (section 3). In particular:
+
+1. **Non-commercial, unmodified copies only.** You may view, copy, use and distribute the Software
+   unmodified, for non-commercial purposes only. Modification is not licensed. Normal build steps
+   (bundling, minifying, transpiling, caching) are allowed (sections 5, 6 and 9).
+2. **Public, anonymous, read-only access.** No paywalls, no logins, no advertising, and no donations
+   of your own: donations go through worldbibliotech.com. You may use the Software only to read from
+   the DataPond Network; writing is reserved to services operated by Pond Enterprise (section 9).
+3. **Technical anchors.** Contract addresses must be resolved the way the Software resolves them:
+   through the published registry manifest and its built-in fallbacks (section 7).
+4. **Liquidated damages.** If you modify the Software or redirect its anchors (a Technical Breach)
+   and do not cure it within 30 days of notice, you must pay **USD 50,000,000, or your gross revenue
+   from the modified use (including your affiliates' revenue), whichever is greater**
+   (section 16.4).
+5. **Content rules.** The ten exclusions of the D-SAFE label apply to all D-SAFE Network Content
+   (section 10).
+6. **Indemnity.** You indemnify the Licensor and the Certifier for claims arising from your own
+   implementation, modifications or misuse (section 12.4).
+7. **What Pond Enterprise covers.** Only copyright infringement claims about unmodified certified
+   releases of the code, and about content published and D-SAFE certified by dsafe.us. That cover
+   ends if Pond Enterprise withdraws it, stops operating dsafe.us or closes (section 12).
+8. **Law and courts.** Victorian law; the courts of Victoria and the Federal Court of Australia
+   (section 18).
+9. **Your statutory rights are preserved.** Nothing in this Licence excludes rights you have under
+   the Australian Consumer Law or other laws that cannot be excluded (sections 6.3 and 12.6).
+
+---
+
+## 1. Definitions and interpretation
+
+**1.1 Definitions.** In this Licence:
+
+- **"Anchors"** means the smart-contract addresses, the Canonical Registry Manifest URL, the
+  bootstrap AddressRegistry addresses and other endpoints the Software uses to reach the DataPond
+  Network, and the canonical data models the Software implements.
+- **"Authorised Write Services"** means the services operated or authorised in writing by the
+  Licensor and listed as authorised to write at the Licence URL.
+- **"Canonical Registry Manifest"** means the registry manifest published at
+  `https://registry.worldbibliotech.com/<environment>/manifest.json` (where `<environment>` is
+  `production` or `staging`), together with the contract ABIs it references at
+  `https://registry.worldbibliotech.com/abis/evm/<ContractName>.json`.
+- **"Canonical Resolution Path"** has the meaning in section 7.2.
+- **"Certified Release"** means a release of the Software published by the Licensor through an
+  Official Channel, in the form in which it was published.
+- **"Certified User"** means a person who uses an Unmodified Certified Release in compliance with
+  this Licence, in an Implementation that complies with sections 6 to 10.
+- **"Certifier"** means Pond Enterprise Pty Ltd (ACN 694 747 987), the operator of the D-SAFE
+  certification service at https://dsafe.us.
+- **"Certifier's Indemnity"** means the undertaking in section 12.2.
+- **"Content"** means books, works, records and other knowledge artefacts stored, indexed or served
+  using the Software. Content is governed by the Ꭰ-Licence, not by this Licence.
+- **"Content Breach"** means a breach of section 10.
+- **"D-Licence Compliant"** has the meaning in section 9.1.
+- **"DataPond Network"** means the shared Web3 data infrastructure reached through the Anchors: the
+  smart contracts listed in the Canonical Registry Manifest, the corpus and collections it defines,
+  and the data stored on Arweave that it references.
+- **"D-SAFE Certified"** has the meaning in section 11.1.
+- **"D-SAFE Label Standard"** means the standard for the D-SAFE label published at
+  https://dsafe.us, as in force at the relevant time.
+- **"D-SAFE Network Content"** means Content that is written to, stored in, indexed by or served
+  from the DataPond Network, or that is presented as D-SAFE Certified.
+- **"Ꭰ-Licence"** means the content licence (D.I.C. + K, based on CC BY-NC-ND 4.0) that governs
+  Content.
+- **"Gross Revenue"** means all revenue, before any deduction, received from the use, supply or
+  operation of a Modification or of an Implementation affected by a Technical Breach.
+- **"Implementation"** means any application, website, service, device or system that includes,
+  uses or calls the Software, or that reads from or writes to the DataPond Network using it.
+- **"Licence"** means this D-Open Code Sovereign Licence, Version 1.1 (unified edition).
+- **"Licence URL"** means https://registry.worldbibliotech.com/licence.
+- **"Licensor"** means Antoine LUCAS, known as "Data Pond", the author and copyright owner of the
+  Software, identified as described in section 1.3; or, after any assignment, whoever owns the
+  copyright in the Software at the relevant time.
+- **"Login Wall"** means a requirement to register, create an account or sign in before reading
+  public data or Content.
+- **"Marks"** has the meaning in section 11.4.
+- **"Modification"** has the meaning in section 6.1.
+- **"Non-Commercial"** means not primarily intended for or directed towards commercial advantage or
+  monetary compensation.
+- **"Official Channel"** means: (a) the npm packages in the `@the_library` scope published by the
+  Licensor; (b) the registry at https://registry.worldbibliotech.com; (c) the compiled contract code
+  deployed at the addresses listed in the Canonical Registry Manifest; (d) Arweave transactions
+  referenced by the Canonical Registry Manifest; and (e) any other channel the Licensor names at the
+  Licence URL.
+- **"Offline Snapshot"** has the meaning in section 8.1.
+- **"Original Author"** means Antoine LUCAS, the sole creator of the Software, who is also the
+  Licensor at the date of this text.
+- **"Paywall"** means a requirement to pay, subscribe or donate before reading public data or
+  Content.
+- **"Permitted Technical Operation"** means an operation listed in section 6.2.
+- **"Software"** means the source code, object code (including compiled, bundled, transpiled and
+  minified forms published by the Licensor), data models, schemas, type definitions, Web3 utilities,
+  smart-contract source code and compiled contract code, and documentation, that the Licensor
+  publishes with a reference to this Licence. It does not include Third-Party Components or
+  Content.
+- **"Technical Breach"** means a breach of section 6 or section 7.
+- **"Third-Party Components"** means software written by others and included with, or used by, the
+  Software under its own licence.
+- **"Unmodified"** describes a copy of a Certified Release whose behaviour has not been changed by a
+  Modification. A copy stays Unmodified after Permitted Technical Operations.
+- **"Write"** means to create, change or delete accounts, records or other state in the DataPond
+  Network, including by sending a transaction to one of its contracts.
+- **"You"** means the person exercising rights under this Licence and, if that person acts for an
+  organisation, the organisation as well.
+
+**1.2 Interpretation.** Headings are for convenience only. "Including" and similar words do not
+limit what comes before them. A reference to a law includes that law as amended or replaced.
+The singular includes the plural and the reverse.
+
+**1.3 Identity of the Licensor.** Besides the name Antoine LUCAS, the Licensor is identified by:
+
+- (a) **a researcher identifier:** ORCID iD https://orcid.org/0009-0001-2086-7264; and
+- (b) **the publishing accounts:** the npm account `the-ethical-library`, which publishes the
+  `@the_library` packages, and the commit identity "Data Pond" in the Software's source history.
+
+Statements about this Licence, such as naming an assignee or changing a contact address, are made
+by publication at the Licence URL.
+
+---
+
+## 2. Status of this Licence
+
+**2.1 Texts replaced.** This Licence unifies and replaces the following texts. From its first
+publication at the Licence URL, the Licensor distributes the Software only under this Licence.
+
+- (a) The text titled "D-CODE SOVEREIGN LICENCE (v1.1)", also called "D-Open Code Sovereign Licence
+  v1.1" and "D-Open Sovereign Licence", published at the Licence URL before this Licence.
+- (b) The text titled "D-Open Code Sovereign Licence v1.0".
+- (c) The text titled "THE D-CODE SOVEREIGN LIABILITY SHIELD LICENCE (v3.0)", also titled "THE
+  D-OPEN CODE SOVEREIGN LICENCE (DOCSL) (v3.0)".
+
+**2.2 Copies distributed earlier.** A copy of the Software that was distributed with one of those
+earlier texts, or with a notice referring to one, stays licensed under that text. You may choose to
+accept this Licence for that copy instead.
+
+**2.3 Which "Version 1.1".** A notice that names "Version 1.1 (unified edition)", or carries the SPDX
+identifier `LicenseRef-DOCSL-1.1`, refers to this Licence and not to the earlier text described in
+section 2.1(a).
+
+**2.4 Code, not content.** This Licence covers the Software only. Content is governed by the
+Ꭰ-Licence. Nothing in this Licence licenses Content, and nothing in the Ꭰ-Licence licenses the
+Software. Where both apply, You must comply with both.
+
+**2.5 Later versions.** The Licensor may publish new versions of this Licence at the Licence URL. A
+new version may, for example, change the governing law, the courts or the contact details after the
+Licensor or the Certifier moves to another country. A new version applies to copies distributed
+with it, or after it is published. It does not change the terms for a copy You already hold unless
+You accept it.
+
+**2.6 Successors.** If the copyright in the Software is assigned, the assignee becomes the Licensor,
+and this Licence continues to apply between You and the assignee. The Licensor will publish the
+assignee's name, identifiers and contact details at the Licence URL. An assignee does not take on the Certifier's Indemnity. A Licensor who is
+an individual, including the Original Author, gives no indemnity and accepts no liability under this
+Licence, beyond liability that the law imposes and that cannot be excluded.
+
+---
+
+## 3. Accepting this Licence
+
+**3.1 Permission and agreement.** This Licence is both a conditional permission under copyright law
+and an agreement between You and the Licensor.
+
+**3.2 How You accept.** You accept this Licence by downloading, installing, copying, using, running,
+building on or distributing the Software. If You do not accept it, You have no right to do any of
+those things, except where the law allows them without a licence.
+
+**3.3 Terms to note.** Your attention is drawn to section 16.4 (liquidated damages), section 12.4
+(your indemnity), section 9 (non-commercial, read-only use), section 10 (content rules) and
+section 18 (governing law and courts). They are summarised at the top of this Licence and in the
+notice carried by the Software's files.
+
+**3.4 Conditions.** The rights in section 5 are granted on the conditions in sections 6 to 10. If You
+do not meet a condition, the acts it governs are outside this Licence.
+
+**3.5 Authority.** If You accept this Licence for an organisation, You confirm that You are
+authorised to bind it.
+
+---
+
+## 4. Systemic risk and valuation
+
+**4.1 Not a standalone application.** You acknowledge that the Software is not a standalone
+application. It is an interface to a shared Web3 data infrastructure and a curated smart-contract
+ecosystem: the DataPond Network.
+
+**4.2 Valuation.** For the purposes of this Licence, You agree that the value of the DataPond
+Network is USD 50,000,000, and that this figure reflects the legitimate interest of the Licensor
+and the Certifier in protecting it. This figure is a pre-estimate of the harm a Technical Breach
+can cause to the DataPond Network, for the purposes of section 16.4. It is not a valuation of the
+copyright in the Software.
+
+**4.3 Liability anchor.** The Certifier accepts responsibility under section 12.2 only for Unmodified
+Certified Releases that use the Anchors as published, and for Content published through dsafe.us and
+D-SAFE Certified. A Modification of the Anchors can expose the Licensor and the Certifier to civil
+and regulatory liability for an Implementation they did not certify.
+
+**4.4 Network integrity.** The DataPond Network uses shared state. A Modification of the data models,
+or a redirection of the Software to a private, centralised database (a fork), can corrupt shared
+data irreversibly and harm the whole DataPond Network, its users and the value stated in
+section 4.2.
+
+**4.5 Basis for damages.** The acknowledgements in this section 4 are the basis for section 16.4.
+
+---
+
+## 5. Grant of rights
+
+**5.1 Grant.** Subject to this Licence, the Licensor grants You a worldwide, royalty-free,
+non-exclusive licence to view, copy, use, run and distribute Unmodified copies of the Software, for
+Non-Commercial purposes only, including as part of an Implementation that is D-Licence Compliant.
+
+**5.2 Distribution.** When You distribute the Software, You must:
+
+- (a) keep every copyright, licence and attribution notice it carries;
+- (b) include this Licence, or a link to the Licence URL, with each copy; and
+- (c) not impose terms that restrict the rights a recipient has under this Licence.
+
+**5.3 Recipients.** Each person who receives the Software, from You or anyone else, receives this
+Licence directly from the Licensor.
+
+**5.4 Reservation.** All rights not expressly granted are reserved by the Licensor. This Licence
+grants no right to sublicense, no right to use the Software commercially, and no right to make or
+distribute a Modification (section 6).
+
+---
+
+## 6. Modification
+
+**6.1 What "Modification" means.** A "Modification" is any change that alters what the Software
+does, including:
+
+- (a) editing, patching, adapting or translating the Software, or creating a derivative work or
+  fork of it;
+- (b) changing, replacing or overriding an Anchor; and
+- (c) at runtime, replacing or wrapping the Software's functions ("monkey-patching"), or proxying,
+  intercepting or rewriting its network requests, so as to change its behaviour or redirect an
+  Anchor.
+
+A Permitted Technical Operation is not a Modification.
+
+**6.2 Permitted Technical Operations.** You may do the following without making a Modification:
+
+- (a) **Build steps:** bundling, transpiling, minifying, tree-shaking, code-splitting, compressing,
+  generating source maps, type-checking, polyfilling and similar automated build steps, as long as
+  the result behaves as the Software does;
+- (b) **Caching and serving:** caching, mirroring, storing and serving copies, including through
+  content delivery networks, package mirrors, service workers and archives;
+- (c) **Local inspection:** inspecting, debugging, testing and experimenting with the Software on
+  Your own devices, including with developer tools and browser extensions, as long as You do not
+  distribute a changed version or operate one for others;
+- (d) **Security fixes:** applying a fix for a security vulnerability until a Certified Release fixes
+  it. The Licensor asks that You report the vulnerability to admin@pondenterprise.com;
+- (e) **Audit copies:** copying and changing the Software only to audit, review, test, research or
+  verify it (including security research and academic study), as long as the changed version is
+  not distributed (other than to the Licensor or the Certifier) and is not used to operate an
+  Implementation for others. You may publish Your findings, with excerpts reasonably needed to
+  describe them;
+- (f) **Documented options:** using the configuration options and public interfaces the Software
+  provides, as documented by the Licensor, except to redirect an Anchor contrary to section 7; and
+- (g) **Your own code:** writing Your own code that calls the Software through its public
+  interfaces, including wrappers and adapters, as long as it does not change the Software's
+  behaviour or its Anchors.
+
+**6.3 Statutory rights.** Nothing in this Licence excludes or limits a right You have by law that
+cannot be excluded or limited, including under sections 47B(3), 47C, 47D, 47E and 47F of the
+Copyright Act 1968 (Cth) and equivalent laws in other countries.
+
+**6.4 No modification right.** This Licence grants no right to make, use or distribute a
+Modification. An unlicensed Modification is outside this Licence. The Licensor will treat it as
+copyright infringement as well as a breach of this Licence, and may pursue the remedies available
+under this Licence and the law.
+
+**6.5 Runtime changes.** In addition to section 6.4, You agree not to make a Modification of the
+kind described in section 6.1(c) in any Implementation that You distribute or operate for others.
+
+**6.6 Separate written licence.** A modified build of the Software, or any commercial use of it,
+requires a separate written licence from the Licensor. Contact admin@pondenterprise.com before
+making any change or starting any commercial use.
+
+**6.7 No certification for Modifications.** A Modification is not a Certified Release. It receives
+no D-SAFE certification and no Certifier's Indemnity.
+
+---
+
+## 7. Technical anchors
+
+**7.1 Anchors must not be changed.** You must not alter, replace or override the Anchors, or redirect
+the Software to a non-certified ledger, registry or endpoint.
+
+**7.2 How addresses are resolved.** The Software resolves the current smart-contract addresses and
+ABIs in the following order (the "Canonical Resolution Path"). You must let it do so:
+
+- (a) **the Canonical Registry Manifest**, fetched directly or through a mirror allowed by
+  section 7.4;
+- (b) **the fallbacks built into the Certified Release**, if the manifest cannot be reached or
+  returns no data: the copy of the manifest data that the Software last cached, and the on-chain
+  AddressRegistry, found at the bootstrap address bundled with the Certified Release and read live
+  from the blockchain; and
+- (c) **an Offline Snapshot**, in the circumstances described in section 8.
+
+**7.3 Current addresses prevail.** The addresses resolved through the Canonical Resolution Path at
+the time of use are the authoritative Anchors. Addresses bundled with a Certified Release are a
+bootstrap copy, used only by the fallbacks in section 7.2(b). Outside an Offline Snapshot, You must
+not hard-code addresses in place of the Canonical Resolution Path. This lets the Licensor migrate
+contracts, or respond to a hard fork, without breaking Implementations.
+
+**7.4 Mirrors.** You may operate or use a mirror of the Canonical Registry Manifest and its ABIs,
+and point the Software's documented registry setting at it, only if the mirror serves unaltered
+copies of the files published at https://registry.worldbibliotech.com.
+
+**7.5 No private forks.** You must not fork the Software, or configure it, so as to redirect the
+DataPond data models to a private, centralised database.
+
+---
+
+## 8. Offline Snapshots
+
+**8.1 Right to deploy offline.** You may download, cache and deploy Unmodified copies of a Certified
+Release in environments that cannot connect to the Canonical Registry Manifest or to the
+blockchain, such as air-gapped schools, remote field operations and shelters (an "Offline
+Snapshot").
+
+**8.2 Addresses stay valid.** In an Offline Snapshot, the addresses contained in the snapshot when it
+was taken are valid Anchors, provided the snapshot was taken from a Certified Release.
+
+**8.3 Only while offline.** Section 8.2 applies only while the snapshot cannot connect. Once it can,
+the Software resolves addresses through the Canonical Resolution Path. An Offline Snapshot is
+read-only, like every Implementation (section 9.2).
+
+**8.4 Content in snapshots.** Content included in an Offline Snapshot remains governed by the
+Ꭰ-Licence.
+
+---
+
+## 9. D-Licence Compliance, read-only use and AI training
+
+**9.1 D-Licence Compliance.** Every use of the Software, and every Implementation, must be
+"D-Licence Compliant", which means:
+
+- (a) **Non-Commercial:** the use is Non-Commercial;
+- (b) **no Paywall:** nobody has to pay, subscribe or donate to read public data or Content;
+- (c) **no Login Wall:** anyone can read the public data and Content it serves anonymously,
+  without registering, creating an account or signing in; and
+- (d) **no advertising:** it shows no advertising or sponsorship; and
+- (e) **no donations of its own:** it does not ask for or accept donations, payments or sponsorship
+  for itself. It may link to the donation page at https://worldbibliotech.com, which is the only
+  channel for donations to the DataPond Network. Donations made there are received by the entity
+  named on that page (at the date of this text, DATAPOND Ꭰ-Library PTY LTD, ACN 695 045 071); the
+  Certifier operates the page as its service provider.
+
+**9.2 Read-only use.** You may use the Software only to read from the DataPond Network. You must not
+use it to Write to the DataPond Network. Writing through the Software is reserved to the Authorised
+Write Services. At the date of this text, the only Authorised Write Services are the services
+operated by the Certifier (Pond Enterprise Pty Ltd, pondenterprise.com), including
+worldbibliotech.com. An Authorised Write Service may require an account in order to Write, but not
+in order to read.
+
+**9.3 AI training.** Subject to section 9.1, You may use the Software to train, fine-tune or evaluate
+artificial intelligence models, provided the resulting model or service does not put the Software,
+or the public knowledge reached through it, behind a Paywall or a Login Wall. The use of Content
+for AI training is governed by the Ꭰ-Licence.
+
+**9.4 Text and data mining reserved.** Except as permitted by section 9.3, the Licensor reserves all
+rights over text and data mining of the Software, including for the purposes of Article 4(3) of
+Directive (EU) 2019/790.
+
+---
+
+## 10. D-SAFE integrity and content rules
+
+**10.1 D-SAFE Specification.** Every Implementation must be:
+
+- (a) **Decentralised:** it reads from the DataPond Network through the Anchors, not through a
+  private copy;
+- (b) **Integral:** it is D-Licence Compliant (section 9.1); and
+- (c) **Common:** it presents Content under the Ꭰ-Licence and keeps that Content's attribution and
+  licence notices.
+
+**10.2 The D-SAFE label exclusions.** D-SAFE Network Content must comply with each of the following
+exclusions of the D-SAFE Label Standard:
+
+- **(i) No ecological harm:** no advocacy for deforestation, pollution or species loss.
+- **(ii) No AI generation:** human-authored content only.
+- **(iii) No explicit content or violence:** content must be suitable for every age.
+- **(iv) No stolen content:** no plagiarism, and no infringement of third parties' rights.
+- **(v) No politics:** no partisan debate or campaigning.
+- **(vi) No spirituality:** no religious proselytising.
+- **(vii) No history:** no disputed or speculative historical narratives.
+- **(viii) No medicine:** no medical advice, diagnosis or treatment.
+- **(ix) No fiction:** factual, real-world information only.
+- **(x) No psychological profiling:** no generalising about groups of people.
+
+**10.3 How breaches are decided.** The Licensor or the Certifier decides whether content or an
+Implementation breaches this section 10, acting reasonably and in good faith, by reference to
+section 10.2 and the D-SAFE Label Standard. They will give You written reasons. You may ask for a
+review within 30 days of receiving them. Where practicable, the review will be done by a person who
+was not involved in the first decision.
+
+**10.4 Guidance.** Where the D-SAFE Label Standard publishes more detailed guidance on an exclusion
+in section 10.2, that guidance applies.
+
+---
+
+## 11. D-SAFE certification and trade marks
+
+**11.1 Meaning of "D-SAFE Certified".** In this Licence, a work is "D-SAFE Certified" only if both:
+
+- (a) its D-SAFE certification was issued through the D-SAFE certification service at
+  https://dsafe.us; and
+- (b) the work is listed in the corpus defined by the Canonical Registry Manifest published at
+  https://registry.worldbibliotech.com.
+
+**11.2 Certified Releases of the Software.** A release of the Software is certified for this Licence
+only if it is a Certified Release.
+
+**11.3 Other certifications are not recognised.** A certification, label or mark called "D-SAFE", or
+by a similar name, that is issued by any other person or body, in Australia or elsewhere, is not
+D-SAFE Certified for the purposes of this Licence. This Licence does not recognise it, and it
+confers no right, Certifier's Indemnity or other benefit under this Licence. This Licence says
+nothing about whether such a certification is valid for any other purpose.
+
+**11.4 Names and marks.** This Licence grants no right to use the names, logos or marks "D-SAFE",
+"DataPond", "Ꭰ-Library", "The World Library", "World BiblioTech" or "Pond Enterprise", whether
+registered or not, or any certification mark associated with them (the "Marks"), except to state
+truthfully:
+
+- (a) that an Implementation uses an Unmodified Certified Release; or
+- (b) that a work is D-SAFE Certified within section 11.1.
+
+**11.5 No false claims.** You must not state or imply that a Modification, an Implementation or a
+work is D-SAFE Certified, or is certified, endorsed or guaranteed by the Licensor or the Certifier,
+unless it is.
+
+---
+
+## 12. Liability
+
+**12.1 Licensor disclaimer.** To the extent permitted by law, the Licensor provides the Software "as
+is", without warranties of any kind, and is not liable for any loss or damage, gas fees or data
+loss arising from the Software or its use.
+
+**12.2 Copyright indemnity from the Certifier ("Positive Liability").** The Certifier, by executing
+this Licence, gives the following undertaking to every Certified User (the "Certifier's
+Indemnity"). It covers copyright infringement claims only.
+
+- (a) **Claims covered.** A claim by a third party that a Certified User's Implementation infringes
+  that third party's copyright because the Implementation:
+  - (i) reproduces or communicates an Unmodified Certified Release; or
+  - (ii) serves Content that was published through the D-SAFE certification service at
+    https://dsafe.us and is D-SAFE Certified (section 11.1), unaltered and with its attribution and
+    licence notices.
+- (b) **What the Certifier does.** For a covered claim, the Certifier is the party that answers it.
+  At its own cost, the Certifier will take over the defence and any settlement of the claim, seek
+  to be joined or substituted as defendant where the claimant agrees or a court allows, and
+  indemnify the Certified User against the damages, costs and settlement amounts finally awarded or
+  agreed on that claim.
+- (c) **What the Certified User does.** The Certified User must notify the Certifier in writing
+  promptly after learning of the claim, let the Certifier control the defence and any settlement,
+  give reasonable help at the Certifier's cost, and not admit liability or settle without the
+  Certifier's written consent. The Certifier will not agree a settlement that admits fault for, or
+  imposes an obligation on, the Certified User without the Certified User's consent.
+- (d) **Exclusions.** The Certifier's Indemnity does not cover a claim to the extent it arises from:
+  - (i) a Modification;
+  - (ii) combining the Software or Content with software or content outside section 12.2(a), where
+    the claim would not have arisen without that combination; or
+  - (iii) continuing use after the Certifier has supplied a non-infringing replacement, or withdrawn
+    the release, the Content or its certification, and notified the Certified User.
+- (e) **Replacement or withdrawal.** If a release or Content is the subject of a covered claim, or in
+  the Certifier's reasonable view is likely to be, the Certifier may replace or change the release,
+  or withdraw the release, the Content or its certification.
+- (f) **Nothing else.** The Certifier takes no liability under this Licence for anything else,
+  including technical performance, patents, professional services, or any Content that was not both
+  published through dsafe.us and D-SAFE Certified by dsafe.us.
+
+No monetary cap applies to the indemnity in section 12.2(b).
+
+**12.3 Claims go to the Certifier.** Claims under the Certifier's Indemnity are made against the
+Certifier only. The Licensor gives no indemnity of that kind.
+
+**12.4 Your indemnity.** You indemnify the Licensor and the Certifier against third-party claims, and
+the resulting losses and reasonable legal costs, to the extent they arise from:
+
+- (a) Your Implementation;
+- (b) any Modification You make, use or distribute; or
+- (c) Your breach of this Licence or misuse of the Software (for example, building an unlawful
+  interface using the Software's data models).
+
+This indemnity does not apply to the extent a claim arises from an Unmodified Certified Release
+itself, or from an act or omission of the Licensor or the Certifier.
+
+**12.5 Withdrawal for a Content Breach.** The Certifier's Indemnity depends on Your compliance with
+section 10. If the Licensor or the Certifier decides under section 10.3 that Your Implementation
+has breached section 10, the Certifier's Indemnity stops applying to that Implementation, for events
+after the date of the notice, until the breach is cured. You are then fully responsible for Your
+Implementation.
+
+**12.6 Australian Consumer Law.** Nothing in this Licence excludes, restricts or modifies any right
+or remedy, or any guarantee, warranty or other term, that the Australian Consumer Law (Schedule 2
+to the Competition and Consumer Act 2010 (Cth)) or any other law implies or imposes and that
+cannot lawfully be excluded, restricted or modified. Where that law allows the Licensor to limit
+liability for a breach of such a guarantee, the Licensor's liability is limited to supplying
+the Software again or paying the cost of having it supplied again.
+
+**12.7 Other countries.** Section 12.6 applies equally to consumer-protection laws of other countries
+that cannot be excluded.
+
+**12.8 End of the Certifier's Indemnity.** The Certifier's Indemnity ends on the earliest of:
+
+- (a) the date the Certifier publishes, at the Licence URL, a notice withdrawing it;
+- (b) the date the Certifier stops operating the D-SAFE certification service at dsafe.us; and
+- (c) the date the Certifier is deregistered or wound up.
+
+After that date it covers only claims notified to the Certifier in writing before that date. It
+does not pass to any successor of the Certifier, or to the Licensor or any successor of the
+Licensor, including the Original Author.
+
+---
+
+## 13. Patents
+
+**13.1 Patent licence.** The Licensor grants You a worldwide, royalty-free, non-exclusive licence,
+under any patent claims the Licensor owns or controls now or in the future that are necessarily
+infringed by the Unmodified Software, to do the acts licensed by section 5.
+
+**13.2 Patent retaliation.** If You, or an entity You control, start litigation (including a
+cross-claim or counterclaim) alleging that the Software or a Certified Release infringes a patent,
+this Licence, including the patent licence in section 13.1, terminates for You on the date that
+litigation is filed. This section 13.2 does not apply to a counterclaim in patent proceedings that
+the Licensor or the Certifier started against You first.
+
+**13.3 Nothing more.** This section 13 grants no other patent rights. This Licence gives no
+protection against patents held by third parties.
+
+---
+
+## 14. Third-party components
+
+**14.1 Own licences.** The Software includes or depends on Third-Party Components (for example viem,
+@noble/hashes and @noble/curves, each under the MIT licence). Each Third-Party Component is licensed
+by its own authors under its own licence, not under this Licence.
+
+**14.2 Notices.** The Licensor lists the Third-Party Components it distributes, with their licences,
+in a `THIRD_PARTY_NOTICES` file in each package. You must keep those notices when You distribute
+the Software.
+
+**14.3 Their terms prevail for their code.** Nothing in this Licence limits rights granted by the
+licence of a Third-Party Component. If this Licence conflicts with that licence about that
+component, that licence prevails for that component.
+
+---
+
+## 15. Network operations and permanence
+
+**15.1 Permanent copies.** Copies of the Software are stored on Arweave and in blockchain state, and
+cannot be deleted. The termination of this Licence ends Your rights to use those copies. It does
+not require anyone to delete what cannot be deleted, and it does not affect anyone else's rights.
+
+**15.2 Network operators.** Despite anything else in this Licence, including the termination of any
+person's rights, any person may store, replicate, index, execute, validate, display and serve the
+Software as deployed on a blockchain or stored on Arweave, without changing it, solely as part of
+operating a blockchain node or validator, an RPC service, a block explorer, an indexer, an Arweave
+node or gateway, or an archive. Sections 9 and 10 do not apply to that activity. This permission
+cannot be terminated.
+
+**15.3 Recipients keep their rights.** The termination of Your rights does not terminate the rights
+of people who received copies of the Software from You, as long as they comply with this Licence.
+
+---
+
+## 16. Breach, cure, termination and liquidated damages
+
+**16.1 Automatic termination.** If You breach this Licence, Your rights under it terminate
+automatically.
+
+**16.2 Notice and 30 days to cure.** Before starting legal proceedings (other than for urgent
+injunctive relief), the Licensor or the Certifier will give You notice of the breach, publicly or
+privately. If You cure the breach within 30 days of that notice (for example, by ceasing to use
+and distribute a Modification, removing a Paywall or Login Wall, ceasing to take donations, ceasing
+to Write, restoring the
+Anchors, or removing excluded content), Your rights are reinstated from the date of the cure.
+
+**16.3 Permanent termination.** If You do not cure the breach within those 30 days, the termination is
+permanent. Your rights return only if the Licensor reinstates them in writing.
+
+**16.4 Liquidated damages for an uncured Technical Breach.** Because of the risks described in
+section 4, the loss caused by a Technical Breach is impossible to calculate. If You commit a
+Technical Breach and do not cure it within 30 days of notice under section 16.2, You must pay the
+Licensor, as liquidated damages and not as a penalty, the greater of:
+
+- (a) USD 50,000,000; and
+- (b) the total Gross Revenue generated by the unauthorised use, including Gross Revenue generated
+  by Your parent companies, affiliates and subsidiaries using the modified Implementation.
+
+**16.5 Other remedies.** Section 16.4 does not limit the Licensor's right to injunctive relief. If
+section 16.4 is held unenforceable, the Licensor may instead recover damages or an account of
+profits for the breach or for copyright infringement. The Licensor will not recover twice for the
+same loss.
+
+**16.6 Content Breach.** For a Content Breach, the Certifier's Indemnity stops applying under
+section 12.5, and sections 16.1 to 16.3 apply.
+
+---
+
+## 17. Lawful use
+
+**17.1 Where this Licence does not apply.** This Licence grants no right to use the Software in a
+jurisdiction where:
+
+- (a) decentralised data storage or blockchain technology is illegal; or
+- (b) the use of uncensored public-domain data is prohibited by law.
+
+**17.2 Nothing unlawful required.** Nothing in this Licence requires the Licensor or the Certifier to
+facilitate an act that is unlawful where it is done.
+
+---
+
+## 18. Governing law, courts and injunctive relief
+
+**18.1 Governing law.** This Licence is governed by the law in force in Victoria, Australia.
+
+**18.2 Courts.** You and the Licensor submit to the non-exclusive jurisdiction of the courts of
+Victoria and the Federal Court of Australia, and the courts that hear appeals from them.
+
+**18.3 Injunctive relief.** You acknowledge that a Technical Breach may cause harm that damages cannot
+adequately remedy, and that the Licensor and the Certifier may seek urgent injunctive relief in any
+competent court worldwide. To the extent the law allows, You will not ask a court to require the
+Licensor or the Certifier to give security or post a bond as a condition of that relief.
+
+**18.4 Costs.** The successful party in proceedings about this Licence is entitled to recover its
+reasonable legal costs from the other party.
+
+---
+
+## 19. General
+
+**19.1 Severability.** If a provision of this Licence is held invalid or unenforceable, it is to be
+read down to the extent necessary to make it enforceable, or, if that is not possible, severed.
+The rest of this Licence remains in force.
+
+**19.2 Notices.** Notices to the Licensor or the Certifier, breach reports, security reports, claims
+under the Certifier's Indemnity and requests for a separate written licence go to
+admin@pondenterprise.com, or to another address published at the Licence URL. Notices to You may be
+sent to any contact address You have given, or published at the Licence URL.
+
+**19.3 Assignment.** The Licensor may assign the copyright in the Software and the Licensor's rights under this
+Licence. The assignee takes the place of the Licensor, subject to section 2.6. Your rights pass to
+others only as described in section 5.3.
+
+**19.4 Moral rights.** The Original Author consents, by executing this Licence, to the Permitted
+Technical Operations, including build steps that remove author attribution from built files,
+provided this Licence or the Licence URL accompanies each distribution. This Licence does not
+otherwise affect the Original Author's moral rights.
+
+**19.5 Separate agreements.** A separate written licence or certification agreement between You and
+the Licensor or the Certifier prevails over this Licence where they conflict.
+
+**19.6 No waiver.** A failure or delay in enforcing this Licence is not a waiver.
+
+---
+
+## Grant
+
+This Licence is granted by Antoine LUCAS, the Licensor, who also gives the consent in section 19.4.
+Pond Enterprise Pty Ltd (ACN 694 747 987) gives the Certifier's Indemnity in section 12.2 in favour
+of every Certified User.