Conversation
In 0.8.0 the handler echoed back params.callData, which fails any test that submits the bytes (polkadot-api's extrinsic codec rejects them because callData[0] is the pallet index, not a v4/v5 prefix). Resolve the keypair from params.signer (product flow → derive from configured root account; legacy flow → match raw 32B pubkey), sign callData || extras || additionalSigned with sr25519 (blake2_256 first when payload > 256B per Substrate convention), and frame as v4 signed: [0x84][0x00 + AccountId32][0x01 + sig][extras][callData]. paseo-asset-hub-next advertises extrinsic.version: [4] only, so v5 general support is deferred until a target runtime negotiates it. Integration test #45 now decodes the returned bytes, asserts the v4 frame, and runs sr25519Verify against the embedded pubkey — would have caught the 0.8.0 stub. 0.8.0 should be deprecated on npm after merge.
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.
host-api-test-sdk 0.8.1
Bumps
@novasamatech/*to0.7.9-4and fixeshandleCreateTransactionto return a real signed v4 extrinsic. In0.8.0it echoedparams.callDataback — fine forresult.ok === truechecks, broken the moment a product tried to submit the bytes.What changed
handleCreateTransaction/handleCreateTransactionWithLegacyAccount— the request is now a flat object (signer,genesisHash,callData,extensions,txExtVersion); no more tuple wrapping, nocontextblock, all fields areUint8Array. ExportsVersionedPublicTxPayload/TxPayloadV1Publicare gone — useProductAccountTransaction/LegacyTransaction.callData || extras || additionalSignedsr25519 and returns a v4 signed-extrinsic frame:[0x84][MultiAddress::Id + AccountId32][Sr25519 + sig][extras][callData]. v5 is not emitted yet (paseo-asset-hub-next runsextrinsic.version: [4]only).@novasamatech/product-sdkis being renamed to@novasamatech/host-api-wrapper(0.7.9-5+is under the new name; we stay onproduct-sdk@0.7.9-4for this release).What you need to do
0.8.1. No product-side code change required — the wrapper API didn't move.createTransactionrequests by hand, switch to the flatProductAccountTransactionshape and includegenesisHash.callData, drop that assumption and decode the response as a v4 extrinsic instead.0.8.0is deprecated on npm; upgrade.