feat: implement integration guide showing how to gate a Soroban contract using has_valid_credential#32
Merged
Conversation
…act using has_valid_credential
Closed
8 tasks
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.
Implementation Summary
Rust contract example:
Added stellar-id dev-dependency to Cargo.toml — the test code imports StellarIdContract/StellarIdContractClient but the dependency was missing
Added annotations explaining the #[contractclient] pattern, why Identity must be replicated, and the cross-contract call flow
Cleaned up unused imports (Symbol, Vec, String)
TypeScript section — completely rewritten:
Full working hasValidCredential() function using Address.fromString().toScVal() for address encoding and nativeToScVal for u32 encoding
Uses Keypair.random() for simulation (no wallet required since has_valid_credential is read-only)
Proper error handling for simulation failures and missing return values
Usage example with a Stellar address check
Express middleware example showing production gating pattern (reads address from x-stellar-address header, returns 401/403/500)
Note:
The compilation failure is pre-existing — the local rustc (1.87.0) predates what darling 0.23.0 requires (1.88.0). This is unrelated to my changes, which are confined to docs/INTEGRATION.md.
Closes #22