Speaker 3
so then I guess green light is also dealing with backups for
Speaker 1
the user, right? Yeah, exactly. So we are actually creating backups that we that we then give to the users in the case of if they want to offboard in an encrypted form. And just using their seed phrase, they can decrypt this whole package and start a new core lightning node against that that backup. And they they pick up exactly where they left off, essentially.
Speaker 2
I think stuff that you'll see similar hybrid approach server assistance software coming from LDK as well, big backups ability to have like a multi device environment ability to have multi app environment require server, such as software. So I think that again, everything is going to be very blurry on what is it? Maybe you want to take away from this post that there's no more nodes. There's different services that are composed differently on different devices.
Speaker 1
Yeah, gotcha. There is a lot of of interaction between us like Roy mentioned before. The LDK guys are building a system called VSS to synchronize state across across multiple multiple instances of their software. And that is that is in response to a need that we are self-tad. Because I mentioned before that you can attach as many signers to a single node as you want, but signers are not stateless. And so we needed a signer state synchronization protocol, where we could say, okay, here is here is my current state. And every signer would get a copy of that state along with requests, verify against that state, and then feed that state back. So that is that is something that that that we knew we had to build. And talking to the LDK guys, we we found out that they want to get one step further and actually synchronize the entire node, whereas we just synchronize the signer state, which I think is probably easier. But we'll see how that turns out.