staking/kms: correct doc — points at Lux KMS not Hanzo KMS

The HTTP KMS service this client talks to is the Lux blockchain-infra
KMS at ~/work/lux/kms (github.com/luxfi/kms), not Hanzo KMS. Hanzo KMS
(~/work/hanzo/kms) serves Hanzo apps and is a distinct service.

Doc-only fix — no behavior change.
This commit is contained in:
Hanzo AI
2026-06-07 01:39:20 -07:00
parent 8e3f3e60d1
commit e21bf09bbe
+10 -6
View File
@@ -1,12 +1,16 @@
// Copyright (C) 2019-2025, Lux Industries Inc. All rights reserved.
// See the file LICENSE for licensing terms.
// Package staking includes a thin HTTP client to the external Hanzo KMS
// service (kms.hanzo.ai / lux KMS). The KMS service speaks JSON over HTTP
// as its public contract — this file therefore stays on json/v2 by design.
// Do NOT migrate to ZAP: the wire format here is defined by the external
// service, not by us. Internal Lux paths that consume the keys MUST hash
// or copy the result into typed Go values before any internal codec.
// Package staking includes a thin HTTP client to the external Lux KMS
// service (~/work/lux/kms, github.com/luxfi/kms). The KMS service speaks
// JSON over HTTP as its public contract — this file therefore stays on
// json/v2 by design. Do NOT migrate to ZAP: the wire format here is
// defined by the external service, not by us. Internal Lux paths that
// consume the keys MUST hash or copy the result into typed Go values
// before any internal codec.
//
// Not to be confused with Hanzo KMS (~/work/hanzo/kms) which serves
// Hanzoai apps — Lux blockchain node staking uses Lux KMS only.
package staking
import (