AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 19 Bitcoin

Rename CryptoMarket rate provider to Notbank (#7526)

Public commit record

What the developer wrote

Authored by Nicolas Dorier

58/100 · Thin
Rename CryptoMarket rate provider to Notbank (#7526)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit renames BTCPay Server's exchange-rate source from 'CryptoMarket' to 'Notbank'. It swaps the old provider code for a new one that calls Notbank's API, and adds a database migration that rewrites existing store settings so they continue to use the new rate source name. There is no indication this fixes a security vulnerability; it appears to be a routine rebranding/integration change.

Recommended action

Treat as a routine provider rename. Verify that api.notbank.com is a trusted endpoint, that the new API's TLS certificate and availability are acceptable, and that the migration correctly preserves store rate-source selections. No security patch urgency is indicated.

Security signals we found

01

Third-party API endpoint changed from api.exchange.cryptomkt.com to api.notbank.com

02

New provider uses HTTP POST with empty JSON body instead of GET

03

Database migration performs in-place JSON text replacement for provider name

04

No authentication or secret handling visible in diff

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 9/10
Evidence quality 4/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.