0

Using testRPC the amount transferred is multiple times of the msg.value if a library call is involved.

There is bug report and it was raised here and here as well.

It's a well documented, long standing bug in testRPC and as of testRPC v4.0.1 it's still there.

Anyone was able to come up with a workaround?

szerte
  • 1,231
  • 1
  • 14
  • 32
  • You can use a private test network, with clique if you need faster block times. – Ismael Aug 18 '17 at 14:34
  • thanks. not ideal, it still slows down dev cycle too much :/ – szerte Aug 18 '17 at 19:27
  • The github issue seems will be fixed in the next version of testrpc https://github.com/ethereumjs/testrpc/issues/122#issuecomment-323528520 – Ismael Aug 19 '17 at 16:59

1 Answers1

1

It has been fixed in latest 4.1.0 release

szerte
  • 1,231
  • 1
  • 14
  • 32