> For the complete documentation index, see [llms.txt](https://mzf-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mzf-protocol.gitbook.io/whitepaper/overview/leadership-team.md). # Leadership Team ### Team #### Jerome Dadon – Co-Founder and CEO Jerome Dadon is an experienced funds manager, property developer, seasoned entrepreneur, professional cryptocurrency trader, and early adopter of Web3. With a background in commerce and finance, Jerome spent several years as a Funds Manager, involved in managing assets and assessing deals worth more than $200 million. From there, Jerome explored his own property development opportunities, as well as numerous and varied personal Mezzanine Finance deals. Choosing to walk his own path, Jerome’s entrepreneurial ambitions were also channelled into Brother Thomas, his café and wholesale coffee business. During the disruptions of COVID-19, Jerome devoted his time and financial acumen to cryptocurrency trading, in the process developing his understanding and expertise in blockchain, non-fungible tokens, and the world of Web3. It is through the culmination of Jerome’s experience and specialisation in finance, property, and Web3 that the idea for MZF PROTOCOL was born, occupying the sweet-spot between highly targeted skills and visionary thinking. It’s Jerome’s goal to use the decentralised power and principles upon which Web3 is built to bring hitherto unimagined levels of accessibility and transparency to an aspect of traditional finance previously reserved for elite, high net-worth investors. #### Jarrod Pyne – Co-Founder & CFO Jarrod Pyne is the Chief Financial Officer at MZF PROTOCOL, where he applies a powerful blend of legal expertise, institutional-grade investment analysis, and strategic execution to originate and manage high-quality credit opportunities. Jarrod began his career as a corporate lawyer at Norton Rose Fulbright, one of the world’s leading law firms, where he advised on complex cross-border transactions and structured finance mandates. Notably, he served as both lawyer and project manager on one of the largest cross-border M\&A deals in Australian history — coordinating multidisciplinary teams, navigating high-stakes negotiations, and delivering outcomes under intense regulatory and commercial scrutiny. Motivated to transition from legal advisory into capital deployment, Jarrod moved into investment management and is a CFA Level III Candidate. His approach integrates deep legal and structural insight with rigorous financial modelling and portfolio construction, focusing on risk-adjusted returns across mezzanine and opportunistic credit strategies. At MZF PROTOCOL, Jarrod leads the acquisitions function — sourcing, structuring, and executing deals across private credit markets. He is instrumental in developing and refining the firm’s underwriting frameworks and investment theses, helping to shape the strategic direction of MZF PROTOCOL’s capital allocation. Jarrod brings to MZF PROTOCOL a unique perspective that spans both the legal and financial dimensions of private markets. His ability to see deals from multiple angles — legal, structural, and investment — makes him a key driver of the firm’s disciplined and high-conviction approach to alternative credit. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mzf-protocol.gitbook.io/whitepaper/overview/leadership-team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.