So after my conversation with Gene about the Windows client, why they made the choices they made and what could be done to improve it (and a few things that I was wrong about in terms of specific behaviour), I decided to create a community project to commission the development of an enterprise ready Windows Chia software suite and client.
What the project is:
- I will donate the first 1 XCH to the project wallet and I am hoping the community contributes more in order to incentivize excellent development on something I think is important for the longevity of the project.
- Anything in the wallet when the client that meets the requirements spelled out in the next section up to 25 XCH will be paid to the developer. If for some reason there is more than 25 XCH in the contest wallet the next 10 XCH (26 – 35) will be held back to fund support and bug fixes for the secure client. Anything over 35 XCH in some insane world would be used to fund other worthwhile infrastructure software projects for the Chia blockchain.
- I will be the sole judge of whether something meets the requirements. I will also hold the funds. I am open to better suggestions on this. The more money involved the more open I am to better solutions.
- It runs as long as it runs. Hopefully not long.
- If you are already underway doing something like then congratulations! You have a big head start. No disqualifiers.
- It must survive strict scrutiny.
- It must be open source.
- It must use the Apache License 2.0.
- If you use the Chia Network trademarks you must secure a license. I can assist with this. Save the jokes about irony.
- It must use completely self contained services for full_node, wallet, harverster/farmer and gui
- Gui must be web based, nginx or iis
- Services must run as separate users
- Configuration for each service must be separatable with no access by default to each other services configuration. Each service should be able to run on a separate VM with single-port access to the other services.
- Web services must be secured with tls client/server certificate auth (or remain secured by certificate auth)
- Certificates must be stored in the user personal certificate stores for each services user
- Private_ca should be signable by enterprise PKI or certificates should be manually deployable. BYOK.
- Web gui should support at least one modern federated authentication protocol. Preferably bearer based.
- Support multiple users with strict auditing
- Support syslog event generation
This is a short list, and there are others. I would really like to see this is a real alternative for the Linux client, which the Windows client currently is not. If you would like to work on this project but aren’t comfortable just building this please reach out to me on the site, by email or on discord. And please, donate to the fund. This won’t be cheap.
Contest Wallet: xch1hew8r5fw70fv6rlk5ur4axlsjzkl4d5uy4d6lj8fme3t5mvwuacq37kgff