In the event of cybersecurity, compliance issues with the Protocols, Treasury, Smart Contracts, Tokens, and breach of Bylaws (insert Link to Panama Bylaws) by token holders, Councilors, or outside attacks.  The current Security council will immediately enact an Emergency HIP’s:

• This is called:
  • HIP-EMERGENZ-#, Subtitle (enter Date and root cause)

The HIP-EMERGENZ will have two parts.

Stage 1:

Issues relating to cyber-attacks, major fraud, or unauthorized treasury access threats will allow the Security Council to proactively act in real-time to correct and mitigate any threats to our environment.

• In such an incident, the Security Council will create a HIP-EMERGENZ-# (outlining the issue, resolution, and execution plan)
• The Security Council will notify the other Council groups and the Chamber of Councilors of the threat and request assistance if necessary.
• If the Security Council successfully corrects the issues, the HIP-EMERGENZ gets closed out as completed.
  • Councilors who participated in curing threats will be recognized via Discord and CODE Forum to promote their dedication to the DAO.
  • If the Security Council cannot correct the issues, the HIP-EMERGENZ will proceed to PART 2.

All high-priority issues relating to Smart Contracts, Operations, Tokens, or Governance models that can potentially impact DAO infrastructure or daily functioning will follow the below process, and the HIP will be sent to the CODE Forum for review:

• The Security Council will review the issue and outline a solution for immediate correction. The new HIP-EMERGENZ-# (details) will outline the issues, causes, and rectification or upgrade required to ensure the ecosystem environment. This HIP-EMERGENZ will be issued to all members of the CODE Forum for immediate review of corrective action to correct the issues. Normal Polling time frames are not mandated for HIP-EMERGENZ. Immediate Polling within 24 Hours of the EMERGENCY HIP creation is required due to the time of the essence in these types of threats.
  • Mobile and DISCORD “SOS – Distress” Push notifications:
    • Build in Push notifications to all CODE Members for participation in HIP-EMERGENZ.
    • Contact information is required when applying for positions. This will be added to the HIP-EMERGENZ for notifications.

Equal Share of Votes:

• Each council (Chamber, Organization, Development, Economic) holds a 25% share of the total votes.

Internal Voting:

• Members within each council vote on decisions.
• The internal vote results are used to determine the council's contribution to the overall vote.
• If a council is unanimous (100% for or against), the entire 25% share is counted accordingly.
• If a faction is split, the votes are proportionally weighted based on the internal distribution.

Calculating the Total Support:

• For each council (i), calculate the weighted vote in favor: Wi = 0.25 × Xi, where Xi is the percentage of members voting in favor.
• Sum the weighted votes from all councils to get the total support: Wtotal = W1 + W2 + W3 + W4

Example:

• Internal vote results: 80% (council 1), 60% (council 2), 50% (council 3), and 100% (council 4).
• Weighted votes:
  • W1 = 0.25 x 0.8 = 0.20
  • W2 = 0.25 x 0.6 = 0.15
  • W3 = 0.25 x 0.5 = 0.125
  • W4 = 0.25 x 1 = 0.25
  • Total support: Wtotal = 0.20 + 0.15 + 0.125 + 0.25 =0.725 (72.5% in favor)

Approval Criteria

For a decision to be confirmed, it must receive over 50% approval.

• If the HIP-EMERGENZ passes, the resolution will be executed immediately.
  • If the HIP-EMERGENZ requires action from the Treasury, a request to release funds will be delivered to a minimum of 3 Chamber of Council members to release the funds via our MultiSig Wallet (insert Link to MultiSig page) to the appropriate groups to correct the issues.
• If the HIP-EMERGENZ Fails, the resolution will not be executed.

Stage 2:

Failure of the HIP-EMERGENZ will trigger its immediate release to the Discord channel/full community (OFF Chain) for expedited assistance in sourcing a solution to correct the current issue.

• The community will provide internal and external solutions to cure the issues outlined in the HIP-EMERGENZ.
• CODE councilors will review the top responses, validate them against current issues, and verify/identify resources that can perform corrective actions if outside the communities’ ability to correct.
• This includes any action for the Treasury for the expedited release of funds for development or other corrective action.
  • Strick adherence to capital expenditure thresholds is required:
    • Expenditures below $10K will be approved via the CODE Forum Polling process within 24-hour time frames.
    • Expenditures above $10K will be approved via the CODE Forum HIP Polling process and moved to SnapShot for community engagement within 24-hour time frames.
  • If a HIP passes with a $10K or higher requirement, the Funds will immediately be released from the Treasury to cure the threat.
• Once a solution is agreed upon by the CODE councilors, it will be pushed to Polling.
• Polling will follow the Convergent Governance - CODE Forum Model with expedited time frames to match the above STAGE 1 time frames.
• If the Stage 2 HIP process fails this process, it is returned to the community for additional support options and input until such time the HIP is approved and issues are corrected.
• Once the Emergency is corrected and neutralized