Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[New Content]: xDomainMessageSender isnt documented

Open
#343 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
blockchain, documentation

Research direction

Start with the “the-scroll-messenger” page and the “scroll-messenger-cross-chain-interaction” guide, then inspect the xDomainMessageSender usage in the ERC20Gateway contract mentioned in the issue. Document what xDomainMessageSender does and how developers use it to gate the initiating contract; update the guide too if the explanation belongs there.

Written by the indexing model from the issue text.

Description

What would you like us to add?

Add xDomainMessageSender to the "the-scroll-messenger" page and maybe add it to the "scroll-messenger-cross-chain-interaction" guide

How important it is?

It's essential in cases where a developer needs to bridge state between contracts on L1 and L2. It allows the developer to gate which contract initiated the bridge transaction.

I needed it for my project and saw it in scrolls erc20Gateway contract. I think it will be very useful to be in the docs :)

Dominant language
MDX
Stars
701
Forks
196
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scroll-tech/scroll-documentation

All issues in scroll-tech/scroll-documentation

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.