Feat/stellar sponsored batch send - #146
Merged
truthixify merged 4 commits intoAug 27, 2026
Merged
Conversation
added 2 commits
August 26, 2026 18:50
Covers the full flow for Python 3.11+ backends that want to talk to
Wraith contracts without the TypeScript SDK:
- guides/quickstarts/python.mdx (new)
- pip install stellar-sdk + cryptography only
- wraith_crypto.py inline utility: scan-key derivation via SHA-256
domain separation, X25519 ECDH, ed25519 point addition, view-tag
prefilter, sign_with_scalar (RFC 8032 compatible raw scalar signing)
- Fetch WRAITH_ANNOUNCEMENT events from Soroban RPC (getEvents + XDR decode)
- scan_announcements with view-tag prefilter (~255/256 skip rate)
- Send: createAccount activation + Soroban announcer invocation
- Spend: withdrawal tx signed with raw stealth scalar
- All Python fences marked no-check for the TS snippet gate
- Targets futurenet; notes testnet contract IDs for live testing
- sdk/overview.mdx: cross-link to Python quickstart under Next Steps
- docs.json: Quickstarts nav group added above Guides in the Guides tab
…attern Add guides/stellar/sponsored-batch-send.mdx covering: - BeginSponsoringFutureReserves + batch send + EndSponsoringFutureReserves pattern - Reserve vs fee cost model with AccountMerge refund lifecycle - End-to-end airdrop example for 100 stealth recipients (chunked at 24/tx) - Failure modes: auth revocation, insufficient reserves, missing EndSponsoring signature, and trustline missing inside sponsorship window - Futurenet testing section Update docs.json: add nav entry in Guides > Operations group. Update guides/stellar-fees.mdx: cross-link to new guide in See Also. All 10 TypeScript snippets pass tsc --noEmit (check:snippets CI).
|
@Mathew2k-hash Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
…group The auto-merge of develop into feat/stellar-sponsored-batch-send produced an invalid docs.json: the Quickstarts group ended up with two separate "pages" keys (python from this branch, rust from develop) with no comma between them. Merged both entries into a single pages array. Fixes: pnpm run check:nav-coverage JSON parse error at position 3128.
Contributor
|
Merged. The sponsored-reserve cost model and the refund timing are explained clearly, which is the bit the Stellar docs gloss over @Mathew2k-hash. |
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
2 participants
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Description:
What
Adds guides/stellar/sponsored-batch-send.mdx — a new guide documenting the
pattern of combining Stellar's BeginSponsoringFutureReserves /
EndSponsoringFutureReserves with Wraith's batch send so a single paymaster
account covers the 1 XLM minimum reserve for every new stealth recipient in one
atomic transaction. This is the top-requested undocumented pattern for airdrops
and payroll.
Why
guides/stellar-fees.mdx explains fee-bump sponsorship but stops short of reserve
sponsorship. There was no page documenting how to combine sponsored reserves
with batch send for multi-recipient flows. Developers building airdrops or
payroll pipelines had no reference for this pattern.
Changes
operation sequence
100-op cap
signed (sponsor + sender + each new stealth address for
EndSponsoringFutureReserves)
reserves, missing EndSponsoringFutureReserves signature, and trustline missing
inside the sponsorship window
paymaster
guides/stellar/ guides
guide
Testing
check:snippets CI does)
Related
Closes the undocumented gap between guides/stellar-fees.mdx (fee-bump) and full
reserve sponsorship for batch stealth sends.
closes #128