mirror of
https://github.com/luxfi/dex.git
synced 2026-09-24 00:26:31 +00:00
The method table is the only caller of submitTx, submitTx is the only caller of mempool.Add, and there is no gossip handler — so a tx type absent from this table cannot exist. TxImport and TxExport are both absent, which is the whole reason the rail moves nothing today and why every C->D deposit would lock on activation: C debits into custody, stages a claim, and nothing on D can consume it. That is a decision, not an oversight, and it was recorded nowhere near the place someone would undo it. An import method is not a method — it is an authorization model. TxImport carries no signature by design, so the ingress is an unauthenticated, free-to-call, value-moving endpoint, and what stands between it and a chain halt is that the proposer screens what it cannot prove and that an already-consumed claim needs no proof. Both are new this week, and neither had ever run in a test before the block authenticator was switched on. Co-authored-by: Hanzo Dev <[email protected]>