The implementation of cross-chain features within Temple Gold renders account abstraction wallets unusable. This affects the core functionality and usability of the wallet system across different blockchain networks. Users with account abstraction wallets have different addresses for the same account across different chains.
Account abstraction wallets are designed to operate on a single blockchain, but the protocol's cross-chain feature implementation does not adequately support these wallets. When a smart wallet tries to bridge a token like Temple Gold there is no guarantee that the user is the owner of the address on the chain to be bridged. An unaware user who uses an account abstraction wallet to send Temple Gold to another chain will lose the token.
The limitation imposed to restrict users only to send token to the same address across chain is the major issue.
Account Abstraction User gets Temple Token through Auction by Sending Dai to DaiGoldAuction
Spice bazaar auctions (bidding TGLD for volatile token) can be on any chain
Account Abstraction User unable to bid TGLD for volatile token or bridge the token and lose it
Users relying on account abstraction wallets will be unable to perform cross-chain operations, leading to a loss of functionality. This could result in significant user dissatisfaction and a potential decrease in user base, as the wallets will not serve their intended purpose in a multi-chain environment.
There is potential for financial loss if users are unable to access or move their assets due to the cross-chain incompatibility
Manual Review
Document that Account Abstraction and smart contracts wallet cannot use the protocol if the design cannot be changed
Reimplemt the cross-chain send function for users to be able to specify the account they want to bridge the token to.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.