Skip to content

Add Valopers Safrochain explorers#3

Merged
danbaruka merged 1 commit into
Safrochain-Org:mainfrom
alxnode:valopers-explorer-listings
Jun 13, 2026
Merged

Add Valopers Safrochain explorers#3
danbaruka merged 1 commit into
Safrochain-Org:mainfrom
alxnode:valopers-explorer-listings

Conversation

@alxnode

@alxnode alxnode commented Jun 9, 2026

Copy link
Copy Markdown

Summary

Checklist (required)

  • I ran npm ci and npm run validate locally — it passed before opening this PR.
  • I ran npm run build:registry and committed the updated registry.json in this PR.
  • New or updated app folder is apps/<slug>/ with json/app.json and img/logo.png.
  • <slug> is 2–64 chars, lowercase letters and digits only (no spaces or hyphens), and slug in JSON matches the folder name.
  • Logo is PNG, 512×512 pixels.
  • I have the rights to submit this listing text and logo.
  • I agree my contributions are licensed under the MIT License in this repository.

Validation output (paste if useful)

Summary by CodeRabbit

  • New Features
    • Valopers Mainnet Explorer application is now available
    • Valopers Testnet Explorer application is now available

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds two new Valopers explorer apps to the SafroDappList registry: one for the Safrochain mainnet and one for the testnet. New app manifests define the apps' metadata and properties, and the central registry is updated to include references to both apps with live status and current timestamps.

Changes

Add Valopers Explorers

Layer / File(s) Summary
Valopers app manifests
apps/valopersmainnet/json/app.json, apps/valoperstestnet/json/app.json
Mainnet and testnet Valopers explorer app manifests define schema versioning, app identity (slug and name), description text, status (live), associated chains (safrochain-mainnet and safrochain-testnet respectively), category/tags, documentation URL, and submission/update timestamps (2026-06-09).
Registry entries and metadata update
registry.json
Two new live app entries are added to the registry for Valopers mainnet and testnet explorers with their manifest paths, URLs, and chain scopes. The registry generatedAt timestamp is updated from 2026-04-15 to 2026-06-09.

🎯 2 (Simple) | ⏱️ ~8 minutes

🐰 Two explorers born today,
Mainnet hops and testnet play,
Valopers dance in registry's way,
Timestamps tell when all was made,
New apps in the list parade! 🚀

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description includes the required template structure with a summary section and complete checklist, but all checklist items are unchecked and no actual summary details or validation output are provided. Provide a meaningful summary of what the PR adds, check off completed validation items, and include validation output if available.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding two Valopers Safrochain explorers (mainnet and testnet) to the registry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/valopersmainnet/json/app.json`:
- Around line 1-18: The manifest declares "url":
"https://safrochain.valopers.com/" and "status": "live" but the URL returns HTTP
520 (unreachable); update the "url" value to a reachable endpoint or change
"status" to a non-live value (e.g., "unreachable" or "inactive") and ensure
links.docs remains correct; also verify the logo at
apps/valopersmainnet/img/logo.png meets required dimensions by running
ImageMagick identify (or provide a valid replacement image that matches logo
requirements) and include the validated logo in the app bundle.

In `@registry.json`:
- Around line 560-585: Regenerate registry.json using the canonical build
script: run npm run build:registry and replace the checked-in registry.json with
the produced output (this will update other apps’ url and links.docs entries as
in the build output), then ensure validation passes by installing or adding the
missing ajv dependency (so npm run validate can import ajv without
ERR_MODULE_NOT_FOUND), rerun npm run validate to confirm the schema passes, and
commit the regenerated registry.json and any package.json/package-lock.json
changes; look for the registry.json object with slug "valoperstestnet" to verify
the entry was updated.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3927c84c-26ab-49a8-95fa-607478219f8b

📥 Commits

Reviewing files that changed from the base of the PR and between 79197f9 and 3f85adf.

⛔ Files ignored due to path filters (2)
  • apps/valopersmainnet/img/logo.png is excluded by !**/*.png
  • apps/valoperstestnet/img/logo.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • apps/valopersmainnet/json/app.json
  • apps/valoperstestnet/json/app.json
  • registry.json

Comment on lines +1 to +18
{
"$schema": "../../../schemas/app.manifest.schema.json",
"schemaVersion": 2,
"slug": "valopersmainnet",
"name": "Valopers Mainnet Explorer",
"shortDescription": "Mainnet block explorer powered by Bitszn for transactions, validators, chain height, and direct links to individual txs.",
"description": "Valopers Mainnet Explorer, powered by Bitszn, tracks Safrochain mainnet activity in real time, including accounts, delegations, SAF transfers, validators, and Cosmos SDK messages.",
"url": "https://safrochain.valopers.com/",
"status": "live",
"chains": ["safrochain-mainnet"],
"category": "analytics",
"tags": ["explorer", "blocks", "validators"],
"submittedAt": "2026-06-09",
"updatedAt": "2026-06-09",
"links": {
"docs": "https://docs.safrochain.com"
}
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify logo file exists and check dimensions
if [ -f "apps/valopersmainnet/img/logo.png" ]; then
  identify -format "Logo: %wx%h pixels, %m format\n" apps/valopersmainnet/img/logo.png 2>/dev/null || echo "Logo file found but could not read dimensions (imagemagick not available)"
else
  echo "ERROR: Logo file apps/valopersmainnet/img/logo.png is missing"
fi

# Check URL availability
curl -s -o /dev/null -w "Main URL (https://safrochain.valopers.com/): HTTP %{http_code}\n" -L --max-time 10 https://safrochain.valopers.com/ || echo "Main URL check failed"

curl -s -o /dev/null -w "Docs URL (https://docs.safrochain.com): HTTP %{http_code}\n" -L --max-time 10 https://docs.safrochain.com || echo "Docs URL check failed"

Repository: Safrochain-Org/SafroDappList

Length of output: 249


Fix main explorer URL reachability (HTTP 520) and validate logo requirements

  • apps/valopersmainnet/img/logo.png exists, but logo dimensions couldn’t be checked (ImageMagick identify not available).
  • https://docs.safrochain.com returns HTTP 200.
  • https://safrochain.valopers.com/ returns HTTP 520, so the manifest’s "status": "live" and url should be made reachable/corrected.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/valopersmainnet/json/app.json` around lines 1 - 18, The manifest
declares "url": "https://safrochain.valopers.com/" and "status": "live" but the
URL returns HTTP 520 (unreachable); update the "url" value to a reachable
endpoint or change "status" to a non-live value (e.g., "unreachable" or
"inactive") and ensure links.docs remains correct; also verify the logo at
apps/valopersmainnet/img/logo.png meets required dimensions by running
ImageMagick identify (or provide a valid replacement image that matches logo
requirements) and include the validated logo in the app bundle.

Comment thread registry.json
Comment on lines +560 to 585
{
"$schema": "../../../schemas/app.manifest.schema.json",
"category": "analytics",
"chains": [
"safrochain-testnet"
],
"description": "Valopers Testnet Explorer, powered by Bitszn, tracks Safrochain testnet activity in real time, including accounts, delegations, SAF transfers, validators, and Cosmos SDK messages.",
"links": {
"docs": "https://docs.safrochain.com"
},
"logoPath": "apps/valoperstestnet/img/logo.png",
"manifestPath": "apps/valoperstestnet/json/app.json",
"name": "Valopers Testnet Explorer",
"schemaVersion": 2,
"shortDescription": "Testnet block explorer powered by Bitszn for transactions, validators, chain height, and direct links to individual txs.",
"slug": "valoperstestnet",
"status": "live",
"submittedAt": "2026-06-09",
"tags": [
"explorer",
"blocks",
"validators"
],
"updatedAt": "2026-06-09",
"url": "https://testnet.safrochain.valopers.com/"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify npm run build:registry produces identical output
echo "Running npm run build:registry..."
npm run build:registry

# Check if registry.json was modified
if git diff --quiet registry.json; then
  echo "✓ registry.json matches build output"
else
  echo "✗ registry.json differs from build output:"
  git diff registry.json | head -50
fi

# Also run validation
echo ""
echo "Running npm run validate..."
npm run validate

Repository: Safrochain-Org/SafroDappList

Length of output: 2492


Update/regen registry.json so it matches npm run build:registry, and rerun validation

  • npm run build:registry produces a different registry.json than the one currently checked in (the output changes other apps’ url / links.docs, not just the valoperstestnet entry).
  • npm run validate fails due to missing ajv (ERR_MODULE_NOT_FOUND), so schema validation isn’t completing.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@registry.json` around lines 560 - 585, Regenerate registry.json using the
canonical build script: run npm run build:registry and replace the checked-in
registry.json with the produced output (this will update other apps’ url and
links.docs entries as in the build output), then ensure validation passes by
installing or adding the missing ajv dependency (so npm run validate can import
ajv without ERR_MODULE_NOT_FOUND), rerun npm run validate to confirm the schema
passes, and commit the regenerated registry.json and any
package.json/package-lock.json changes; look for the registry.json object with
slug "valoperstestnet" to verify the entry was updated.

@danbaruka danbaruka requested review from Yannick243 and mbagalwa June 13, 2026 19:02
@danbaruka danbaruka added documentation Improvements or additions to documentation good first issue Good for newcomers labels Jun 13, 2026
@danbaruka danbaruka merged commit 93b6bc6 into Safrochain-Org:main Jun 13, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation good first issue Good for newcomers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants