Skip to content
\n

The <- arrow to the right indicates which data source/asset ID will be automatically selected by the price tool. So it's currently selecting Strike via CryptoCompare as you described.

\n

If you want to change this so that Starknet is used instead, you would need to change the data_source_select parameter in your bittytax.conf file as follows:

\n
data_source_select: {\n    'STRK': ['CoinGecko:starknet'],\n    }\n
\n

Your bittytax.conf file is held in the .bittytax folder within your home directory, to find more information about the config file see here.

\n

You may already have some entries defined in data_source_select so add STRK as an additional row, the ordering is not important.

","upvoteCount":1,"url":"https://GitHub.com/BittyTax/BittyTax/discussions/361#discussioncomment-9068750"}}}

Problem with STRK symbol - This has two token associated with it, how to define the correct one? #361

Answered by nanonano
grumpydolphin asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @grumpydolphin,

You can use the Price Tool to find all tokens with that symbol name.

$ bittytax_price list STRK 
STRK (Strike) via CryptoCompare <-
STRK (Starknet) via CoinGecko [ID:starknet]
STRK (Strike) via CoinGecko [ID:strike]
STRK (Starknet) via CoinPaprika [ID:strk-starknet]
STRK (Strike) via CoinPaprika [ID:strk-strike]
STRK (StarkWare) via CoinPaprika [ID:strk-starkware]

The <- arrow to the right indicates which data source/asset ID will be automatically selected by the price tool. So it's currently selecting Strike via CryptoCompare as you described.

If you want to change this so that Starknet is used instead, you would need to change the data_source_select parameter in your b…

Replies: 1 comment 5 replies

Comment options

You must be logged in to vote
5 replies
@grumpydolphin
Comment options

@grumpydolphin
Comment options

@nanonano
Comment options

@grumpydolphin
Comment options

@nanonano
Comment options

Answer selected by nanonano
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #360 on April 10, 2024 09:06.