Currently we do a full sync every time, but we want to modify that to just sync the data since the last sync, but might need the new wait API to handle that nicely, or maybe use the SQL plugin.

No not using any new rpcs at the moment, we are syncing all payment data and storing in a local DB rather than using the node as a kind of server. We want a view of all payment data so that in future releases we can render charts and have accounting exports, profit loss statements etc without having to fetch from the node each time. It also allows us to do nice payment summaries for when you have multiple nodes (and in the future xpubs, custodial and exchange wallet data) and really show the sats flow across multiple wallets.

Let us know if you have had a chance to give v2 a go yet with your node. We saw your post when you tried another client that you had over 100k payments 🤯, so we spent some time making sure Clams can handle that kind of scale. It will take a good while to sync and look like it is stuck, but it is still syncing, but should be able to handle it.

We have been heads down since BTC++ in April doing a full refactor of Clams, and have just published a beta v2 release. If you currently use Clams v1 or run a CLN node we would love to get your feedback before we do a full release in a couple of weeks.

We’ll be sharing some more info in the coming weeks about where Clams is headed now that we have set the app up to be much more scalable and flexible. You can check out the open beta here:

https://github.com/clams-tech/App/releases/tag/clams-2.0.0-beta.1

Running nostr