BCard - Rewards Flow
BCard redirects payment card fees to the web3 community of your choice in exchange for the community's social token. This project is limited to the token claim flow which we tackled in June 2024.
Demo
About
The problem it solves Every web3 community can benefit from using BCard: * BCard provides communities with monthly recurring funding through their members' everyday spending * BCard makes it easy for community members to signal support and represent their favourite brands/causes in real life * BCard reduces the onboarding friction of joining a web3 community by allowing new members an easy way to contribute and earn tokens even without a self-custodial wallet Put simply: BCard strengthens web3 communities with funding, proliferation, and onboarding.
How it's made
Challenges we ran into This project is limited to the reward claim process which we tackled in June 2024, and the biggest issue we had with this is sheer volume of different clients users can use to claim rewards. Users can be on desktop or mobile, using one of 5 different browsers, and one of dozens of web3 wallets. This proves to be a difficult challenge, as every wallet/browser/platform combination can act differently. Wallet connection state was especially difficult to deal with. The way we handled this problem was via visbility and iteration. We created a matrix of our top browsers/wallets (as reported by our users), and plainly output the wallet connection state in the rewards flow (which can be seen on the demo video). We then had users test their combination and gathered feedback from them, allowing us to quickly squash bugs and inconsistencies (there were a lot of them). This worked very well - users could easily see the connection state of their wallet, and submit a screenshot of our rewards screen in bug reports. This allowed us to narrow in on bugs, release a fix, and get the user to test immediately. We worked our way through our testing matrix (>20 combinations) and ended up with a reward claim process that works reliably for 80% of users. Ultimately we'd like to have 100% coverage, but we're happy that we're able to handle the users that we can so far, and also have "proven" platforms that we can suggest as workarounds for now.