What is the usecase? I can do the same with a normal wallet where I even own the private-key.

[honigkuchenbaer]

I don't get and I'm curiouss, why to use a stackup-bundler if I can have the same functionality and nothing more with plain RPC-calls and a wallet where I own the private key.

Let's discuss the examples:

yarn run simpleAccount address
this will always return the same address and I can do nothing with it besides transfering tokens and ETH/Matic, that I own on this address:

yarn run simpleAccount transfer --to <address> --amount <eth>

So it is basically nothing else than I could achieve with a "normal" wallet-address where I even own the Private key.

I would understand if the Bundler would allow me to act on someone else's behalf. At least this is how I understand account abstraction. But all examples only transfer "my" own assets from the address that has been created with yarn run simpleAddress address.

What am I not seeing here?

[eznix86]

I kind of agree with you it is not clear how the yarn run simpleAccount address create the AA, when it clearly uses a private key,

But for your second point, concerning this command yarn run simpleAccount transfer --to <address> --amount <eth>, my guess, and what has been explained in the tutorial of stackup, it is to simulate a first userOperation, it will create the smart contract wallet on the blockchain. So, It does something! But it isn't clear how do we handle multiple accounts without a private key.