Skip to content

BE-19: Signed Payloads for Client-to-Server Requests (Anti-Tamper) #254

@Cedarich

Description

@Cedarich

Labels: backend, security, wave4
Complexity: 200 points
Branch: feat/be-signed-payloads
Summary
Add optional signed payload verification for sensitive requests (e.g., bids, refunds, disputes) to reduce tampering risk in untrusted clients.
Tasks

  • Define signing scheme (timestamped payload + wallet signature).
  • Add verification middleware and replay protection window.
  • Apply to selected high-risk endpoints.
  • Add tests with valid/invalid signatures and replay attempts.
    Acceptance Criteria
  • Server rejects tampered payloads and replayed signatures.
  • Verification errors are consistent and client-actionable.
  • Sensitive endpoints can require signatures via config/flag.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions