Authentication & Signature Verification

All Firetip REST requests must be authenticated using the SC01 Signature Header. This signature binds each request to your hardware identity and prevents spoofing, replay attacks, and unauthorized routing.

Header Format

X-SC01-Signature: <sha256_hmac>

Signature Algorithm

HMAC_SHA256(secret_key, timestamp + method + endpoint + body)

Required Fields

• Timestamp (UNIX)
• HTTP Method
• Endpoint Path
• Raw JSON Body

Example Payload

{
  "timestamp": 1719920041,
  "signature": "a8f2c9e1..."
}

See also: SDK Signature Examples

Error Codes & Diagnostic Responses

Firetip uses a structured error model designed for automated recovery, cluster triage, and sovereign‑priority routing.

See also: Cluster Control API

Webhook Event Catalog

Firetip emits real‑time webhook events for delivery, verification, and identity‑bound telemetry.

Event Types

• DELIVERED: Message accepted by remote MTA.
• OPEN: Pixel‑verified open event.
• CLICK: Link interaction event.
• OTP_VERIFIED: OTP successfully validated.
• BOUNCE_HARD: Permanent delivery failure.
• BOUNCE_SOFT: Temporary delivery failure.

Example Webhook Payload

{
  "event": "OPEN",
  "message_id": "MSG-9912",
  "timestamp": 1719921123,
  "user_agent": "Mozilla/5.0",
  "ip": "82.21.44.19"
}

See also: Verification Listener

Message Object Schema

All Firetip dispatch operations use a unified message schema for email, SMS, and OTP workloads.

{
  "message_id": "MSG-4421",
  "type": "email | sms | otp",
  "to": "user@example.com",
  "subject": "optional",
  "html": "optional",
  "text": "optional",
  "status": "QUEUED | SENT | DELIVERED | OPEN | FAILED",
  "timestamp": 1719920041,
  "metadata": {
    "campaign_id": "CMP-8842",
    "sc01_node": "SC01-442",
    "priority": "standard | sovereign"
  }
}

See also: Dispatch API

Rate Limits & Throughput Profiles

Firetip uses dynamic throughput scaling based on domain authority, sc01 warmup state, and cluster load.

• Warmup Mode: 50–500 msgs/min
• Standard Mode: 5,000–20,000 msgs/min
• Sovereign Priority: 50,000+ msgs/min
• External SMTP Mode: Provider‑limited (Gmail, Hotmail, Yahoo)

See also: Delivery Pipeline

SC01 Hardware Identity Specification

The SC01 node is the cryptographic anchor for all Firetip routing, identity validation, and sovereign authority enforcement.

Core Attributes

• Hardware‑bound identity: Non‑spoofable routing signature.
• Reputation isolation: Each domain maintains its own authority profile.
• Zero shared‑cloud exposure: No cross‑tenant contamination.
• Real‑time telemetry: Millisecond‑accurate event reporting.

See also: Architecture Overview

SMTP Bridge Documentation

The Firetip SMTP Bridge provides a direct SMTP interface for sending email through the sc01 hardware identity layer. It is designed for platforms that require traditional SMTP compatibility while retaining sovereign routing, deterministic delivery, and Firetip’s Triple‑Auth authority model.

Overview

The SMTP Bridge acts as a translation layer between legacy SMTP clients and Firetip’s sovereign dispatch engine. Incoming SMTP commands are validated, cryptographically signed, and routed through the sc01 node before entering the Firetip delivery pipeline.

• Protocol: SMTP (RFC 5321 compliant)
• Transport: TLS 1.2+ required
• Identity Binding: SC01 hardware signature
• Authority Model: Triple‑Auth (SPF + DKIM + DMARC)
• Compatibility: Any SMTP client or MTA

Connection Details

SMTP Host: smtp.firetip.pro
Port (TLS): 587
Port (SSL): 465
Auth Method: LOGIN / PLAIN
Username: <your_firetip_username>
Password: <sc01_signature_token>

The password is not a static credential — it is a rotating SC01 signature token bound to your hardware identity.

Required Headers

Firetip requires specific headers to ensure sovereign routing and identity validation.

• X-SC01-Signature: Hardware-bound HMAC signature
• X-Firetip-Node: SC01 node identifier
• X-Firetip-Route: Routing path (primary / fallback / sovereign)
• X-Firetip-Priority: standard / high / sovereign

SMTP Envelope Requirements

MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
DATA
Subject: Example Email
X-SC01-Signature: <signature>
X-Firetip-Node: SC01-442
X-Firetip-Route: primary
X-Firetip-Priority: standard

Hello from Firetip.
.

Native vs External Relay Modes

Example SMTP Session

220 smtp.firetip.pro ESMTP Firetip-Bridge
EHLO example.com
250-smtp.firetip.pro
250-AUTH LOGIN PLAIN
250 STARTTLS

AUTH LOGIN
334 VXNlcm5hbWU6
<base64_username>
334 UGFzc3dvcmQ6
<base64_sc01_signature>
235 Authentication successful

MAIL FROM:<sender@example.com>
250 OK

RCPT TO:<recipient@example.com>
250 Accepted

DATA
354 End data with <CR><LF>.<CR><LF>

Subject: Firetip SMTP Test
X-SC01-Signature: a8f2c9e1...
X-Firetip-Node: SC01-442
X-Firetip-Route: primary

Hello from Firetip SMTP Bridge.
.
250 Message queued for delivery

Security Model

• TLS enforced: No plaintext SMTP allowed.
• Hardware-bound identity: SC01 signature required.
• Replay protection: Timestamped HMAC tokens.
• Header integrity: All Firetip headers validated.

Throughput Profiles

• Warmup: 50–500 msgs/min
• Standard: 5,000–20,000 msgs/min
• Sovereign Priority: 50,000+ msgs/min
• External SMTP: Provider-limited

Troubleshooting

• 535 AUTH FAILED: Invalid SC01 signature token.
• 550 DOMAIN NOT PROVISIONED: Use Domain Bridge API first.
• 451 TEMPORARY FAILURE: Node sync or cluster warmup.
• 421 RATE LIMITED: External SMTP provider throttling.

See also: Domain Bridge API · Delivery Pipeline · Verification Listener

Firetip Campaign Engine Documentation

The Firetip Campaign Engine is a high‑volume, hardware‑accelerated dispatch system designed for sovereign‑grade email, SMS, and hybrid message campaigns. It operates on top of the sc01 identity layer, ensuring deterministic routing, isolated domain authority, and real‑time telemetry.

Architecture Overview

The Campaign Engine is built on a three‑layer architecture:

• Ingestion Layer: Accepts campaign payloads via REST or Streaming API.
• Queue Shaping Layer: Applies priority, warmup rules, and sovereign routing logic.
• Dispatch Layer: Executes high‑velocity delivery through sc01 hardware.

Campaign Payload Structure

{
  "campaign_id": "CMP-4421",
  "batch": [
    { "to": "user1@example.com", "subject": "Hello", "html": "
Hi
" },
    { "to": "user2@example.com", "subject": "Hello", "html": "
Hi
" }
  ],
  "priority": "standard | high | sovereign",
  "metadata": {
    "sc01_node": "SC01-442",
    "warmup": false
  }
}

Execution Modes

• Standard Delivery: Balanced throughput with adaptive queue shaping.
• High‑Velocity Blast: Maximum throughput; bypasses shaping rules.
• Sovereign Priority: Reserved for domains with full Triple‑Auth authority.

Streaming Dispatch

Channel: /stream/v1/dispatch/execute
Protocol: WebSockets / SSE

Streaming mode is recommended for campaigns exceeding 10,000 messages.

Real‑Time Telemetry

• Queue depth
• Node load
• Delivery rate
• Open & click events
• Warmup progression

Error Handling

• ERR_503_SYNC: Node synchronization in progress.
• ERR_429_LIMIT: External SMTP provider throttle.
• ERR_007_GSM: GSM carrier rejection.