The tests are run in a docker container to ease the portability.

	* Stop raising errors when OP_ROLL is used

	* Testing timeout raised to 30 s
	* Bug fix for RIPEMD160 which can no longer be imported from
	  hashlib
	* Bug fix: some scripts were badly parsed when no else clauses
were present

	* Bug fix in case the memory is not symbolic

New testing scenario for symbolic execution

This reverts commit 1cd54fe9.

	It is possible to reverse them thanks to mempool sniffing

	* Fix- The number of bytes to push onto the stack was incorrect.
	  Example: a0 should be interpreted as 160, not -32

	* Remove constrain on operand size for OP_CHECKLOCKTIME and
OP_CHECKSEQUENCE
	Some scripts were marked as unsatisfiable while they are, e.g. :055707ce7fea7b9776fdc70413f65ceec413d46344424ab01acd5138767db137

	* New value for the enum Satifiability: Satifiability

	* including a few scripts that are marked as unsafe, while they
	are not. -> Needs a fix

	* Typo in ram: the symbol for the size should follow the naming
	convention of the values.
	* OP_IFDUP: if the top item is False, keep it on the stack
	* If the script is malformed because of an OP_IF, raise an
	error.
	* OP_CHECKLOCKTIME/OP_CHECKSEQUENCE: The top item was dropped.
	* Fix for consecutive OP_ELSE

	* Set a timeout for the symbolic execution
	* More tests for the symbolic execution

	* Optimizations:
		* Enable packrat
		* Use MatchFirst instead of Or
		* Increase recursions limit

	* Proxy to support multisig op. Always return False.
	* Bug fix for unreachable block when OP_RETURN and OP_VERIFY are
used

	* Fix: Reversing a hash function should always be considered as
imposible. The fix consists into parsing the ast tree in depth.

	* Tests for symbolic execution

	* Fix signature constraints: enforce throught the constraints
	that it's not possible to find a valid signature for a given
	pubkey

	All operands are passed at once to the constraint function.
	It allows to create different conditions based on the order
	of the operands.

	Example: for the division, only the second operand
	must be != 0

	* Clean the way hash fucntions are represented
	* Add a util function to interpret the results

	* Now the operators really compute the hash if a known value
	  is passed to the operator. On the other hand, if a symbol
	  is passed, a symbol is returned.

	* False is encoded over 0 byte. The operators were returning
	  a value encoded over 1 byte.

	* Different memories should generate different symbols.
	* During a merge, entries from the other memory should be
	  "deepcopied"

	* OP_FALSE is supposed to be different from '00'

	* Integers values are represented in little endian format.
	* Moreover, BTC does not use two's complement representation.