Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

frame_system::remark: Allow any kind of origin #14260

Merged
merged 2 commits into from
Jun 4, 2023
Merged

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented May 29, 2023

There should be no downside in allowing any kind of origin for remark.

There should be no downside in allowing any kind of origin for `remark`.
@bkchr bkchr added A0-please_review Pull request needs code review. D5-nicetohaveaudit ⚠️ PR contains trivial changes to logic that should be properly reviewed. B1-note_worthy Changes should be noted in the release notes T1-runtime This PR/Issue is related to the topic “runtime”. labels May 29, 2023
@bkchr bkchr requested review from a team May 29, 2023 15:07
@bkchr bkchr added the C1-low PR touches the given topic and has a low impact on builders. label May 29, 2023
Copy link
Member

@ggwpez ggwpez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So in theory this is fine, but in practice this can be used to inflate indexers / archive nodes.

@bkchr
Copy link
Member Author

bkchr commented May 30, 2023

but in practice this can be used to inflate indexers / archive nodes.

What?

@ggwpez
Copy link
Member

ggwpez commented May 30, 2023

but in practice this can be used to inflate indexers / archive nodes.

What?

Ah i thought it would allow unsigned TX, but it does not. Okay 👍

frame/system/src/lib.rs Show resolved Hide resolved
@bkchr bkchr merged commit e0752b1 into master Jun 4, 2023
@bkchr bkchr deleted the bkchr-remark-every-origin branch June 4, 2023 21:15
nathanwhit pushed a commit to nathanwhit/substrate that referenced this pull request Jul 19, 2023
* frame_system::remark: Allow any kind of origin

There should be no downside in allowing any kind of origin for `remark`.

* Fix tests
@shawntabrizi
Copy link
Member

Sorry, dumb question: Why does this not allow unsigned? Do we not allow unsigned by default?

@command-bot

This comment was marked as spam.

@ggwpez
Copy link
Member

ggwpez commented Jul 24, 2023

Sorry, dumb question: Why does this not allow unsigned? Do we not allow unsigned by default?

Who would then pay the TX fee?
I think to support unsigned tx, the pallet needs a dedicated validate_unsigned hook to manually do the spam protection.

@bkchr
Copy link
Member Author

bkchr commented Jul 24, 2023

Sorry, dumb question: Why does this not allow unsigned? Do we not allow unsigned by default?

Unsigned transactions are rejected by default. As @ggwpez said you need a proper validate_unsigned to accept them.

@shawntabrizi
Copy link
Member

great, makes sense, i just didnt remember explicitly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B1-note_worthy Changes should be noted in the release notes C1-low PR touches the given topic and has a low impact on builders. D5-nicetohaveaudit ⚠️ PR contains trivial changes to logic that should be properly reviewed. T1-runtime This PR/Issue is related to the topic “runtime”.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

8 participants