The problem Alibuda Habit Builder solves

• Alibuda Habit Builder is more than just a habit tracker; it is a comprehensive solution that combines financial incentives, psychology and community-driven rewards to promote personal growth and well-being. By addressing key issues in habit formation and leveraging the power of incentives and community, Alibuda supports individual users and contributes positively to the broader community.
• Commitment and Motivation: One of the biggest challenges in habit formation is maintaining commitment. Alibuda solves this by requiring users to stake a certain amount of cryptocurrency as a sign of their commitment to new habits.
• Ease of Access and Inclusivity: Registering for Alibuda is streamlined and user-friendly, especially with the integration of the Base Smart Wallet. Within just three taps, users can set up their identity and wallet, making the platform accessible even to those who are new to Web3 technology.
• Asset Efficiency: During the staking period, users' stakes are deposited into DeFi protocols. This ensures the efficient use of assets and generates additional rewards, further incentivizing users to participate and maintain their habits.

Challenges we ran into

Base Chain

• There is no faucet support for the Base Smart Wallet, so to simulate the user experience of interacting with a faucet or on-ramp for more ETH, we created our own faucet by bridging ETH from Mainnet Sepolia.

Base Smart Wallet

• Safari's popup blocker posed a challenge. The support from the Coinbase Developer Platform was exceptional. They were highly responsive and provided actionable suggestions throughout. Despite our efforts, we couldn't fully resolve this issue. As a workaround, users can disable the popup blocker in Safari.
• It would be beneficial to have an embed or overlay window option instead of popups. Building on the previous issue, more integration methods with the Base Smart Wallet would be valuable.
• We could potentially solve the popup issue by leveraging session keys stored in the browser's local storage for daily sign-ins. However, there is a lack of documentation on using session keys or initiating requests with the default wagmi connection.

Nouns API

• Documentation is quite limited. We attempted to query a single trait using the API but couldn't find any relevant examples. Ultimately, we managed to resolve this by passing 'undefined' for all other traits.
• The Cloud Nouns tools are outdated. Despite trying several tools from the Cloud Nouns GitHub, we encountered issues with the example provided in the "kit". As a result, we developed our own component.

Strava API

• Authentication integration documentation is scattered across multiple sites, requiring significant effort to determine the correct approach.
• Finding the API session in the user dashboard was challenging; we had to manually enter the path in the URL to locate the page.
• The default user limit is restrictive (1), and it takes 5 days to increase. Before the limit was raised, we had to create a mock account and share it among the team to complete testing.