Placement

Operational
def:opusPlatform familyMaturity: builtOrchestration & Placement
Explorer
def:opus

Decides where work runs

Matches work to the machines best placed to do it, by where they are and what they offer.

Every node runs it

Depends on

No other modules: it stands on its own.

7
Nodes
7 of 7 active last epoch
2
Metros
2 nodes not grouped yet
0GRID
Bonded stake
No bond taken
None
Min stake
Every node runs it
None
Unbonding period
Leave at any time
OverviewNodes 7RegionsHistoryDetails

Nodes in this module

7
NodeMetroStandingParticipationAnswers checksStake hereScore
volatile-digital-central-labelMetro · North AmericaOperationalActiveClear—55.3
proactive-computed-floor-sensorMetro · North AmericaOperationalActiveClear—51.3
immutable-interactive-calm-routineMetro · North AmericaOperationalActiveClear—51.2
parallel-genius-bordered-lighthouseMetro · North AmericaOperationalActiveClear—51.1
multiplexed-simulated-peak-navigatorMetro · AsiaOperationalActiveClear—48.9
optimized-storm-tunnel-scannerMetro · EuropeOperationalActiveClear—46.6
stored-rocket-hamlet-satelliteMetro · EuropeOperationalActiveConfirmed unresponsive—0.0

Capacity

Last closed epoch

This module does not report capacity.

Changes

Epochs 2,341–2,358

Nothing changed

Its verdict did not change in epochs 2,341–2,358.

Built on by

0

No other module depends on it.

More in Platform

  • def:msgMessaging
  • def:paasPackages
  • def:paas/mirrorRegistry mirror
  • def:paas/vuln-scanVulnerability scan
  • def:triggerScheduled actions