Page MenuHomePhabricator

[Cashtab] [chronik] Add hash160 strings to wallet state
ClosedPublic

Authored by bytesofman on May 17 2022, 16:50.

Details

Reviewers
emack
Group Reviewers
Restricted Project
Commits
rABC43e1c094449c: [Cashtab] [chronik] Add hash160 strings to wallet state
Summary

T2447

Chronik requires hash160 to get utxo info for an address.

This diff adds hash160 to wallet state so it is available throughout the app.

Test Plan

npm start
Check local forage by opening dev console --> Application --> indexedDb
Note that hash160 is listed in Path145, Path245, and Path1899 objects under wallet
Activate a different wallet
Confirm the same

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

emack added a subscriber: emack.

Looks good - I'll add a task to find a library to carry out this hash160 conversion to replace the current api call towards the tail end of the chronikfication initiative.

This revision is now accepted and ready to land.May 20 2022, 00:18

Looks good - I'll add a task to find a library to carry out this hash160 conversion to replace the current api call towards the tail end of the chronikfication initiative.

While we do want to deprecate bch-js, this is at least not an api call

https://github.com/Permissionless-Software-Foundation/bch-js/blob/master/src/address.js#L205

so -- it's something we want in xec-js.