Skip to content
This repository was archived by the owner on Jul 14, 2025. It is now read-only.

Conversation

Thatfocker
Copy link

No description provided.

skmgoldin and others added 30 commits July 20, 2017 08:56
Ignore environment test contracts
Make non-state-changing methods in Factory constant
This is not the fancy Simon-approved way of checking for throws.
However. In a few short weeks the reverts we have in place will return
real error messages to Truffle and then we'll be able to make small
changes to this script such that checking for reversion in this way
won't be at all hacky, but in fact proper.

I don't want to go through the complexity of testing exceptions in the
more rigorous way when Metro will be out so soon... And really this
is only slightly hacky.
The solidity compiler throws by default if no fallback function is
specified.
Change return falses and throws to reverts
This enables people to run npm install and truffle from the base directory, which IMO is more common.
Clean up dead code, since infura doesn't support morden anymore
* Moved the funny quote to look a bit less out in the middle of nowhere
* Links for convenience
* Clarify how to contribute
* Update README.md

* Moved the funny quote to look a bit less out in the middle of nowhere
* Links for convenience
* Clarify how to contribute

* Update README.md

* Test async await (Consensys#71)

* Rewrite tests with async/await

* Rewrite tests with async/await

* Move helpers to utils.js, remove todos

* add blank lines between sub-tests, refactor the normal ether transfer test

* Await test result
maurelian and others added 29 commits January 10, 2018 14:51
The verifyEIP20 function does two checks to assert whether the code at a
given address is known EIP20 code. In the first check, it simply
compares the length (in bytes) of the code at the provided address to
the length of the known EIP20 code. If that check passes, it would then
iterate though the code at the provided address byte by byte and compare
each byte to the known EIP20 code, returning false if any byte did not
match.

A run of the linter initially committed at
a783747, the `return true` statement
which had come after the byte-comparing for loop was moved inside the
for loop such that if the first byte compared was matching, this
function would return true even if the rest of the bytes did not match.

* Move verifyEIP20's `return true` statement to after both check have
  completed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.