Elliot.

The rippled team is aware of this and there's no need to change it. It was discussed in the PR you linked to, https://github.com/ripple/rippled/pull/4097 There's nothing strictly canonical about the...

1) Can we add a caveat in the release notes to say that the limit is 8 unless the [ExpandedSignerList](https://xrpl.org/known-amendments.html#expandedsignerlist) amendment is active? 2) What error should users expect if...

I think something like @lathanbritz 's approach is ideal -- it's best to specify `value`s without trailing zeros, as the error simply reflects the fact that trailing zeros are "dropped"...

Canceling this because the issue is old and this doesn't apply to the current version of the library (xrpl.js v2)

Fixed in moneyd v4.6.2 https://github.com/interledgerjs/moneyd/commit/cb4b0891d3c0196a6bbaac8212f18be6327950c5

Thanks for asking about this! We have a `teardown()` function that you should call to destroy Drop-in. Example: ``` var dropinInstance; braintree.dropin.create({ // ... }, function (err, dropin) { //...

Great! Thanks again for pointing out this issue.

More important than other enhancements, but not truly a bug fix

More important than adding response objects

May make sense to prioritize if/when devs request it