Operation_Identity

Core Infrastructure Setup

To enable high-velocity relaying, you must authorize the Firetip Native DNS records. Alternatively, you can configure a Custom Relay to route your traffic through external gateways such as Gmail, Hotmail, or Yahoo via the proprietary sc01 hardware cluster.

SYSTEM_INITIALIZATION

Deployment Paths

Choose your relay method to initialize the sc01 hardware.

PATH 01 - NATIVE GATEWAY

Firetip Native DNS

Required: Configure your SPF, DKIM, and DMARC. This activates the Triple-Auth Pass, allowing the sc01-Node cluster to blast with maximum authority.

Triple-Auth Handshake
SPF DKIM DMARC

HIGHER_DELIVERY_RATE_ENABLED

PATH 02 - CUSTOM RELAY

External Bypass

Skip DNS: Use your Gmail, Hotmail, or Yahoo. The sc01-Node acts as a high-speed tunnel, bypassing Native DNS requirements.

SYSTEM LIMITS & RESTRICTIONS
  • Subject to provider daily caps (e.g. Gmail 500-2k/day).
  • Throttling and abuse handled by the external provider.
FINAL STEP

Ignite Firetip

The Triple-Auth Pass guarantees a Higher Delivery Rate. Once configured, Firetip silicon takes over for 100% throughput.

HARDWARE ACCELERATION ACTIVE TRIPLE AUTH PASSED
sc01 Native Bridge

Authorized sCloud bypass. Pre-configured for mass-scale dispatching with zero-config SMTP overhead.

AUTH: REPUTATION_LOCKED
Custom SMTP Relay

Dedicated hardware tunneling. Maintain full header authority and X-Mailer signature control.

AUTH: EXTERNAL_TUNNEL
sc01 - IDENTITY V3 CONTROL
Firetip Identity Setup
STEP_01

Handshake Protocol

Automatic AUTH CRAM MD5 negotiation ensures your node is live before deployment.

STEP 02

Header Masking

Inject custom signatures to mask the sc01 relay footprint. Effectively bypasses enterprise-grade SPAM filters.

Node_Advisory

"Synchronizing DNS SPF/DKIM with the SC01 IP block is mandatory for 99.9% delivery rates."

01

Initialize

Trigger SMTP Handshake via Aura Hub.

02

Signate

Apply custom X-Mailer spoofing headers.

03

Authorize

Confirm sc01-Node readiness for broadcast.

NETWORK_PROTOCOL

Direct SMS Broadcasting

Execute global SMS dispatch via the sCloud Private Gateway. By bypassing traditional web aggregators, your traffic routes directly through the sc01-Node hardware stack.

Dashboard
HTTPS_AES256
sc01_Node
GSM/LTE_RELAY
Cell_Tower
Instant Dispatch

Low-latency burst technology. Messages are injected into the carrier radio tower within 10s of dispatch from the node.

Tower-Level Verification

Real-time "Delivered" status is pulled directly from the sc01 cellular logs, bypassing typical API lag.

INFRASTRUCTURE_SPEC

Tier Capabilities

Resource Cluster Standard Entry Firetip Premium [SC01]
Email Output
Hourly SMTP Throughput
 50 / hr 5,000 / HR
SMS Dispatch
Global Cellular Relay
 10 / day UNLIMITED*
OTP Allowance
Secure Auth Delivery
 50 / day 500+ / DAY
API
Infrastructure Layer
 Unlimited
Unlimited
SC01_OTP_RELAY_STATUS Ready for Dispatch

*High-priority delivery. Pro users utilize sc01 dedicated radio towers for mission-critical SMS/OTP verification.

DEVELOPER_API_v2.0

Broadcast Engine

PROTOCOL: HTTPS/JSON
POST https://firetip.pro/api/v2/broadcast

The Broadcast endpoint triggers a multi-vector dispatch. When channel: "dual" is specified, the sc01-Node synchronizes SMTP and GSM relays for near-instant delivery. 

					{
					"api_key": "YOUR_AURA_KEY",
					"uid": "",
					"channel": "dual",
					"email": {
					"subject": "Critical Node Alert",
					"body": "Relay sc01 status verified."
					},
					"sms": {
					"body": "sc01 Alert: Uplink Active."
					}
					}
channel Values: email, sms, or dual.
api_key Your unique infrastructure access token.
uid Dispatcher ID for log attribution.
SECURITY_PROTOCOL_v3

OTP / 2FA Verification

Deploy the sc01 hardware relay for high-entropy password delivery. Firetip generates the secure token and handles the radio injection; you simply verify the handshake.

POST /api/v1/otp/generate
API_Payload_Request
							{
							"api_key": "YOUR_AURA_KEY",
							"recipient": "+447700900123",
							"app_name": "Firetip_Secure"
							}
SC01_Relay_Response
							{
							"status": "relayed",
							"otp_code": "882914",
							"node": "sc01_v3"
							}
Node_Status Ready for Dispatch
Logic_Implementation_Guide
1. PERSIST THE SECRET

When the sc01 node returns the otp_code, save it immediately to your Server Session. This ensures the code never lives in a public database.

2. VALIDATE THE INPUT

The user inputs the code they received via SMS. Compare their input against your $_SESSION variable. Match = Authenticated.

Auth_Controller.php 
					// Capture the sc01 response
					$otp = $firetip->generateOTP("+447700900123");
					$_SESSION['vault_auth'] = $otp['otp_code'];

					// Compare on POST request
					if ($_POST['input_code'] === $_SESSION['vault_auth']) {
					return access_granted(); // Handshake Verified
					}

SMS Gateway

{
  "auth_key": "YOUR_SCLOUD_KEY",
  "phone": "+447700900123",
  "body": "Radio Dispatch via sc01."
}
TOWER_LINK: READY
sc01_NODE: PROCESSING
INFRASTRUCTURE_ACCESS_KEY
ACTIVE
Treat this key as a password. It grants direct access to your **sc01 node** relay. 
curl -X POST https://firetip.pro/api/v1/sms/send \
  -H "X-Firetip-Key: " \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+447700900000",
    "message": "Security Alert: New login detected on your sCloud account."
  }'
EXTERNAL_WEBHOOK_ENDPOINT

Connect any external website or landing page to your Firetip engine. Use this endpoint to inject leads directly into your sc01-Node for immediate auto-responder dispatch.

POST
JSON_RESPONSE
CORS_ENABLED
SSL_SECURED
Payload Structure
					{
					"email": "user@example.com",
					"fname": "John",
					"source": "Landing_Page_A"
					}

Fields are automatically mapped to your Firetip Audience Vault.

PROTOCOL_SPECS

Relay Signature Headers

When the sc01-Node relays an email or SMS, it injects specific metadata headers. Use these to track hardware-level delivery paths or to bypass internal filters.

Header_Key Description Typical_Value
X-Firetip-Node Identifies the hardware cluster origin. sc01-v3-cluster
X-Relay-Latency Handshake time between sc01 and Tower. 142ms
X-Dispatcher-ID Your unique system UID for log tracking.
INFRASTRUCTURE

Hardware Backbone

sCloud sc01 Node

Firetip is powered exclusively by sCloud sc01 nodes. High-performance hardware using Ryzen architecture to ensure maximum delivery speed for over 1 million users.

PROPRIETARY_SILICON
REPUTATION_ENGINE

IP Warmup Protocol

To maintain the 99.9% delivery rate of emails, new accounts must follow the automated warmup sequence. Firetip handles this logic internally, but understanding the throttling is key for planning large campaigns.

WEEK_01
Throttled: 500/day
WEEK_02
Moderate: 2,500/day
WEEK_03+
Unrestricted: 5,000+/hr

Throttle Control

Don't burn your reputation. Firetip's Adaptive Pulse technology automatically spreads your campaign across the Firetip network to mimic human sending patterns.

99.9%
Inbox_Delivery_Rate

Aura Test Environment

Before deploying to the main sCloud sc01 cluster, use the Aura Sandbox to validate your headers and DNS signatures. This ensures your Custom Relay (Gmail/Yahoo) is properly authenticated.

SYSTEM_DIAGNOSTICS

Handshake Error Codes

CODE IDENTIFIER RESOLUTION
ERR_401_AUTH NODE_REJECTED_KEY Your API Key is invalid or has been regenerated. Update your headers.
ERR_429_LIMIT THROTTLE_ENGAGED You have exceeded your hourly tier limit. Upgrade to Premium sc01 access.
ERR_503_SYNC NODE_OFFLINE The sc01 hardware is undergoing a sync cycle. Retry in 60 seconds.
ERR_007_GSM RADIO_FAILURE The SIM relay failed to handshake with the tower. Check recipient number format.
DATA_MANAGEMENT

Audience Hub

Vault Segmentation

Every lead injected via the External Webhook is assigned a List_ID. Use these IDs to trigger automated follow-up sequences via the sc01 relay.

Pixel Tracking & IP Logic

Firetip injects a 1x1 transparent tracking pixel into every payload. When the recipient opens the mail, the sc01 node logs the IP, User-Agent, and Timestamp.

NOTE: For Gmail/G-Suite recipients, Google utilizes a Proxy Image Cache. The sc01 node will record the Google Proxy IP rather than the recipient's local IP to protect end-user privacy.

NETWORK_INTEGRITY

Compliance & Abuse

To maintain the elite deliverability of the sc01-Nodes, all Firetip traffic must adhere to global anti-spam and privacy standards.

GDPR Ready

Firetip and sCloud are built with privacy by design. We provide automated Unsubscribe Headers and data-erasure tools to ensure your campaigns are fully compliant with EU GDPR and California CCPA regulations.

Abuse Policy

We operate a Zero-Tolerance policy for phishing, malware, or non-permission-based marketing. The sc01-Node cluster monitors bounce rates and spam reports in real-time. Accounts exceeding 1.5% spam threshold are auto-suspended.

CAN-SPAM Requirements:
  • Must include a valid physical postal address in every footer.
  • Deceptive subject lines or "From" headers are strictly prohibited.
  • One-click unsubscribe links must remain active for 30 days post-campaign.
DATA_RELAY

Event Webhooks

Firetip can push real time event data to your external endpoint. Every time an email is Verified or Opened, Firetip sends a JSON payload to your listener.

EXAMPLE PAYLOAD
{ "event": "open", "node": "sc01-firetip", "ip": "masked", "timestamp": "1714986000" }
SYSTEM_DIAGNOSTICS

Protocol Status Codes

STATUS_CODE DESCRIPTION SC01_ACTION
200_OK Handshake Successful Payload injected into relay queue.
429_LIMIT Tier Limit Exceeded Request held for 60s cooldown.
503_SYNC Node Syncing Hardware is updating; retry in 30s.
007_GSM_ERR Radio Timeout Tower handshake failed; check recipient.
DEVELOPER_TOOLS

Firetip Engine SDK

The Firetip SDK is a high-performance wrapper designed to interface directly with the sc01-Node cluster.

Initialization

bash — firetip-install.sh
$ npm install @scloud/firetip-sdk
# or via direct cURL
$ curl -X POST https://api.firetip.pro/v1/node/sc01/init
NODE_LOGIC_EXAMPLE 
const firetip = require('@scloud/firetip');

const node = new firetip.sc01Node({
    apiKey: 'YOUR_SCLOUD_KEY',
    relay: 'native'
});

node.ignite({
    to: 'target@gmail.com',
    subject: 'High Velocity Sync',
    body: 'Powered by Ryzen 9'
});

SDK_BENEFITS:

  • 40ms Latency
  • Triple-Auth Sign
  • sc01 Native