Skip to content

[submit] No Authorization header support — API key forced into URL path #196

@obchain

Description

@obchain

Refs #44

File: crates/charon-executor/src/submit.rs, crates/charon-core/src/config.rs

Problem

Bloxroute and blocknative support Authorization: Bearer headers as the preferred secret-passing mechanism. URL-embedded tokens appear in server-side access logs regardless of TLS. The PR forces operators to embed API keys in the URL.

Fix

Add optional ChainConfig.private_rpc_auth: Optionsecrecy::SecretString field. Plumb through Submitter::connect(url, auth, timeout) → attach Authorization header on every JSON-RPC POST. Document expected env var as CHARON_BSC_PRIVATE_RPC_AUTH.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestlayer:rustRust crates (core / scanner / protocols / executor / cli)pr-reviewFindings from PR review processpriority:p1-coreCore MVP scopestatus:readyScoped and ready to pick up

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions