Skip to content

Add validator info for 404 Labs#863

Open
deranalabs wants to merge 1 commit intomonad-developers:mainfrom
deranalabs:add-404labs-validator
Open

Add validator info for 404 Labs#863
deranalabs wants to merge 1 commit intomonad-developers:mainfrom
deranalabs:add-404labs-validator

Conversation

@deranalabs
Copy link

Validator Name: 404 Labs
Node Name: validator_404labs
Operator: Derana

Participating in Monad testnet as a node operator.

@deranalabs deranalabs requested a review from a team as a code owner March 15, 2026 22:43
@greptile-apps
Copy link

greptile-apps bot commented Mar 15, 2026

Greptile Summary

Adds a new testnet validator entry for 404 Labs (operator: Derana). The JSON file follows the correct schema structure with valid SECP (66-char) and BLS (96-char) key lengths, and the filename correctly matches the SECP key.

  • The id field is set to 0, which appears to be a placeholder. Every other testnet validator has a unique, non-zero on-chain ID (1–235+). This should be corrected to the actual validator ID before merging.
  • The website and x fields both point to the same X/Twitter URL (https://x.com/NotFoundLabs), which is valid but worth noting — typically website points to a dedicated site.
  • The logo URL points to a .PNG file hosted on GitHub raw content, which is acceptable.

Confidence Score: 2/5

  • PR should not be merged until the validator ID is confirmed to be correct rather than a placeholder value.
  • The JSON schema and key formats are correct, but the id: 0 value is unique among all testnet validators and is very likely a placeholder. The validation script relies on this ID to verify on-chain key matches, so an incorrect ID would mean the validator data is unverified.
  • Pay close attention to testnet/0292128b110a21ae123e2217cc8b551796a08f4c65cabba284ee2082761ba0fd7e.json — the id field needs to be verified.

Important Files Changed

Filename Overview
testnet/0292128b110a21ae123e2217cc8b551796a08f4c65cabba284ee2082761ba0fd7e.json New validator JSON for 404 Labs. Schema and key lengths are correct, but id: 0 is likely a placeholder — no other testnet validator uses this ID. Needs the correct on-chain validator ID before merge.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: New validator JSON] --> B{Schema Check}
    B -->|Fields match example| C{Key Length Check}
    C -->|SECP: 66 chars ✅| D{BLS: 96 chars ✅}
    D --> E{Filename matches SECP ✅}
    E --> F{On-chain ID Validation}
    F -->|id: 0 ⚠️| G[Fetch validator 0 keys from chain]
    G --> H{SECP/BLS match?}
    H -->|Likely mismatch| I[❌ Needs correct validator ID]
Loading

Last reviewed commit: 6179e62

@@ -0,0 +1,10 @@
{
"id": 0,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validator id appears to be a placeholder

The id field is set to 0, but no other validator in the testnet directory uses id: 0. All existing validators have their actual on-chain validator ID (ranging from 1 to 235+). This value is used by the validation script (scripts/validate.py) to fetch and verify on-chain keys via get_validator_keys(id, network), so an incorrect ID would cause key verification to fail.

Please update this to your actual on-chain validator ID.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant