Audit validator deployment conflicts API
Compare a caller-supplied validator deployment inventory for duplicate active public keys, simultaneous primary and backup activation, overlapping activation windows, and failover rules that disagree. Windows are absolute instants, including offsets. An inactive standby covered by an exclusive failover rule is not treated as concurrent. audit_status is clean, conflicts_detected, warnings, or incomplete. risk_level is low, medium, high, or critical. Activation status is an assertion. No host is contacted and no private key is read.
The Audit validator deployment conflicts operation is part of the Validator Slashing Protection API on BRAINIAC.software. Compare a caller-supplied validator deployment inventory for duplicate active public keys, simultaneous primary and backup activation, overlapping activation windows, and failover rules that disagree. Windows are absolute instants, including offsets. An inactive standby covered by an exclusive failover rule is not treated as concurrent. audit_status is clean, conflicts_detected, warnings, or incomplete. risk_level is low, medium, high, or critical. Activation status is an assertion. No host is contacted and no private key is read. It is exposed as POST /api/v1/staking-security/validator-key-deployment-conflict-audit and priced at $0.05 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied EIP-3076 slashing protection interchanges processed locally Caller-supplied validator deployment inventories processed locally Caller-supplied validator withdrawal credentials processed locally Limitations: An export is not a complete signing history and does not protect against a later signature. Confirmed conflicts use the phase 0 proposer and Casper FFG attester conditions on the supplied records. Records without signing_root are not treated as a confirmed slash when the slot or epochs match. No beacon node is queried, no signature is verified, and private keys are not accepted. Deployment activation is a caller-supplied assertion. It does not show that a validator process is running or stopped. An inactive standby covered by an exclusive failover rule is not reported as a concurrent deployment. Withdrawal credentials are decoded only for prefixes 0x00, 0x01, and 0x02. An execution address is reported only when the 11-byte padding is zero. A matching withdrawal address is not proof of control, and the credentials were not read from a beacon node. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Audit validator slashing protection, Audit validator withdrawal credentials. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/staking-security/validator-key-deployment-conflict-auditExample request
curl -i -X POST "https://www.brainiac.software/api/v1/staking-security/validator-key-deployment-conflict-audit" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"deployments": [
{
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"environment": "prod-a",
"node": "cluster-a",
"role": "primary",
"activation": "active",
"owner": "ops",
"activationWindow": {
"start": "2026-01-01T00:00:00Z",
"end": "2026-01-02T00:00:00Z"
}
},
{
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"environment": "prod-b",
"node": "cluster-b",
"role": "backup",
"activation": "active",
"activationWindow": {
"start": "2026-01-01T12:00:00+00:00",
"end": "2026-01-01T20:00:00+01:00"
}
}
],
"maintenanceWindows": [
{
"environment": "prod-a",
"start": "2026-02-01T00:00:00Z",
"end": "2026-02-01T01:00:00Z"
}
],
"failoverRules": [
{
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"environments": [
"prod-a",
"prod-b"
],
"exclusive": true
}
],
"expectedTopology": [
{
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"environment": "prod-a",
"node": "cluster-a",
"role": "primary",
"activation": "active"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Audit validator slashing protection — $0.05 USDC
- Audit validator withdrawal credentials — $0.05 USDC