Implications of ag-solo vs. smart wallet architecture on Agoric smart contracts

[migueldingli1997]

As a newcomer to smart contract development on Agoric, I would like to understand more concretely the implications of the transition from ag-solo to the smart wallet architecture, especially on how smart contracts are developed/structured/deployed/etc.

I've been going through the getting started docs. Knowing about the above made me question some of the documentation such as the Agoric Wallet page since it might get phased out eventually due to the mention of ag-solo.

The ag-solo based docs points out that:

The Dapp architecture presented here is a beta preview of our eventual permissionless contract deployment model, extending our Distributed Computing Framework to a stateful peer on end-user machines.

The Mainnet-1 launch uses a "smart wallet" architecture with a lower client-side footprint.

I was also made aware that ag-solo style deployment is supported in devnet but not in mainnet. This makes me wonder about how I should be approaching smart contract development given that I want to be developing contracts that run on both the devnet and mainnet. It also makes me wonder about what I should be on the lookout for if I'm looking at example contracts, given that these might have been developed with ag-solo in mind.

[dckc]

One-shot contracts like the PSM work well.

For longer flows like vaults, the continuing invitation pattern is well supported... though documentation is scattered:

• continuing invitation pattern documentation#667

One aspect of several of our example contracts that's not supported by the smart wallet architecture is invitations as offer results; here's hoping we remove that limitation before long:

• handle invitation offer results in smart wallet #8550

Here's hoping for time to think of a more exhaustive answer.