A cool bounty for superteam member from ChapterX
ChapterX is a Web3 social infrastructure platform powering social interactions through tokenized NFC products and interoperable digital identity. Users can tap their ChapterX cards to connect with others and manage all connections through a proprietary CRM platform, while event organisers can achieve higher returns on events through drastically improved engagement with sponsors and attendees. ChapterX’s partners include Solana Foundation, MonkeDAO, SAMO DAO and more.
ChapterX has developed a “ChapterX telegram bot”, which is linked to the profile of the user. Whenever the cardholder (tapper) meets a new friend (tappee) in a real-life event, the cardholder can tap his NFC card on the tappee’s phone, which pops up a profile in the browser. When the tappee clicks the “Telegram button” at the bottom of the profile, it is redirected to the ChapterX bot in telegram. Once the tappee click starts, the bot sends a message to both the tapper and tappee with their contact information so they can track all their new connections made in an event within one telegram channel.
Allow the telegram bot to obtain the user’s telegram ID without directing them to the bot within telegram. The ideal case is that users are directed to DM channels and the bot can still obtain the telegram ID and track the connections
Simplify the “tracking new connection” features
Right now, when a tappee clicks the “Telegram button” on my profile, the tappee needs to “start” the telegram bot in order to record the telegram ID of this “new connection”
We want to simplify the process for tappees, who don’t get much value from the bot. Tappees are very unfamiliar with the bot and are often confused by the need to click “Start” on the bot
The goal here is to record the telegram ID when the tapper and tappee connect through the card and store it in the system
Submit a production-level functioning bot with well-written code that fulfils the requirements above, that is linked to a MVP profile page to demonstrate the feature before 7th April 2023 UTC 12 noon
Functionality - how well does the application work?
Design - how intuitive and easy the user experience is? Is it a lot better than your current experience?
Code quality - how clean is the code?
For any questions, please email firstname.lastname@example.org