Decide future direction of library

[luke-jr]

With the adoption of Bech32, there is likely to be no need for a Base58-specific library.

Would it make sense to transform libbase58 into a generic libbitcoinaddress library, adding Bech32 and perhaps Bitcoin Script generation?

[luke-jr]

Any thoughts, @CoperNick8 @holland01 @randolf @sipa @laanwj @e271828- @voisine ?

[laanwj]

I tend to agree - base58 has so few stand-alone uses outside of bitcoin, that including bechs32 functionality and making it a combined library makes sense imo.

…

On Tue, Jul 3, 2018, 13:00 Luke Dashjr ***@***.***> wrote: Any thoughts, @CoperNick8 <https://github.com/CoperNick8> @holland01 <https://github.com/holland01> @randolf <https://github.com/randolf> @sipa <https://github.com/sipa> @laanwj <https://github.com/laanwj> @e271828- <https://github.com/e271828-> @voisine <https://github.com/voisine> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHutvLx1mbENiNpOK_tUnmHDZo9wzGSks5uC1z6gaJpZM4SvWAL> .

[e271828-]

This seems reasonable to me as well.

[CoperNick8]

I do not know. I'm new. I just add that I thought that libbase58 is part of the Bitcoin Core, but now I see that Bitcoin Core has its own base58.cpp .