The order in which you GRAB them doesn’t matter. But ultimately YOU ARE ordering them when you write them down. So they are ordered when the exercise is finished, yielding 2048 possible combinations, which is perfect given there are exactly 2048 words in the BIP 39 word list.
Discussion
we tested zaps on this note… we made six attempts to⚡zap this note, at me@dplus.plus, over a period of about 3 hours. six of the zaps were successfully paid... please check for 6 satoshis received. however, we did find that only one of the payments produced zap receipts in time for our server to recognize them. this is a problem because the user who zapped you would not see an active ⚡icon after zapping. they might think the zap failed, and therefore might not zap you again.... if you wanted to fix this... you could try getting a free rizful lightning address -- https://rizful.com ... if u get it set up, pls reply here so we can do this ⚡zap test again.
I am showing zap receipts for all six.
interesting test case! your granular data is below.... interesting that it was #3 where we saw the zap receipt... this can sometimes happen due flakiness on whatever server you have producing your zap receipts -- or could possibly be whatever relays you are sending zap receipts to... or could be something else...
Individual Zap Attempts:
1. Attempted at: 2025-12-28 04:52:07 UTC
LNURL: 1710ms
Callback/Invoice Generate: 1040ms
Attempt âž¡ Lightning Confirmation: 2602ms
Lightning Confirmation âž¡ Zap Receipt: N/A
---
2. Attempted at: 2025-12-28 05:49:51 UTC
LNURL: 1605ms
Callback/Invoice Generate: 1071ms
Attempt âž¡ Lightning Confirmation: 1058ms
Lightning Confirmation âž¡ Zap Receipt: N/A
---
3. Attempted at: 2025-12-28 06:38:14 UTC
LNURL: 552ms
Callback/Invoice Generate: 921ms
Attempt âž¡ Lightning Confirmation: 5153ms
Lightning Confirmation âž¡ Zap Receipt: 4049ms
---
4. Attempted at: 2025-12-28 07:01:14 UTC
LNURL: 1794ms
Callback/Invoice Generate: 1083ms
Attempt âž¡ Lightning Confirmation: 1038ms
Lightning Confirmation âž¡ Zap Receipt: N/A
---
5. Attempted at: 2025-12-28 07:36:26 UTC
LNURL: 1929ms
Callback/Invoice Generate: 1100ms
Attempt âž¡ Lightning Confirmation: 1171ms
Lightning Confirmation âž¡ Zap Receipt: N/A
---
6. Attempted at: 2025-12-28 08:18:20 UTC
LNURL: 547ms
Callback/Invoice Generate: 1074ms
Attempt âž¡ Lightning Confirmation: 1013ms
Lightning Confirmation âž¡ Zap Receipt: N/A
---
what zap receipt implementation are you using? are you sure it is sending the zap receipt to the relays specified in the zap attempt?
I made my own zap receipt server with some random relays hardcoded. Maybe that’s the issue.
Yep. Check out this line in the nip 57 spec:
" publish it to the `relays` specified in the `zap request`."
... almost everyone gets this wrong the first time they create a zap receipt server... we definitely did...
Okay… maybe I should add a few extra relays though just in case? Like at least one that I’m connected to so I can see my own zap receipts.