d-bis/explorer-monorepo
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename SolaceScanScout to Solace and update related configurations

Browse Source 
- Updated branding from "SolaceScanScout" to "Solace" across various files including deployment scripts, API responses, and documentation.
- Changed default base URL for Playwright tests and updated security headers to reflect the new branding.
- Enhanced README and API documentation to include new authentication endpoints and product access details.

This refactor aligns the project branding and improves clarity in the API documentation.
This commit is contained in:
defiQUG
2026-04-10 12:52:17 -07:00
parent bdae5a9f6e
commit f46bd213ba
160 changed files with 13274 additions and 1061 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/CHANGELOG.md
View File

@@ -1,4 +1,4 @@
# Changelog — SolaceScanScout Explorer
# Changelog — SolaceScan Explorer
All notable frontend and docs changes are listed here.

5
docs/ERROR_REPORT_AND_FIXES.md
View File

@@ -300,7 +300,7 @@ Once the backend is running:
### Backend Logs
The backend uses Go's standard `log` package. Logs will show:
- Server startup: `Starting SolaceScanScout REST API server on :8080`
- Server startup: `Starting SolaceScan REST API server on :8080`
- Request logs: `GET /api/v2/stats 200 2.5ms`
- Errors: Database connection errors, query failures, etc.
@@ -330,7 +330,7 @@ Expected response:
},
"chain_id": 138,
"explorer": {
"name": "SolaceScanScout",
"name": "SolaceScan",
"version": "1.0.0"
}
}
@@ -359,4 +359,3 @@ Expected response:
---
**Next Steps**: Start the backend server and re-run the diagnostic script to verify all issues are resolved.

2
docs/EXPLORER_ADDITIONAL_RECOMMENDATIONS.md
View File

@@ -1,4 +1,4 @@
# SolaceScanScout — Additional Recommendations
# SolaceScan — Additional Recommendations
This document lists **further improvements** beyond the upgrades already implemented (Tier 1–3 frontend, API docs, watchlist, labels, i18n, etc.). Items are grouped by effort and dependency (frontend-only vs backend).

10
docs/EXPLORER_API_REFERENCE.md
View File

@@ -1,11 +1,11 @@
# SolaceScanScout Explorer — API Reference
# SolaceScan Explorer — API Reference
The SolaceScanScout frontend uses the **Blockscout v2 API** for chain data. When the explorer is served from the same origin (e.g. `https://explorer.d-bis.org` or VM IP), requests go to `/api` and are proxied to Blockscout (port 4000). This document lists the endpoints used by the frontend.
The SolaceScan frontend uses the **Blockscout v2 API** for chain data. When the explorer is served from the same origin (e.g. `https://blockscout.defi-oracle.io` or VM IP), requests go to `/api` and are proxied to Blockscout (port 4000). This document lists the endpoints used by the frontend.
## Base URL
- **Same-origin:** `window.location.origin + '/api'` (e.g. `https://explorer.d-bis.org/api`)
- **Fallback:** `https://explorer.d-bis.org/api`
- **Same-origin:** `window.location.origin + '/api'` (e.g. `https://blockscout.defi-oracle.io/api`)
- **Fallback:** `https://blockscout.defi-oracle.io/api`
All paths below are relative to this base (e.g. `/v2/stats` → `{base}/v2/stats`).
@@ -81,7 +81,7 @@ The frontend does not send API keys. Rate limits are determined by the Blockscou
## OpenAPI / Swagger
If your Blockscout instance exposes an OpenAPI (Swagger) spec, it is often at `{base}/api-docs` or `{base}/swagger`. Document that URL for your deployment (e.g. `https://explorer.d-bis.org/api-docs` if enabled).
If your Blockscout instance exposes an OpenAPI (Swagger) spec, it is often at `{base}/api-docs` or `{base}/swagger`. Document that URL for your deployment (e.g. `https://blockscout.defi-oracle.io/api-docs` if enabled).
## Recent changes

2
docs/FINAL_DEPLOYMENT_REPORT.md
View File

@@ -5,7 +5,7 @@
## Executive Summary
The SolaceScanScout tiered architecture has been successfully deployed and tested. The API server is running and all core functionality is operational.
The SolaceScan tiered architecture has been successfully deployed and tested. The API server is running and all core functionality is operational.
## Deployment Status

16
docs/METAMASK_AND_PROVIDER_INTEGRATION.md
View File

@@ -1,13 +1,13 @@
# MetaMask and Dual-Chain Provider Integration
The explorer (SolaceScanScout) provides add-to-MetaMask and token list discovery for **Chain 138** (DeFi Oracle Meta Mainnet), **Ethereum Mainnet**, and **ALL Mainnet** (651940).
The explorer (SolaceScan) provides add-to-MetaMask and token list discovery for **Chain 138** (DeFi Oracle Meta Mainnet), **Ethereum Mainnet**, and **ALL Mainnet** (651940).
## Explorer as discovery source
- **Add to MetaMask:** Use the [Wallet](/wallet) page to add Chain 138, Ethereum Mainnet, or ALL Mainnet to your wallet via `wallet_addEthereumChain`.
- **Token list URL:** The explorer API serves the dual-chain token list at:
- **Path:** `/api/config/token-list`
- **Full URL:** `{EXPLORER_API_BASE}/api/config/token-list` (e.g. `https://explorer.d-bis.org/api/config/token-list` if the API is on the same origin).
- **Full URL:** `{EXPLORER_API_BASE}/api/config/token-list` (e.g. `https://blockscout.defi-oracle.io/api/config/token-list` if the API is on the same origin).
Add this URL in MetaMask **Settings → Token lists** so tokens for Chain 138 and Mainnet appear automatically.
As of April 3, 2026, the public explorer token list exposes `190` entries, including the full Mainnet `cW*` suite.
- **Networks config:** `/api/config/networks` returns the same chain params (Chain 138 + Ethereum Mainnet) in JSON for programmatic use.
@@ -29,13 +29,13 @@ Discovery is via **token list** (hosted at the explorer token list URL above), *
- **Custom MetaMask Snap:** For in-wallet swap quotes, bridge routes, and pricing on Chain 138, see [SNAP_IMPLEMENTATION_ROADMAP.md](../../docs/04-configuration/metamask/SNAP_IMPLEMENTATION_ROADMAP.md).
- **Feature parity and optional actions:** [METAMASK_CHAIN138_FEATURE_PARITY_ANALYSIS.md](../../docs/04-configuration/metamask/METAMASK_CHAIN138_FEATURE_PARITY_ANALYSIS.md) — Section 7 lists optional next steps (Snap, CoinGecko, Consensys outreach, market data API).
## Live explorer (https://explorer.d-bis.org)
## Live explorer (https://blockscout.defi-oracle.io)
- **Wallet page:** https://explorer.d-bis.org/wallet
- **Token list URL:** https://explorer.d-bis.org/api/config/token-list
- **Networks config:** https://explorer.d-bis.org/api/config/networks
- **GRU v2 public rollout status:** https://explorer.d-bis.org/config/GRU_V2_PUBLIC_DEPLOYMENT_STATUS.json
- **GRU v2 deployment queue:** https://explorer.d-bis.org/config/GRU_V2_DEPLOYMENT_QUEUE.json
- **Wallet page:** https://blockscout.defi-oracle.io/wallet
- **Token list URL:** https://blockscout.defi-oracle.io/api/config/token-list
- **Networks config:** https://blockscout.defi-oracle.io/api/config/networks
- **GRU v2 public rollout status:** https://blockscout.defi-oracle.io/config/GRU_V2_PUBLIC_DEPLOYMENT_STATUS.json
- **GRU v2 deployment queue:** https://blockscout.defi-oracle.io/config/GRU_V2_DEPLOYMENT_QUEUE.json
For backend deployment and integration tests, see [EXPLORER_D_BIS_ORG_INTEGRATION.md](../../docs/04-configuration/metamask/EXPLORER_D_BIS_ORG_INTEGRATION.md).
For token-list publishing, use `explorer-monorepo/scripts/deploy-explorer-config-to-vmid5000.sh`; it now falls back through the Proxmox host automatically when local `pct` is not installed.

4
docs/README.md
View File

@@ -1,6 +1,6 @@
# Explorer Monorepo – Documentation
Overview of documentation for the ChainID 138 Explorer (SolaceScanScout).
Overview of documentation for the ChainID 138 Explorer (SolaceScan).
---
@@ -9,7 +9,7 @@ Overview of documentation for the ChainID 138 Explorer (SolaceScanScout).
| Doc | Description |
|-----|-------------|
| **[INDEX.md](./INDEX.md)** | Full documentation index (bridge, setup, verification, operations) |
| **[EXPLORER_API_ACCESS.md](./EXPLORER_API_ACCESS.md)** | API access, 502 fix, CSP, frontend deploy for https://explorer.d-bis.org |
| **[EXPLORER_API_ACCESS.md](./EXPLORER_API_ACCESS.md)** | API access, 502 fix, CSP, frontend deploy for https://blockscout.defi-oracle.io |
| **[../README.md](../README.md)** | Project README: quick start, frontend, architecture, config |
---

2
docs/TIERED_ARCHITECTURE_IMPLEMENTATION.md
View File

@@ -2,7 +2,7 @@
## Overview
The SolaceScanScout Explorer has been successfully upgraded to a 4-track tiered architecture with feature-gated access control.
The SolaceScan Explorer has been successfully upgraded to a 4-track tiered architecture with feature-gated access control.
## Implementation Status: ✅ COMPLETE

2
docs/TIERED_ARCHITECTURE_SETUP.md
View File

@@ -1,6 +1,6 @@
# Tiered Architecture Setup Guide
Complete setup and integration guide for SolaceScanScout tiered architecture.
Complete setup and integration guide for SolaceScan tiered architecture.
## Quick Start

11
docs/api/openapi.yaml
View File

@@ -1,21 +1,21 @@
openapi: 3.0.0
info:
title: SolaceScanScout API
title: SolaceScan API
version: 1.0.0
description: |
SolaceScanScout - The Defi Oracle Meta Explorer API
SolaceScan API for the Chain 138 explorer surface
Comprehensive blockchain explorer API for ChainID 138 with cross-chain bridge monitoring,
WETH utilities, and real-time transaction tracking.
contact:
name: SolaceScanScout Support
url: https://explorer.d-bis.org
name: SolaceScan Support
url: https://blockscout.defi-oracle.io
license:
name: MIT
url: https://opensource.org/licenses/MIT
servers:
- url: https://explorer.d-bis.org/api
- url: https://blockscout.defi-oracle.io/api
description: Production server
- url: http://localhost:8080/api
description: Local development server
@@ -307,4 +307,3 @@ components:
security:
- ApiKeyAuth: []

3
docs/api/track-api-contracts.md
View File

@@ -1,6 +1,6 @@
# Track API Contracts
Complete API contract definitions for all 4 tracks of SolaceScanScout Explorer.
Complete API contract definitions for all 4 tracks of SolaceScan Explorer.
## Track 1: Public Meta Explorer (No Auth Required)
@@ -778,4 +778,3 @@ Paginated endpoints use consistent pagination:
}
}
```

3
docs/feature-flags/track-feature-matrix.md
View File

@@ -1,6 +1,6 @@
# Track Feature Matrix
Feature flag mapping for SolaceScanScout Explorer tiered architecture.
Feature flag mapping for SolaceScan Explorer tiered architecture.
## Overview
@@ -278,4 +278,3 @@ Get available features for current user.
"permissions": [...]
}
```