In order to list your fork, exchanges often want answers to the following questions:
Q. What is the original codebase you have used?
A. Bitcoin Core
Q. Have you modified the block and transaction serialization formats?
A. No. Note however that the coinbase transaction has an additional requirement of including the fork hash (32 bytes). In return, the maximum coinbase script sig size has been raised from 100 to 132 bytes.
Q. Have you modified the block proof of work hash function?
A (sha256d). No.
A (scrypt). The fork uses the Litecoin scrypt proof of work hash function after the fork point.
Q. Have you modified the block id hash function as is reported in the RPC?
Q. Have you modified the transaction id hash function?
Q. Have you modified the cryptographic signature algorithm in any way?
A. Yes. Signature hash now embeds the fork hash as well, right at the beginning, before the transaction version.
Q. Have you modified the standard scripts for sending, receiving or in general?
Q. Have you modified the script language in any way?