Update OwlStake validator information

[owlstake]

Updated validator details for OwlStake with new BLS key, website, description, logo, and X profile.

[greptile-apps]

Greptile Summary

This PR adds a new validator entry for OwlStake in the testnet directory. The file follows the required format defined in the repository's example and README, containing all mandatory fields (id, name, secp, bls, website, description, logo, x).

Key observations:

• The filename 031c2421e8e34ed6a017a40f119deb2d97c33ffb09d52d08567aff248cc4aa9a4e.json correctly matches the secp field value inside the file.
• The secp key is 66 hex characters (33 bytes), which is the correct length for a compressed secp256k1 public key.
• The bls key is 96 hex characters (48 bytes), which is the correct length for a BLS12-381 G1 compressed public key — consistent with all other validators in the repository.
• The id value of 231 is unique; no other file in the testnet/ directory uses this ID.
• No prior OwlStake entry exists in the directory, so there are no conflicts.
• All URL fields (website, logo, x) are properly formatted.

Confidence Score: 5/5

• This PR is safe to merge — it adds a single, well-formed validator JSON entry that conforms to the repository format.
• The change is a single data-only JSON file addition. All fields are present, key lengths are correct, the filename matches the secp key, the ID is unique, and the structure mirrors existing validator entries exactly.
• No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Add OwlStake Validator JSON] --> B{Filename == secp key?}
    B -- Yes --> C{All required fields present?}
    C -- Yes --> D{BLS key length = 96 hex chars?}
    D -- Yes --> E{Secp key length = 66 hex chars?}
    E -- Yes --> F{ID 231 unique in repo?}
    F -- Yes --> G[✅ Valid Validator Entry]

Loading

_{Last reviewed commit: 02be093}