-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Multisig accept arbitrary messages #1253
Comments
@vyzo could you implement this and submit a micro FIP documenting the change? |
sure, but whats a microfip?
…On Thu, Mar 2, 2023, 01:29 Steven Allen ***@***.***> wrote:
@vyzo <https://github.com/vyzo> could you implement this and submit a
*micro* FIP documenting the change?
—
Reply to this email directly, view it on GitHub
<#1253>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAI4SRDCAYZG52FOF4P6JTWZ7LUNANCNFSM6AAAAAAVKGH544>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I mean, write a FIP but keep it short. |
Ah, ok. Yessir, can do.
…On Thu, Mar 2, 2023, 18:34 Steven Allen ***@***.***> wrote:
I mean, write a FIP but keep it short.
—
Reply to this email directly, view it on GitHub
<#1253>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAI4SV3BQN33Y2E4SLC3KDW2DD2LANCNFSM6AAAAAAVKGH544>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This was referenced Mar 20, 2023
Was this all done? |
Unless I'm mistaken this has landed for multisigs in nv19. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To match the behavior of accounts, multisig and payment channel actors should default-accept arbitrary messages. See how "fallback" is handled in the account & ethaccount actors.
The text was updated successfully, but these errors were encountered: