Skip to content

Simplify TurnkeySigner: collapse signing methods, move activity logic to CLI#20

Open
natefikru wants to merge 2 commits intonatefikru/eng-3860-tk-cli-commandsfrom
natefikru/eng-3860-refactor-activity-commands
Open

Simplify TurnkeySigner: collapse signing methods, move activity logic to CLI#20
natefikru wants to merge 2 commits intonatefikru/eng-3860-tk-cli-commandsfrom
natefikru/eng-3860-refactor-activity-commands

Conversation

@natefikru
Copy link
Copy Markdown
Contributor

Summary

  • Collapse sign_ed25519 and sign_ssh_auth_payload into a single sign_raw_payload method (they were identical wrappers)
  • Remove approve_activity and reject_activity from TurnkeySigner, move API calls to the CLI activity command using client() directly
  • Remove the silent swallow of already-rejected status from reject, letting the CLI handle errors transparently
  • The CLI should be a thin pass-through to the API, not a place for custom design choices

Test plan

  • All workspace tests pass (43 tests)
  • E2e consensus demo still works (setup, sign, approve, teardown)

… to CLI

Collapse sign_ed25519 and sign_ssh_auth_payload into a single
sign_raw_payload method since they were identical. Remove
approve_activity and reject_activity from TurnkeySigner, moving the
API calls to the CLI activity command using client() directly. This
removes the silent swallow of already-rejected status from reject,
letting the CLI decide how to handle errors.
Treat UnexpectedActivityStatus(REJECTED) as success in tk activity
reject so retries and races do not fail with a hard error when the
activity was already rejected by another actor.
@natefikru
Copy link
Copy Markdown
Contributor Author

@emostov does Sign_raw_payload bypass any of the turnkey internal parse functions?

Copy link
Copy Markdown
Collaborator

@emostov emostov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good

@emostov
Copy link
Copy Markdown
Collaborator

emostov commented Apr 1, 2026

@emostov does Sign_raw_payload bypass any of the turnkey internal parse functions?

Yes - it doesn't go through the parser at all so you can only write consensus policies against it.

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.

2 participants