Skip to content
Client Focus

Run

Client Focus operates the infrastructure that digital asset services depend on. The Digital Asset NOC monitors node health, validator performance, RPC latency and integration status continuously, and manages incidents, problems and changes under ITIL practice.

Node, validator, RPC and integration health, 24/7/365
ITIL-based incident, problem and change management
Availability held to the published standard in the client's service agreement

One process from monitoring to change

Node, validator, RPC and integration health are managed under one ITIL-based process, measured against published targets.

Run operating cycleMonitoring, detection, incident, problem and change management under one ITIL-based process.ContinuousMonitor

Node, validator, RPC and integration health

EventDetect

Alerts measured against published targets

ResponseIncident

ITIL incident management to restoration

ReviewProblem

Root cause and prevention

ControlChange

Approved change with a rollback position

Targets

Network operations are held to the targets set out in the client's service agreement.

The Digital Asset NOC

The practice is delivered through the Digital Asset NOC, a named Client Focus solution.

Digital Asset NOC

The Digital Asset NOC holds availability to a published standard, with ITIL-based incident, problem and change management.

What the practice delivers

Monitoring, managed operations and the control work that supervisors expect to see evidenced.

Cloud and infrastructure management

Capacity planning, patching, backup and failover across IBM, Microsoft Azure, Oracle and Amazon Web Services estates.

Technology risk controls

Encryption, access management, fraud detection and control frameworks including PCI DSS, FFIEC, GDPR, ISO 27001 and NIST CSF, applied to chain and banking systems alike.

Regulatory readiness

Operational evidence, reporting and resilience testing aligned to the GENIUS Act, MiCA and DORA expectations.

Global support services

Support delivered 24/7/365 across Ashburn and Hyderabad, with documented handover at every shift boundary.

How coverage is staffed and escalated

Three shifts

Three shifts cover the day with deliberate overlap, so handover happens with both teams present.

Escalation from L1 to L4

Watch Officer, senior analyst, incident manager and operations lead, each with a defined responsibility and a named individual on duty.

Published notification clock

Notification within 10 minutes of detection; client acknowledgment within 15 minutes (targets stated in the client's service agreement).

Where automation narrows the queue

Automated analysis reduces noise. The decision to escalate remains with the officer on duty.

  • Anomaly detection on node and RPC telemetry, surfaced before static thresholds are breached.
  • Alert grouping, so one infrastructure fault produces one ticket rather than many.
  • Change risk scoring on release plans, reviewed by the change owner before approval.
  • Forecasting of node resource exhaustion, validator performance drift and RPC saturation, so capacity work is scheduled before an outage.

Engaged on its own or combined

Each practice can be engaged on its own. Most clients combine them, because the operational risk of a digital asset service does not divide neatly between engineering and security.

Continue reading

Regulatory readiness reference

DORA, MiCA, the GENIUS Act and US bank supervision, mapped to operational obligations and evidence.

Secure

Security across the lifecycle: assessments, contract assurance, 24/7 security operations through C'ROC and incident response.

Build

Chain engineering, integration and contract work planned around the operating model that supports it.

Support

Support channels for existing clients, including instructions for reporting an active incident.

Put your infrastructure under management.

Discuss node, validator and RPC coverage under published service levels. Every request is reviewed by a principal of the firm.