[Cashtab] [chronik utxo handling p10] chronik token minting
ClosedPublic
Actions

Authored by bytesofman on Sep 13 2022, 18:00.

Details

Reviewers

emack

Group Reviewers

Restricted Project

Commits

rABC969bd16bcce7: [Cashtab] [chronik utxo handling p10] chronik token minting

Summary

T2447

Depends on D11977

Patch token creation function to support new chronik utxo format. Patch qty bug in mint calculation.

Test Plan

npm start
Create a token. Review the tx on block explorer to confirm change, fees, general sanity check.
Inspect tx history and observe correct display of genesis qty.

Diff Detail

Repository

rABC Bitcoin ABC

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

bytesofman created this revision.Sep 13 2022, 18:00

Herald added a reviewer: Restricted Project. · View Herald TranscriptSep 13 2022, 18:00

bytesofman requested review of this revision.Sep 13 2022, 18:00

Harbormaster completed remote builds in B20024: Diff 34956.Sep 13 2022, 18:03

bytesofman added a child revision: D11979: [Cashtab] [chronik utxo handling p11] chronik token burns.Sep 13 2022, 23:49

emack requested changes to this revision.Sep 20 2022, 06:12

emack added a subscriber: emack.

emack added inline comments.

web/cashtab/src/components/Home/Tx.js
548 ↗	(On Diff #34956)	changing this to `qtySent` now parses to 0 zeros for the genesis tx, which I don't think is expected behaviour whereas the original `qtyReceived` reference was correctly parsed to the token mint amount in the genesis tx, which makes sense because it's what this wallet is receiving from the genesis tx I think qtySent only makes sense for something like a token burn when you're sending the tokens outbound in the burn action.