Return not just the raw balance, but also the allocated amounts when running the command /balance

also, maybe round all values to the nearest milli-satoshi?

e.g.:

Total Amount Allocated to Laisee: 2516
Available Balance for New Laisee: 223.36200000000008```

Currently Lightning addresses are created from the user's Telegram handle, including uppercase characters.

This means users with uppercase characters in their username cannot use their Lightning address.

Solution: Convert usernames to lowercase before creating the Lightning Address and placing the .well-known file.

Spec: https://github.com/fiatjaf/lnurl-rfc/blob/luds/16.md

Ideal to get an automated balance update from LNBits when a user redeems a laisee.
however there is currently no webhook on LNURLw on Lnbits so this would need to be added somehow before it can be added here.

Need a method to recreate an old laisee if it gets lost or deleted in telegram and wasn't claimed.

example:

/replay <laisee id number> 

Right now there is no way to do it for the end user, but they can use lnbits url link for claiming laisee sats.

The LNURL-pay that is generated for each user asks for a comment to be submitted.

Ideally we don't ask for a comment because we don't display it anywhere.

Use newly release SatsPayServer Extension to permit OnChain top ups for users who have BTC but no exposure to LN

The command /laisee 100 should create a Laisee for 100 sats.

At the moment it adds a fee to the Laisee, which should be added elsewhere, if at all.

for non technical admin users, please see this sub repo for details.

the QRimgtest repo is for testing the background image placement and is subsection of the laiseebot code.

Please see detailed issue at:
https://github.com/bitkarrot/QRimgtest/issues/11

For each Laisee I create, I should have to add a certain amount of funds to my account.
In the current configuration, I can create 100 Laisee with 0 balance.
I later have no way of finding out how many Laisee I have created, e.g. how many Laisee I have outstanding.

Possible solutions:

• I have to pay an invoice before I get the Laisee
• I can see how many outstanding Laisee I have, and I can only create new Laisee as long as my balance is larger than the outstanding Laisee

The "total amount allocated to Laisee" includes Laisee that have already been redeemed, possibly resulting in a negative balance and requiring the user to over allocate funds to their Laisee bot account.

Is there a way to sum up only the unredeemed Laisee?

Total Amount Allocated to Laisee: 2516
Available Balance for New Laisee: -113.8690000000001```

so that end user is notified when invoice is paid (topup) or by Lightning Address (topup) or QR code/LNURL topup

When creating a Laisee, some metadata could be sent to its creator in a separate message:

• Date created
• Amount
• ID
• Expiration date
• Raw LNURL (ideally as a hyerlink with the lightning: prefix)

update laiseebot to use lnurlp for lightning addresses, kill off modify well-known update to forward to LNBits lnurlp.

currently well-knowns are created for each new user on https://github.com/bitkarrot/laisee-frontpage

if we migrate to the new lnurlp (post feb 2023, see leo's test instance), we don't need to do use the laisee-frontpage for .well-known.

However, it does mean that the LN addresses are now [email protected] instead of [email protected] because the LNbits instance is at ln.laisee.org

To be fixed:

• The Laisee has a white frame
• The QR code is the wrong color (should be 5b1110ff)
• The QR code background is the wrong color (should be dcb866ff)
• Amount isn't centered
• Expiration date and id isn't legible)
  

.....for this thing. Majordomo involved. 😂

lnbits.hapax.io returned an invalid invoice. Expected description_hash == 6bcd23eb74f39e0d48122fe28cf38bfb8730549ba6e755110a3ea25a8b26c691, got 17c4b49068c3a6998bfe6f1a55c3e0fa9ffcd8356999d2117b528e8b605ed23b.

As tested in lnbits

in SBW:

requirement failed: Metadata hash mismatch, original =6bcd....., later provided=Some(17c4b...)```

REPRO:

• Start Laiseebot
• Fund Laiseebot
• Run command laisee 100

ACTUAL:

• Error creating laisee: local variable 'session' referenced before assignment

EXPECTED:

• Get a Laisee

Creating a Laisee through the menu works, so maybe it's just a function that needs to be updated, or is wrongly called?

We could create a lnbits user account for @laiseebot

Everytime the bot creates a Laisee, it first sends the appropriate fee to the @laiseebot, as if the laiseebot was another user. This can happen silently in the background.

1. I deposit some sats, either through the lnurl, lightning address or invoice
2. No matter how many times i run /balance, the balance does not update

The balance only updates after I click on the lnbits wallet link.

Surely there would be another way of triggering that update?

At present, a Laisee is labelled Laisee amount: {amount}

Instead, only labeling the Laisee Laisee or Lightning Laisee would be more fitting, as the amount is displayed in any wallet.

If we want to be creative we could choose from a list of new year's greetings that are randomly chosen to accompany the label Laisee:

金玉滿堂
大展鴻圖
迎春接福
萬事如意
吉慶有餘
竹報平安
一本萬利
福壽雙全
招財進寶

Repro:

• /laisee 100

I get the image, but can only redeem it after 3600 seconds.

Reason:

Wait time in LNbits is set to 3600 (should be set to 0)

When selecting 'defund the wallet' the user is sent a QR code and a link. The link however only links to the img.

As an alternative, a hyperlink like the one below could be displayed:

lightning:LNURL1DP68GURN8GHJ7MRWVF5HGUEWDPSHQCTC9E5K7TMHD96XSERJV9MN7ATNWG7NWCFS8Q6NVE3SXQEKGCE5X5UR2WRP

The way the Laisee bot currently works, do we want to give the option to defund the wallet? As it would allow the user to defund the Laisee they already handed out.

Update requirements so that pylnbits and supabase are not used with git+https://

I believe both of these libraries are now under stable release and we don't need to pull from branch. However please test and make sure that is the case before pr. thanks

It seems it's impossible to defund the wallet properly because the reserve fee is not correctly calculated.