inkan-standard

The verification path of the Inkan Standard — BRC-145, a registry-free typed content anchor with on-chain code provenance.

This package verifies three things, offline, with no network and no keys:

from inkan_standard import verify

r = verify.canonical_seal("1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2", "address")
print(r["code"])        # ik112cf1aaca7ef5079...

No required dependencies

Verification never goes dark because an install failed. bitcoinx is used for ECDSA when present; otherwise the bundled pure-Python _secp256k1 takes over — differentially tested against bitcoinx across 1270 cases with zero divergences. Signing a canary is operator-side and needs the extra:

pip install inkan-standard            # verify
pip install "inkan-standard[sign]"    # verify + sign your own canary

The distribution is inkan-standard, and the package you import is inkan_standard. An unrelated PyPI project named inkan installs an import package called inkan; the two names do not collide.

Licence

The code in this distribution is Apache-2.0 — the verification path only, with a patent grant. You may verify Inkan codes and seals, and generate your own, in any product, commercial or not, forever.

The wider Inkan repository is multi-licence: the specification is CC BY 4.0, the conformance vectors are CC0, and the product tier (on-chain anchoring, minting workflows, application surfaces) is BSL 1.1 until 2030-07-09. None of the BSL-licensed code is in this package. See NOTICE for the exact file list this Apache-2.0 grant covers. The conformance vectors bundled for the self-test (inkan_standard/vectors/*.json) are CC0, per the included LICENSE-VECTORS.