test: pin DOMAIN_IDENTITY to 1660078172; fix stale docstring examples
Regression guards for the staging key incident (issue #97). Three changes:
- test_core_hdkeys.py: assert DOMAIN_IDENTITY != 0 and == 1_660_078_172 directly; pin the exact canonical hd_path string for DOMAIN_IDENTITY - test_cmd_auth_keygen_hd.py: verify keygen JSON output hd_path contains the literal 1660078172 (hash-derived), not the legacy 0 - hdkeys.py: fix stale docstring examples that showed the old legacy 0 values
sha256:b1c3df42f619990f2419d243d1f23b076e269f633f0b05fe19b64962423c6b73
sha
+3
~3
symbols
3 changed · 1078 in snapshot
files
sha256:7a6bef23615626b70e84955beaac58b662d541c94892f4792aa9f3ba1caf0553
snapshot
+3
symbols added
~3
symbols modified
3
files changed
1078
files in snapshot
0
dead code introduced
Semantic Changes
6 symbols
+
test_hd_path_uses_hash_derived_identity_domain_not_legacy_zero
method
method test_hd_path_uses_hash_derived_identity_domain_not_legacy_zero L355–373
+
test_DOMAIN_IDENTITY_is_hash_derived_not_legacy_zero
method
method test_DOMAIN_IDENTITY_is_hash_derived_not_legacy_zero L85–90
+
test_identity_hd_path_uses_hash_derived_segment
method
method test_identity_hd_path_uses_hash_derived_segment L92–98
Files Changed
~3
1078 in snapshot
~3
1078 in snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:b1c3df42f619990f2419d243d1f23b076e269f633f0b05fe19b64962423c6b73 --body "your comment"
No comments yet. Be the first to start the discussion.