Compulsory KYC for all L1 developers

3rd-party KYC is set to become compulsory for all developers who create code for the chain. Currently, anybody can supply code anonymously, posing a serious risk to the blockchain. Examples: A trojan could be inserted to compromise the chain. Deliberate harm could be inflicted to take advantage of a short position. This initiative aims to provide the community, investors, and utility providers with confidence that we do not have completely anonymous development teams working on the chain. It assures that legal recourse would be available if necessary, with details accessible only through the correct legal channels. Arrangements have been made with a 3rd-party company, Solidproof, to perform KYC at a cost of $100 per developer. Each developer will be responsible for making contact with Solidproof, payment & completion of the KYC process, obtaining confirmation from Solidproof before any code is merged. An agreement has been made for all personal details to remain confidential, with only the screen name being disclosed. It is the responsibility of the developer to clarify that their KYC is for the Luna Classic chain, with all details to be kept confidential except the screen name. Solidproof Requirements: Passports (Front/Back) including a self-portrait. Personal address. One invoice (electricity, government tax, etc.) for address verification. Live Zoom call to verify documents, including SMS for phone verification. Verification of identity through random requirements. What Solidproof Will Provide After Successful Verification: KYC certificate. Solidproof badge for announcement. KYC data storage held offline on an AES-256 encrypted disk. Profile on Solidproof SAAT. Announcement across all Solidproof channels including KYC certificate on Github using the screen name only. Average Completion Time: 48 Hours KYC Requirements: KYC will be a requirement for all team members working on Layer 1 coding, regardless of whether paid through a community spend proposal or working on a voluntary basis. No pull requests are to be submitted or any code merged until KYC is successfully completed and confirmed publicly by the KYC provider for ALL members who have worked on the code. Only governance-passed KYC providers will be recognized for this process. To add an additional 3rd-party KYC provider, a governance proposal will be required to pass. KYC from additional 3rd party providers must meet or exceed the specifications outlined above. Addressing Concerns: "I don't want to be doxxed; it poses a serious risk to myself & family!" This is not doxxing; no personal details will be made public. "KYC goes against the fundamental crypto spirit." No, it doesn't. Research on the top 20 crypto projects shows that all developers are either KYC'd, fully doxxed, or have an extremely robust review process for third-party developer code. LunaClassic is in a fairly unique situation without the teams in place for thorough code review; a KYC process would provide some level of accountability. "This will limit the devs available to work on the chain!" Great, we only require professional developers who should have no problem with a simple KYC process. There is no reason not to KYC unless there is malicious intent. Many developers have publicly stated they would be happy to KYC, including Genuine Labs, Tax2Gas Team, and others who have already completed KYC. "SOMEONE would be in charge of handling and coordinating the KYC pipeline!" No, they wouldn't. KYC will be directly between the developer and the 3rd-party KYC provider. Link to the original Commonwealth discussion: https://commonwealth.im/terra-classic/discussion/12545-compulsory-kyc Cosigned by: Axiom Consortium, DNC, Lunanauts, LVS Node, Mazaltech, M Van S, NaatiePaat, Nueng Handsome, Pink Unicorn, Rostrum, SolidVote Validator, Vivid. Vote "YES" if you would like every developer to complete the KYC process. Vote "NO" if you do not agree and want developers to remain anonymous. Vote "Abstain" if you are unsure or have no opinion either for or against. Vote "NO WITH VETO" is non-applicable.