I'm trying to build a transaction hex string which I could later broadcast using the daemon rpc, the my-monero-core lib doesn't seem to have an API to do, so I used the code that I found here Eventually I got it to build the following transaction string
01000102d0beb08196010100417b816f03f3da689e68f56217bf8d5bd8b858f71b66b84c7e95c19142ecae160280a8d6b90702b02dec621648c4060e40e1a9a774808adf3d678c83a0027e9a2f7313cbd7bd1980f8e7c78d0102ae92396f3c9c2e7d46bf1b6fe102b32036b7953f7fea21817226cc163473e79a21016e8efb46025e60f22d815ce16fe2dad9d9b8620f4faecfe9897a5de056f276af2569ab5d4a413b63d383db6b02faefdf2bbf3c65cf2d1a0efab49e0304e6280f9ef3f62b340dd047b26ff71aa5aff17a475f790ec96b5da7f4d766144cab040d
which according to this tool is at least a valid hex string. However when I try to broadcast it I get a response stating either "invalid_output": true or "invalid_input": true depending on number of mixin and destinations that I play with. Unfortunately boolean isn't very helpful to figure out what the problem actually is. So the questiond are
- Is there a well-known valid piece of code to build a transaction hex string given valid UTXOs and spend keys for them? (preferably JS but anything would do)
- Is the code that I'm using valid? I noticed it builds transactions of
version 1, are those still supported?
