Conversation
Pulls in RFC-0021 coin top-ups, the PaymentTopUpSource codec fix
(PrivateKey/Coins keys are now 64-byte sr25519 secrets), the
deriveProductEntropyFromSource export, and host-chat / host-papp
internals. All existing handlers behave identically.
Adds setPaymentTopUpBehavior test control so tests can drive products
through the PartialPayment error path — `{ type: 'partial', credited }`
credits the balance by `credited` and rejects with
PaymentTopUpErr.PartialPayment({ credited }), mirroring how a real host
reports a partially-fulfilled Coins top-up. Coins-source top-ups flow
through to paymentLog.source as { tag: 'Coins', value: Uint8Array[] }.
Integration tests cover the coins round-trip and the partial-payment
balance/error semantics.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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.
Summary
@novasamatech/host-api,host-container,host-api-wrapperfrom^0.8.0→^0.8.6. Pulls in RFC-0021 coin top-ups (triangle-js-sdks#194), thePaymentTopUpSourcecodec fix (#198 —PrivateKey/Coinskeys are now 64-byte sr25519 secrets), thederiveProductEntropyFromSourceexport (#205), and host-chat / host-papp internals. All existing handlers behave identically.setPaymentTopUpBehavior(behavior)test control plumbsPaymentTopUpErr.PartialPayment({ credited })throughhandlePaymentTopUp.{ type: 'partial', credited }credits the balance bycreditedand rejects with the matching error — mirroring how a real host reports a partially-fulfilledCoinstop-up. Also supports{ type: 'reject', reason: 'InvalidSource' | 'InsufficientFunds' }.paymentLogalways records the attemptedamountandsourceregardless of outcome.PaymentTopUpSource.Coins(Vector<Sr25519SecretKey>)flows through topaymentLog.sourceas{ tag: 'Coins', value: Uint8Array[] }(each key is 64 bytes).paymentLog, and the partial-payment path asserting both the rejected promise'spayload.creditedand the resulting balance increment.CHANGELOG.md,forum-post.md(new section + 0.9.x blocks moved to the bottom to match the ascending-order convention),README.md(new "Payment control" subsection).0.8.7-0is a prerelease (host-papp SSO V2 storage migration); not pulled.