Rob Clarkson

I've changed it to be an object {tx: 'XXXX'} But looks like it prefers a string as I'm getting a new validation error: ``` Uncaught (in promise) AssertionError [ERR_ASSERTION]: Assertion...

Its a compiled version of bcoin/lib/client/node.js ``` /** * Add a transaction to the mempool and broadcast it. * @param {TX} tx * @returns {Promise} */ broadcast(tx) { assert(typeof tx...

I've tried sending my json object in a string: ``` const result = await client.broadcast('{tx:'+raw+'}'); ``` same as the initial problem with the content type

So as far as i can tell you were right my initial code was wrong as i was sending just the raw transaction hex, but now i've fixed it, seems...

It wont work either way. If i send raw TX hex server rejects it due to content type. If i try to send the correct {tx: 'xxxx'} object the client...

Heres what happens when i pass raw TX: ``` const result = await client.broadcast(raw); ``` 

Just to add, i think the bcoin libraries and code are awesome, thank you for all your work!

Yeah that puzzled me, but seems to work for the gettransactions call so i've left it. Heres my client config options:  I think its a hex string. I'm using...

Heres both ways at the same time going wrong twice:  

I've removed the type:null from the config, that was just another test i did, no effect