AlgoVoi Policy Binding: now on PyPI and npm (Apache-2.0) #1959
Replies: 1 comment
-
|
Hi @chopmob-cloud — thanks for sharing your work on the AlgoVoi substrate, and for keeping it Apache-2.0. 🙏 To keep Show and Tell easy to browse for everyone, we try to keep things to roughly one thread per project, with ongoing updates posted as comments or edits on that thread rather than as new discussions. Over the past few days this project has produced several near-duplicate release announcements, so we're closing this one as a duplicate. Your consolidated substrate thread (#1961) and the Agent Trust Bench thread (#1855) both remain open — please post future updates (new packages, version bumps, conformance changes) there instead of opening new discussions. Appreciate your contributions to the ecosystem! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What it is. Policy Binding is an additive, Apache-2.0 layer for the AlgoVoi substrate. It binds a content-addressed snapshot of the policy in force to an existing AlgoVoi reference (a settlement-action binding, or a retention-chain entry), so a decision is verifiable against the exact policy version that admitted it, and a policy change is detectable by recomputation. It is offline-verifiable: any party recomputes the binding with SHA-256 over JCS (RFC 8785) canonical bytes, with no operator trust required. The canonicalisation base and the underlying binding and chain are unchanged; this layer only references them by hash.
It works across v0 and v1 (it binds over retention-chain v0 and v1, and the settlement-action binding), and it ships natively in Substrate 2.
Install. Pin the version, preserve the NOTICE (an Apache-2.0 requirement), and run the conformance suite.
Both packages are byte-for-byte identical and cross-checked against the public conformance vectors. Pin the exact version, not a range.
Licence. Apache-2.0. A NOTICE file ships with each package and must be preserved in any distribution (Apache-2.0 section 4(d)).
For L2 developers across the ecosystem. AlgoVoi maintains the L1 canonicalisation base, stable and cross-validated across eight independent implementations, openly under Apache-2.0, as a foundation the whole ecosystem can build on. Policy Binding is how we extend it: never by changing the base, always by adding layers on top that import the base by hash. That keeps every layer interoperable and makes attribution structural. We want L2 builders to build on this. Pin the version, keep the NOTICE, and your work composes cleanly with ours as the base evolves.
Beta Was this translation helpful? Give feedback.
All reactions