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

Implement EVM permission engine #7

New Issue
Closed
opened 2026-02-14 11:34:29 +00:00 by Skipper · 0 comments
Skipper commented 2026-02-14 11:34:29 +00:00
Owner
Copy Link

Implement the EVM permission engine as described in ARCHITECTURE.md section 6.

This is the core policy system that governs what SDK clients are allowed to sign. No permission logic exists yet.

Requirements:

  • SDK clients have no access by default
  • User Agent grants access scoped to specific wallets and chain IDs
  • Three transaction categories: known contract (ABI decoded), unknown contract, plain ether transfer
  • Volume limits and rate limits for known contracts
  • Transaction count limits for unknown contracts
  • Global limits: gas cap per transaction, time-window restrictions
  • Ensure transaction nonces are never reused
Implement the EVM permission engine as described in ARCHITECTURE.md section 6. This is the core policy system that governs what SDK clients are allowed to sign. No permission logic exists yet. **Requirements:** - SDK clients have no access by default - User Agent grants access scoped to specific wallets and chain IDs - Three transaction categories: known contract (ABI decoded), unknown contract, plain ether transfer - Volume limits and rate limits for known contracts - Transaction count limits for unknown contracts - Global limits: gas cap per transaction, time-window restrictions - Ensure transaction nonces are never reused
Skipper added the
Kind
Feature
 label 2026-02-14 11:34:29 +00:00
Skipper added the
Difficulty
High
3
Priority
High
2
 labels 2026-02-14 11:44:16 +00:00
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
Difficulty
High
3
Kind
Feature
Priority
High
2
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#7
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?