cardanowall-sdk 0.0.0__tar.gz

cardanowall_sdk-0.0.0/.github/workflows/ci.yml

@@ -0,0 +1,56 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    name: test (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Sync dependencies (runtime + dev)
+        run: uv sync
+
+      - name: Lint (ruff)
+        run: uv run ruff check .
+
+      - name: Type-check (mypy --strict)
+        run: uv run mypy --strict src tests
+
+      - name: Test (pytest)
+        run: uv run pytest -q
+
+  build:
+    name: build distribution
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build sdist + wheel
+        run: uv build
+
+      - name: Check distribution metadata (twine)
+        run: uvx twine check dist/*

cardanowall_sdk-0.0.0/.github/workflows/release.yml

@@ -0,0 +1,107 @@
+name: release
+
+# ONE-TIME registry setup: at pypi.org configure a GitHub Actions Trusted
+# Publisher (OIDC) with these EXACT fields:
+#     Owner             : cardanowall
+#     Repository        : cip309-py
+#     Workflow filename : release.yml
+#     PyPI Project Name : cardanowall-sdk
+#     Environment       : (leave blank)
+#
+# PyPI supports a PENDING publisher: this mapping can be created BEFORE the
+# project exists, so the very first publish already authenticates over OIDC and
+# no token is ever required. The PYPI_API_TOKEN secret (UV_PUBLISH_TOKEN) is an
+# OPTIONAL fallback only — leave it unset when a (pending) Trusted Publisher is
+# configured.
+
+on:
+  push:
+    tags:
+      - "v[0-9]+.[0-9]+.[0-9]+"
+      - "v[0-9]+.[0-9]+.[0-9]+-*"
+  workflow_dispatch:
+    inputs:
+      dry_run:
+        description: "Dry-run (build + twine check; skip the PyPI upload and the GitHub Release)"
+        required: false
+        default: "false"
+
+concurrency:
+  group: release-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: false
+
+permissions:
+  contents: write
+  # id-token is required for PyPI Trusted-Publisher OIDC (`uv publish`).
+  id-token: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+
+      - name: Sync dependencies (runtime + dev)
+        run: uv sync
+
+      # ---- Gates: the standalone CI suite, re-run as release-blockers ----------
+      - name: Lint (ruff)
+        run: uv run ruff check .
+
+      - name: Type-check (mypy --strict)
+        run: uv run mypy --strict src tests
+
+      - name: Test (pytest)
+        run: uv run pytest -q
+
+      # ---- Build + validate artifacts -----------------------------------------
+      - name: Build sdist + wheel
+        run: uv build
+
+      - name: Check distribution metadata (twine)
+        run: uvx twine check dist/*
+
+      # ---- Publish to PyPI (OIDC Trusted Publishing) -----------------------------
+      # Publishes via the repo's configured PyPI Trusted Publisher (OIDC) — no
+      # token. Do NOT set UV_PUBLISH_TOKEN to an empty value here: uv would then
+      # attempt empty-token auth and fail with 403 instead of using trusted
+      # publishing. For a token-based publish instead, set UV_PUBLISH_TOKEN in the
+      # job env from a PYPI_API_TOKEN secret.
+      - name: Publish to PyPI (dry-run on workflow_dispatch)
+        run: |
+          set -euo pipefail
+          if [ "${{ github.event_name }}" = "workflow_dispatch" ] && [ "${{ inputs.dry_run }}" = "true" ]; then
+            # uv publish has no --dry-run flag; the build + twine check above
+            # already validated the artifacts, so skip the upload entirely.
+            echo "Dry-run: skipping uv publish"
+          else
+            uv publish dist/* --trusted-publishing automatic
+          fi
+
+      # ---- GitHub Release ------------------------------------------------------
+      - name: Detect pre-release tag
+        id: prerelease
+        if: ${{ github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') }}
+        run: |
+          if [[ "${{ github.ref_name }}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+-.+$ ]]; then
+            echo "is_prerelease=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "is_prerelease=false" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Create GitHub Release
+        if: ${{ github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') }}
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ github.ref_name }}
+          name: "CIP-309 Python SDK ${{ github.ref_name }}"
+          generate_release_notes: true
+          draft: false
+          prerelease: ${{ steps.prerelease.outputs.is_prerelease }}
+          files: |
+            dist/*

cardanowall_sdk-0.0.0/.gitignore

@@ -0,0 +1,38 @@
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+
+# Build output
+build/
+dist/
+*.whl
+*.tar.gz
+
+# Resolver lockfile — this is a library; it resolves fresh against the
+# published dependency ranges rather than pinning a committed lock.
+uv.lock
+
+# Virtual environments
+.venv/
+venv/
+
+# Tool caches
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Logs
+*.log
+
+# Editor and IDE directories
+.idea/
+.vscode/
+*.swp

cardanowall_sdk-0.0.0/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+All notable changes to `cardanowall-sdk` are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+> **Pre-1.0 notice.** `cardanowall-sdk` is a pre-1.0 release. The public API,
+> the wire format it implements, and the conformance vectors it tracks may
+> change in backward-incompatible ways until a 1.0 release. Pre-1.0 versions do
+> not carry the stability guarantees of [Semantic Versioning](https://semver.org/).
+
+## [Unreleased]
+
+### Added
+
+- Initial public release of the CIP-309 Python SDK: the standalone verifier
+  (structural / public / recipient roles), the gateway-agnostic HTTP client,
+  the canonical-CBOR structural validator, the sealed-PoE wrap/unwrap
+  primitives, off-host signing, and the raw-seed identity surface. A
+  byte-identical parity twin of the TypeScript and Rust reference SDKs.

cardanowall_sdk-0.0.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,85 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at hello@cardanowall.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+

cardanowall_sdk-0.0.0/CONTRIBUTING.md

@@ -0,0 +1,171 @@
+# Contributing to cardanowall-sdk (CIP-309 Python SDK)
+
+Thank you for your interest in improving `cardanowall-sdk`, the Python SDK for
+CIP-309 — an open standard for **Proof of Existence (PoE)** anchored on the
+Cardano blockchain.
+
+This repository is a **reference implementation** of the standard. It is a
+byte-identical parity twin of the TypeScript SDK (`cip309-ts`) and the Rust SDK
+(`cip309-rs`). The standard itself — the wire format, the registries, and the
+canonical conformance vectors — lives in the separate `cip309` repository.
+
+All contributions are made under the licensing and sign-off terms described in
+[Licensing](#licensing) and [Developer Certificate of Origin](#developer-certificate-of-origin-dco).
+
+---
+
+## What belongs in this repository
+
+This repository holds the **Python implementation**: the standalone verifier,
+the gateway-agnostic HTTP client, the structural validator, the sealed-PoE
+primitives, the raw-seed identity surface, and their tests. Bug fixes,
+performance work, new SDK surface, packaging, and Python-specific issues belong
+here.
+
+### What does NOT belong here
+
+- **Changes to the wire format, the grammar, the schemas, the registries, or
+  the conformance vectors** — those are normative changes to the standard and
+  belong in the `cip309` repository. A change here that would alter canonical
+  bytes is an implementation bug, not a spec change: the vectors are
+  authoritative.
+- **Cross-language behaviour changes** — if a change would make this SDK diverge
+  from `cip309-ts` or `cip309-rs`, open an issue first. Byte-parity is a hard
+  guarantee, not a goal.
+
+If you are unsure which repository a change belongs to, open an issue here and
+ask.
+
+---
+
+## Development setup
+
+This project uses [uv](https://docs.astral.sh/uv/) for environment and
+dependency management, and targets **Python 3.11+**.
+
+```sh
+uv sync          # create the venv and install runtime + dev deps
+uv run pytest -q             # the full test suite
+uv run ruff check .          # lint
+uv run mypy --strict src tests   # type-check (strict)
+```
+
+All four must pass before a pull request is ready. The CI workflow runs exactly
+these gates.
+
+---
+
+## The byte-parity contract
+
+Cross-implementation **byte-parity** is the core guarantee of CIP-309: the
+TypeScript, Python, and Rust SDKs produce and accept byte-identical output for
+the same inputs, validated against the **same canonical conformance vectors**
+(mirrored into this package's `tests/fixtures/`). The vectors — not any one
+implementation — are the source of truth.
+
+This imposes one rule:
+
+> **A change that alters the bytes this SDK produces or the verdicts it
+> reaches must trace to a vector, and must keep this SDK identical to its
+> sibling implementations.**
+
+Concretely:
+
+- If a test fixture and the code disagree, the **fixture is right** unless the
+  fixture itself is being corrected to match a ratified change in the standard.
+- A behaviour change that has no corresponding change in the standard's
+  conformance vectors is almost certainly a bug.
+- New behaviour adds tests that pin the new bytes; changed behaviour updates the
+  affected tests and explains the change in the pull request description.
+
+---
+
+## Tests
+
+- **Assert behaviour, not strings.** Pin returned values, raised error codes,
+  decoded bytes, and end states — not log lines or incidental phrasing.
+- **Use the committed fixtures.** Tests load their vectors from
+  `tests/fixtures/`; do not hand-inline byte constants that a fixture already
+  pins.
+- A change to a public function's behaviour ships with a test that would fail
+  without it.
+
+---
+
+## Style and house rules
+
+- Code is type-checked under `mypy --strict` and linted with `ruff`; keep both
+  green. The lint config bans unvetted crypto and HTTP libraries — use the
+  project's closed crypto catalogue and its outbound-HTTP wrapper.
+- Cite only stable, public references in comments — RFCs, CIPs at a permanent
+  address, NIST/FIPS publications, BIPs. A comment must justify itself on
+  engineering merit, not on traceability to any private document.
+
+---
+
+## Pull request checklist
+
+- [ ] The change is in the right repository (this SDK vs. the standard).
+- [ ] `uv run pytest -q`, `uv run ruff check .`, and `uv run mypy --strict src tests` all pass.
+- [ ] Wire-affecting changes trace to conformance vectors and keep byte-parity
+      with the sibling SDKs.
+- [ ] New or changed behaviour is covered by a test.
+- [ ] Every commit is signed off (see DCO below).
+
+---
+
+## Developer Certificate of Origin (DCO)
+
+This project uses the **Developer Certificate of Origin**. There is **no CLA**.
+
+The DCO is a lightweight attestation that you have the right to submit your
+contribution under the project's license. You make it by adding a
+`Signed-off-by` line to every commit:
+
+```
+Signed-off-by: Your Name <your.email@example.com>
+```
+
+Add it automatically with `git commit -s`. The name and email must be real and
+must match the commit author. By signing off, you certify the statements in the
+Developer Certificate of Origin, version 1.1:
+
+> **Developer Certificate of Origin, Version 1.1**
+>
+> By making a contribution to this project, I certify that:
+>
+> (a) The contribution was created in whole or in part by me and I have the
+> right to submit it under the open source license indicated in the file; or
+>
+> (b) The contribution is based upon previous work that, to the best of my
+> knowledge, is covered under an appropriate open source license and I have the
+> right under that license to submit that work with modifications, whether
+> created in whole or in part by me, under the same open source license (unless
+> I am permitted to submit under a different license), as indicated in the file;
+> or
+>
+> (c) The contribution was provided directly to me by some other person who
+> certified (a), (b) or (c) and I have not modified it.
+>
+> (d) I understand and agree that this project and the contribution are public
+> and that a record of the contribution (including all personal information I
+> submit with it, including my sign-off) is maintained indefinitely and may be
+> redistributed consistent with this project or the open source license(s)
+> involved.
+
+---
+
+## Licensing
+
+By contributing, you agree that your contributions are licensed under the
+project's license: the **Apache License 2.0** (see [`LICENSE`](LICENSE)).
+
+## Code of Conduct
+
+All participation is governed by our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please read it before contributing.
+
+## Security
+
+Do not report security-impacting issues through public issues or pull requests.
+Follow the private process in our [Security Policy](SECURITY.md).

cardanowall_sdk-0.0.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.