user127318: When dealing with normal on-chain transactions, we can generate a large number of bitcoin addresses that can then be stored separately and used to receive payments at a later date.
I am aware that a lightning node must be reachable when a sender wants send a payment. I am also aware that reusing a lightning transaction compromises both older and newer transactions.
That said, I would still like to know if it is technically possible to generate a large pool of lightning invoices (to store on a server) in the same way normal bitcoin addresses can be generated.

user41313: No; unlike a Bitcoin address, Lightning invoices have a built-in timestamp and an expiration time. They also have information, such as the amount of Bitcoin (and sometimes routing information), that changes in an unpredictable fashion.

127318: <p>When dealing with normal on-chain transactions, we can generate a large number of bitcoin addresses that can then be stored separately and used to receive payments at a later date.</p>
<p>I am aware that a lightning node must be reachable when a sender wants send a payment. I am also aware that reusing a lightning transaction compromises both older and newer transactions.</p>
<p>That said, I would still like to know if it is technically possible to generate a large pool of lightning invoices (to store on a server) in the same way normal bitcoin addresses can be generated.</p>
 41313: <p>No; unlike a Bitcoin address, Lightning invoices have a built-in timestamp and an expiration time. They also have information, such as the amount of Bitcoin (and sometimes routing information), that changes in an unpredictable fashion.</p>
