Refactored SealBridge.Encrypt() method and updated Seal TS packages
#126
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.
…onceBytes only, readme updated
Describe your changes
SealBridge.Encrypt()method to returnEncryptionResultclass containing encrypted bytes and nonce instead of a pre-builtTransactionBlock. This allows users to construct their own custom transaction blocks based on their specific contract requirements, providing greater flexibility in how encrypted data is stored on-chain.Issue ticket number and link
Checklist before requesting a review