The problem Super Reciept solves

Problem Statement

Superfluid supports these wallets - Metamask, Coinbase connect and wallet connect. If a recipient is using a different non-custodial wallet or using a centralized exchange wallet address to receive the payments, they can’t see the stream details on request. Superfluid requires the sender to add the recipient email address to send email notifications to the receiver. If a recipient wants to see the streaming details they have to go to the superfluid dashboard or console and view it everytime. Moreover it is not possible to view the history of transfer or transfer details at a particular point of time from the past.

Proposed Solution:

An on-request superfluid tool that generates a PDF document with all the details about the stream created with Streamflow for both senders & receivers. Senders can create a PDF with stream details to be shared with the recipients as soon as the stream is created or the recipients can themselves check the stream details and get a receipt pdf at any time. This also makes the financing and accounting more web2-like where once can get invoices and check bank statements anytime.

Input:

• Superfluid ID
• Network
  ‍

Output:

• PDF with stream details :
• Sender
• Receiver
• Average tokens per second
• Start timestamp
• End timestamp
• Total money transferred till now

Future prospects:

• Currently the tool supports only some primary fields and generates receipts of a transfer. As a part of further enhancement -
• Allow users to create pdf for multiple streams at once
• Add an option to generate a statement for a particular wallet address
• Shareable Url for previewing stream info
• Scheduling of PDFs

Challenges we ran into

Ideation phase:

Superfluid does have one of the best data gathering of their own protocol so coming up with a problem statement that felt it has potential and is useful to the community was a very deliberate experience

Building phase:

Even tho, superfluid does gather pretty verbose information about their protocol, understanding the ecosystem and getting familiar with the terminology used took efforts

Technical:

Being unfamiliar with Typescript & picking it cost unnecessary problems.