Hacash deep monetary assessment
12 dimensions and 96 research questions. Documented facts, interpretations and missing data remain distinct.
All 96 questions are listed; 46 need dedicated data. Coverage does not mean every finding is established.
Monetary constitution / Hacash · L1 · self-custody
| Criterion / research question | Hacash preliminary finding | Evidence |
|---|---|---|
03.01Issuance rulesUnder what conditions are new units created and put into circulation? | The cited code checks height-based rewards and separately accounts for channel interest/burns; mining rewards alone are not circulation. Verification & limitsReplay all issuance routes, burns and fees by height, checking claimed rewards rather than caps alone. | Documented factEvidence records & gaps |
03.02SeigniorageWho receives new units and issuance benefits? Report fees and other income separately. | Block rewards, channel interest and fees/burns have different recipients/effects and cannot be collapsed into miner income. Verification & limitsSeparate subsidy, fees, funds, channel interest and pool payouts by period. | InterpretationEvidence records & gaps |
03.03PredictabilityCan future quantities or calculation rules be known in advance? Fixed rules need not imply fixed future quantities. | The block schedule is height-projectable, while channel settlement and burns affect net supply; mainnet balances need replay. Verification & limitsSeparate height-based projections from actual block dates and identify rule changes. | InterpretationEvidence records & gaps |
03.04Supply accountingHow many units exist and circulate? How are locks, burns, lost coins and cross-chain tokens counted? | New criterion; a project-specific finding is not yet available. Verification & limitsCheck the project version, implementation and actual use before adding evidence and findings. | Data neededMeasurement neededEvidence records & gaps |
03.05Cap and tail issuanceIs there a supply cap? Does issuance eventually stop or continue at a low rate? | The cited standard parameters return 1 HAC per block after the reward table; they do not support a fixed terminal HAC cap. Verification & limitsCheck terminal subsidy, unit rounding and non-mining issuance, not a promotional supply figure. | Documented factEvidence records & gaps |
03.06Monetary hardnessWhen price rises, how difficult is it to expand new supply? What time and cost does that require? | The cited block reward has no price input; other issuance/burn routes require separate net-supply elasticity analysis. Verification & limitsHold protocol rules constant and distinguish mining expenditure from extra units issued. | InterpretationEvidence records & gaps |
03.07Monetary elasticityCan supply adjust when people want to hold more or less money? How is changing demand identified? | Locking/burning may affect supply and float without price targeting; BTC-transfer designs require activation verification before counting issuance. Verification & limitsCheck price/demand feedback and separate custodial credit from native supply. | InterpretationEvidence records & gaps |
03.08DiscretionWho can change issuance, allocation or other monetary rules? What limits that power? | Reward/channel logic is inspectable; deployed versions and all state-changing authority still need review before certifying no discretion. Verification & limitsInspect issuance privileges, upgrade authority and exceptions; open source alone does not remove discretion. | InterpretationEvidence records & gaps |
Scope: native assets, L1 and self-custody. Zcash, MWEB and channels are path-specific; pinned HAC code is separate from deployed-mainnet evidence. Each criterion includes a review method, without a mainnet replay audit or independent peer review.