Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@packages/vechain-kit/src/components/AccountModal/Contents/Assets/Components/AssetsTabs.tsx`:
- Line 31: The onChange handler currently casts Chakra's idx to AssetsTabIndex
which skips runtime validation; change the onChange passed to Tabs so it
validates idx before calling onTabChange: check that idx is a number and within
the valid range for AssetsTabIndex (e.g., 0 <= idx < numberOfTabs or validate
against a known array of allowed indices) and only then call onTabChange(idx as
AssetsTabIndex), otherwise call onTabChange(0) as the safe fallback; reference
the onChange prop on the Tabs component, the onTabChange handler, and the
AssetsTabIndex type when making this change.

In
`@packages/vechain-kit/src/components/AccountModal/Contents/Assets/Components/StakingCards/JuicyFinanceCard.tsx`:
- Around line 95-98: The code unsafely casts currentCurrency to
SupportedCurrency before calling formatCompactCurrency (used in
JuicyFinanceCard), which can pass invalid values; add a type guard (e.g.,
isSupportedCurrency(value): value is SupportedCurrency) and validate
currentCurrency before passing it to formatCompactCurrency, and handle the
fallback case (use a default currency or render a safe placeholder) so both the
formatCompactCurrency call at the currentCurrency usage and the duplicate
occurrence later in the component use the validated currency instead of an
unchecked cast.

In
`@packages/vechain-kit/src/components/AccountModal/Contents/Assets/Components/TokensTab.tsx`:
- Line 82: The code is unsafely converting token.balance to Number which can
lose precision if TokenWithValue.balance is a string or BigInt; inspect the
TokenWithValue type declaration to confirm the balance type and then fix either:
1) adjust TokensTab.tsx (the place using token.balance and the amount prop) to
accept and handle bigint/string balances using a safe big-number library (e.g.,
BigInt, Big.js, or ethers.BigNumber) and pass a properly formatted
decimal/string to the child component, or 2) change the child component’s amount
prop type to accept string/BigInt and update its internal arithmetic/display to
use big-number handling; ensure TokenWithValue.balance and any consumers are
type-consistent so no implicit Number() conversion occurs.

In `@packages/vechain-kit/src/components/common/AssetButton.tsx`:
- Line 19: The import in AssetButton.tsx uses a relative path for
PriceChangeBadge; update the import to use the repository path alias for
components (e.g., `@components/`...) so it follows the project's alias-import
convention; locate the import statement referencing PriceChangeBadge in
AssetButton (symbol: PriceChangeBadge) and replace the relative path with the
appropriate alias path for the components folder.

In `@packages/vechain-kit/src/components/common/CopyIconButton.tsx`:
- Around line 20-25: The copied-state timer in CopyIconButton's handleClick
schedules a new timeout on every click without clearing prior timers; modify
handleClick to clear any existing timer before creating a new one (store the
timer id in a ref, e.g. timeoutRef.current), then setCopied(true) and assign
timeoutRef.current = setTimeout(...). Also add a useEffect cleanup that clears
timeoutRef.current on unmount to avoid stray timers; update references in
CopyIconButton, handleClick, and the cleanup effect accordingly.

In `@packages/vechain-kit/src/config/testnet.ts`:
- Around line 91-94: Update the three testnet contract address values
(stargateContractAddress, stargateNftContractAddress,
navigatorRegistryContractAddress) to use EIP-55 checksummed addresses instead of
all-lowercase; compute and replace each string with the checksummed form (e.g.,
via ethers.utils.getAddress or another EIP-55 routine) so the values match the
checksummed format used in mainnet.ts.

In `@packages/vechain-kit/src/hooks/api/staking/useBetterSwapLpPositions.ts`:
- Around line 90-114: The hook useBetterSwapLpPositions enables and calls
contracts without validating addresses; update the enabled condition and the
queryFn to use isAddress() checks: ensure address and factoryAddress pass
isAddress() before setting enabled (replace !!address/!!factoryAddress with
isAddress(address) && isAddress(factoryAddress)), and in the pairs handling
filter/validate each pair with isAddress() before mapping into
executeMultipleClausesCall (skip invalid entries or return [] early). Keep the
same symbols (enabled, queryFn, executeMultipleClausesCall, pairs,
UniswapV2Pair__factory) and make sure any address casts to `0x${string}` only
occur after validation.
- Around line 93-99: The query key in useBetterSwapLpPositions uses only
pairs.length which can lead to cache collisions when the pairs list changes but
its length stays the same; update the queryKey (in useBetterSwapLpPositions) to
include a stable representation of the pairs themselves (for example a
deterministic identifier array like pairs.map(p => p.id) or
JSON.stringify(pairs) or similar) instead of or in addition to pairs.length so
React Query discriminates different pair sets and returns correct LP positions.

In `@packages/vechain-kit/src/hooks/api/staking/useNavigatorPosition.ts`:
- Around line 34-38: The code currently does prices[b3trAddress] which can miss
matches if keys are normalized (e.g., lowercased); update useNavigatorPosition
logic to normalize the b3trAddress key the same way the prices map uses (for
example lowercase or checksum) before lookup—specifically normalize the
b3trAddress variable and then use prices[normalizedB3trAddress] (or fallback to
alternate normalizations) to compute b3trPriceUsd; ensure the normalization step
is applied where b3trAddress is read and referenced in this file (symbols:
b3trAddress, prices, b3trPriceUsd).

In `@packages/vechain-kit/src/hooks/api/transferHistory/useTransferHistory.ts`:
- Around line 56-61: The code is hardcoding decimals to 18 when populating
symbolByAddress, causing wrong formatting; update the population logic in
useTransferHistory where symbolByAddress.set(...) is called to use the actual
token decimals (e.g., use the decimals property from the balance object
`b.decimals` or a reliable token metadata lookup) and fall back to a safe
default only if decimals is undefined; ensure this change feeds into the same
path used by formatUnits so amounts are formatted with the correct decimals.

In `@packages/vechain-kit/src/hooks/api/wallet/useOraclePriceChanges24h.ts`:
- Line 58: The TypeScript error is caused by passing a plain string `feedId`
into the contract call; update the call site where
`oracle.read.getLatestValue(feedId)` is invoked to cast `feedId` to the typed
address pattern (feedId as `0x${string}`) so the argument matches the contract
signature, and ensure any method name literals used with `oracle.read` are typed
with `as const` per guidelines; specifically locate the `feedId` variable and
the `oracle.read.getLatestValue` invocation and apply the cast and `as const`
typing where appropriate.

In `@packages/vechain-kit/src/hooks/api/wallet/useTokenBalances.ts`:
- Around line 29-33: The VVET balance query is currently only gated by
config.vvetContractAddress and can run when address is missing; update the
query's enabled condition in the useGetErc20Balance call (the destructured
result vvetBalance / vvetLoading) to require both the contract address and the
wallet address (e.g., enabled: !!config.vvetContractAddress && !!address) so the
hook only runs when all required params are present.

In `@packages/vechain-kit/src/languages/en.json`:
- Around line 458-461: Remove the duplicate JSON translation keys by deleting
the repeated entries "From", "To", and "View on explorer" in the newly added
block; keep the original occurrences earlier in the file and ensure only the
earlier definitions of the keys "From", "To", and "View on explorer" remain so
the JSON object has unique keys and no later overwrites occur.

---

Nitpick comments:
In
`@packages/vechain-kit/src/components/AccountModal/Contents/Assets/Components/StakingCards/NavigatorsCard.tsx`:
- Around line 39-43: The valueInCurrency calculation uses a fallback of 1 when
(stakedB3TR + delegatedAmount) === 0 which assigns the full totalValueInCurrency
arbitrarily; update both occurrences where valueInCurrency is computed (the
expression using totalValueInCurrency * ((stakedB3TR + delegatedAmount) > 0 ?
stakedB3TR / (stakedB3TR + delegatedAmount) : 1) and the similar delegatedAmount
expression) to use 0 as the fallback instead of 1, or alternatively remove the
fallback if you can guarantee the denominator is never zero and document that
assumption in the component (NavigatorsCard / the valueInCurrency calculations
referencing stakedB3TR, delegatedAmount and totalValueInCurrency).

In
`@packages/vechain-kit/src/components/AccountModal/Contents/Assets/Components/TokensTab.tsx`:
- Around line 84-86: The prop currentCurrency is being unsafely cast to
SupportedCurrency in TokensTab.tsx; either remove the type assertion if
useCurrency() already returns SupportedCurrency (i.e., ensure the hook's return
type is corrected), or add a runtime guard before passing it down (create/use an
isSupportedCurrency(value) check or validate against the SupportedCurrency
enum/set and handle the fallback case) so you only pass a validated
SupportedCurrency into the component.

In
`@packages/vechain-kit/src/components/AccountModal/Contents/TokenDetail/TokenDetailContent.tsx`:
- Line 42: Replace the local VET_SENTINEL constant with the centralized
VET_TOKEN_SENTINEL: remove the const VET_SENTINEL = '0x' and import
VET_TOKEN_SENTINEL from the transfer-history types module where it is declared,
then replace all usages of VET_SENTINEL inside the TokenDetailContent component
(the places that check or compare token sentinel values) with VET_TOKEN_SENTINEL
to avoid duplication.

In
`@packages/vechain-kit/src/components/AccountModal/Contents/TransactionHistory/TransactionDetailContent.tsx`:
- Line 102: Extract the inline ZERO_ADDRESS into the shared constants module
used by the transfer history layer (the same place that exports
VET_TOKEN_SENTINEL and VTHO_TOKEN_ADDRESS); add and export a ZERO_ADDRESS
constant there, then replace the inline declaration in TransactionDetailContent
(referencing ZERO_ADDRESS) with an import from that shared constants module so
all components use the single canonical value.
- Around line 43-50: Extract the inline date helpers into a shared utility by
creating a new module (e.g., dateUtils.ts) that exports functions matching the
existing helpers' signatures—move formatFullDate and formatDayLabel into it,
retain the locale and timestamp parameters and Intl.DateTimeFormat options, then
update TransactionDetailContent (replace the local formatFullDate) and
TransactionHistoryContent (replace formatDayLabel) to import these helpers;
ensure existing behavior and formats are preserved and run tests/compile to
confirm no type or import issues.

In `@packages/vechain-kit/src/hooks/api/staking/useStargatePositions.ts`:
- Around line 36-50: Replace the inline sentinel const VET_ADDRESS = '0x' in
useStargatePositions with the shared canonical VET constant used by the
wallet/history hooks: import that exported VET token key (the shared VET
constant) at the top of the file and use it in the pricing lookup (vetPriceUsd =
prices[SHARED_VET_CONSTANT] || 0). Update any references to VET_ADDRESS in this
module (e.g., vetPriceUsd) to the imported constant so the stargate price lookup
matches the rest of the app.

In `@packages/vechain-kit/src/hooks/api/wallet/useOraclePriceChanges24h.ts`:
- Line 131: The unused constant SCALE is defined but only referenced via a no-op
"void SCALE;" which should be removed or documented; delete the SCALE
declaration and the "void SCALE;" line inside useOraclePriceChanges24h (or, if
SCALE is intended for future use, replace the void usage with a comment
explaining its planned purpose) so there are no dead symbols left in the hook.
- Around line 56-64: The map callback silently swallows errors from
oracle.read.getLatestValue; update the catch block in the feedEntries.map(async
([token, feedId]) => { ... }) callback to log the failure (including token and
feedId and the caught error) before returning [token, null]; use the project's
logger if available (e.g., processLogger or a provided logger), otherwise
fallback to console.error, and keep the behavior of returning [token, null]
unchanged.
- Around line 95-113: The event-decoding loop swallows all decoding errors,
hiding malformed events or ABI mismatches; update the catch block around
viemDecodeEventLog(...) in the loop (where OracleVechainEnergy__factory.abi,
events, and pastByFeedId are used) to log the failure details and the error
(include event.data, event.topics and the caught error). Use the existing logger
(e.g., processLogger or a module logger) if available, otherwise fallback to
console.warn, so decoding failures are visible for debugging while still
continuing to ignore that single malformed entry.