XELIS XEL
Protocol-level amount and balance confidentiality makes default-transfer exposure worth examining.
The site and repository describe homomorphic protection for amounts and balances; documentation also specifies developer rewards.
Encrypted values do not imply hidden address links, and developer rewards require a separate distribution assessment.
Reproduce a default transfer, record six exposure fields, then reconcile current reward allocation.
Open research card & sourcesNew to research
Initial source review; no 96-criterion assessment or independent execution. Sources reviewed: 2026-10-02
Monetary thesis
Privacy without a separate user mode could support fungibility; real transactions must establish the protection.
Native-token demand
Native payments and fees are hypotheses to test; contract counts do not establish holding demand.
Distribution & authority
Documents list developer rewards and transition ranges; verify active height, recipients and control.
Valuation status
Circulation, quote identity and executable depth are unverified; no cheap/expensive judgment.
Review trigger
Review reproducible changes to default privacy, reward shares or material security audits.
What would weaken the thesis
Reliably linkable default transfers weaken the fungibility thesis; unreconciled supply blocks valuation comparison.
Latest record
Added to this research queue on October 2; this is not a launch date.