Herd

the new porto contracts from ithaca are a supercharged version of 7702,  let me explain how it works using /herd 👀 

the protocol page on Herd is shown below, with four main contracts:

Here's a graph from their github docs showing the call and execution process across contracts, you can see it's mainly the orchestrator acting as an "entrypoint" to interface with the account.

All five contracts were all deployed in one transaction: 
https://herd.eco/base/tx/0x583b2c9b2c0ad11f6784ee868fc46fa220b8d80759c58563c76abff21bf98630?isSimulated=false

Our transaction interpretation page explains even constructor function logic on deploys:

To learn more, let's look at specifically the orchestrator and account. 

The account is a 7702 proxy, which not only has a batch execute function but has execution permissions and spend permissions built in! It's a key system within a contract for any wallet.

The orchestrator acts as the entrypoint (think 4337), and handles executions/sponsors. 

Most interesting is that the ithaca team has built simulations directly onchain - no need to use another service offchain to simulate data. That's actually insane!