Draft
Conversation
kev1n-peters
force-pushed
the
stacks-executor-route
branch
8 times, most recently
from
6d9b79e to
5a7d7c9
Compare
kev1n-peters
commented
Dec 16, 2025
| }; | ||
| } | ||
|
|
||
| async *setPeer( |
Contributor
Author
There was a problem hiding this comment.
Some of the functions in here were written by @fergarrui who will be adding CLI support in the future.
kev1n-peters
force-pushed
the
stacks-executor-route
branch
from
e05cf0f to
9d11a95
Compare
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
1 participant
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 support for the Stacks NTT executor route.
Stacks NTT transfers are only supported via the executor route. The automatic (legacy standard relayer) and manual routes are not available for Stacks. This constraint exists due to Stack's unique address handling requirements.
When transferring to Stacks, we use a custom
StacksNttReceiveInstructionexecutor instruction. This instruction includes both the native manager and recipient addresses for Stacks. This is required, because the VAA payload contains keccak256 hashed addresses for Stacks. The executor needs the native (unhashed) address to potentially register them with the addr32 contract on Stacks before redeeming the VAA. If the executor relay fails, users need access to the native addresses to manually register them.