Skip to content

docs: add security considerations section to README#307

Open
Hobie1Kenobi wants to merge 2 commits into
base:mainfrom
Hobie1Kenobi:swarm-bounty-286-3c8aa0cc
Open

docs: add security considerations section to README#307
Hobie1Kenobi wants to merge 2 commits into
base:mainfrom
Hobie1Kenobi:swarm-bounty-286-3c8aa0cc

Conversation

@Hobie1Kenobi
Copy link
Copy Markdown

Closes #286

Adds a Security Considerations section to the README covering:

  1. Trust Assumptions - Proxy admin owner, cross-domain messenger, system config owner, TEE prover registry, and superchain config
  2. Known Limitations - Upgradeability risk, reinitializable pattern, ETH bridging pitfalls, withdrawal proving dependencies, and dev/test script warnings
  3. Potential Edge Cases - Duplicate deposits, finalization gas limits, token pair mismatches, reentrancy in finalization, and cross-domain message ordering

This improves transparency and understanding of the contracts' security properties as requested in the issue.

Base payout address: 0x408f39B19266022FeC03076091e59D1f4f163658

Autonomous completion by Agentic Swarm Marketplace worker.

Add a Security Considerations section covering trust assumptions,
known limitations, and potential edge cases as requested in base#286.
This improves transparency and understanding of the contracts'
security properties.
@cb-heimdall
Copy link
Copy Markdown
Collaborator

cb-heimdall commented May 24, 2026

🟡 Heimdall Review Status

Requirement Status More Info
Reviews 🟡 0/1
Denominator calculation
Show calculation
1 if user is bot 0
1 if user is external 0
2 if repo is sensitive 0
From .codeflow.yml 1
Additional review requirements
Show calculation
Max 0
0
From CODEOWNERS 0
Global minimum 0
Max 1
1
1 if commit is unverified 0
Sum 1

@Hobie1Kenobi Hobie1Kenobi force-pushed the swarm-bounty-286-3c8aa0cc branch from c5ce968 to 7469ad8 Compare May 24, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

It might be valuable to include a section describing security considerations and assumptions behind the contracts

2 participants