diff --git a/.vitepress/config.mts b/.vitepress/config.mts index 739b698..8be4064 100644 --- a/.vitepress/config.mts +++ b/.vitepress/config.mts @@ -74,6 +74,7 @@ export default defineConfig({ { text: 'Taking Notes In-App', link: '/usage-guides/user-notes' }, { text: 'Global Search', link: '/usage-guides/global-search' }, { text: 'Settings', link: '/usage-guides/customization' }, + { text: 'Help & Support', link: '/usage-guides/help-support' }, ], }, { diff --git a/public/images/events_query_status.png b/public/images/events_query_status.png index 6e1f401..18e17db 100644 Binary files a/public/images/events_query_status.png and b/public/images/events_query_status.png differ diff --git a/public/images/help_support_menu.png b/public/images/help_support_menu.png new file mode 100644 index 0000000..e0f5112 Binary files /dev/null and b/public/images/help_support_menu.png differ diff --git a/public/images/mark_as_spam.png b/public/images/mark_as_spam.png new file mode 100644 index 0000000..4d774eb Binary files /dev/null and b/public/images/mark_as_spam.png differ diff --git a/public/images/redecode_events.png b/public/images/redecode_events.png index 12eb098..55704a7 100644 Binary files a/public/images/redecode_events.png and b/public/images/redecode_events.png differ diff --git a/public/images/report_issue_dialog.png b/public/images/report_issue_dialog.png new file mode 100644 index 0000000..7bf8eb7 Binary files /dev/null and b/public/images/report_issue_dialog.png differ diff --git a/public/images/repull_transactions2.png b/public/images/repull_transactions2.png deleted file mode 100644 index 6b528f5..0000000 Binary files a/public/images/repull_transactions2.png and /dev/null differ diff --git a/public/images/repull_transactions_notification.png b/public/images/repull_transactions_notification.png new file mode 100644 index 0000000..5436997 Binary files /dev/null and b/public/images/repull_transactions_notification.png differ diff --git a/public/images/see_query_status.png b/public/images/see_query_status.png index a4833f3..5b3348c 100644 Binary files a/public/images/see_query_status.png and b/public/images/see_query_status.png differ diff --git a/usage-guides/api-keys.md b/usage-guides/api-keys.md index e3612cf..63cebf9 100644 --- a/usage-guides/api-keys.md +++ b/usage-guides/api-keys.md @@ -19,7 +19,7 @@ For detailed information about premium plans, pricing, payment options, and how You can integrate many different exchanges with rotki via API Keys. Currently supported exchanges are: -- Kraken +- Kraken (Spot and Future) - Poloniex - Binance - Bitmex diff --git a/usage-guides/assets.md b/usage-guides/assets.md index afc7268..fc67370 100644 --- a/usage-guides/assets.md +++ b/usage-guides/assets.md @@ -124,6 +124,14 @@ It is also possible to ignore NFTs. To do this navigate to `Balances → NFT Bal ![Ignoring NFTs](/images/rotki_ignore_nfts.png) +## Mark asset as spam + +If you encounter an asset that you believe is spam (such as airdropped scam tokens), you can manually mark it as spam. This will add the asset to the ignored list and help keep your portfolio clean from unwanted tokens. + +To mark an asset as spam, navigate to `Manage Assets → Assets`, find the asset you want to mark, and click the arrow button beside the ignore/unignore switch to access the spam option. Once marked as spam, the asset will be treated the same as other ignored assets and will be excluded from all calculations and balance queries. Additionally, spam assets will not be decoded in history events. + +![Mark asset as spam](/images/mark_as_spam.png) + ## Whitelisting of ignored assets Spam assets are a plague in EVM chains. rotki has an automatic algorithm trying to match assets as spam to not bother the user with automatically ignoring them. You can see all ignored assets in `Manage Assets → Assets` and filter by ignored. A problem with automatic algorithms marking something as spam is that mistakes can be made and a legit token may be ignored. diff --git a/usage-guides/help-support.md b/usage-guides/help-support.md new file mode 100644 index 0000000..b13454f --- /dev/null +++ b/usage-guides/help-support.md @@ -0,0 +1,47 @@ +# Help & Support + +To access the Help & Support menu, click the **?** icon in the toolbar. + +![Help & Support Menu](/images/help_support_menu.png) + +The Help & Support menu provides quick access to: + +- **[Report Issue](#report-issue)** - Report bugs or request features +- **Usage Guide** - Get started with the documentation +- **FAQ** - Common questions about the application +- **Discord** - Join the community and get support +- **Github** - Review the code and open issues +- **Twitter / X** - Follow for updates + +## Report Issue + +If you encounter a bug or want to request a new feature, click on **Report Issue** to open the issue submission form. + +![Report Issue Dialog](/images/report_issue_dialog.png) + +### Filling Out the Form + +1. **Title** - Enter a brief summary of the issue (up to 100 characters) +2. **Description** - Provide detailed information about the bug or feature request (up to 1500 characters) + +### Submission Options + +You can submit your issue through one of the following channels: + +- **GitHub** - Opens an issue on the rotki GitHub repository +- **Google Form** - Submit via a form for private matters +- **Email** - Send directly to the team + +::: tip +GitHub issues are publicly visible. For private matters, use Google Form or Email instead. +::: + +### Tips + +#### Need Immediate Help? + +Get quick help from the community in the **#support** channel on [Discord](https://discord.rotki.com), or you can DM the team directly. + +#### Taking Screenshots? + +Before taking screenshots, enable privacy or scramble mode to hide sensitive data like balances and addresses. You can find this option in the privacy settings. diff --git a/usage-guides/historical-events.md b/usage-guides/historical-events.md index cfab0fd..8fe51ea 100644 --- a/usage-guides/historical-events.md +++ b/usage-guides/historical-events.md @@ -150,9 +150,9 @@ You can pull blockchain transaction events and events that come from exchanges. ![Repull transactions](/images/repull_transactions.png) -If any missed transactions are found, you'll see a notification indicating how many new transactions were discovered. +If any missed transactions are found, you'll see a notification indicating how many new transactions were discovered. You can click the action in the notification to view the pulled transactions. -![Repulled transactions result](/images/repull_transactions2.png) +![Repulled transactions result](/images/repull_transactions_notification.png) After the transactions are pulled, blockchain transactions need to be decoded, while events from exchanges will appear directly. For blockchain transactions, you can either: