Security #1301
-
|
Is it possible to make a public/private key check at consensus level while processing txn, to verify the transaction is coming from genuine node |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
A user that can access to the API of a node, and has an account (a private key to sign) can place a transaction, like the ethereum network. For a private tx, you need to know the public key(s) of the node-member(s). |
Beta Was this translation helpful? Give feedback.
-
|
When using config files there's nothing stopping a node being miss-configured. Say you have a 3 node network (A,B,C) and 1 (C) of the nodes has an extra node allowed (D). D will be able to create transactions and have them propagated to the network through C. A and B will not allow direct connection to the network from D. It's imperative that all nodes have the same config. In a nutshell, you need to trust the members in the consortium to no let someone else in. If you use the smart contract solution this is much easier to enforce. |
Beta Was this translation helpful? Give feedback.
When using config files there's nothing stopping a node being miss-configured. Say you have a 3 node network (A,B,C) and 1 (C) of the nodes has an extra node allowed (D). D will be able to create transactions and have them propagated to the network through C. A and B will not allow direct connection to the network from D. It's imperative that all nodes have the same config. In a nutshell, you need to trust the members in the consortium to no let someone else in.
If you use the smart contract solution this is much easier to enforce.