#Project title MagnaSim is intended to simulation clients usage of the Magna ecosystem. #Motivation From that simulation we want to obtain different information : - What should be the pricing ? - What should be the descrease rate of token's volume, assuming the current eurostat demographic projections ? #Status __to be done__ *Build status of continus integration i.e. travis, appveyor etc. Ex. -* ##Task list - [x]Population generation. - []Crypto fees : - []BTC fees calculation - [x]simple form - []ETH fees calculation - [x]simple form - []Stellar fees calculation - [x]simple form - []Setting user interface to modify parameters - []Command Line - [x] %transaction fees from MGN #Code style [PEP8](https://www.python.org/dev/peps/pep-0008/) #Screenshots __to be done__ *Include logo/demo screenshot etc.* #Tech/framework used __to be done__ #Features __to be done__ *What makes your project stand out?* #Code Example __to be done__ *Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.* #Installation __to be done__ Provide step by step series of examples and explanations about how to get a development env running. #API Reference __to be done__ *Depending on the size of the project, if it is small and simple enough the reference docs can be added to the README. For medium size to larger projects it is important to at least provide a link to where the API reference docs live.* #Tests __to be done__ *Describe and show how to run the tests with code examples.* #How to use? __to be done__ *If people like your project they’ll want to learn how they can use it. To do so include step by step guide to use your project.* #Contribute __to be done__ *Let people know how they can contribute into your project. A contributing guideline will be a big plus.* #Credits __to be done__ #License __to be done__ *MIT © Yourname*