zeekayandHanzo Dev 27979a225c The wallet has no C-Chain, so stop asking it for one ...

The SDK's primary wallet no longer builds a C-Chain wallet, and every
caller here was carrying scaffolding for the one it used to build: an
emptyEVMKeychain that answers nothing, passed as the EVMKeychain of a
wallet that never consults it, and in one case a nil.

rpc transfer went further and reached around the wallet, building
C-Chain atomic import and export transactions by hand against
lux.issueTx and polling lux.getAtomicTxStatus. Value on the C-Chain
moves by an ordinary EVM transaction against /v1/bc/C/rpc; an atomic
export from an EVM chain is a different act with a different settlement
path, and this command was not the place for it. transfer now moves
value between P and X, names an unsupported chain in its error, and
reports both the export and the import transaction rather than one.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-06 12:19:00 -07:00

..

atomic_utxo_test.go

Take the utility package under its new name

2026-09-06 12:18:26 -07:00

atomic_utxo.go

Take the utility package under its new name

2026-09-06 12:18:26 -07:00

rpc.go

A chain address is built in one place

2026-08-30 15:05:42 -07:00

transfer.go

The wallet has no C-Chain, so stop asking it for one

2026-09-06 12:19:00 -07:00