chore: update paykit to rc56 - #823
ben-kaufman wants to merge 4 commits into
Conversation
|
There was a problem hiding this comment.
Advice: ✅ Approve
Review: diff 12 files.
Equivalent to synonymdev/bitkit-android#1365.
Findings:
2 inline (2 MEDIUM)
Audit:
Awaits QA.
Coverage:
QA: waits for the other reviewers' approval, or @ovi-reviewer test
Reviewed by gpt-6-sol-xhigh via gh-pr-review-loop skill
Commands: @ovi-reviewer review · test · retest · audit (author or owner) · wrong <why> (owner)
There was a problem hiding this comment.
Advice: ✅ Approve
Reaudit: diff 2 files.
No new findings; the rest is in the review.
Pair PR synonymdev/bitkit-android#1365: equivalent.
Reviewed by gpt-6 via gh-pr-review-loop skill
Commands: @ovi-reviewer review · test · retest · audit (author or owner) · wrong <why> (owner)
jvsena42
left a comment
There was a problem hiding this comment.
Two LOW inline. No SDK-adaptation findings.
Checked and clean:
- The pbxproj change is only the version pin.
- Released tags: v2.5.0 = rc51, v2.4.x = rc31, v2.3.x = rc8. The SDK storage schema is unchanged rc55→rc56, and app-side Codable stores are untouched.
parse(... requiresActionableRequest: true)rejects deadline requests before amount parsing, and every pay entry point requires membership inpendingRequests.finishPayment/paymentRequestForRetryare unreachable for a deadline request.hasPaymentDeadlinegates proposal acceptance, payment due on acceptance, recurring materialisation, commit and reminders. Paid periods are keyed by period, so rc56's retained proofs cannot double-count.- Outbound
conversion/paymentDeadline/allowanceId/conversionQuoteIdare nil. - A payee cancellation after payment derives
.canceledand is excluded from pending, and crossing acceptances do not resurrect it.
There was a problem hiding this comment.
Advice: ✅ Approve
Reaudit: diff 5 files.
No new findings; the rest is in the review.
Pair PR synonymdev/bitkit-android#1365: equivalent.
Reviewed by gpt-6-sol-xhigh via gh-pr-review-loop skill
Commands: @ovi-reviewer review · test · retest · audit (author or owner) · wrong <why> (owner)
There was a problem hiding this comment.
Verdict: ✅ Approve
Tests for the review: Tests 1 and 3 passed; Test 2 and journey J1 could not be verified without the required test services.
Audit:
Already done in review.
No findings remain.
QA:
Tested on two iOS 26.5 simulators (iPhone 17 Pro)
Test 1 ✅ passed
Test 2
Test 3 ✅ passed
Test J1
Warning
Payment request delivery and deadline history remain unverified without the issuer and rc56 peer.
Note
Tests 1 and 3 passed.
Tip
Try this journey:
Test 1
- Create two regtest wallets, enable Paykit UI, and save each wallet's Pubky profile as a contact on the other.
- Open the recipient contact on the funded payer and tap Send, then Pay.
- Enter 5,000 sats and continue to the confirmation screen.
- Swipe to pay and verify Bitcoin Sent.
- Verify the recipient shows Received Bitcoin for 5,000 sats.
Test 3
- Create two linked regtest wallets with Paykit UI enabled and fund the payer above 5,000 sats.
- On the creator, make a monthly Journey Sub for 5,000 sats and propose it to the payer contact.
- On the payer, review the proposal and swipe to subscribe and pay.
- Confirm the 5,000 sat Bitcoin send and verify the Subscribed result.
- Open the payer's subscription detail and verify Active, the next month's renewal date, and the first payment.
- Open the creator's subscription detail and verify one subscriber, one payment, and the matching received installment.
Reviewed by gpt-6-sol-xhigh via gh-pr-review-loop skill
Commands: @ovi-reviewer review · test · retest · audit (author or owner) · wrong <why> (owner)
|
@ben-kaufman conflicts |
fbe69c1 to
91b43c8
Compare







Closes #824
This PR updates Bitkit to the Paykit 0.1.0-rc56 release and adapts the existing Bitcoin payment request and proof calls.
Companion: synonymdev/bitkit-android#1365
Description
This upgrade is independent of the USDT integration. It adds no migrations, legacy compatibility paths, or wallet resets.
Screenshot / Video
Reuses the existing subscription review layout and unsupported-payment explanation.
Design
N/A — no design available. Reuses the existing subscription review components and copy.
QA Notes
Manual Tests
Journeys
journeys/payment-requests/payment-deadline-history.xmlis included on both platforms. Not run end to end: it requires a controlled rc56 peer with accepted and paid deadline-bearing records. The repository tests exercise those states with fixtures.Automated Checks
PaykitPaymentRequestServiceTests.swiftcovers deadline payment rejection, one-time and paid recurring history, proof-delivery retries, and reminder suppression. Other fixture changes match rc56 constructors; no existing test coverage was removed.git diff --check, independent UI and journey/docs reviews, XML parsing and cross-platform journey comparison passed. Existing unrelated compiler warnings remain.