the shielded account keys are derived from the user’s public Ethereum address. So, there’s no extra headache of managing a new set of keys or seed phrases...

intersend.io | via sequence. pimlico. poap. polygon. consensys. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

 the public address is used to resolve the transaction off-chain at the SDK level. it is never exposed on-chain. "

"As user deposits their funds, Labyrinth generates an encrypted note memo that holds the details of the user’s asset—completely encrypted. 

for every transaction users have to generate a zk proof of inclusion, for the note(s) they are spending and also verify their ownership over those notes.

The bundler acts as an intermediary that submits transactions on behalf of the user. Instead of paying gas fees directly from their public wallet, which would reveal their address, the bundler covers these fees upfront. 

Users then reimburse the bundler from their shielded balance once the transaction is complete"

"Our Selective De-Anonymization (SeDe) network ...

 having users register their public wallet address which points to their shielded address. This mapping is stored as event data on-chain, so the sender only needs to know the recipient’s public address (or even their ENS name) as the public address can be resolved to a shielded address.