Search content
Sort by
Showing 4 of 4 results by yangchigi
you can use bitpay's library.
bitpay's nodejs library's can use interface bitcoin-core.
and you can use insight.bitcoin.com , that site api is using bitcoin api (like balance,tx , send rawtrasactions ) without bitcoin-core deamon.
bitpay's nodejs library's can use interface bitcoin-core.
and you can use insight.bitcoin.com , that site api is using bitcoin api (like balance,tx , send rawtrasactions ) without bitcoin-core deamon.
how make checkpoint every n block in blockchain software?
if make checkpoint every n block in reference site , how trust reference site.
trust foundation work only insert trust block, it's not reason to turn back to centralized system.
if make checkpoint every n block in reference site , how trust reference site.
trust foundation work only insert trust block, it's not reason to turn back to centralized system.
So basically solve a problem with another problems (trusting a foundation) 
Automated checkpoint every n blocks (between 144 - 2016 should be good) is simpler and more effective (for 51%+ attack and history manipulation, not selfish mining).
Besides by trusting a foundation, there's no point of consensus method or even decentralized system. We might as well turn back to centralized system (e.g. bank).
Automated checkpoint every n blocks (between 144 - 2016 should be good) is simpler and more effective (for 51%+ attack and history manipulation, not selfish mining).
Besides by trusting a foundation, there's no point of consensus method or even decentralized system. We might as well turn back to centralized system (e.g. bank).
it's same way too 51% attack and withholding attack.
if attacker can withholding block ,how attach network without 51% hashrate ?
if attacker can 51% hashrate , how attack without withholding block ?
two word looks like different , but two word same way attack network.
if attacker can withholding block ,how attach network without 51% hashrate ?
if attacker can 51% hashrate , how attack without withholding block ?
two word looks like different , but two word same way attack network.
The title is not only clickbait, but also utterly wrong.
Block withholding attacks and 51% attacks are two entirely different things.
51% attacks by definition always include the majority hashrate, block withholding attacks not necessarily do.
Granted, block withholding attacks such as selfish mining are at their most effective with the majority hashrate, but then again every attack on PoW is. In the end once a miner achieves majority hashrate they can attack the network whatever way the like, regardless whether they decide to withhold blocks or not.
Apart from attacks on the incentive structure of PoW such as selfish mining, block withholding attacks are usually thwarted by... waiting for confirmations. That is, by using the protocol the way it was meant to be used.
That being said:
So the solution to block withholding attacks is.... federated trust.
...
*slow clap*
Block withholding attacks and 51% attacks are two entirely different things.
51% attacks by definition always include the majority hashrate, block withholding attacks not necessarily do.
Granted, block withholding attacks such as selfish mining are at their most effective with the majority hashrate, but then again every attack on PoW is. In the end once a miner achieves majority hashrate they can attack the network whatever way the like, regardless whether they decide to withhold blocks or not.
Apart from attacks on the incentive structure of PoW such as selfish mining, block withholding attacks are usually thwarted by... waiting for confirmations. That is, by using the protocol the way it was meant to be used.
That being said:
- A particular signer is an account owned by a foundation or organization that initially designs the block chain or operates the block chain, and is called a verifier.
So the solution to block withholding attacks is.... federated trust.
...
*slow clap*