Closed gruve-p closed 4 years ago
@prusnak Tests are not yet updated because we want a review if these changes are acceptable to get merged.
Implementation has been tested as working on Zelcore: https://github.com/TheTrunk/bitgo-utxo-lib/pull/2
@gruve-p thank you for contributing to this open source library. I'm guessing that none of the maintainers from BitGo have taken a look at this yet because:
.......
So, what are our options here....
In it's current form, I'm doubtful this will get merged :/
@cooncesean thank you for your honest and transparant answer. We had low expectations that this would be merged so no heart feelings there.
We think we will go with option 1 as Trezor is planning to use their own fork and keep up to date with upstream.
Should I keep this PR open or close it?
FWIW This PR has been tested by @TheTrunk on https://github.com/TheTrunk/bitgo-utxo-lib and is being used for Zelcore wallet: https://zeltrez.io/ It is rebased from https://github.com/wlc-/bitcoinjs-lib mady by @wlc- and is being used for CoinID wallet: https://coinid.org/
Should I keep this PR open or close it?
Your call. Leaving it open would be a nagging reminder for us to re-think the architecture. Closing it would clean up a request that likely won't be merged.
Thanks again for the work 👍 -- if you have thoughts for changing the architecture to be able to support future requests like this, by all means open up a proposal.
@cooncesean We have changed the methodology and fixed some unit tests. With the new methodology other coins that use different algo for base58 (For example Decred uses blake2b for base58) can follow our way to get supported without making the architecture too complex. What do you think of the new methodology as any feedback would be welcome.
@prusnak We will fix the test suite shortly so it passes.
we are restructuring bitgo-utxo-lib a bit to be more compatible with upstream and be more modular
Should we resubmit a new PR after the restructuring? If so when should we resubmit?
I will use https://github.com/BitGo/bitgo-utxo-lib/issues/45 to track the progress
@gruve-p It seems your changes do not pass the test suite. Can you work on these failures?