feat: add transferTransaction action endpoint #60
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a new RPC action for transferTransaction in compliance with the action specification. The endpoint accepts required parameters, returns a signed transaction, and is integrated into the actions.json configuration.
Changes include:
Added transferTransaction endpoint to RPC crate
Implemented request validation and signing logic
Updated actions.json with the new action
Added unit and integration tests for the endpoint
Included a working blink to demonstrate functionality
Acceptance Criteria Covered:
Endpoint adheres to spec
Proper signing and return of transaction
Full test coverage
Demonstration of action execution
.
This pull request was created for https://app.gib.work/bounties/4fcf8fb1-e80c-4a37-9eb8-a4e6f0651e3a in an attempt to solve a bounty #16 . Payment for the bounty is immediately sent to the contributor after merge.