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?


1 Answer 1


It has been fixed in latest 4.1.0 release

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.