vird

Results 60 issues of vird

https://solidity.readthedocs.io/en/v0.4.24/units-and-global-variables.html https://solidity.readthedocs.io/en/v0.5.0/units-and-global-variables.html We should support or explicitly say that it unsupported **Address Related** * `.balance : uint` * `address(this).balance` * `.transfer(uint256 amount)` * `.send(uint256 amount) returns (bool)` * `.call(...) returns...

https://solidity.readthedocs.io/en/v0.4.24/units-and-global-variables.html We should support or explicitly say that it unsupported **Contract Related** * `this` * `selfdestruct(address recipient)` * `suicide(address recipient)` Intersecting with #33

Old-style with reentrancy vulnerability * `msg.sender.call.value(42)` * `msg.sender.call.value(1 ether)` * `msg.sender.call.value(1 ether)("register", "myName")` * `msg.sender.call.value(42)()` * `msg.sender.call.value(42).gas(2300)()` Safe way * `msg.sender.send(42)` (don't throws if failed to send) * `msg.sender.transfer(42)` (...

Checked `pragma solidity ^0.4.0;` Checked `pragma solidity ^0.4.10;` Checked `pragma solidity ^0.4.11;` (works, but need recheck for other issues)

We should warn user that after compilation this address would be not valid and contact needs to be changed with proper tezos address

* Code style * How to test * Keep code coverage * Future proof code * Ligo is not only 1 target language

This MR makes user experience really bad because instead of focusing on typing, I'm focusing on words which nobody ever uses in texts https://github.com/aradzie/keybr.com/pull/344 Theoretical "dictionary correctness" totally doesn't match...

- [x] tests and linter show no problems (`npm t`) - [ ] (NOT NEEDED) tests are added/updated for bug fixes and new features - [x] code is properly formatted...