Cloning POA

[j0xhn]

Title

  Title: Cloning POA
  Layer: Discussion

Abstract

Our team will create one of the first Clones of POA Core Network honed for our community. This Clone will run under the POA Model and codebase, as well as adopting a few of the trappings of the Dash system. As we gain significant attention from the dash community, we plan to use the POA Network tools to build a bridge from our Clone to the Dash network. This would be our second bridge, with our primary bridge (and route to the global financial markets) connecting with the POA Core Network. Some Configuration modifications on our Clone blockchain may include:

• staking in order to be a validator -- similar to dash's master node system, except we would ask Validators to provide Stake prior to be considered as a Validator

• mining rewards to be shared between the miner and a shared escrow account that validators vote on how it is used

Since our Clone network relies fully on the POA Codebase and only requires certain configuration and branding changes, what is the best management strategy to maintain consistent underlying POA Network code based and our branded clone with? Would this best be served with a playbook strategy to overly certain config files from the default? Is it recommended to create a fork of the POA repository and maintain 'even number' or similar pulls, or for consistency should our Clone Repo contain only the branded configuration environmental variables/ files/ scripts while referencing the PoA repo's software directly?

Thanks very much! We look forward to supporting both our target community and the entire POA Network Universe. If another form or channel is better suited to hold this conversation please let me know :)

[j0xhn]

Also, is the website POA uses for their landing page open source? I'd love to throw something up for the clone to gauge interest and have it keep some of the POA branding elements. Is that encouraged or is it preferred that each clone brand themselves individually?