feat: Protocol Fee, Security Hardening & Solita SDK Refactor#43
Open
feat: Protocol Fee, Security Hardening & Solita SDK Refactor#43
Conversation
…ig Spoofing, Lamport Burns)
…n instruction account validation by reordering instruction accounts.
…ith a new client method, and remove outdated local test workflow documentation.
…utability and ordering, and remove `AccountDiscriminator` type.
…on and update existing tests to utilize it.
…ers, setup streamline, and English translate
…use native Web Crypto API for secp256r1
- Rename findWalletByOwner to findWalletsByEd25519Pubkey - Rename findWalletByCredentialHash to findWalletsByCredentialHash - Standardize addAuthority and transferOwnership param names (newAuthType, newAuthPubkey, newCredentialHash) - Update all test files to use the new names
- Fix hardcoded origin in Secp256r1 WebAuthn payload builder - Enforce stricter TypeScript boundaries on wrapper APIs - Add comprehensive JSDocs mappings matching C-Struct byte offsets - Refine naming conventions across pdas and builders - Improve security, ownership, and execution tests - All 69 E2E tests maintain 100% pass rate
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
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.
🚀 Comprehensive Update: Protocol Fee, Security Hardening & Solita SDK
This PR consolidates the implementation of global contract configuration, protocol fee collection mechanics, critical audit security hardening, and a complete revamp/E2E implementation of the Solita Client SDK framework.
🛠️ Key Modules & Changes
🦀 1. Rust Smart Contract (Core & Security)
collect_protocol_feeapplied to initialization and action processors.CloseWalletandCloseSessionprocessors incorporating rent refunds procedures securely.wallet_pdastrictly into payload hashes (ExtendedData) ensuring signatures bound strongly to local instance contexts.📜 2. TypeScript SDK & Test Infrastructure (
solita-client)01- configthrough08-security) matching 70/71 passes sequences securely.📚 3. Manuals & Docs
Architecture.md,README.md, and Guidelines bundles mapping fees, security checkpoints updates synchronized.