-
Notifications
You must be signed in to change notification settings - Fork 100
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
MultiSigInbox Plugin #487
MultiSigInbox Plugin #487
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good @shargon.
I like the name you gave to the plugin.
I think this will be very useful to the ecosystem.
} | ||
|
||
[ConsoleCommand("inbox list", Category = "MultiSigInbox", Description = "List pending transactions")] | ||
private void OnInboxList(bool pending = true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shargon, I think that signers can send both a complete transaction that is partially signed or just the hash and a partial signature.
In this way we avoid unnecessary traffic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However, transactions are usually small and not really a problem for the P2P.
Perhaps all should send the complete tx.
Let's move on? I think it's useful although it's too late for RC1 but maybe we could implement it in RC2. |
The plugin only could be used by white listed wallets, it's this ok? |
I think it's enough. |
@neo-project/ngd-shanghai could you help me with testing? |
Sure. |
The code looks good. Please wait for the test. |
{ | ||
public class MultiSigInboxPlugin : Plugin, IP2PPlugin | ||
{ | ||
public const string StatePayloadCategory = "MultiSignatureInbox"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
public const string StatePayloadCategory = "MultiSignatureInbox"; | |
public const string MutiSigPayloadCategory = "MultiSignatureInbox"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Do we need this if we can have more generic Notary subsystem (neo-project/neo#1573)? This only works for a whitelist of addresses while Notary subsystem is available for anyone and can handle a lot more cases. It also adds another proper paid-for service for the network which can be beneficial for project economics. Notary subsystem has complete implementation in neo-go and it's already integrated into NeoFS (nspcc-dev/neofs-contract#51), it works. |
@superboyiii could you check it again please |
|
Co-authored-by: Owen Zhang <38493437+superboyiii@users.noreply.github.com>
@superboyiii please copy your input as text here |
neo> inbox list You could try it in my tempo testnet. |
@superboyiii Thanks, please test it |
Maybe we could advance on this, could be a good feature besides Neo Committee that is now consolidated. |
I still think this is a good plugin, @shargon. Specific nodes can use it if they want. |
It's still too limited (hi, #487 (comment)), extensible messages can be sent by a very limited set of addresses. |
close as inactive |
Close neo-project/neo#2269