feat: add Porto + Para EIP-7702 smart account example #151
Conversation
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
Add aa-porto-7702 example demonstrating: - Para authentication with Porto smart account upgrade - Raw signing integration (bypassing EIP-191 prefix) - RelayActions.prepareUpgradeAccount + upgradeAccount flow - Account persistence check via RelayActions.getKeys - Comparison UI showing EOA vs Smart Account features
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.
Summary
aa-porto-7702example demonstrating Para + Porto integrationRelayActions.getKeysKey Implementation Details
para.signMessage({ walletId, messageBase64 })instead ofviemAccount.signMessage()to avoid EIP-191 prefixhttps://rpc.porto.shendpoint for Porto-specific methodsprepareUpgradeAccount()→ sign digests →upgradeAccount()getKeys()on mount to detect already-upgraded accountsTest Plan
yarn installandyarn dev