5. Marketing & Outreach: a. When is the Kraken Crowdloan reward distribution? i. Kraken, like all other participants, is in a position to claim their rewards currently. However, they've brought to our attention some unique requirements. Specifically, they cannot claim rewards using the conventional UI or Web wallet methods because their signers operate offline in an air-gapped environment, which limits the types of extrinsic signatures they can process. ii. In response to their needs, we've proposed a solution to them. While we're awaiting their feedback, it's essential to note that if we're to develop a custom solution exclusively for Kraken, it might face some delays. Our tech team is currently operating at full capacity, attending to a range of tasks. Thus, any bespoke solution for Kraken would be prioritised once our existing workload is cleared. b. What are your plans with the Ambassador Program? i. We genuinely value our Ambassador Program and the enthusiastic individuals who have come on board to support Polkadex. During the initial phase when the Polkadex Orderbook was in its pre-release stage with no pairs and limited functionality, the scope of the Ambassador Program (PAP) was understandably restrained. Still, it was heartening to see the dedication and effort many put in, and we are thrilled to have them as a part of our growing community. ii. Now, as we progress with listing pairs on the Polkadex Orderbook and enhancing the UI/UX, the horizon for our ambassadors is expanding. We have charted a clear roadmap, outlining specific roles and responsibilities that our ambassadors can undertake. Moreover, to ensure our collective efforts remain aligned with Polkadex's vision, we have established KPIs that will guide and measure our progress. We're excited about this next phase, and we'll be sharing more detailed updates in the upcoming weeks to keep our community informed and engaged.

h. Could the team separate the accounts for the operations and other purposes? i. Yes, based on the inputs we have received in the past few weeks, we have decided to separate certain expenditures into dedicated wallets to enhance transparency in the process. Our approach will now consist of a monthly rebalancing routine, wherein tokens will be systematically moved from the primary team's wallet to designated wallets tailored for specific transactions or purposes. ii. However, in the interest of preserving Non Disclosure Obligations, stability and preventing any undue speculation, we refrain from publicising transaction-by-transaction details. It will be revealed only at the time of the public audit. 4. Team & Governance: a. How many developers are actively working on PDEX? Are there plans to expedite development through additional hires? i. There are five developers, two designers, one project manager working on the product development full-time. Hiring more engineers will not make the process faster as it is an iterative and sequential process as there are third party dependencies. b. How can developers and builders contribute to the Polkadex Orderbook? i. We will be rolling out a systematic bounty program to engage developers from the ecosystem in contributing to the project. Currently, we are in discussions with the council to finalise the details of how this plan should be implemented. This initiative will be led by someone from the community. c. What’s the plan with the DAO? When do you plan to implement it? i. Implementing the DAO will ensure that every expenditure from the treasury is subject to legal audits under recognized international law. We are currently in discussions with our legal advisors to identify a suitable jurisdiction for registration. Switzerland appears to be a long-term viable option. However, the final decision will be made once the protocol side is stable. We are waiting to ensure the protocol is stable and secure enough to remove the sudo keys and pass control to a technical council. Once that is complete, DAO implementation can coincide with this process. d. How would the licence that polkadex (Estonia company) acquired work when it's a DAO? i. The Estonian company will be necessary to continue the developmental activities of the network. The company will also focus on the following: 1. Building a talent pool to work on Polkadex. 2. Developing Value Added Services on the network to offer to enterprise and business clients. 3. Providing services that require EU licensing. 4. It will collaborate directly with the council and the DAO to meet all future technical and developmental needs. As the pioneers who built this chain, we have an obligation to continue supporting the network even after the protocol side of the project transitions into a DAO. e. When is the next AMA to update the community on the plans? i. As part of our initiative to stay connected, we're thrilled to introduce our AMA series. Our aim is to conduct these sessions ideally once every month, but you can certainly expect one at least every 6 weeks. These platforms will serve as an opportunity for us to delve into our achievements, address challenges, and illuminate our path forward. We eagerly anticipate these insightful exchanges with our community. f. Do you have any comments on the previous AMA and the way it turned out to be? i. We appreciate the feedback from everyone during the AMA. Our main goal was to foster a constructive and respectful environment. We understand the concerns raised by some, and while we felt the need to step in when the discussion seemed to go off track, we always welcome constructive feedback and are open to listening to all perspectives. Let's continue to collaborate and work towards a more respectful and inclusive conversation.

f. When does the team plan to provide an audit report on the team’s wallet and what does it signify? i. Our aim is to seek a reimbursement for the tokens used from the team's allocation to fund the project, as mentioned. This report will be made public before removing the Sudo-key.If we continue to conduct a public audit for every decision we make today, it will significantly slow down our execution and should only be initiated after the project is handed over to the DAO for further scaling and growth. If we initiate a public audit now, it will require a full-time auditor, and while it can be done unofficially, that resource is best allocated as part of the DAO formation. At that point, it will have the proper backing of a recognized jurisdiction and its laws governing that process. g. For what purposes does the team use their wallet? Why not ask the on-chain treasury? i. As mentioned, primarily so far it has been used to distribute the vested investor's token raised from the team allocation. Also, for advisory andteam compensation, as well as to engage with strategic partners on both short and long-term collaborations. These collaborations often include audits, and services from vendors – all of which can be time-sensitive and require a degree of discretion to ensure smooth operations. Additionally, these tokens were part of the funds raised previously, and their vested payouts are still ongoing and have not yet been completed. Hence, they are a part of the project's obligation and should be fulfilled without requiring any additional vote or consensus. ii. Historically, while the on-chain treasury is a valuable resource, its decentralised nature posed challenges for swift and discrete transactions, especially when time is of the essence. However, recognizing the importance of decentralisation and community participation, we've recently begun directing vendors and partners towards the on-chain treasury for their engagements. Service providers like CoinAlpha, Subscan, GSR, CoinDCX, Simplex, Onfinality, and Subquery, among others, are now actively interfacing with the on-chain treasury for transactions. Our discretion is currently limited to development decisions and engagements that have been previously committed to. iii. Our aim remains to strike a balance between efficiency and embracing decentralised principles, always keeping the project's best interests at heart. The transition from a fully centralised to a decentralised governance is not always black and white. What you are witnessing is the transitional phase.

i. Establishing an HFT infrastructure, especially one that integrates Thea as a native connector to all L1s and L2s within the Substrate framework, is indeed complex. We acknowledge that our initial capital estimations were off-mark. Having said that, HFT infrastructure was already a part of the initial capital estimates, while Thea connector was not. Initially, we thought of utilizing available connectors in the Polkadot ecosystem. However, none of those projects were able to deliver exactly what we wanted to provide the UX we were looking for. Therefore, we utilised the team allocation to push the project to its current stage of development, believing that accessing the on-chain treasury during pre-release wasn't in the best interest of our community and backers. c. Does the team have the capital to scale and operate the Orderbook? i. At Polkadex, our commitment has always been to transparently and responsibly pave the way for a robust community driven Orderbook DEX. When we secured the $6M funding, it was earmarked for this foundational work, ensuring we had the tools and systems in place. But accurately predicting operational costs for running a platform like the Orderbook is challenging, especially when it involves an R&D of this scale. These costs become clearer as the platform scales and encompasses factors such as liquidity provisions, licensing, servers and integrations, among others. That's where our strategic tokenomics comes into play, our tokenomics — which can be reviewed here — ensures that over 50% of the Total Supply (T.S.) is strategically allocated to on-chain treasury. This isn't just a financial decision; it's built in tokenomics. Rather than taking a more conventional route which is allocating single digit T.S to the on-chain treasury, like some of the existing DEXs, we chose a path that champions community engagement. By doing so, we've created an avenue for our community to have a say in our shared future. With the on-chain treasury as a backbone, independent contributors, teams such as us and many others will continuously refine the Orderbook and introduce innovative offerings, such as Thea and other financial tools/instruments built on top of the Polkadex Orderbook. d. Are there any funding gaps, how significant is it, and what are the plans to close this gap? i. No, there are no funding gaps, as mentioned we've been fortunate to have the backing of strategic investors, and their continued support ensures that we're on track to launch the OB and Thea to the public with the vision and innovation that Polkadex stands for. e. What is the difference between the ecosystem and the team's wallet and what are they used for? i. The ecosystem wallet is the on-chain treasury, which held ~8.5M PDEX tokens governed by the token holders with 80% community representation in the on-chain council (4/5). The on-chain treasury has a pivotal role in growing the ecosystem by supporting network participants to contribute to the protocol and its dAPPs, and that's why, according to the tokenomics linked here, it had 50% of the total supply. The Polkadex team does not control this, and neither have any ownership of it. The community has the final say in the utilisation. As there is an evolutionary arc to decentralisation, the team has gradually removed its representation from 100% to 20%. Any treasury expense can go to a public referendum to support or object to the proposal. ii. However, the team's wallet is represented by this account linked here. It is governed by the team and to be utilised at their sole discretion, as it represents the team ownership of the network, according to the tokenomics linked here. As mentioned, the allocation so far has been majorly used to fund the project keeping in mind the best interest for the protocol. After a public audit, any such amounts spent for building equity value to the network, needs to be returned to the team from the Treasury.