After consulting with devs here is the answer to your questions:

getauxblock returns ChainID. In case of Crown it is  "chainid" : 20

Any other MM coins that have a conflicting chainID can not be merge mined together.

The problem seems to be specific to these two mentioned examples, probably because of same chainid - would be awesome if you could check if it is also "20" - and thus is not a general MM problem caused by Crown code mining.

the code relevant to auxpow mining is to be found here https://github.com/Crowndev/crowncoin/blob/master/src/primitives/pureheader.h

Here is an (old) list of chainIDs https://bt.irlbtc.com/view/769073.0

Crownfan

Note that a potential issue with that is IPv6.  From all thrones listed by my node currently, all with IPv6 address belong to the same64.  It depends on the hosting company, but AFAIK, it would fit well to the design of IPv6 if a hosting company provided individual customers with such a range to use by default.  In other words, with IPv6 you can quite probably run multiple thrones on a single VPS, which somewhat defeats the purpose of having a diverse set of masternodes.

I have discovered this project for a few weeks, it is very interesting, very well done and deserves to be better known, but I think it will become more and more known and will go a long way in the times to come. Excellent idea the promotional video published on YouTube on April 12 with over 45 thousand views in less than a month, incredible! 

So what are you waiting for?

Here is the link for those who missed the video ...

https://youtu.be/Kffc1l1a73c

Build your kingdom! 

Could someone tell me what turned out of the campaign we had some months ago to be listed in a big exchange?

Crown Consensus Mechanism Change

Dear Crown Community,

The Crown Core Team is delighted to announce that after pertinent research and availability of adequate resources, the Crown Platform is ready to go one step further towards implementing a unique consensus mechanism that has been referred to as The Third Way.

The Crown project has always had an innovative vision, which is one of the main reasons it decided to implement merge mining with Bitcoin through the SHA256D algorithm. Arguments for merge-mining were mainly ecological benefits and network security. While miners do not need any additional infrastructure to mine Crown, this has secured the network with up to 10–12% of the total hash rate of Bitcoin, the first and largest peer to peer blockchain network in the world.

Times have changed and so has the situation we are in. Mining has become the principal centralization vector of cryptocurrencies, with an industry that only allows big corporations to have a significant hashing power and mine blocks.

As a merge-mined Coin, Crown has also been affected by this. Crown is currently mined by a few very powerful mining pools, which has led to a massive centralization of 36% of every block reward into a few hands. Network stability is similarly affected when one of these big miners drops out or has network connectivity issues.

The Crown project no longer wants to be dependent on a few large mining corporations and thus has been working hard to make a new solution viable. We are now looking to present and publish this solution for discussion and voting to the Crown community:

Implementation of The Third Way — a unique masternode/servicenode based Proof of Stake consensus system — into the Crown Project.

- Moving to a Masternode Systemnode based PoS system is a step towards the unique consensus mechanism that Crown is developing.
- The suggested consensus mechanism eliminates Proof of Work and makes transactions instantly verified by a distributed network of Masternodes and Systemnodes.
- Masternodes and Systemnodes will be able to vote and participate in the network.
- Masternodes and Systemnodes carry out all of the relevant tasks for validation of transactions and propagation/security of the network.
- The implementation will be carried out hand in hand by an external and trusted team of developers with a proven track record of migrating projects to PoS, together with internal Crown developers.
- The Crown Developers will survey the changes and analyse every line of code, making sure the integrity of the blockchain is kept while acknowledging the process for further development.

A consensus change is something comparable to the modification of the constitution of a country. Crown is a community driven blockchain project and thus is committed to asking the members of this community if you are ready and agree to move in this direction.

For this reason, the Crown Core Team has submitted a proposal that the community can now vote on.

YES: mnbudget vote-many a26efe84713df144888f284a9f40a474925af8c86634d79be37fb1e4b2b0ec7d yes

The proposal is to start a discussion. Right now it seems that wallet staking will not be included in the PoS, there are many reasons for that from the dev perspective. The PoW rewards should go evenly to MN and SN. Regarding your other questions, I recommend you join our main chat at mm.crownlab.eu and talk to our devs, we expect an very open discussion with the community since it will take 4 to 5 months to implement this, and we want to be sure all major concerns from the community are included in the PoS solution our devs have in their head, should the proposal pass through our governance.

This is a great point  

[/quote]
Very well! Excellent initiative! Let's build our kingdom together and be the kingdom of all and not just some!  
[/quote]

The right to vote for who exactly is?  And when they close the polling stations of the Kingdom?   

The voting goes through our proposal system https://crown.tech/governance/ maybe you can find more relevant info how the Superblocks work there

thank you, very clear explanations!