[Bug]: Potential Scam
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Open the Scroll upgrades page at https://docs.scroll.io/en/technology/overview/scroll-upgrades/ and inspect the Telegram technical-updates link. Remove the non-functional Telegram link, correct the reported “Scoll” typos, and verify that the page no longer directs users to the inactive channel.
Written by the indexing model from the issue text.
Description
Describe the bug
The official documentation website includes a link to a Telegram channel named scroll_tech_updates. Currently, this link is non-functional, displaying a message that the channel does not exist. To address this issue and mitigate potential security risks, a commit was made to remove the Telegram link from the project repository.
Key Risks of Maintaining the Inactive Link:
Impersonation by Scammers: Malicious actors could create a Telegram channel with the same name, misleading users into believing it is the official channel. This deception could facilitate the spread of fraudulent information or malicious links.
Phishing Attempts: Scammers might redirect users to phishing websites designed to steal sensitive information or funds from their wallets.
Erosion of Trust: Fraudulent activities originating from a seemingly official channel could severely damage the project's reputation and undermine user trust.
I have encountered similar situations in other projects. Here is an example: https://github.com/farcasterxyz/docs/pull/297
Additionally updated typos in docs Scoll -> Scroll
To Reproduce
- Go to https://docs.scroll.io/en/technology/overview/scroll-upgrades/
- Click on Telegram channel for technical updates
- See that the Telegram channel does not exist
URLs
Expected behavior
No response
Additional context
No response
- Dominant language
- MDX
- Stars
- 701
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scroll-tech/scroll-documentation
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
enhancement
scroll-tech/scroll-documentation#427 · 1 comment · 1 assignee ·
All issues in scroll-tech/scroll-documentation
Similar issues
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·