@catch-21 It's what's on the current version of Figma, right?

I assume Figma is correct, in that multiple transactions are to always be grouped into a single activity.

It's about intention. Bitkit loses that intent when we restore because it doesn't back up which transactions were boosted vs transactions that were sent-to-self. They are effectively the same thing, we just bundle boosted transactions together.

Potential solution. If we wanted to retain that intent and have boosted transactions bundled together on restore we would have to add boosted transactions to our backup flow and adjust the activity list UI accordingly during restore.

Personally, I'm against using backups for anything that is non-critical or UI-related as it adds a lot of complexity and increases the calls we need to make when reading/writing from backups. Therefore, I would argue that keeping the way it currently restores is an acceptable fallback instead of additional complexity.

Draft PR here: #2128

There is currently an issue with restoring boosted transactions, onchain activity is restored before boosted transactions are in state. Will revisit after RBF is implemented.