Closed barchef closed 6 years ago
I understand the move to the new key format but would argue that there will always be a need for the legacy format and, as a result, having a dynamic prefix should still be supported.
The Scatter team made some minor changes in a new branch to allow support for EOSIO forks, which will pass through a prefix to eosjs-ecc. See changes here: https://github.com/GetScatter/ScatterDesktop/pull/19
We hope you don't find an issue with approving this proposed change to make the hardcoded EOS prefix configurable.
Looks good .. Hope you don't mind if it remove "TELOS addition: " .. Git already tracks the contributer in the history.
Sounds good - thank you very much. Change whatever you see fit!
@jcalfee can you let me know once this is pushed to npm please? thx in advance
ok .. I'll publish soon.
Released in eosjs@16.0.2 and eosjs-ecc@4.0.3
Thanks @jcalfee!
Please consider adopting this PR to further expand the reach of EOSIO. It supports variable public key prefixes for EOSIO-based chains, while maintaining the default prefix of 'EOS' for backwards compatibility with any existing references.