Here's the summary of this week's Tech Issues AMA. 1.) MTVs websocket (wss://websocket.mtv.ac) seems to be configured to only accept incoming connections from 'localhost', which means I can't acess it on my service frontend (using a browser). Is it the expected behavior? Is there any way I get access rights from a different origin? Shawn: We have responded to your question by mail. However, we need to disclose our answer: our websocket server rejects users from cross-site requests for safety reasons. If it is really necessary to request on-chain data on the client side, I recommend using the RPC server instead of directly connecting to the websocket server by initiating client requests on the browser page, which may have greater security risks. The same goes for Ethereum's default settings. The websocket server is only for server-side applications. However, if you think it is really necessary, you can contact us to ask for an archival node, and you can set up this node for your users to connect to. relevant link: https://github.com/ethereum/go-ethereum/issues/16608 2.) Will we get a blockchain Explorer like etherscan, bscscan and ftmscan? Shawn: We are still in communication with the etherscan team, but their offer is way above our expectations (millions of dollars per year) and is currently very busy and has not been able to work with us in recent quarters. We are still striving for the possibility of further cooperation. Additionally, our community is building new browser projects that are expected to provide more functionality. In any case, we are working hard to build a new explorer and are committed to providing a better on-chain application experience for everyone. 3.) Some people told that the whole MTV network runs on one server. Into the last AMA you told that the network will add automatically so many nodes as needed. How many server you have ready for this and are they hosted at different locations? Shawn: We have thousands of nodes running on hundreds of servers spread across Asia, North America, Europe. We have used many different cloud service providers such as Google Cloud, Amazon EC2, and Alibaba Cloud. MultiVAC's network can resist force majeure such as earthquakes, storms, tsunamis and other regional natural disasters. To say we only have one server is really ridiculous. Just an insult to us. 4.) As per last questions, it was stated that the gas limit for a single transaction is about 4 million which limit it to ~480 transfers per call & increasing this will increase the size of a single block, affecting broadcast speed. Is the broadcast speed determined by gas per block or net gas of total blocks (all shards)? (i.e. do 10,000,000,000 blocks with a blocksize of 1 process faster than 1 block with a block size of 10,000,000,000). Shawn: The more gas a single block has, the larger the block may be (but this is not absolute). The larger the block, the more time it takes to propagate. Just like the difference between BCH and BTC, the block of BTC is only 1MB, while the block of BCH can be very large. For a block generation period of 10 minutes, a slightly larger block is fine. But for the 3-second MultiVAC network, once our block is too large, when the entire network is completely decentralized in the future, it may become a problem whether our miner node can receive the block in time. I think at this stage we are confident to increase the gas limit of a single block, so that a single contract can run more content. However, we still make this decision cautiously, because it is not necessary to do so at present, but it may bring risks.