# Public Release Announcement #Mar-15 2026

[YutaHoshino]

Public Release Announcement

We have updated the hazBase contracts, SDK helpers, deployment tooling, and documentation to make operational flows safer and more explicit across reserve routing, factory deployments, and MTC/KPI bootstrap steps.

This release focuses on reducing ambiguous setup paths and tightening operational assumptions around:

• Splitter -> ReservePool routing
• ContractFactory implementation registration and clone deployment
• MultiTrustCredential / KpiRegistry proof bootstrap setup
• SDK and docs alignment with the current on-chain behavior

Release Scope

• contracts — reserve routing and deployment policy safeguards
• @hazbase/kit — explicit reserveBucket handling and proof bootstrap helper updates
• @hazbase/factory — policy-aware implementation registration via initializer signatures
• hazbase-docs — updated SDK pages and factory deployment runbook

Highlights

1. Explicit reserve bucket routing in Splitter

Splitter routes can now explicitly specify how funds should be handled when the destination is a ReservePool.

• Added reserveBucket to Splitter.Route
• Supported values:
  • direct
  • compensation
  • liquidity
• ERC20 and native routing now distinguish between direct transfers and reserve funding targets more clearly

This removes the previous ambiguity where reserve-directed flows could implicitly fall into compensation-oriented behavior.

2. Safer native asset behavior in ReservePool

ReservePool now makes the liquidity/compensation distinction more explicit for native assets.

• Native funding to the liquidity bucket is now rejected
• Native funding remains supported for the compensation bucket
• Buyback assumptions remain ERC20-based

This change is intended to prevent silent operational mismatches between funding and buyback flows.

3. Policy-aware implementation registration in ContractFactory

ContractFactory now supports deployment policy metadata per implementation version.

• Added setImplementationWithPolicy(...)
• Added getImplementationPolicy(...)
• Added ImplementationPolicySet(...) event
• Clone deployment can now enforce:
  • whether a version is cloneable
  • whether initializer calldata is required
  • which initializer selector is expected

This helps catch missing or mismatched initData earlier during deployment.

4. Clearer proof bootstrap flow for MultiTrustCredential / KpiRegistry

The proof path now has clearer operational expectations.

• MultiTrustCredential proof flows assume verifier setup happens after deployment
• KpiRegistry integrations require the correct writer-role wiring on the MTC side
• SDK helper guidance has been updated to reflect this setup sequence

This is aimed at making “deploy complete” and “proof-ready” meaningfully distinct operational stages.

SDK Notes

@hazbase/kit

This release introduces a minor version update with a breaking change.

Breaking change

Splitter.Route now requires reserveBucket.

Before:

{ dest: "0xRecipient...", bps: 5000 }

After:

{ dest: "0xRecipient...", bps: 5000, reserveBucket: "direct" }

If your integration routes funds into a ReservePool, please review each route explicitly instead of relying on the previous implicit behavior.

@hazbase/factory

Factory tooling now supports policy-aware implementation registration.

Example:

npx @hazbase/factory set 0xAbCd...1234 \
  --chainId 137 \
  --contractType BondToken \
  --initSignature 'initialize(address,address[])'

This allows the factory to reject clone deployments that omit required initializer calldata or use the wrong selector.

Documentation Updates

We also updated the docs to match the current implementation.

• SDK helper pages now reflect the new reserve routing behavior
• MTC/KPI pages now clarify verifier and role bootstrap requirements
• @hazbase/factory docs now include a deployment runbook covering:
  • implementation registration
  • clone deployment
  • privilege handoff
  • post-deploy wiring

Status & Requests

• These are still early 0.x releases; APIs and operational guidance may continue to evolve
• We strongly recommend validating new integrations on testnets before production rollout
• Ongoing security and operational review will continue
• Please report bugs, inconsistencies, or integration feedback via GitHub Issues / Discussions

Notes for Upgraders

Please review the following before upgrading:

• Splitter route definitions now require reserveBucket
• Native liquidity funding into ReservePool is no longer allowed
• ContractFactory registrations can now carry initializer policy metadata
• MTC/KPI proof flows should be treated as a post-deploy bootstrap step, not as deploy-time complete by default

Your feedback will directly shape the next round of SDK and contract improvements.