Class NativeBlockChainListener
- java.lang.Object
- 
- org.bitcoinj.jni.NativeBlockChainListener
 
- 
- All Implemented Interfaces:
- NewBestBlockListener,- ReorganizeListener,- TransactionReceivedInBlockListener
 
 public class NativeBlockChainListener extends java.lang.Object implements NewBestBlockListener, ReorganizeListener, TransactionReceivedInBlockListener An event listener that relays events to a native C++ object. A pointer to that object is stored in this class using JNI on the native side, thus several instances of this can point to different actual native implementations.
- 
- 
Field SummaryFields Modifier and Type Field Description longptr
 - 
Constructor SummaryConstructors Constructor Description NativeBlockChainListener()
 - 
Method SummaryAll Methods Instance Methods Concrete Methods Modifier and Type Method Description voidnotifyNewBestBlock(StoredBlock block)Called when a new block on the best chain is seen, after relevant transactions are extracted and sent to us via eitherTransactionReceivedInBlockListener.receiveFromBlock(Transaction, StoredBlock, AbstractBlockChain.NewBlockType, int)orTransactionReceivedInBlockListener.notifyTransactionIsInBlock(Sha256Hash, StoredBlock, AbstractBlockChain.NewBlockType, int).booleannotifyTransactionIsInBlock(Sha256Hash txHash, StoredBlock block, AbstractBlockChain.NewBlockType blockType, int relativityOffset)Called by theBlockChainwhen we receive a newFilteredBlockthat contains the given transaction hash in its merkle tree.voidreceiveFromBlock(Transaction tx, StoredBlock block, AbstractBlockChain.NewBlockType blockType, int relativityOffset)Called by theBlockChainwhen we receive a new block that contains a relevant transaction.voidreorganize(StoredBlock splitPoint, java.util.List<StoredBlock> oldBlocks, java.util.List<StoredBlock> newBlocks)Called by theBlockChainwhen the best chain (representing total work done) has changed.
 
- 
- 
- 
Method Detail- 
notifyNewBestBlockpublic void notifyNewBestBlock(StoredBlock block) throws VerificationException Description copied from interface:NewBestBlockListenerCalled when a new block on the best chain is seen, after relevant transactions are extracted and sent to us via eitherTransactionReceivedInBlockListener.receiveFromBlock(Transaction, StoredBlock, AbstractBlockChain.NewBlockType, int)orTransactionReceivedInBlockListener.notifyTransactionIsInBlock(Sha256Hash, StoredBlock, AbstractBlockChain.NewBlockType, int). If this block is causing a re-organise to a new chain, this method is NOT called even though the block may be the new best block: your reorganize implementation is expected to do whatever would normally be done do for a new best block in this case.- Specified by:
- notifyNewBestBlockin interface- NewBestBlockListener
- Throws:
- VerificationException
 
 - 
reorganizepublic void reorganize(StoredBlock splitPoint, java.util.List<StoredBlock> oldBlocks, java.util.List<StoredBlock> newBlocks) throws VerificationException Description copied from interface:ReorganizeListenerCalled by theBlockChainwhen the best chain (representing total work done) has changed. In this case, we need to go through our transactions and find out if any have become invalid. It's possible for our balance to go down in this case: money we thought we had can suddenly vanish if the rest of the network agrees it should be so.The oldBlocks/newBlocks lists are ordered height-wise from top first to bottom last (i.e. newest blocks first). - Specified by:
- reorganizein interface- ReorganizeListener
- Throws:
- VerificationException
 
 - 
receiveFromBlockpublic void receiveFromBlock(Transaction tx, StoredBlock block, AbstractBlockChain.NewBlockType blockType, int relativityOffset) throws VerificationException Description copied from interface:TransactionReceivedInBlockListenerCalled by the BlockChainwhen we receive a new block that contains a relevant transaction.A transaction may be received multiple times if is included into blocks in parallel chains. The blockType parameter describes whether the containing block is on the main/best chain or whether it's on a presently inactive side chain. The relativityOffset parameter is an arbitrary number used to establish an ordering between transactions within the same block. In the case where full blocks are being downloaded, it is simply the index of the transaction within that block. When Bloom filtering is in use, we don't find out the exact offset into a block that a transaction occurred at, so the relativity count is not reflective of anything in an absolute sense but rather exists only to order the transaction relative to the others. - Specified by:
- receiveFromBlockin interface- TransactionReceivedInBlockListener
- Throws:
- VerificationException
 
 - 
notifyTransactionIsInBlockpublic boolean notifyTransactionIsInBlock(Sha256Hash txHash, StoredBlock block, AbstractBlockChain.NewBlockType blockType, int relativityOffset) throws VerificationException Description copied from interface:TransactionReceivedInBlockListenerCalled by the BlockChainwhen we receive a newFilteredBlockthat contains the given transaction hash in its merkle tree.A transaction may be received multiple times if is included into blocks in parallel chains. The blockType parameter describes whether the containing block is on the main/best chain or whether it's on a presently inactive side chain. The relativityOffset parameter in this case is an arbitrary (meaningless) number, that is useful only when compared to the relativity count of another transaction received inside the same block. It is used to establish an ordering of transactions relative to one another. This method should return false if the given tx hash isn't known about, e.g. because the the transaction was a Bloom false positive. If it was known about and stored, it should return true. The caller may need to know this to calculate the effective FP rate. - Specified by:
- notifyTransactionIsInBlockin interface- TransactionReceivedInBlockListener
- Returns:
- whether the transaction is known about i.e. was considered relevant previously.
- Throws:
- VerificationException
 
 
- 
 
-