Seraphis VS monero-cpp

Seraphis is a next-gen transaction protocol abstraction, which means it defines various high-level rules for a concrete transaction protocol. RingCT can be thought of as the current tx protocol abstraction of Monero, even though the RingCT paper specified concrete proving structures directly without abstraction.

Anyway, you can check here and here.

Work is well under way to implement something you could call a "second-generation protocol" for Monero called Seraphis. You can find details on the author @UkoeHB 's GitHub here. In parallel @tevador designs a new addressing and wallet tiers scheme to be used with Seraphis called Jamtis that is currently documented and discussed here.

Anyway. The concern raised here may be rendered nearly moot by the upcoming Seraphis/JAMTIS upgrade. As I understand it, this upgrade will significantly speed up remote wallet scanning time, while also making remote wallets much more secure.

More information on Seraphis can be found here: https://github.com/UkoeHB/Seraphis

I get the gist of what he is trying to do and how the transactions function. https://github.com/UkoeHB/Seraphis/issues/3

It's worth to mention here that Monero dev @woodser has defined a new and clean wallet API quite a while ago already and implemented it in C++, Java and JavaScript. The design is documented here, its C++ implementation is here. It's only for the current Monero technology of course, but maybe it could serve as a good starting point for wallet3.