Moved the go directive to 1.27.1 and verified the module with go build,
go vet and the full test suite, all clean.
Co-authored-by: Hanzo Dev <[email protected]>
Lux Partners Limited is not the entity behind this work. Every place the
old name stood — copyright lines, site footers, brand config, legal and
compliance text — now names the company that actually holds it.
lux.fund is the exception and is not renamed to match: that site belongs
to Lux Assets Management LLC, a different company, and it says so.
Two kinds of line were left for a person rather than rewritten. A dated
news item recording that Lux Partners Limited was established in the Isle
of Man is a historical fact, and renaming it would falsify the record. And
a sentence asserting that the company is domiciled in the Isle of Man is a
claim about a jurisdiction, not a name — an Inc or an LLC is not an Isle
of Man company, so swapping the name there would assert something untrue.
Co-authored-by: Hanzo Dev <[email protected]>
github.com held commits this host lacked, which refuses the mirror push
("fetch first") and stops github receiving anything at all. Merging rather
than overwriting, so the mirror is a fast-forward again and neither side's
work is dropped.
Adds .hanzo/workflows/cicd.yml calling the canonical pipeline and drops the
GitHub-hosted workflows it replaces. Lands here because this is where the repo
is written — git.hanzo.ai is upstream and github.com is its push mirror, so the
same change made on github.com never reaches the runner fleet.
Parsing is the expensive half and the result is immutable, so a per-call parse
buys nothing; holding it also means the key is zeroed once, at Wipe. The
comments explaining that were a walkthrough of a library defect instead, which
is both more than a reader needs and — since crypto v1.20.5 makes the
constructor own its copy — no longer true.
crypto v1.20.5 comes with it, so this module gets the owning constructor too.
Co-authored-by: Hanzo Dev <[email protected]>
The four callers reached github.com/luxfi/vm/platformvm/signer for a BLS key
plus a signature over it. That module no longer publishes the path, and keys
sits below the node: it manages keys, so it should not need a VM to make one.
crypto/bls, already a dependency, has everything the type needs.
Co-authored-by: Hanzo Dev <[email protected]>
service_identity.go + hybrid.go are pure-function, I/O-free derivation (BIP-39
-> BIP-32 -> ML-DSA-65 NodeID) that imports only luxfi/crypto + go-bip32/39 +
ids — NO kms import, so no keys<->kms cycle. Previously these lived only
vendored-in-kms; consumers (hanzoai/kms/sdk, bank, kms-operator) referenced
keys.ServiceIdentity/NewServiceIdentity that the released keys lacked. This is
the canonical home. (LoadMnemonic stays out of keys — it needs kms/zapclient.)
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev