Consensus algorithm in Corda
up vote
0
down vote
favorite
Normaly the nottary node is defined like as shown below in build.gradle file
From above image how do we understand the consensus algorithm of this particular notary?
or from where(which file) we can get information regarding the consensus algorithm of Notary Used?
corda
add a comment |
up vote
0
down vote
favorite
Normaly the nottary node is defined like as shown below in build.gradle file
From above image how do we understand the consensus algorithm of this particular notary?
or from where(which file) we can get information regarding the consensus algorithm of Notary Used?
corda
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Normaly the nottary node is defined like as shown below in build.gradle file
From above image how do we understand the consensus algorithm of this particular notary?
or from where(which file) we can get information regarding the consensus algorithm of Notary Used?
corda
Normaly the nottary node is defined like as shown below in build.gradle file
From above image how do we understand the consensus algorithm of this particular notary?
or from where(which file) we can get information regarding the consensus algorithm of Notary Used?
corda
corda
asked Nov 19 at 11:16
Jk_
234
234
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
All that notary does is check that no states have been spent already when a transaction is sent to it. It does so by storing hashes of spent states and checks that the states in the transaction are not stored in the notary.
It is not using a consensus algorithm.
The validating=true is saying that it will execute the contract validation as part of checking the transaction. If that was set to false, it would only check for double spends.
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
All that notary does is check that no states have been spent already when a transaction is sent to it. It does so by storing hashes of spent states and checks that the states in the transaction are not stored in the notary.
It is not using a consensus algorithm.
The validating=true is saying that it will execute the contract validation as part of checking the transaction. If that was set to false, it would only check for double spends.
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
add a comment |
up vote
0
down vote
All that notary does is check that no states have been spent already when a transaction is sent to it. It does so by storing hashes of spent states and checks that the states in the transaction are not stored in the notary.
It is not using a consensus algorithm.
The validating=true is saying that it will execute the contract validation as part of checking the transaction. If that was set to false, it would only check for double spends.
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
add a comment |
up vote
0
down vote
up vote
0
down vote
All that notary does is check that no states have been spent already when a transaction is sent to it. It does so by storing hashes of spent states and checks that the states in the transaction are not stored in the notary.
It is not using a consensus algorithm.
The validating=true is saying that it will execute the contract validation as part of checking the transaction. If that was set to false, it would only check for double spends.
All that notary does is check that no states have been spent already when a transaction is sent to it. It does so by storing hashes of spent states and checks that the states in the transaction are not stored in the notary.
It is not using a consensus algorithm.
The validating=true is saying that it will execute the contract validation as part of checking the transaction. If that was set to false, it would only check for double spends.
answered Nov 19 at 11:23
Dan Newton
1512
1512
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
add a comment |
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
then where does this Consensus algorithm, which is associated with Notary come to picture?
– Jk_
Nov 19 at 11:26
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
@dan-newton That's true, but when you have pools of notaries, they need to use some consensus algorithm to ensure the pool is in agreement about which states are spent.
– Joel
Nov 19 at 12:11
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373452%2fconsensus-algorithm-in-corda%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown