Plugin doesn't support dynamic fee transactions? [APE-623]

[PoCk3T-SPAI]

Environment information

• ape and plugin versions 0.6 - all from ApeX/ape:latest Docker image + ape install --upgrade bsc

What went wrong?

Please include information like:

• what command you ran

  with networks.bsc.testnet.use_provider("geth") as provider: 
  account.deploy(project.MyContract)

• full output of the error you received:

  INFO: Connecting to existing Erigon node at 'https://rpc.ankr.com/bsc_testnet_chapel'.
  WARNING: There are no token lists installed
  ValueError: Default token list has not been set.
  (Use `--verbosity DEBUG` to see full stack-trace)
  Using cached key for 'dev'
  ERROR: (VirtualMachineError) (-32000) dynamicfee tx is not supported by signer Signer[chainId=97,malleable=false,unprotected=true,protected=true,accesslist=false,**dynamicfee=false**

How can it be fixed?

• I've tried 3 different RPC endpoints, the one of Ankr is based on Erigon and provides the detail seen above in the ERROR message. Other RPC endpoints (Binance.org & BlastAPI.io) only mention invalid sender
• If I understand correctly, the "signer" is ape and somehow the way the requests to the RPC are formatted end up triggering this part of the RPC endpoint
• Is there anything missing in this plugin that would bring back compatibility with BSC nodes?

[fubuloubu]

For this one, type=0 kwarg with your transaction should get it working for you (e.g. account.deploy(project.MyContract, type=0))

[PoCk3T-SPAI]

That works, thank you @fubuloubu ! Closing, hope it helps other users if they face an invalid signer or dynamicfee tx is not supported by signer error

[fubuloubu]

Gonna reopen the issue because there's still a problem here, if BSC doesn't support eip1559

[PoCk3T-SPAI]

Oh sorry, I didn't know I should keep it open.

Further help for anyone else using this plugin, as far as I could experience so far: Not only the type=0 parameter needs to be set for deploy, but for any other existing contract interactions as well