Tobias (tschubotz)

Multisigs are prone to leaking alpha if the transaction queue is public. The sensitive info that's leaked? Treasury strategy, trade plans, operational decisions, etc. 👉 Meet Secret Harbour: End-to-end encryption between signers

• 1 reply
• 0 recasts
• 1 reaction

Transaction batching is key for good UX @safe. The enabler: Multisend via delegatecall. The challenge: How to ensure _safe_ use of delegatecall? The solution: Guardrail, a @safe guard that limits the scope of delegatecall.

• 2 replies
• 1 recast
• 2 reactions

The current SafeDAO vote shapes up to be an important milestone for the SAFE token: transferability! Make your voice heard on the proposal before April 15th. https://snapshot.org/#/safe.eth/proposal/0x5b7b35a5baa1b5fe02f2264191d068d7c4270d7975dfcce2cb05b88dcf8d5080

• 0 replies
• 0 recasts
• 0 reactions

Transaction batching is key for good UX @safe. The enabler: Multisend via delegatecall. The challenge: How to ensure _safe_ use of delegatecall? The solution: Guardrail, a @safe guard that limits the scope of delegatecall.

• 2 replies
• 1 recast
• 2 reactions

In early @safe days, the north star was TVL. $ 1B was a huge milestone. 100x'ing it now puts @safe into spheres of banks, except: - All transparent. - All permissionless. - All self-custodial. - All onchain.

• 0 replies
• 1 recast
• 4 reactions

Why is this cool? It could be enabled on your existing @safe multisig. It adds another security layer for DAOs and power users. Note: This is a prototype, code is NOT audited yet. We are looking for feedback.

• 1 reply
• 0 recasts
• 2 reactions

Use case of wallets beyond crypto storage: Smart accounts can be your secure yet user-friendly way to manage your digital identity. Enables seamless interaction with DeFi, social platforms, and more. 👉 https://safe.global/blog/safe-case-decentralized-social-id

• 0 replies
• 0 recasts
• 1 reaction