I think the technical solution is a good trade off, but in the current status it's all controlled by one single entity, but you have permissionless exit, it's also very poor on privacy, and very likely that somewhere in the future some form of KYC will be enforced. So I like it, is cool that is one more option but i don't use for large ammounts.
Discussion
I think if it was like the Lightning Network, and anyone could run "an entity", and it seemed like there were lots of organizations/individuals gearing up to run "entities", this would be a different thing. But literally now there is one entity, and it's just one super-rich Los Angeles family, who likely own a lot of real estate and other assets they need to protect... so you can bet that they will readily comply with any sort of request for information, right?
I think other entities can run the SE and I think they want that to happen, I think they are very transparent about that about not having enough SE. But yes, now it's just one or so and they will absolutely comply if they have to imo.
"Want that to happen" Hm... but not "want that to happen" enough to reveal how the entities work, to open-source the code, anything like that?
don't they? The GH seems to have instructions for the SO, and there is an SO folder in the code, don't know if it's that or if it's all of it.
Can you post a link to the instructions for the SO?
it's just a one liner but it references the SO :
https://github.com/buildonspark/spark?tab=readme-ov-file#bitcoind and the folder i mentioned : https://github.com/buildonspark/spark/tree/main/spark/so
again don't know if this is it. this is beyond my knowledge.
