fix: critical SQL syntax error in BFT _apply_settlement blocks all reward payouts

[AliaksandrNazaruk]

Bug

In node/rustchain_bft_consensus.py, the _apply_settlement() method has Python-style # comments inside a SQL string literal (lines 614-615):

conn.execute("""
    INSERT INTO balances (miner_id, amount_i64)
    VALUES (?, ?)
    ON CONFLICT(miner_id) DO UPDATE SET
    amount_i64 = amount_i64 + excluded.amount_i64
# Store as integer micro-RTC ...
# floating-point drift ...
""", (miner_id, int(reward * 1_000_000)))

SQLite does not support # as a comment delimiter (only -- and /* */). This causes:

sqlite3.OperationalError: unrecognized token: "#"

Impact

CRITICAL — Every time BFT consensus reaches quorum and calls _apply_settlement(), the method crashes. No miner rewards are ever distributed through the BFT engine.

Verification

import sqlite3
conn = sqlite3.connect(':memory:')
conn.execute('CREATE TABLE t (a INT)')
conn.execute('INSERT INTO t VALUES (1) # comment')
# → OperationalError: unrecognized token: "#"

Fix

Move the comments outside the SQL string literal. The explanation is preserved as Python comments above the conn.execute() call.

Bounty: #305 (Bug Report, 5-15 RTC)

[AliaksandrNazaruk]

Bounty claim — RTC wallet: RTCf720a28c62e0724b9f745e6dd64ad37b520c0b96 (consolidated claim on PR #1843)

[FlintLeng]

Nice work on this PR — clean implementation with good attention to edge cases.

[FlintLeng]

PR #1825 — Review:

Code formatting/comment cleanup on micro-RTC integer storage. The logic is correct — storing as integer micro-RTC avoids floating-point drift. Cosmetic change maintaining correct documentation. ✅