🧰 PeakeCoin USDT Bridge — Debug Mode and Verbose Logging

Sometimes, the best progress happens when you step away for a bit — and that’s exactly what happened here.
After a quick detour for real-world chores, it’s time to come back and fine-tune the bridge for tomorrow’s test with verbose debugging enabled.

🧠 Why Verbose Logging Matters

When bridging across blockchains — Hive Engine to Polygon in this case — a single missed detail can mean hours of guessing.
Verbose logging turns every transaction step into a transparent timeline.

Instead of just:

[SWAP] Sent 10.00 USDT to 0x185d...

You’ll get:

[SWAP-DEBUG] Reading line 102 from usdt_transactions.jsonl
[SWAP-DEBUG] Extracted memo: 0x185deE705cBd272Dbf597C6419Ba035B660B95c9
[SWAP-DEBUG] Valid Polygon address detected
[SWAP-DEBUG] Nonce retrieved: 85
[SWAP-DEBUG] Built raw transaction with gas 100000 @ 50 Gwei
[SWAP-DEBUG] Transaction hash: 0x4d62f...

That’s the kind of visibility you need when syncing multiple networks.

⚙️ Enabling Debug Mode

In each script (monitor_usdt.py, usdt_swap.py, usdt_runner.py), add this block near the top:

import logging

logging.basicConfig(
    level=logging.DEBUG,
    format='%(asctime)s - %(levelname)s - [%(threadName)s] %(message)s',
    handlers=[
        logging.FileHandler('bridge_debug.log'),
        logging.StreamHandler()
    ]
)

Now, both your terminal and your bridge_debug.log file will show detailed activity — including timestamps and thread origins.

🧩 What to Expect

When you restart the system:

python3 usdt_runner.py

Your output will now include:

• [MONITOR-DEBUG] entries for Hive Engine polling
• [SWAP-DEBUG] entries for Polygon transactions
• [RUNNER-DEBUG] entries for thread coordination

It’ll look like a constant stream of diagnostics, perfect for catching API hiccups or confirming successful state syncs.

🧪 Why It Helps Tomorrow’s Test

Verbose logging will make it easy to:

• Track when each Hive block is fetched
• Confirm when transactions are appended to usdt_transactions.jsonl
• Verify Polygon gas prices and transaction nonces
• Detect if any step hangs or skips due to rate limits

Instead of wondering where the bridge paused, you’ll see exactly *why
This report was published via Actifit app (Android | iOS). Check out the original version here on actifit.io

Daily Activity