marsface

I see, thanks

BTC.rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B/XRP and BTC.rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B/BRL.rfNZPxoZ5Uaamdp339U9dCLWz2T73nZJZH Haven't tested any other pair.

Probably because there are breaking changes in the current ripple-lib version when compared to the client's version.

https://ripple.com/build/ripple-test-net/ > Test Net Servers > > Use the following addresses to connect to the Ripple Test Net and send transactions from your account. > > WEBSOCKETS > > wss://s.altnet.rippletest.net:51233...

Maybe its just an interface problem, but its quite frustrating.

I got this error message in dev version when performing the task above: `[4017:1130/093532:INFO:CONSOLE(106817)] ""Error: Exceeding max value of 100000000000\n at Amount._check_limits (http://localhost:3000/js/vendor.js:39000:14)\n at Amount._set_value (http://localhost:3000/js/vendor.js:38784:9)\n at Amount._copy (http://localhost:3000/js/vendor.js:39019:9)\n at...

ok, it looks like the error is inprocesing the returning results from pathfind, for XRP > IOU payments, generating wrong values for XRP, and this error causes the other paths...

Probably because 0.49 btc returns no paths for xrp > btc, only IOU > btc, so the xrp limit bug is not triggered. Em sáb, 16 de jan de 2016...