Repository navigation
feat(sdk): surface the HyperCore origin tx hash once the send lands - #1140
Merged
pedromcunha merged 2 commits intoSep 29, 2026
Merged
Conversation
Contributor
|
@officialchengyud is attempting to deploy a commit to the Uneven Labs Team on Vercel. A member of the Team first needs to authorize it. |
|
This comment has been minimized.
This comment has been minimized.
officialchengyud
force-pushed
the
hypercore-origin-tx-hash
branch
from
September 24, 2026 07:57
e20c73a to
65a3187
Compare
officialchengyud
marked this pull request as draft
September 24, 2026 08:19
pedromcunha
marked this pull request as ready for review
September 28, 2026 16:59
pedromcunha
requested changes
Sep 28, 2026
pedromcunha
approved these changes
Sep 29, 2026
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.
For HyperCore origins (chain 1337), the SDK posts the signed action to Hyperliquid's
/exchange, which acknowledges it without a hash. The step then stays invalidating, with no origin tx hash, until Relay's status reports one. On fast routes that first status is alreadysuccess, so the step goes fromvalidatingstraight tocompleteand the origin is never reported as confirmed while the fill is in progress.Once the action is posted, the SDK now also looks the send up in the sender's Hyperliquid ledger (
userNonFundingLedgerUpdates) by its signed nonce. The entry appears about a second after posting. If it's found before Relay reports a status, the step item gets the hash ininternalTxHashesand the same state Relay's ownpendingstatus produces (checkStatus: 'pending',progressStatecleared,isValidatingSignature: false). Latersubmittedandsuccessstatuses overwrite it as before.sendAssetactions with a nonce (nofromSubAccount).pending.Covered by unit tests for the ledger lookup and the signature step: the pending state, polling not being held up, no
pendingafter a polling failure, no overwrite of a websocket-reported status, and lookup misses and errors.🤖 Generated with Claude Code