`invoke`/`call` fail finding the contract to call and return different parsed contract addresses about starknet-devnet

[FabijanC]

Regarding your original issue, did using the --no_wallet flag help? Or running unset STARKNET_WALLET?

Yes, that was it! Can you explain why I needed not to use a wallet?

The important thing to note is that your wallet uses your account, and your account is also a contract that has to be deployed.
So you could use the wallet in your case, but then the network you are interacting with (Devnet in this case), should have the wallet account deployed. You may have deployed your account at some point, but then you shut the Devnet instance down and the account was lost.

Anyway, if the function you are calling doesn't require any wallet/account verification, you can call it directly and not through a wallet/account (by specifying --no_wallet)

I can see my transactions are not moving passed the "ACCEPTED_ON_L2" status. Is this because it is outside the scope of the devnet to actually communicate with Starkware's STARK prover?

That's right, Devnet is completely local. The furthest any transaction goes is getting included in the local list of blocks (each block having just one transcation).

[sebastiendan]

Feel free to use my test gateway at http://52.179.101.122:5000.

[FabijanC]

Hi, thanks for providing your gateway, pretty cool to be testing on something other than localhost.

I'm suprised that your starknet call command works because it expects --feeder_gateway_url to be provided and you are providing --gateway_url.

Does your contract do any calling by proxy? Also, is your STARKNET_WALLET environment variable set by any chance? If so, you are implicitly running your invokes/calls through an account that was probably deployed either on Alpha goerli testnet or in a previous devnet session. either unset it or use the --no_wallet flag with Starknet CLI commands.

[FabijanC]

Also, if I may guess, you aren't using the latest version of devnet. The latest version (0.1.17) offers dumping/loading with which you can preserve a devnet instance set up with an account and load it whenever you want.

[sebastiendan]

Hi, thanks for providing your gateway, pretty cool to be testing on something other than localhost.

I'm suprised that your starknet call command works because it expects --feeder_gateway_url to be provided and you are providing --gateway_url.

Does your contract do any calling by proxy? Also, is your STARKNET_WALLET environment variable set by any chance? If so, you are implicitly running your invokes/calls through an account that was probably deployed either on Alpha goerli testnet or in a previous devnet session. either unset it or use the --no_wallet flag with Starknet CLI commands.

I got from the naming and from my tests that ---gateway_url was used to write (deploy and call contracts) while --feeder_gateway_url was used when reading the state (tx_status).

My contract is the example one from Starknet's docs. As to the wallet, I'm following these guidelines (alpha-goerli network and OpenZeppelin account).

[sebastiendan]

Also, if I may guess, you aren't using the latest version of devnet. The latest version (0.1.17) offers dumping/loading with which you can preserve a devnet instance set up with an account and load it whenever you want.

I'm using docker. I will the latest image.

[FabijanC]

I got from the naming and from my tests that ---gateway_url was used to write (deploy and call contracts) while --feeder_gateway_url was used when reading the state (tx_status).

Yes, and call doesn't write, it only reads, that's why it requires --feeder_gateway_url.

My contract is the example one from Starknet's docs. As to the wallet, I'm following these guidelines (alpha-goerli network and OpenZeppelin account).

Regarding your original issue, did using the --no_wallet flag help? Or running unset STARKNET_WALLET?

[sebastiendan]

Regarding your original issue, did using the --no_wallet flag help? Or running unset STARKNET_WALLET?

Yes, that was it! Can you explain why I needed not to use a wallet?

[sebastiendan]

I can see my transactions are not moving passed the "ACCEPTED_ON_L2" status. Is this because it is outside the scope of the devnet to actually communicate with Starkware's STARK prover?