Why are tier 5 and 6 (park rates and NSR sales) only being partially utilised?

[masterOfDisaster]

It’s under construction:

FLOT NSR Operations (buy side)

I had to do all calculations manually. Cointoolkit wasn’t able to load the inputs. I based the first attempt of creating a tx with Cointoolkit on @jooize’s groundwork. The high fee was my choice. 3,175,000 to masterOfDisaster Poloniex account Signed 1 (mOD) of 3/5 01000000a4f454570119ed095f89b3d92e7c79096aee990e52386cf09ff17fbf5aeb8dbf57d94243b2010000006a47304402203487325f2ab80724028cff9393ab88af6f5a31e7142387ffbb81e5b9bd97a740022006ffa1e51d2c39822ad52495f0f3dc41d31c5bc89ccd72672f6ea4d…

Explanation of the Cointoolkit trouble (which is in fact related to the blockexplorer(s):

Cointoolkit FLOT guide and changelog

Actually after a bit of debugging, it seems that @ttutdxh multisig code expects data.result.json.json which does not exist in yahoo reply, since there’s only one output available for the address you are using. My internet is very bad so I’ll try to fix that tomorrow if @ttutdxh doesn’t get to do it first.

Cointoolkit FLOT guide and changelog

Please don't. This is a hack to circumvent CORS policy on the browser. This is the second hack to it (before we used a cors proxy) and as you would expect it is far from perfect. What needs to be fixed is the API in the blockexplorer to include a "Access-Control-Allow-Origin: *" header with all the API requests. That is the only way this will be solved for good.

[Cybnate]

What needs to be fixed is the API in the blockexplorer to include a “Access-Control-Allow-Origin: *” header with all the API requests.

But is it going to be fixed?

[backpacker]

I’ve fixed what I could.

[masterOfDisaster]

Looks very successful so far. I was able to create a tx to transfer the NSR, that need to be sold.
Thanks to you!

[backpacker]

I don’t need to be paid regularly for fixes to other software, donations are just fine if you think they are worth it )