Add AnyValid Validator info

[bulgakovvlad]

Added a new JSON configuration file for AnyValid.

[greptile-apps]

Greptile Summary

Adds a new validator configuration file for AnyValid (ID 225) to the testnet directory. The JSON follows the standard schema with all required fields populated.

• New testnet validator entry for AnyValid with sequential ID 225
• All fields match the expected schema: id, name, secp, bls, website, description, logo, x
• Filename correctly corresponds to the SECP public key
• No issues found during review

Confidence Score: 5/5

• This PR is safe to merge — it adds a single, well-structured JSON data file with no code changes.
• The change is a single new JSON configuration file that follows the established schema exactly. The filename matches the secp key, the ID is sequential, all required fields are present with correct types, and key lengths are consistent with existing validators. The CI validation script will further verify the on-chain key match.
• No files require special attention.

Important Files Changed

Filename	Overview
testnet/033ba2e56080613c3282856e5a7720240b4ed7566dab62ce73a3c3faebca3393b1.json	New validator config for AnyValid (ID 225). JSON structure matches the example schema with all required fields (id, name, secp, bls, website, description, logo, x). Filename correctly matches the secp key. Key lengths are consistent with existing validators (66-char SECP, 96-char BLS). ID is sequential (previous was 224).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Add AnyValid JSON] --> B[CI: validate.py]
    B --> C{Valid JSON?}
    C -->|Yes| D{Schema matches example?}
    C -->|No| X[❌ Fail]
    D -->|Yes| E{Name non-empty?}
    D -->|No| X
    E -->|Yes| F{Logo URL valid image?}
    E -->|No| X
    F -->|Yes| G{SECP/BLS match on-chain?}
    F -->|No| X
    G -->|Yes| H{Filename == secp.json?}
    G -->|No| X
    H -->|Yes| I[✅ Validation Successful]
    H -->|No| X

Loading

_{Last reviewed commit: 74df586}