John Cantrell

# App Submission ### App name Sensei ### Version v0.0.2 ### One line description of the app A lightning node with super powers ### Summary of the app Sensei is...

Currently says the blinding is done using the processing node's public key which is not correct. Instead of trying to explain how blinding works again, just link to the section...

Add IndexedChain trait and implement for Esplora & Electrum

3

### Description This PR introduces the trait IndexedChain that Blockchains can implement if they have access to chain data. There are lots of methods that could be added to this...

fix(multitenancy.mdx): role should be on user not organization

10

I was reading through the multitenancy docs and I'm pretty sure the example schema definition has the global role defined in the wrong place. Seems like it belongs on the...

document cli

4

the cli tool is completely undocumented at the moment other than the basic `help` flow provided through `clap`.

Right now we just use Access::None meaning we don't verify any of the channel announcements that get added to the graph. We should probably either require this or I guess...

Umbrel integration

5

Once (https://github.com/L2-Technology/sensei/pull/17) lands an Umbrel integration should be pretty straight forward. Here are the instructions from Umbrel: https://github.com/getumbrel/umbrel/blob/master/apps/README.md It mostly boils down to writing a Dockerfile for Sensei

would be nice to see some stats about our view of the graph and maybe limited ability to query it.

It would be nice to see some stats about current height, fee estimates, poller status, etc.

Pretty self-explanatory. I keep getting annoyed by this ux so want to add issue here to fix it.