Avatar
BilligsterUser
af4b1cdc624a1be8f31fbf6702d0d873410867f9675755601d8bc1e8cfb84cf9
"I’m better with code than with words though." – Satoshi Nakamoto GitHub: https://github.com/BilligsterUser NostrTool: https://nostrtool.vercel.app #bitcoin ⚡⚡⚡ #cashu 🥜🐿️🌰 #nostr

We need an Awesome-Cashu List/Site

Back to writing code

Replying to Avatar calle

# ⚡️ Nostr zaps - a guide 💜

Time to get you zappin' with LightningTipBot (https://ln.tips). This is my personal setup. There are other ways and services to do this. Do you own research. This is just a suggestion.

## 1) Set up LightningTipBot wallet

- Click here: https://LN.tips 👈

- You're done.

## 2) Sending zaps

Let's start with sending. You don't need much. Any Lightning wallet will do. I will describe how to use LightningTipBot to zap with.

### Sending zaps in the browser

- Get the Alby brower extension at https://getalby.com/

- Go to LightningTipBot and enter "/link"

- Copy the details and go to Alby and add a new "LNDHUB" wallet

- Enter your details

- Your LightningTipBot wallet can now be controlled from your browser

- Click on the ⚡️ zap icon for example in iris.to and you'll be able to send zaps.

### Sending zaps on mobile

- You can also "/link" your wallet to BlueWallet

- Get BlueWallet from the App store

- Import a new Lightning wallet

- Enter your credentials from LightningTipBot

- You can now control your LightningTipBot wallet from Bluewallet

- Click the ⚡️ zap icon for example in Amethyst or Damus and open BlueWallet.

- Pay and zap on

## 3) Receiving zaps

You can receive zaps with pretty much any Lightning address provider. There are many options. See: https://lightningaddress.com/

However, if you want the zaps to appear under your posts in Damus or Snort.social, you'll have a few less options (still). Here is how to do it with LightningTipBot:

- Go to LightningTipBot. Enter "/help" if you don't know your Lightning address.

- See your address? Mine is callebtc@ln.tips

- Optional: Enter "/advanced" to get an anonymous address if you don't want to doxx your Telegram username.

- Put your Lightning address into your nostr profile

- In LightningTipBot, register your nostr pubkey with "/nostr add "

- You're done! You'll receive zaps and they will be shown under your zapped posts!

## 3) NIP-57 support

Zaps (those which appear under a note) are formalized in NIP-57. Currently, they are supported by the following services. This is probably not a complete list and tomorrow there might be even more:

### 💜 Sending (Nostr clients):

- Snort.social (https://snort.social/)

- Damus (http://damus.io/)

### ⚡️ Receiving (Lightning wallets):

- LightningTipBot (https://LN.tips)

- VIDA (https://vida.live/)

- Stacker.news (https://stacker.news/)

- strike.army (https://strike.army/)

ZAP ZAP ZAP

#[0]

Replying to Avatar calle

Yes! We just cracked another nut in Cashu's protocol development: How to handle Lightning's unpredictable fees with no additional rounds of communication?

This was one of the weakest points of the protocol.

Background: https://gist.github.com/callebtc/a6cc0bd2b6f70e081e478147c40fc578

Proof of concept:

## Very short summary of the problem

In Lightning, you don't know the fee in advance. But in ecash, you need to pay for everything upfront (ecash isn't divisible, the mint can't simply return the change back to the user when they overpay Lightning fees).

Solution: The wallet provides a set of "blank outputs" (blinded secrets) when asking a mint to make a Lightning payment.

The blank outputs don't have an amount but the mint can "imprint" amounts in them and return blind signatures (= ecash) to the wallet if they overpaid fees.

This is beautiful. We sat down in a virtual circle (thank you phyro, #[0] ) and thought hard about possible solutions and discovered this.

Unpredictable LN fees and backups were the two big issues in Cashu's protocol design and now we fixed both! 🎉

#[0]

good morning nostr

VB6

Visual Basic

PHP

Go

sh

C

Typescript

C#

Java