Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Zaps #32

Open
miladsoft opened this issue Oct 2, 2024 · 1 comment · Fixed by #40
Open

Support for Zaps #32

miladsoft opened this issue Oct 2, 2024 · 1 comment · Fixed by #40
Assignees

Comments

@miladsoft
Copy link
Member

Integrate support for Zaps, allowing users to interact with content using the Lightning Network.

@miladsoft miladsoft self-assigned this Oct 5, 2024
@miladsoft miladsoft linked a pull request Oct 5, 2024 that will close this issue
@miladsoft
Copy link
Member Author

The integration of Zaps has been successfully completed. Users can now seamlessly send and receive Zaps using the Lightning Network, enabling more interactive and decentralized financial transactions within the application. The following features were added:

  1. Send Zap Dialog: Users can now generate a Lightning invoice to send payments (Zaps) by specifying an amount. The invoice is displayed via QR code for easy scanning, or it can be copied directly for sharing.

  2. Receive Zap Dialog: Users can generate and share invoices to receive payments via the Lightning Network. The dialog allows setting a specific amount and displaying a QR code for easy scanning.

  3. Improved Error Handling: Both dialogs provide informative feedback to the users, ensuring smooth interactions even when errors occur during payment processes.

With this feature, users can interact with content by sending and receiving Zaps directly within the application, leveraging the power of the Lightning Network.

Status: The issue is now resolved, and the feature is fully integrated and functional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant