Currently developing an eosio based token with some semi intricate business logic that frequently modifies aspects of the token contract( staking, supply, etc ) based on a variety of factors including incoming on_notify ( eos.token ) transactions. Assume it's similar to an exchange contract where you send some of token a in exchange for token b.
Which is more likely to be accepted/considered for listing on an exchange ( dex || cex ), which is more desirable for another dev to review, & which is best from the perspective of a user/hodlr?
a) Two Contracts: Stand alone token contract && stand alone business logic.
b) One Contract: Token with business logic included.
c) Too many moving parts, it depends.
As it stands, I have everything bundled under one contract. But I'm thinking two separate contracts would be more desirable ( assuming the token contract would carry permissions from the business logic contract ).
Any tips on contract security audits, expectations, and/or 'general' costs associated with it?
