We want to facilitate the recording of Web3 community activities on the blockchain. Currently, these communities in the region are making enormous efforts to incorporate new users and developers into the blockchain ecosystem. However, these efforts are limited by the lack of simple tools that allow them to record the participation of their community members onchain.

Our community faces challenges in blockchain adoption and usage, which we address with Base's help. We simplify these processes for our members by leveraging Base's account abstraction tools, specifically Basenames and Coinbase Wallet.

We developed SEAL Attendance, a Discord bot that validates event attendance using account abstraction, attestations, and NFTs. This system enables Web3 ecosystem event organizers to record participants' attendance simply, securely, and transparently. It employs blockchain technology to ensure the authenticity and integrity of the information. Moreover, each attestation is tokenized as a unique NFT, offering on-chain connectivity through our API.

SEAL Attendance comprises three main components:

• Discord Integration: Embedded in the server's event announcement channel, it allows creators to easily generate events and users to register their attendance with minimal effort.
• Attestations and NFTs in SEAL: To ensure security, event creators must link their wallet on our page and sign the transaction via Coinbase Wallet. This process guarantees the integrity of event attestations.
• Visualization in Farcaster from Basenames: Information is displayed through a Farcaster frame, accessible via Basenames, seamlessly integrating both services.

A significant technical challenge we faced was validating signatures from smart wallets created under the EIP-4337 standard on the Base network. While the EOA account connected correctly to RainbowKit, the smart wallet generated the signature. Our attempts to validate the signature using traditional methods (ethers.verifyMessage) failed. This failure stemmed from these signatures requiring verification through the EIP-1271 standard—an aspect not clearly addressed in the documentation. To overcome this hurdle, we opted to use basenames for identifying application users.