feat: support multi range request

[keiya01]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

If you have any plan to support the multi range, you can close this PR freely :)

[JonasKruckenberg]

Your commits are not signed, so we can only merge this PR once you set that up and we have a plan on how we want to handle feature additions going forward.

[keiya01]

It looks like my commit is signed 👀
And is this PR not needed?

[lucasfernog]

First of all thank you for your contribution! We did not merge it because we didn't have the resources to audit it and I also couldn't find a way to test it (I'm still not sure if this is needed, no one requested it so far). I believe Amr also implemented this on the protocol refactor so I'll close this.