# Expensive Servers ## Description The network run the servers which can become expensive for the user based on the demands, usage and availability. In this case, to maintain the users the following plans and ideas can be useful. Also, the point of contact to understand the issue is listed in this section. ## Mitigation Ideas 1. Increase liquidity to bring value to the token. 2. Run a node with less demand, Find a way for it. 3. To avoid compilation, provide the binaries of witness\_node and cli\_wallet. 4. Create best practices to build cost effective nodes 5. Have Periodic sync-up with other witnesses to learn about the ways remain economical. 6. Static-linking of libbitcoin 7. Publish minimum requirements to witnesses to maintain the standard spec across the platform. 8. Provide the Personal Package Archives (PPA) on ubuntu. ## Response Plan 1. Increase witness / SON pay ## Responder Team In order to find the solution/ to know in details about the risk that has happened, responder team is one to be communicated first. ### First Responder Team **Point of Contact:** DOCS Team ### Second Responder Team **Point of Contact:** Dev Team (For Static Link / PPA) --- # Agent Instructions: 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: ``` GET https://community.peerplays.com/risk-register/introduction/core-block-issue/expensive-servers.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.