getNewAddress() soon becomes extremely slow about iota.js HOT 5 CLOSED

If you just want the actual address without the checks, you can use the _newAddress function instead and add the checks in later.

https://github.com/iotaledger/iota.lib.js/blob/45d5214a10f7a14da7121c2f2b30e7c448ee36ef/lib/api/api.js#L685

from iota.js.

We need the checks, though, I fear. We just need them to be performed in a rather efficient manner 😉

(Btw, I would try not to use undocumented internal methods)

from iota.js.

I need it to pregenerate addresses for my iota wallet, so I have no other option. Besides, the method should be public. This library needs an api review.

from iota.js.

@andywer You need to check all the possible options for getNewAddress(), since it returns a lot of things apparently. Don't just rely on their unstable documentation.
@bmavity You can get the unused address without the checks also with getNewAddress(). Just experiment with it.

Or, just live with this slowness. 🐌 🐌 🐌

from iota.js.

Closing as this relates to an unmaintained branch of the library, which will be incompatible with the new Chrysalis release of the network.

from iota.js.