Skip to content

Add security threat model for secret handling and transaction flows #18

Description

@El-swaggerito

Description

Difficulty: Expert

Type: Security

Summary

Create a security threat model covering Stellar secret handling, payment intent validation, transaction readiness, anchor metadata, diagnostics, and Soroban escrow actions.

Current Behaviour

Security assumptions may be spread across README notes, package code, and contributor expectations.

Expected Behaviour

AnchorKit should have a clear threat model identifying risks, mitigations, assumptions, and out-of-scope production behaviours.

Suggested Implementation

Document threat areas, sensitive data boundaries, unsafe logging risks, mainnet risks, testnet assumptions, contract misuse, and review requirements.

Files or Areas Likely Affected

  • docs/
  • README.md
  • packages/stellar-kit/
  • packages/anchor-utils/
  • contracts/treasury-escrow/
  • apps/web/

Acceptance Criteria

  • Security threat model is added.
  • Secret key handling risks are covered.
  • Payment and transaction readiness risks are covered.
  • Anchor metadata risks are covered.
  • Soroban escrow misuse risks are covered.
  • Mainnet and custody limitations are clearly documented.
  • README links to the threat model.

Additional Notes

Be explicit that AnchorKit MVP is not production custody software.

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked for GrantFox OSS contributionMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Official GrantFox campaign labelexpertExpert difficultypaymentsPayment flow related worksecuritySecurity sensitive worksorobanSoroban smart contract workstellarStellar ecosystem workwalletWallet related work

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions