CAP-0009 introduces new account flags that can prevent any transactions not signed by your account from modifying your account. This prevents accidental or malicious changes to your account when you are merging it or removing trustlines.
In CAP-0018 (an alternative to CAP-0016’s cosigned assets), Jonathan Jove suggests a new approach to giving asset issuers more control over their assets. This CAP would add a new flag to trustlines that “offers a level of authorization intermediate between unauthorized and fully authorized.” This new flag would allow an issuer to maintain control over who can send and receive payments using their asset while at the same time allow asset holders to maintain offers.
Because Stellar is intended to be securities-friendly, some asset issuers need additional levels of control over their assets beyond authorizing asset holders. Some issuers are spinning up solutions that require them to be co-signers on asset holders’ accounts (see SEP-0008), preventing holders from maintaining full custody of other, unregulated assets. “Cosigned Assets” is a draft CAP by David Mazières that attempts to address this issue by requiring cosigning of transactions that involve a “cosigner authorized” asset without requiring the asset issuer to also be a cosigner on the holder’s account.
CAP-0014 proposes a change in transaction ordering to prevent transaction front-running.
CAP-0013 proposes core changes that would cause Stellar assets to behave more similarly to ERC-20 tokens, allowing an account to add any asset to another account as long as the sending account covers the increased base reserve for the receiving account. It also proposes updates to the AccountMerge operation that would allow non-lumen assets to be merged into the new account without having to manually remove each trustline (which would be renamed to balances). This is an alternative to SEP-0013