<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=23560607" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/sqrrm">@sqrrm</a> I don't understand the phrase "splits in two fairly equal parts".</p>
<p>The case of splitting into <em>exactly</em> equal parts can be ignored as it is not realistic. For any other scenario, one part <em>must be bigger</em> than the other (voting-power wise), hence this is the "right DAO" and can be verified check using the system we created.</p>
<p>The bigger part then has no problem.</p>
<p>The smaller part can choose to create a <em>new</em> DAO of its own with a new genesis block and/or new consensus rules. Then they have the job of convincing people to switch the Bisq version, to one that follows their new DAO.</p>
<p>I still think that using the word "fork" is confusing here. Is it more similar to blockchain forks, or to creating a new rival DAO, hoping users will switch to it?</p>
<p>Maybe I didn't understand what you mean though:-)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/compensation/issues/259#issuecomment-479909183">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtnQqK-4VWHltpwEr_81MBp1Ui4Ykks5vdgWIgaJpZM4cUboh">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtsFOot_rN-iiywwwXrznCI_oZHxIks5vdgWIgaJpZM4cUboh.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/compensation","title":"bisq-network/compensation","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/compensation"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eyalron33 in #259: @sqrrm I don't understand the phrase \"splits in two fairly equal parts\".\r\n\r\nThe case of splitting into *exactly* equal parts can be ignored as it is not realistic. For any other scenario, one part *must be bigger* than the other (voting-power wise), hence this is the \"right DAO\" and can be verified check using the system we created.\r\n\r\nThe bigger part then has no problem. \r\n\r\nThe smaller part can choose to create a *new* DAO of its own with a new genesis block and/or new consensus rules. Then they have the job of convincing people to switch the Bisq version, to one that follows their new DAO.\r\n\r\nI still think that using the word \"fork\" is confusing here. Is it more similar to blockchain forks, or to creating a new rival DAO, hoping users will switch to it?\r\n\r\nMaybe I didn't understand what you mean though:-)"}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/compensation/issues/259#issuecomment-479909183"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/compensation/issues/259#issuecomment-479909183",
"url": "https://github.com/bisq-network/compensation/issues/259#issuecomment-479909183",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>