Understand Rizful's security model...

Two-factor authentication, using Google Authenticator (or similar) is required for all Rizful users with balances above 100,000 satoshis. This is a powerful and widely-tested security strategy that should serve to keep bad actors out of your Rizful node.

But please understand the tradeoffs we've made: While studying the Lightning design space, we've realized there is a big, nasty problem with giving users a seed phrase and assuming they could restore their node at any time: Most users won't be able to successfully restore their node! Lightning's "static channel backup" restore model is confusing, even for experienced node-runners. Do "an SCB" wrong, and you'll lose all your sats. We think that giving new users a seed phrase, and asking them to take responsibility for all backup and restore.... that's a challenging route. So we've made a big tradeoff: We store the encrypted backups and retain the ability to restore nodes in the event of hardware failure. This should work well for new users and users with small balances, but is NOT designed for large production-scale nodes with high balances.

Don't expect an "abstracted" Lightning experience...

A common recent pattern is for apps and websites to attempt to "hide" the actual behavior of the Lightning Network -- instead of showing lightning channels, peers, and channel balances, an "abstracted" app might just show one "satoshis balance," and not even show the user anything called a "channel". This can be a good approach, but we've decided with Rizful to try the opposite: We provide ALL the data, directly from the underlying node instance, with the aim of providing a detailed, fully-annotated "teaching" node, that is also high-performance.