xln

Rejected ideas

Owner decisions. Do not propose these again; argue only with new evidence that changes the premise.

Idea Why it is rejected
Hub proof-of-solvency / proof-of-reserves Cannot prove a withdrawal guarantee. Users rely on collateral in their own Account; the shared hub reserve is visible only as hope.
Batching or socializing mass exits so every user can dispute A jurisdiction machine protects balances where dispute cost is rational (roughly 100x the dispute fee). Lowering safety to serve every balance drives security to zero. Below that threshold an Account works on credit, exactly like a bank deposit.
“Only the rich are protected” framing Wrong. The threshold is economic: a $100 dispute fee protects balances from about $10k, which is many users. Cheaper jurisdictions lower it.
Compliance as a delta transformer Delta transformers are delta-change logic only. Compliance is a hub (bank) policy, copied from banking like credit and regulation.
Multilateral netting as a new feature Already built into routing and rebalancing.
Framing xln as a better Lightning, Raiden or L2 xln is a breakthrough in banking. Collateral-only channels are the degenerate credit = 0 case; rollups have a hard TPS cap and unproven data-availability trust.
Cutting launch scope (Pay, same-J Swap, Cross-J, Lending on EVM and native TRON) The wide scope is deliberate: it buys generality forever.
Deleting the Svelte frontend Both frontends stay.
Assignable jurisdiction debts / distressed-claim market Rejected by owner.
Selling provable payment authorization to corporate treasuries as the angle Rejected by owner.
T+0 DvP for tokenized securities as a product direction Rejected by owner.
Live dashboards of hub reserves or “exposure” as a selling point Same premise as proof-of-solvency.