🚨 API BREAKING CHANGE DETECTED

To see the changes click details on "Check semver breaks / PR Semver - stable toolchain" job then expand "Run semver checker script" and scroll to the end of the section.

I think we have a weak consensus against this change, unless we need to break this structure's API for other reasons.

Pull Request Test Coverage Report for Build 15572079372

Details

• 16 of 16 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.03%) to 84.41%

Totals
Change from base Build 15568752627:	0.03%
Covered Lines:	23542
Relevant Lines:	27890

💛 - Coveralls

Yeah I thought that is what we discussed as well.

🚨 API BREAKING CHANGE DETECTED

To see the changes click details on "Check semver breaks / PR Semver - stable toolchain" job then expand "Run semver checker script" and scroll to the end of the section.

I think we have a weak consensus against this change

Yes, I understand that, but this will eventually get patched. Is it better to rip the band-aid now or later?

What do you mean "this will eventually get patched"?

It's not the plan to leave the inaccurate name forever, right?

The bip32 module needs a total overhaul but its not high priority right now. This change can easily be made when we do that and then we don't unnecessarily break downstream until there is real benefit.

Got it, I'll just leave this here as draft then.