Feature/master collateral pool

[0xean]

Description

Quick and dirty POC of a master collateral pool

In this implementation - each Factory has its own Collateral Pool, that all contracts feed into that are created from that factory.

Pros of this approach

• significant gas savings for deployment of new contracts, however we can further reduce this I believe relatively easily but want to avoid premature optimizations.
• single transaction to deploy a new MarketContract! simplifies our lives in the UI of the dApp
• Collateral deposited in a single collateral pool, can be used with ANY MarketContract that is created by the factory. This is a far superior UX to having collateral spread across many contracts. For example, if I deposit WETH, I can trade ALL contracts now denominated in WETH!

Cons of this approach

• Collateral for all contracts is in a single place, bigger target.
• Cannot implement per contract functionality for some owner to be able to provide some specific functionality with contracts they have deployed.

[coveralls]

Pull Request Test Coverage Report for Build 533

• 38 of 39 (97.44%) changed or added relevant lines in 5 files are covered.
• 4 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.2%) to 55.608%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
contracts/oraclize/MarketContractFactoryOraclize.sol	0	1	0.0%

Files with Coverage Reduction	New Missed Lines	%
contracts/Linkable.sol	4	0.0%

Totals
Change from base Build 518:	-0.2%
Covered Lines:	359
Relevant Lines:	603

---

💛 - Coveralls