01. Choose your connection
Create an email-verified account, choose a daily or monthly (30-day) subscription at the current displayed price, and enter each server IP, delivery region and UDP port. Each IP and region is a separate subscription; charges add up. Service starts after endpoint verification and activation.
02. Start a UDP receiver
Use a server with a public IPv4 address and a UDP port between 1024 and 65535. Open that port in your host and provider firewalls. The example below uses Python’s standard library.
import socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.setsockopt(socket.SOL_SOCKET, socket.SO_RCVBUF, 16 * 1024 * 1024)
sock.bind(("0.0.0.0", 20000))
while True:
packet, sender = sock.recvfrom(65535)
if packet.startswith(b"SHREDHARBOR_VERIFY "):
print("Verification:", packet.decode(), flush=True)
else:
# Raw Shred bytes: verify, deduplicate, recover and decode.
print(f"{len(packet)} bytes from {sender}", flush=True)This example prints every packet for initial setup. Remove per-packet printing before receiving a full stream; it can cause packet loss. A production consumer also needs bounded queues, Shred verification, deduplication, FEC reconstruction and version-aware decoding.
03. Verify your destination
- Open My streams and select Verify beside your receiving endpoint.
- Copy the generated command and run it on your receiving server. It already includes your UDP port and requires only Python 3; no script file or editing is needed. It exits and releases the port after receiving your code.
- The terminal prints your 48-character code when the regional relay sends a
SHREDHARBOR_VERIFYmessage. - Paste the code into the console. Codes expire after 10 minutes; request a new code if needed. The relay repeats pending verification packets about every 30 seconds. Stop the temporary verifier before starting your production receiver on the same port.
Only a verified endpoint can receive the data stream. You must control the destination server. If no verification packet arrives, check your firewall and the regional relay status.
04. Activation & delivery
Verify the receiving endpoint. New subscriptions activate automatically once the regional relay is healthy. Subscriptions end automatically at expiry; delivery authorization updates within 15 seconds. Renewing retains unused time; expired subscriptions restart from renewal. No automatic renewal.
Pending subscriptions can be cancelled for a full refund to your account balance. Active service does not renew automatically. Remove a destination in the console to stop delivery to it; the relay’s configuration expires within 15 seconds if the control plane becomes unavailable.
05. Fund your account with USDC
Create a deposit address in Balance & billing. Each new order has its own Solana address. Scan the address in your wallet, choose the displayed USDC token and enter an amount. No memo or website wallet connection is needed. Keep some SOL for transaction fees and creation of the receiving USDC account if required.
The actual USDC received is credited automatically after the successful transaction reaches finalized status, even if this page is closed. Each deposit saves its amount, receiving account, signature and chain time. Background collection does not delay account credit. You can reopen the order and submit a transaction signature for an immediate check. A payment to the same address is credited only once.
Payments to a dedicated order address remain assigned to the original account. Automatic confirmation stops after a short grace period following expiry; a late payment can be checked using its transaction ID. Historical shared-address orders retain their memo and amount requirements. Other tokens do not trigger a USDC deposit. Contact [email protected] for assistance with an incorrect transfer. After collection, the platform closes the receiving USDC account and retains its refundable SOL rent; credited USDC is not reduced. Balances are prepaid service credits and wallet withdrawals are unavailable.
Your deposit address is valid for 30 minutes. Reopening checkout during that time shows the same address. Start a new deposit after it expires, and do not send to an old address. If you already paid and your balance has not updated, use the transaction lookup or contact [email protected].
06. Know the delivery semantics
Packets are forwarded as received from the configured regional input. Data and coding Shreds can be duplicated, arrive out of order, or be missing. UDP delivery has no acknowledgment, retransmission or guaranteed completeness. Decode results can belong to an unconfirmed fork.
Frankfurt and Amsterdam are delivery regions and may share upstream providers. The current early-access product does not promise a fixed latency, guaranteed throughput or uptime SLA. Region status reports actual relay heartbeats and recent input data, not end-to-end customer reception.
We support public IPv4 destinations only in this release. See the service terms for the current product scope.