thinking about how we communicate "operating accounts" vs "automation accounts" and looking for feedback on this direction. operating accounts = shared multisig accounts. automation accounts = execute calls (swaps etc) when funds are received. both types are dedicated crosschain accounts, with unique addresses and ru... Show more

Save time and clicks by batching transactions. Especially helpful for multisig accounts where wrangling approvals can be tedious.

asking claude to help with an openclaw setup really does make you question what's being lobotomized over there...

Request for roast: We reworked the splits.org website. Would love to improve it based on your feedback.

Have enjoyed this Claude + Obsidian flow: A PostToolUse hook on write/edit that, whenever Claude touches a file under .claude/plans/, auto-opens it in Obsidian so I can review/edit the plan in Obsidian instead of leaving paragraph so feedback in Ghostty. My obsidian/plans folder is a symlink to .claude/plans/ so plan... Show more

Temporary, agent-specific subaccounts. Agents are human shaped, and benefit from the same guardrails, rules, and oversight you'd have for other employees.

balancing speed and care is hard

Delegate funds to your agents while maintaining full control over and visibility into their actions

Save time by batching a number of transactions into a single approval - particularly helpful when you need other people to counter sign

Decentralized blockchains are equalizing technology because they equalize access to economic infra in a way virtually no other technology does

Yes. Our view at the moment is when delegating to an agent, API key > private key because it gives you (the human/orchestrator) more granular control with the ability to revoke access.

Your agents can now create transactions and accounts using the CLI. You remain in full control, and can revoke access at any time.