Add Liquify JSON configuration file

[Luke-Liquify]

No description provided.

[greptile-apps]

Greptile Overview

Greptile Summary

Adds validator configuration for Liquify (ID: 204) to the testnet directory with all required fields.

• File naming follows the convention <SECP_KEY>.json
• All required schema fields are present: id, name, secp, bls, website, description, logo, and x
• BLS key length (110 chars) differs from all other testnet validators (96 chars) - CI validation will verify against on-chain data

Confidence Score: 4/5

• This PR is safe to merge pending CI validation of the BLS key
• The configuration follows the standard validator info schema with all required fields properly formatted. The only concern is the BLS key length (110 chars vs standard 96 chars), but the CI validation will verify this against on-chain data. If CI passes, the key is correct.
• Verify that CI validation passes for the BLS key in testnet/036e9a29494a621d10ec4c80f5ec5cdb2288024c587ded91aa32d77c5b542cea25.json

Important Files Changed

Filename	Overview
testnet/036e9a29494a621d10ec4c80f5ec5cdb2288024c587ded91aa32d77c5b542cea25.json	New validator configuration for Liquify with BLS key that is 110 chars instead of standard 96 chars

Sequence Diagram

sequenceDiagram
    participant Dev as Liquify Developer
    participant Repo as validator-info Repository
    participant CI as GitHub CI/Validation
    participant Chain as Monad Testnet Chain
    
    Dev->>Repo: Add 036e9a...cea25.json
    Note over Dev,Repo: New validator config with:<br/>- ID: 204<br/>- SECP: 036e9a...cea25<br/>- BLS: 924dc4...c595
    Repo->>CI: Trigger validation workflow
    CI->>CI: Validate JSON schema
    CI->>CI: Check required fields
    CI->>CI: Verify logo URL accessibility
    CI->>Chain: Query validator ID 204
    Chain-->>CI: Return on-chain SECP & BLS keys
    CI->>CI: Compare local vs on-chain keys
    CI-->>Repo: Validation result

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}