But with what coin??
sorry for nbt
Merged pull request from @backpacker to add nuexplorer.ddns.net provider to Cointoolkit.
Thank you for your contribution, keep it up!
6 Likes
Nice to see commits activities for this project.
Cointoolkit may work as an alt easy way to use client-side wallet in the near future so that noobs donāt get required to download all gigabytes from blockchain before using Nu.
1 Like
Right. I have put it under wallet part of the suggested wikipedia contents
Itās not quite suitable for noobs yet as itās easy to send all change to tx fee. Some safety net need to be in place.
I agree about the change danger.
A BIG warning msg should be displayed for that situation, shouldnāt it?
When creating a tx a warning shows up if the fee is bigger than 0.011. Will have to hard code a different value for every currency though.
When the NSR tx was made a few days ago I noticed that the fee was never displayed, nor when verifying and signing. Was it a bug?
Blockexplorer woes
OK. Thanks. Would be nice give this explanation as part of the warning when the explorer is down. I thought whoever generated the tx had forgotten to set fee.
I didnāt forget the fee. And without the fee, the tx wouldnāt have been processed, but it did.
Itās just strange, that it wasnāt displayed, but @ttutdxh explained why.
@backpacker, any idea, why I canāt create an NSR tx using your Cointoolkit fork and nuexplorer.ddns.net?
I tried that when I realized that @ttutdxhās Cointoolkit couldnāt create the tx, because blockexplorer.nu was reported as down.
Then I tried @ttutdxhās Cointoolkit with nuexplorer.ddns.net. Didnāt work either.
The thing is: neither nuexplorer.ddns.net nor blockexplorer.nu is down at the moment.
Since cointoolkit is using helper api from yahoo, we are out of luck when thatās playing up. Logs show no abnormalities, requests from yahoo come and answered correctly, but yahoo doesnāt respond properly back to the browser.
Itās working now, for me anyway.
1 Like
Not working here, but thank you for the explanation.
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.
1 Like
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.
2 Likes
Iāve added access control allow origin header to nuexplorer.
Iāve also modified my version of coin toolkit to deal with single output properly.
4 Likes
Dir you already lose count how often I told you that you are amazing?
This was possible thanks to you:
I hope we finally get the NSR thereā¦
Now it depends on the FLOT NSR group.
@ttutdxh unfortunately BKS is automatically send in 1 BKS transactions which leads to a huge list for the inputs on cointoolkit link. Could you adjust Cointoolkit for BKS so that the transactions are grouped by transaction ID?
1 Like
You canāt create a tx if you donāt specify every transaction id.
That is not a cointoolkit problem, it is the way the network is designed. It even hangs the official client sometimes.
How are we supposed to work around that?