Elliot.

We can keep this issue open until [XRPFees](https://github.com/XRPLF/rippled/pull/4247) successfully activates (and @mDuo13 confirms that it fully resolves this issue)

This is related: https://github.com/ripple/rippled/issues/2599 [Sorry for closing -- accidental click.]

@giorgosHadji - I do not think anyone is working on this. You can pick it.

@KumarUjjwal2022 which rippled servers are you using? It would be best to [run your own rippled servers](https://xrpl.org/manage-the-rippled-server.html).

@shawnxie999 thanks. The recommendation to run your own rippled servers remains. @WietseWind could it be useful to connect with @KumarUjjwal2022 (see above) to debug any potential connectivity issues?

I think it's worth considering keeping `xrpl` as-is to avoid churn and keep the name short, while still renaming/moving the other packages to be under `@xrplf`.

By "currency code", do you mean the [40-character hexadecimal string](https://xrpl.org/currency-formats.html#nonstandard-currency-codes)?

Closing due to inactivity. If the issue persists, please re-open (or open a new issue) and provide the xrpl.js version you're using.

On other blockchains, making previously-valid transactions invalid is a soft fork, so such changes do not need an amendment or timed switch. Restricting what memos can contain - tightening the...

> Can you assign me this issue ? Are you actually working on this issue?