the injected custom warning message

Signed-off-by: Cyrill Leutwiler <bigcyrill@hotmail.com>
This commit is contained in:
Cyrill Leutwiler
2025-12-17 10:34:33 +01:00
parent 8a908374d4
commit 2062bf8711
2 changed files with 5 additions and 4 deletions
+2
View File
@@ -16,10 +16,12 @@ Supported `polkadot-sdk` rev: `unstable2507`
- Standard JSON mode: Don't forward EVM bytecode related output selections to solc. - Standard JSON mode: Don't forward EVM bytecode related output selections to solc.
- The supported `polkadot-sdk` release is `unstable2507`. - The supported `polkadot-sdk` release is `unstable2507`.
- The `INVALID` opcode and OOB memory accesses now consume all remaining gas. - The `INVALID` opcode and OOB memory accesses now consume all remaining gas.
- Emit the `call_evm` and `delegate_call_evm` syscalls for contract calls.
### Fixed: ### Fixed:
- The missing `STOP` instruction at the end of `code` blocks. - The missing `STOP` instruction at the end of `code` blocks.
- The missing bounds check in the internal sbrk implementation. - The missing bounds check in the internal sbrk implementation.
- The call gas is no longer ignored.
## v0.5.0 ## v0.5.0
@@ -113,10 +113,9 @@ impl Error {
let message = r#" let message = r#"
Warning: It looks like you are using '<address payable>.send/transfer(<X>)'. Warning: It looks like you are using '<address payable>.send/transfer(<X>)'.
Using '<address payable>.send/transfer(<X>)' is deprecated and strongly discouraged! Using '<address payable>.send/transfer(<X>)' is deprecated and strongly discouraged!
The resolc compiler uses a heuristic to detect '<address payable>.send/transfer(<X>)' calls, The revive runtime uses a heuristic to detect '<address payable>.send/transfer(<X>)' calls and
which disables call re-entrancy and supplies all remaining gas instead of the 2300 gas stipend. the gas stipend used by the runtime is different from the EVM.
However, detection is not guaranteed. You are advised to carefully test this, employ You are advised to carefully test this, employ re-entrancy guards or use the withdrawal pattern instead!
re-entrancy guards or use the withdrawal pattern instead!
Learn more on https://docs.soliditylang.org/en/latest/security-considerations.html#reentrancy Learn more on https://docs.soliditylang.org/en/latest/security-considerations.html#reentrancy
and https://docs.soliditylang.org/en/latest/common-patterns.html#withdrawal-from-contracts and https://docs.soliditylang.org/en/latest/common-patterns.html#withdrawal-from-contracts
"# "#