How-To Guide: on how to sign contract invocations using C-accounts #2206
Conversation
…s from a client and hand it over to a feePayer, facilitator, relayer, sponsor, or similar role
marcelosalloum
changed the title
There was a problem hiding this comment.
Pull request overview
This PR introduces a comprehensive how-to guide for signing Soroban smart contract invocations, addressing a significant documentation gap. The guide covers two distinct signing methods: traditional transaction signing for G-accounts and the more complex auth-entry signing for both G-accounts and C-accounts (contract accounts/smart wallets). The guide emphasizes auth-entry signing, which enables sponsored transactions, relayed transactions, and smart wallet integrations.
Changes:
- Added comprehensive guide documenting transaction signing and auth-entry signing methods with working code examples
- Included detailed explanations of simulation modes (Recording vs Enforcing) and their importance
- Added visual diagrams illustrating the difference between transaction signing and auth-entry signing flows
- Added image reference to fee-bump transaction structure diagram
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/build/guides/transactions/signing-soroban-invocations.mdx | New comprehensive guide (459 lines) covering two methods for signing Soroban contract invocations, with complete code examples, tables comparing approaches, and detailed explanations of simulation modes and security considerations |
| docs/build/guides/transactions/fee-bump-transactions.mdx | Added image reference to visualize fee-bump transaction structure |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Preview is available here: |
|
Preview is available here: |
1 similar comment
|
Preview is available here: |
What
How-to guide on how to sign contract invocations using G-accounts or C-accounts.
Although the guide covers both signing types (transaction signing, and auth-entry signing), it focuses more heavily on the auth-entry signing, which is new(er), more complicated and lacks documentation.
Why
Having the opportunity to interact with multiple projects that enforce that flow (Launchtube, OpenZeppelin Relayer, WalletBackend, MeridianPay), I know very well how that's poorly documented and has many pitfalls.
This guide provides working code examples using
AssembledTransaction, explains simulation and auth requirements, and includes visual diagrams to clarify the authorization flow.AI
The guide and snippets have been tested by multiple AI agents for functionality and clarity ✅
Preview
Should be deployed to:
https://developers-pr2206.previews.kube001.services.stellar-ops.com/docs/build/guides/transactions/signing-soroban-invocations