Working on a new feature for ape-safe, something I am calling "queue scripts" h/t @johnnyonline_ @milkyklim

The way they work is that you add scripts for your @safe under `scripts/nonceN.py`, and `ape safe pending ensure` will search that directory for scripts *at or above* current on-chain nonce, and make sure that they are reflected in your Safe's current API queue

The scripts themselves will take advantage of a new feature we are adding to `ape-safe` that simplifies building MultiSend transactions using a sequence of transactions executed within a temporary fork (executed as if the safe were doing the transactions itself)

This is perhaps the most-requested feature from @bantg's original `ape-safe` library (now called `brownie-safe`), but using the ensure-queue command drastically simplifies setup for professional operations This is inspired by @yearnfi's Robowoofy project

With this feature released (still WIP), you will be able to set up a github repo to track your Safe scripts using extremely simple python syntax, and test/execute them safely and securely in github actions We will probably create a github action to do exactly this

Automating high-frequency transaction queues for a production-level safe (storing 7+ figures of value in it) is probably the hardest thing to do well in Crypto (as the Bybit hack evidenced). To do it well, you need great tools!

@eth_sign @Ledger @Trezor To do that in a foundry script seems like... quite a stretch It's just not expressive enough