It should be easy to create a NEO smart contract which implements the Link and Prover interfaces.
How would the 'lithium daemon' be adapted for NEO? e.g. events vs transactions.
NEO only supports RIPEMD160 and SHA256, and doesn't support SHA3/Keccak, this was considered when initially choosing SHA256 for this project. For NEO compatibility SHA256 should be used for anything which would need to be verified on-chain.
It should be easy to create a NEO smart contract which implements the Link and Prover interfaces.
How would the 'lithium daemon' be adapted for NEO? e.g. events vs transactions.
NEO only supports RIPEMD160 and SHA256, and doesn't support SHA3/Keccak, this was considered when initially choosing SHA256 for this project. For NEO compatibility SHA256 should be used for anything which would need to be verified on-chain.
See: https://github.com/neo-project/neo/blob/41c9aabd75eed85958c1300da974e1f9dcd3b37b/neo/SmartContract/ApplicationEngine.cs