MetaYoshi Raptoreum Infrastructure Server Control Surface

MetaYoshi Application Homepage

Unified web surface for wallet bridge operations, chain monitoring, and documentation. This deployment keeps daemon RPC private and exposes only controlled routes.

Bridge endpoint: /v1/bridge through HTTPS domain.

Homepage route: Root path / proxies to homepage service.

Application Scope

Browser wallet extension for Raptoreum (RTM) with bridge-first architecture.
Asset and coin transfer support through allowlisted method groups.
dApp integration with permissions, approvals, and anti-replay controls.
Operational routing through one domain for web and API surfaces.

Core Features

Encrypted HD vault lifecycle: create, import, lock, unlock.
Bridge-authenticated JSON-RPC forwarding for mainnet and testnet.
Node discovery, sync watchdog, and diagnostics export.
Rate limiting, write caps, TX key gate, and emergency write kill switch.

Security Model

Daemon RPC stays local/private; clients consume only bridge routes.
Bridge uses Basic Auth and optional TX authorization key.
Origin and extension allowlisting are supported by API policy.
CORS restrictions and method allowlists reduce attack surface.

Connector Scopes

External connector scopes isolate permission boundaries: read, sign, send_rtm, send_asset.

Requests include schema versioning and anti-replay envelope with nonce and timestamp.

Operational Endpoints

Endpoint	Auth	Purpose
`/health`	None	API liveness, watchdog state, and guard telemetry.
`/v1/status`	`X-API-Key`	Chain + wallet status summary for admin and monitoring.
`/v1/bridge`	Basic Auth	Primary JSON-RPC bridge endpoint consumed by extension.
`/v1/bridge/methods`	Basic Auth	Expose active allowlisted method groups by coin.
`/v1/bridge/nodes`	Basic Auth	Read discovered SmartNode list and routing hints.

Domain routing: / and /api/* serve the homepage service, while /health and /v1/* are routed to the bridge API service.