README.md's feature table and API reference for stellar_send describe pause()/unpause(), transfer_admin()/accept_admin() two-step rotation, and ContractConfig.min_amount/max_amount bounds — but stellar_send/src/lib.rs's actual ContractConfig struct only has admin, fee_bps, fee_collector, active, and none of these functions exist in the #[contractimpl] block.
The same mismatch applies to fee_collector (README claims "Period limits" withdrawal feature, not implemented) and token_bridge (README claims "Supply cap" and pause/unpause, not implemented). This is misleading to integrators and should either be implemented or the README corrected to reflect current (v0.1.0) scope, distinguishing shipped vs. planned features — the stubs.rs files in each contract's src/ directory already contain an informal backlog that could seed a real roadmap section.
README.md's feature table and API reference forstellar_senddescribepause()/unpause(),transfer_admin()/accept_admin()two-step rotation, andContractConfig.min_amount/max_amountbounds — butstellar_send/src/lib.rs's actualContractConfigstruct only hasadmin,fee_bps,fee_collector,active, and none of these functions exist in the#[contractimpl]block.The same mismatch applies to
fee_collector(README claims "Period limits" withdrawal feature, not implemented) andtoken_bridge(README claims "Supply cap" and pause/unpause, not implemented). This is misleading to integrators and should either be implemented or the README corrected to reflect current (v0.1.0) scope, distinguishing shipped vs. planned features — thestubs.rsfiles in each contract'ssrc/directory already contain an informal backlog that could seed a real roadmap section.