Update JSON file with new ID and BLS key Nodeify

[kw1knode]

No description provided.

[greptile-apps]

Greptile Summary

This PR updates the validator registration entry for Nodeify by replacing the existing secp256k1 identity key, BLS key, and validator ID, and renaming the file accordingly.

Key changes:

• File renamed from 02f2c116...bcbd.json → 02b03c0c...1326.json to match the new secp key (correct convention across the repo)
• secp field updated to 02b03c0cbf064dbc2c1a0ad765af236d01c930ab98c2e6aa235990beb81e6d1326 (66 hex chars — valid compressed secp256k1 public key)
• bls field updated to b24d2ceb9ada0ac757c9e9e243e3f52ea16912c36ee8d9c48f60c3114049ed6d66a4936bb98f1a4cc24d24dddef87c05 (96 hex chars — valid compressed BLS12-381 G1 public key)
• id updated from 173 → 201; no other file in the repo currently uses either value
• All other validator metadata (name, website, description, logo, X handle) is unchanged

Confidence Score: 5/5

This PR is safe to merge; all field formats are valid and consistent with the rest of the registry.

The secp key (66 hex chars, 02 prefix) and BLS key (96 hex chars, b prefix with compression flag) are both correctly formatted and match conventions seen throughout the mainnet/ directory. The filename matches the new secp field. The new ID 201 is unique — no duplicate found across the repo. No other metadata fields were altered.

No files require special attention.

Important Files Changed

Filename	Overview
mainnet/02b03c0cbf064dbc2c1a0ad765af236d01c930ab98c2e6aa235990beb81e6d1326.json	Validator "Nodeify" file renamed to match new secp key; id updated from 173 to 201, secp and bls keys both updated with correctly-formatted hex values.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Old file\n02f2c116...bcbd.json\nid: 173\nsecp: 02f2c116...bcbd\nbls: b6ca1f2e...d171"] -->|"Key rotation\n+ ID update"| B["New file\n02b03c0c...1326.json\nid: 201\nsecp: 02b03c0c...1326\nbls: b24d2ceb...c05"]
    B --> C["✓ Filename matches secp field"]
    B --> D["✓ secp: 66 hex chars (valid compressed secp256k1)"]
    B --> E["✓ bls: 96 hex chars (valid BLS12-381 G1 compressed)"]
    B --> F["✓ id: 201 unique across all mainnet/ files"]

Loading

_{Reviews (1): Last reviewed commit: "Update JSON file with new ID and BLS key..." | Re-trigger Greptile}

[a26nine]

Please create a new JSON file instead of updating the current one. The old records should remain for auditing.

[kw1knode]

#908