Can't deposit tokens about bridgel

[bgokcol]

Hey, I saw you closed the issue but feel free to open it again if you think there is something wrong.

[PeerpayCorp]

Ok, I reopened it, because I still think it doesn't make sense. Shouldn't you be able to send tokens to the contract address on both sides of the bridge to give liquidity?

[PeerpayCorp]

This is what happens if I send tokens to both sides of the bridge, then try to do a swap.

[bgokcol]

I think your problem is different, not the liquidity. Because in the deposit process it just transfers tokens from your wallet to bridge contract. Can you provide blockchain explorer links if possible. I can take a look.

[PeerpayCorp]

I'm using private test nets at the moment, so no links sorry. Maybe you can explain how I should be depositing tokens in the bridge, because I think I'm doing it wrong. I basically just sent it from my wallet to the contact address on side B of the bridge, then also side A

Is that not what I'm supposed to do before starting swaps? What is the proper way to provide the liquidity?

[bgokcol]

Let's say you make a bridge for $XYZ. There are $XYZ (BSC) and $XYZ (ERC) versions. To create BSC to ETH and ETH to BSC bridges, you need to deploy bridge.sol to ETH and BSC networks.

After that you need to transfer $XYZ (ERC) (this is what you call liquidity) to ETH bridge contract and $XYZ (BSC) to BSC bridge contract.

I think your problem might be related with the token or configuration in the config.js file. Does your token have any tax or max wallet limits?

[PeerpayCorp]

It turns out my problem was that I was directly sending from my wallet to the contract address. I should have been using the deposit function to send the initial liquidity.

I have to do some more testing, but I think everything is woking now. Thank you.

[PeerpayCorp]

Well, now remix.ethereum.org won't even let me deposit tokens into the contract. I don't know what's going on but I'm tired of troubleshooting this thing.

[PeerpayCorp]

Issue solved. You need to use the deployer private key in config.js. I had switched it during testing and that's why there were so many problems.