Say, whenever A is sending B a TX in contract M, C will be sending D a TX in contract N, by listening to events on M.

Yeah quite possible. M should emit an event and a listener listening on this event can initiate a transaction on N

Well that's the basic principle of oracles

Any reference on this specific topic?

I think Julian have a video on it. Not oracles, the event listening and triggering new transaction

check liquity protocol.. they provide loans in LUSD (stable coin) thorugh ETH as collateral (110%).
and uses chainlink oracles, if price of eth decreased suddenly then they liquidate positions automatically.

Thanks, @mark123mark . This is very relevant.

Haven't seen their code yet. But it isn't hard to implement though

You cannot manipulate the ether value while calling function, but if it is via some website, then possible

no they are saying that they charges 2 bnb and take it in a pool they own. something like this

You have a link to their contract?

sure 1 sec

https://bscscan.com/token/0x68590a47578e5060a29fd99654f4556dbfa05d10

Yep they have that check

You cannot transfer amount > maxtxamount without paying 2 BNB

yes but they can't take it

If people want to transfer that much, they have to pay 2 bnb

Using that disruptivetransfer function

right?

Which can easily be bypassed making 2-3 transactions🙃

I'd say that function exists only for the stubborn people

You can simply make some number of transactions to achieve same result by paying only a fraction of that 2 BNB as fee

ahahah yes lol

do you agree?

I mean they can't take those 2 Bnb and put in a "pool" they hold

They cannot force the amount yes, but the thing about pool and claim seems true

nono wait that yes is true

but they say this

That, also is true. Because they haven't mentioned that 0.01% in a single transaction. If you are making a single transaction, you must use disruptivetransfer and send that 2 BNB alongside

What?

this 2 bnb won't go in the pool
just gas fees

Mm no, it is taken as msg.value

then?

Stored in the contract. So the 'pool' here is contract itself. When people call claim, the bnb is being sent from contract itself

Ohh alleluiaa ahahah

this is what I was searching

I will continue to test
thank you

And their claimbnb logic is faulty. Anyone with some good amount of token and skill can easily drain the whole pool🙃

let's try😂😂