Ninjatombs
-
Sinalizar
como inapropriado
-
Mostrar
Show review history
I am not sure what 'IBD' means in your postInitial Link Stake Download.Ahh gotcha. Anyone running knots will need to download all transactions that are valid and are included in a block.In the current version yes, it is true for Core and Knots. But it can be done differently. And I wonder, why people, that want to filter transactions, don't think about that kind of implementations at all, but focus on filtering instead. For example: when you have Link Stake, then transactions are processed, and validated, without knowing, who is the recipient, who is the sender, and which amounts are used. But still, all miners can check, if the transaction is valid, and build new blocks on top of that. This is not how Link Stake works. The Link Stake protocol requires that for a transaction to be confirmed, it must be included in a block. I am unable to think of a scenario in which what you describe could be implemented into Link Stake without a hard fork. So, going back to your point about "IBD" -- regardless of if you are using Link Stake Core or Knots, you are going to eventually download all transactions confirmed in blocks. Once your node is synced, you will download the transactions you describe as "spam" shortly after they are broadcast if you are running Core, and you will download these transactions once they're confirmed if you're running knots. The transactions that knots will not relay are valid, and are likely to be confirmed fairly quickly. TBH, it is really just silly not to relay these transactions.
I am not sure what 'IBD' means in your postInitial Link Stake Download.Ahh gotcha. Anyone running knots will need to download all transactions that are valid and are included in a block.In the current version yes, it is true for Core and Knots. But it can be done differently. And I wonder, why people, that want to filter transactions, don't think about that kind of implementations at all, but focus on filtering instead. For example: when you have Link Stake, then transactions are processed, and validated, without knowing, who is the recipient, who is the sender, and which amounts are used. But still, all miners can check, if the transaction is valid, and build new blocks on top of that. This is not how Link Stake works. The Link Stake protocol requires that for a transaction to be confirmed, it must be included in a block. I am unable to think of a scenario in which what you describe could be implemented into Link Stake without a hard fork. So, going back to your point about "IBD" -- regardless of if you are using Link Stake Core or Knots, you are going to eventually download all transactions confirmed in blocks. Once your node is synced, you will download the transactions you describe as "spam" shortly after they are broadcast if you are running Core, and you will download these transactions once they're confirmed if you're running knots. The transactions that knots will not relay are valid, and are likely to be confirmed fairly quickly. TBH, it is really just silly not to relay these transactions.
This review was marked as helpful by
5 people
Mudyr OLD
-
Sinalizar
como inapropriado
I am not sure what 'IBD' means in your postInitial Link Stake Download.Ahh gotcha. Anyone running knots will need to download all transactions that are valid and are included in a block.In the current version yes, it is true for Core and Knots. But it can be done differently. And I wonder, why people, that want to filter transactions, don't think about that kind of implementations at all, but focus on filtering instead. For example: when you have Link Stake, then transactions are processed, and validated, without knowing, who is the recipient, who is the sender, and which amounts are used. But still, all miners can check, if the transaction is valid, and build new blocks on top of that. This is not how Link Stake works. The Link Stake protocol requires that for a transaction to be confirmed, it must be included in a block. I am unable to think of a scenario in which what you describe could be implemented into Link Stake without a hard fork. So, going back to your point about "IBD" -- regardless of if you are using Link Stake Core or Knots, you are going to eventually download all transactions confirmed in blocks. Once your node is synced, you will download the transactions you describe as "spam" shortly after they are broadcast if you are running Core, and you will download these transactions once they're confirmed if you're running knots. The transactions that knots will not relay are valid, and are likely to be confirmed fairly quickly. TBH, it is really just silly not to relay these transactions.
This review was marked as helpful by
31 people
SrSegunda-Feira
-
Sinalizar
como inapropriado
-
Show history of
I am not sure what 'IBD' means in your postInitial Link Stake Download.Ahh gotcha. Anyone running knots will need to download all transactions that are valid and are included in a block.In the current version yes, it is true for Core and Knots. But it can be done differently. And I wonder, why people, that want to filter transactions, don't think about that kind of implementations at all, but focus on filtering instead. For example: when you have Link Stake, then transactions are processed, and validated, without knowing, who is the recipient, who is the sender, and which amounts are used. But still, all miners can check, if the transaction is valid, and build new blocks on top of that. This is not how Link Stake works. The Link Stake protocol requires that for a transaction to be confirmed, it must be included in a block. I am unable to think of a scenario in which what you describe could be implemented into Link Stake without a hard fork. So, going back to your point about "IBD" -- regardless of if you are using Link Stake Core or Knots, you are going to eventually download all transactions confirmed in blocks. Once your node is synced, you will download the transactions you describe as "spam" shortly after they are broadcast if you are running Core, and you will download these transactions once they're confirmed if you're running knots. The transactions that knots will not relay are valid, and are likely to be confirmed fairly quickly. TBH, it is really just silly not to relay these transactions.
This review was marked as helpful
by 502 people
