-
|
Hello guys, Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
The transaction interacts with a contract, which in turn executed other operations. It isn’t executing a bunch of transactions. The use of the term “internal transaction” is poorly named and should probably just be called a “call” or “calls”. The transaction called a contract, which in turn made many calls to other contracts. That’s just a feature of how contracts work. :) |
Beta Was this translation helpful? Give feedback.
-
|
that means user sends the transaction to the contract and the contract will send some transactions to another contract? |
Beta Was this translation helpful? Give feedback.
-
|
Yes (more or less). :) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you :) |
Beta Was this translation helpful? Give feedback.
-
|
By the way, I have a small question about performance when using ethers.providers.JsonRpcProvider from https://bsc-dataseed.binance.org and from WebSocketProvider of another provider? |
Beta Was this translation helpful? Give feedback.
-
|
If your client makes a lot of requests, you can notice faster performance since queries over websocket resolve faster, but it adds more load on the server. |
Beta Was this translation helpful? Give feedback.
The transaction interacts with a contract, which in turn executed other operations.
It isn’t executing a bunch of transactions. The use of the term “internal transaction” is poorly named and should probably just be called a “call” or “calls”.
The transaction called a contract, which in turn made many calls to other contracts. That’s just a feature of how contracts work. :)