MarketTakers/arbiter
5
0
Fork 0
Code Issues 27 Pull Requests 4 Packages Projects Releases Wiki Activity

Client approval quorum differs from documented consensus model #70

New Issue
Open
opened 2026-04-05 16:23:10 +00:00 by Skipper · 0 comments
Skipper commented 2026-04-05 16:23:10 +00:00
Owner
Copy Link

Info

Severity: LOW
Attack vector: network-only

Impact

Allows a smaller set of online user agents than the documentation implies to approve new SDK clients.

Description

The current approval flow requires unanimous approval from currently connected user agents, not the broader quorum model described in the architecture. In a multi-user-agent deployment where only one agent is online, that single agent can approve a new SDK client.

Example flow

  1. Deploy multiple user agents but leave only one connected.
  2. Start a new SDK client approval flow.
  3. Collect approval only from currently connected user agents.
  4. Approve the client with fewer approvals than the documented model suggests.

Mitigation

Align the implementation with the documented quorum semantics and define how offline user agents affect approval decisions.

# Info **Severity**: **LOW** Attack vector: network-only ## Impact Allows a smaller set of online user agents than the documentation implies to approve new SDK clients. ## Description The current approval flow requires unanimous approval from currently connected user agents, not the broader quorum model described in the architecture. In a multi-user-agent deployment where only one agent is online, that single agent can approve a new SDK client. ## Example flow 1. Deploy multiple user agents but leave only one connected. 2. Start a new SDK client approval flow. 3. Collect approval only from currently connected user agents. 4. Approve the client with fewer approvals than the documented model suggests. ## Mitigation Align the implementation with the documented quorum semantics and define how offline user agents affect approval decisions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat
Breaking
Breaking change that won't be backward compatible
Difficulty
High
3
Hard difficulty. Experience needed to fix: A lot.
Difficulty
Low
1
Easy difficulty. Experience needed to fix: Not much. Good first issue.
Difficulty
Medium
2
Medium difficulty. Experience needed to fix: Intermediate.
Kind
Bug
This is a bug.
Kind
Enhancement
Improve existing functionality.
Kind
Feature
New functionality
Kind
RFC
Request for comments
Kind
Security
This is security issue
Kind
Testing
This is testing issue.
Kind
Tracking issue
An issue tracking the progress of sth. like the implementation of an RFC
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Pending
4
Requires review by dev
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
CleverWild Skipper goodvin testuser
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MarketTakers/arbiter#70
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?