Skip to content

problem: can't validate zap publisher when lightning providers endpoints are set up incorrectly  #100

@gsovereignty

Description

@gsovereignty

most of the custodial lightning providers don't have their zap endpoints set up correctly, so we can't get the authorised pubkey for zap reciepts.

possible solution: manually get all these buy zapping people and finding all the commonly used lightning service providers' pubkeys and hard code them into the client.

It's shitty but it will solve the problem for now.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions