I am sorry but either this explanation of burner connect is bogus
or it is a really bad idea in many ways
1. The Blockchain is always involved in a transaction (if you know how cryptocurrencies work you might understand why)
2. this does not add any kind of anonimity
3. it requires you to trust the sender since he created the wallet address and could be keeping the priv. key to tranfer the coins somewhere else before you have a chance to do so
4. why not just create the wallet on the receiver side. Would be more secure (no priv. key over the wire, even if its ssl encrypted) and trustless (burnerconnect seems here like a complicated way to achieve a simple thing)
You and everyone else are making assumptions. The dev has not gone into details and gave a simple explanation.
1. The Blockchain is always involved in a transaction (if you know how cryptocurrencies work you might understand why)
If the client is sending the wallet.dat or something similar, technically it is avoiding the blockchain. If I create a wallet and put 50 burnercoins in it, and then I email you that wallet, there is no trace of me sending you that 50 burnercoins in the blockchain.
2. this does not add any kind of anonimity
That depends on what he is doing before he sends the file.
3. it requires you to trust the sender since he created the wallet address and could be keeping the priv. key to tranfer the coins somewhere else before you have a chance to do so
That is if the users has access to that information. Maybe the dev is encrypting the file.
4. why not just create the wallet on the receiver side. Would be more secure (no priv. key over the wire, even if its ssl encrypted) and trustless (burnerconnect seems here like a complicated way to achieve a simple thing)
Think about your solution, that wouldn't work.