I am deving on a dapp for it. Plan to have something up and running this weekend or next week. The MVP from xstelea works fine but is a bit limited. That said. It does serve a very important function of being a fallback solution in any case a backend dapp like mine or others are failing from serving anyone. The fallback is for ensuring the multisig controlled account is easy accessible through instantiating xstelea’s public repo.
My current view after devving for some days is:
-
Using subintents in a backend orchestrator is safer than you may think. The validation and execution is done on Ledger and it is the Wallet that acts as the Access Controller together with the native security controls. The dapp only orchestrate the signatures. The weakest point in the dapp may be the backend account that is the feepayer and wraps the intents into a final transaction. But the backend accounts role is no more than paying fees and collecting some platform fees. So the risk is on the platform owner and not the Multisig Account Owners.
That said. Any fresh new features like this should mature for a while and undergo some stress testing before handling large buckets of funds. -
The DAO should probably use PrimeVault as the main vault for storing any major reserves. While considering using onchain services like these new upcoming Multisig account dapps, Rebix for repeated payments to merchants and lockers for XRD related funds that is close the the network operations. Then over time adjust where the funds are stored and managed.
It is a matter of spread the risk and use the tools where it make the most sense.