AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 29 Monero

clean up epicbox/http/https check

Public commit record

What the developer wrote

Authored by Julian

45/100 · Thin
clean up epicbox/http/https check
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a logic bug in how Stack Wallet decides whether to use an Epicbox server or an HTTP/HTTPS receiver when sending Epic Cash transactions. The old code used OR instead of AND when checking for HTTP/HTTPS prefixes, which meant every receiver address was treated as needing an Epicbox check. The new code cleanly separates the two paths and adds a unit test to confirm HTTP/HTTPS addresses bypass Epicbox while email-style Epicbox addresses use it.

Recommended action

Review whether the always-true condition caused any user-facing transaction failures or unexpected Epicbox dependency. Consider backporting this cleanup to stable releases and verifying that HTTP/HTTPS Epic Cash sends now skip the Epicbox check as intended. No immediate emergency response appears necessary.

Security signals we found

01

Logic bug in protocol routing condition (OR instead of AND)

02

Unnecessary Epicbox connectivity check for HTTP/HTTPS receivers

03

Potential transaction failure or unexpected network behavior due to incorrect path selection

04

Added unit test for routing behavior

Risk score

Why this scored 29/100

Our methodology →
Potential impact 5/30
Exploitability 5/25
Stealth signal 5/15
Affected reach 5/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.