[sdk]: align sdk with latest ABI changes, add docs, fix tests#911
Merged
Conversation
Point the EVM registry, SDK chain configs, and indexer testnet config at the redeployed Gargantua V3 IsmpHost and HandlerV2 addresses.
Delete the TokenGateway/asset-teleport handlers, services, ABI, schema entities and config entries, plus the one-off entity-data migration script and its test.
Update erc6160ext20 to the redeployed testnet fee token across the indexer configs, and skip the IntentGateway integration tests in the SDK and simplex since those contracts were not redeployed.
Version the entity that lost its teleport fields so it gets a fresh table, and restore the TOKEN_TELEPORTED_POINTS enum value to avoid downstream changes.
Point the HyperFungibleToken test at the redeployed host, faucet, and token addresses, and skip the suite until the host's uniswapV2Router is configured and the test account is funded.
seunlanlege
reviewed
May 25, 2026
5c9460f to
c86a86b
Compare
…d-intent-gateway-v2 # Conflicts: # sdk/packages/indexer/src/configs/abis/TokenGateway.abi.json # sdk/packages/indexer/src/mappings/mappingHandlers.ts
…hft-and-intent-gateway-v2
- Point tesseract registry, SDK chain configs, and indexer mainnet config at the new mainnet IsmpHost (0x6201...) and HandlerV2 (0x2a18...). - Add Polkadot Hub mainnet (EVM-420420419) to tesseract, SDK, and indexer. - Remove Unichain (130) from tesseract, SDK, and indexer mainnet configs. - Update indexer startBlocks to the host deployment blocks for both testnet and mainnet. - Re-enable the @hyperbridge/sdk test workflow.
Collaborator
Author
|
@Wizdave97 |
Wizdave97
reviewed
May 26, 2026
Wizdave97
reviewed
May 26, 2026
Wizdave97
reviewed
May 26, 2026
The indexer's RequestService.computeRequestCommitment and the SDK's post/getRequestCommitment were hashing the packed encoding of request fields in the wrong field order. The V3 EVM host commits with keccak256(abi.encode(PostRequest)) using the struct's tuple layout, so every SDK lookup against the indexer (and every mmr_queryProof) missed. Switch both to encodeAbiParameters with the outer tuple wrapper and fields in struct order: PostRequest: source, dest, nonce, from, to, timeoutTimestamp, body GetRequest: source, dest, nonce, from, timeoutTimestamp, keys, height, context End-to-end verified: lock-bsc HFT test now runs SOURCE -> SOURCE_FINALIZED -> HYPERBRIDGE_DELIVERED -> HYPERBRIDGE_FINALIZED -> DESTINATION.
tsup's dts build rejected the positional-array form against viem's tuple component types. Switch post/getRequestCommitment to the named-object form to satisfy the inferred TS types; encoding result is unchanged.
…ology + tier pricing table
The test hardcoded "POL0" for chain 80002, but the SDK's defaults map and the published Gargantua deployment both use "POLY". For lock-bsc Polygon is the destination so the mismatch never bit, but for burn-polygon Polygon is the source — SDK calls like latestStateMachineHeight and the on-chain proof submission key off this id, so SOURCE_FINALIZED / proof construction never finds a match and the test never reaches DESTINATION.
Wizdave97
approved these changes
May 27, 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.
Summary
Docs
docs/content/developers/evm/bandwidth/— overview, purchasing, governance, configuration. Documents the subscription model,BandwidthManager/pallet-bandwidth/BandwidthGateloop, end-to-end flow, and per-chain bring-up checklist.SDK
perByteFeefromEvmHost.quote()(now returns0n) and from the exportedHostParamstype.quoteNative();quote()is treated as native cost. Fixes a latent bug where paying in native was silently no-op becausetotalNativeCostwas always 0.stateCalls.test.tssources the BSC Chapel host fromchainConfigs[97]instead ofprocess.env.BSC_ISMP_HOST_ADDRESS.abi.encodeto match the V3 host (SolValue::abi_encodeparity instead ofabi_encode_params).encodeAbiParameters.Simplex
OrderPlaced.source/destination→string,NewDeploymentAdded→DeploymentAdded,DestinationProtocolFeeUpdatedcarriesstring chain.perByteFeecache +initCachefetch loop now that bandwidth replaces per-byte pricing.Indexer
DailyProtocolFeesStats,protocolFeesEarned, related compute helpers.HyperBridgeChainStats→HyperBridgeStats(entity, service, file).EthereumHost.abi.jsonagainst the new EvmHost; fixGetRequestEventtopic in YAML codegen.UserActivity→UserActivityV2.gnosis-chiadofrom testnet/local/nexus-ci configs (no longer supported on testnet).