Skip to content

Conversation

@themorlock
Copy link
Collaborator

Added TAO/Alpha information for dTAO staking events (unstake/stake).
Screenshot 2026-01-01 at 4 02 05 PM

It seems like even for swap details (SimpleSwap), we still just say "Confirmed/Failed", so I didn't change the dTAO history items to stay "Stake/Unstake" (but this can easily be added if we want).

@themorlock themorlock requested a review from 0xKheops January 4, 2026 21:53
@prury prury added the QA pass QA testing passed label Jan 5, 2026
@themorlock
Copy link
Collaborator Author

Consolidated stake and unstake into a single type. Also added TAO <-> ALPHA in history.

Screenshot 2026-01-06 at 1 29 29 PM Screenshot 2026-01-06 at 1 44 18 PM

Copy link
Contributor

@0xKheops 0xKheops left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great now, but can be further simplified

@themorlock themorlock requested a review from 0xKheops January 8, 2026 02:34
Copy link
Contributor

@0xKheops 0xKheops left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 little issues to fix

Comment on lines 43 to 44
fromTokenId: nativeToken.id,
toTokenId: nativeToken.id,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if using native token id for both, the label in the details form will be incorrect for unstake txs.
one of them is not the native token but alpha for netuid 0, can generate its id using subDTaoTokenId("bittensor", 0).

Comment on lines 191 to 195
defaults={
isStake
? "Stake <FromTokens /> for <ToTokens />"
: "Unstake <FromTokens /> for <ToTokens />"
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i18n strings cannot be conditional or they wont be parsed and sent to our translation platform.
sadly we need 2 different <Trans /> components here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or maybe have the operation name being output by a 3rd entry in the components property

@themorlock themorlock requested a review from 0xKheops January 10, 2026 01:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

QA pass QA testing passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants