Thank you for taking some time to read the question. So, I ran several tests, sending without waiting for completion and sending one by one, only after the previous transaction was finished. In both cases, reorgs still happen on the parachain, and therefore, all extrinsics in that block are discarded and temporarily banned. I don't know what causes these constant reorgs, and I'm not sure if it’s normal to lose all the transactions within that block, but these reorgs always happen even when I'm not sending anything to the parachain. Any ideas?

is there a way to improve or be sure that your parachain will not produce forks or reorgs? Like, increase the number of validators or collators in your network, improve the latency, or something else?

I'm having the same problem here. Is there one version 1.09, 1.05 or lower where we don't have this issue? Or how to avoid these forks or prevent these transactions from being rejected?

@Purple_Turtle hey, have you found a solution for this --rpc-cors problem? Because I tried a long time ago to use this flag and it wasn't working when I specified the domains

Thanks, for your answer Alex. So, every time I want to make a new transaction do I have to call keyring.addUri(seed, password, options) in order to sign a transaction? Isn't there an unlock function that only needs the password? Because there is a boolean "unlock for 15 mim" when I enabled this bool I don't have to type my password during this time

In this example, I'm using a wallet created by Polkadot UI. This account is already in my browser. Every time I try to make a transaction using the Balance pallet this modal appears asking for my password. I'm trying to simulate this same process using PolkadotJs API.