Section 7: Protocol Governance and Parameter Management — Layers 7
|
Section 7: Protocol Governance and Parameter Management
The governance framework for OTCM Protocol'Protocol’s operating parameters — defining precisely what can be adjusted, what cannot be changed by any party, who holds adjustment authority, and the security controls that protect parameter changes from unauthorized modification.
7.1 Governance Philosophy
OTCM Protocol'Protocol’s governance architecture reflects a straightforward principle: the parameters that protect investors from harm must be structurally impossible to change, while the parameters that affect platform economics must be adjustable within defined bounds by accountable human decision-makers operating under identified security controls.
This approach deliberately differs from anonymous token-based governance models. Groovy Company, Inc. dba OTCM Protocol is a Wyoming Corporation with named officers, a board of directors, and legal counsel on record with the SEC. Protocol governance is an extension of corporate governance — transparent, accountable, and subject to the same securities law obligations as any other corporate action affecting investors.
The Core Governance Principle — The 42 Transfer Hook security controls embedded in OTCM |
7.2 Immutable Parameters — What Cannot Be Changed
The following parameters are embedded in OTCM Protocol'Protocol’s immutable on-chain program. No corporate resolution, no multi-signature execution, no legal process, and no technical action can modify these parameters without deploying an entirely new smart contract program — which would require investors to migrate to a new token, breaking the existing custody and ownership chain:
|
Parameter |
Status |
Authority / Mechanism |
|
|
|
|
42 Transfer Hook security controls |
Immutable — on-chain program |
No authority — architecturally impossible to modify |
|
1:1 token-to-share backing requirement |
Immutable — Transfer Hook Control 1 |
Cannot be relaxed by any party; any discrepancy halts all transfers |
|
LP token burn at pool initialization |
Immutable — pool contract design |
No withdrawal function exists; LP tokens already burned |
|
OFAC/SDN screening on every transfer |
Immutable — Controls 8–10 |
Cannot be disabled or bypassed by any participant including OTCM Protocol |
|
AML risk scoring on every transfer |
Immutable — Control 11 |
Cannot be disabled or bypassed |
|
Accreditation verification on every transfer |
Immutable — Controls 12–18 |
Cannot be disabled or bypassed |
|
Rule 144 / Reg S holding period enforcement |
Immutable — Control 24 |
Cannot be waived by any party; no administrative override |
|
5% transaction fee — total rate |
Immutable — Token-2022 Transfer Fee Extension |
Configured at mint creation; cannot be changed post-mint |
|
2% staking reward reinvestment to Global Pool |
Immutable — Transfer Hook logic |
Cannot be reduced or disabled |
|
Wallet concentration limit — 4.99% maximum |
Immutable — Control 20 |
Cannot be increased beyond this ceiling |
Why Immutability Is the Stronger Governance Position — For an institutional investor or regulator reviewing OTCM Protocol, the question is not |
7.3 Adjustable Parameters — What Can Be Changed
The following parameters may be adjusted within defined bounds by OTCM Protocol'Protocol’s authorized governance process. All adjustments are subject to multi-signature execution and a 48-hour on-chain timelock before taking effect. No parameter can be adjusted outside its defined range in a single governance action — preventing incremental boundary erosion.
|
|
|
| |
|
|
|
|
Rationale for Adjustability |
|
|
TWAP calculation window |
30 minutes |
15–60 minutes |
Market conditions may warrant a longer or shorter reference window |
|
|
Maximum price impact per trade |
|
|
1–5% |
May need tightening or loosening as liquidity depth matures |
|
|
|
|
|
|
|
|
|
Platform economics evolve with scale |
|
|
Circuit breaker cooldown period |
24 hours |
12–72 hours |
May need tuning based on observed market patterns |
|
|
AML enhanced review threshold |
Score 31 |
25–45 |
Risk tolerance calibration as AML model matures |
|
|
TWAP outlier rejection threshold |
3σ from median |
2–5σ |
Statistical tuning as price feed data accumulates |
|
|
Emergency circuit breaker trigger |
3-of-5 multi-sig |
Fixed at 3-of-5 |
Quorum for emergency platform halt |
Adjustment Bounds Are Hard Limits — Each adjustable parameter has a defined minimum and maximum. No single governance action can move a parameter outside its defined range. If market conditions require a parameter to move beyond its range, a separate protocol upgrade process is required — subject to the full upgrade security controls described in §7.5. |
7.4 Governance Authority Structure
7.4.1 Corporate Governance Layer
All material protocol decisions originate at the corporate governance level of Groovy Company, Inc. dba OTCM Protocol. Major decisions — fee structure changes, new issuer onboarding policies, platform security posture changes — require board resolution before on-chain execution. This provides a documented, auditable decision trail consistent with the Company'Company’s obligations as an SEC-reporting public company (CIK: 1499275).
• Board of Directors — Approves material changes to platform economics, security posture, and issuer onboarding standards
• Chief Technology Officer — Frank Yglesias — Technical authority over smart contract upgrade proposals and security architecture decisions
• Chief Legal Counsel — Jeff Turner (JDT Legal) — Legal authority over all regulatory compliance determinations, including any interaction with Control 42 (Regulatory Compliance Override) UPDATED V8
• Chief Operating Officer — Patrick Mokros — Operational authority over platform parameter adjustments within pre-approved bounds
7.4.2 Multi-Signature Execution
All on-chain parameter changes and smart contract upgrades require multi-signature execution. The multi-signature architecture ensures that no single individual — regardless of title or authority — can unilaterally modify platform parameters:
|
Action Type |
Multi-Sig Threshold |
Timelock |
Additional Requirements |
|
|
|
|
|
Adjustable parameter change (within bounds) |
3-of-5 authorized signers |
48 hours |
Written record of approving authority |
|
Emergency circuit breaker activation |
3-of-5 authorized signers |
None — immediate |
P0 incident declaration required; post-incident review within 24 hours |
|
Smart contract program upgrade |
5-of-9 authorized signers |
48 hours |
Security audit attestation required; see §7.5 |
|
Emergency pool migration (catastrophic vulnerability only) |
5-of-9 authorized signers |
48 hours |
Independent security audit of destination contract; |
|
Control 42 — regulatory compliance freeze |
|
None — immediate |
Written legal process documentation required |
Multi-signature key holders are geographically distributed across multiple jurisdictions. Key rotation follows a defined schedule and requires the same multi-signature threshold as the actions the keys authorize. No key holder may hold more than one signing position in any quorum.
7.5 Smart Contract Upgrade Protocol
Smart contract program upgrades are the most sensitive governance action available — they modify the executable code that enforces compliance on every ST22 transfer. The upgrade protocol is designed to ensure that no upgrade can weaken investor protections, and that any upgrade is subject to independent technical review before activation.
7.5.1 Upgrade Requirements
• Security audit attestation — Every upgrade proposal must include a schema compatibility attestation signed by a PCAOB-registered or recognized blockchain security firm (Quantstamp, Halborn, or OtterSec). Proposals without a valid attestation are automatically rejected by the upgrade timelock contract.
• Account schema compatibility — The new program version must handle all existing account schema versions via a migrate() function. No upgrade may activate until all existing accounts can be migrated without data loss.
• Immutable control preservation — The upgrade must preserve all 42 Transfer Hook security controls at their current specifications. Any upgrade that would weaken, remove, or bypass any control is rejected regardless of multi-sig approval.
• 48-hour observation window — The 48-hour timelock between approval and activation provides time for community observation, independent security review, and legal intervention if needed.
• 5-of-9 multi-sig threshold — A higher quorum than parameter changes — reflecting the elevated risk profile of code-level modifications.