I guess these are the fields in Wallet.proto you mentioned

optional bytes last_seen_block_hash = 2;
// The height in the chain of the last seen block.
optional uint32 last_seen_block_height = 12;
optional int64 last_seen_block_time_secs = 14; What might be a good way to 
ensure correctness ? My current plan is I to 1. disable `autosave` in 
`Wallet` class and 2. add a bunch of listeners to the `Wallet` class and 
persist the wallet only after successful event processing. But I am 
concerned about whether the event handlers are triggered in any specific 
sequence so that replaying is not an issue ? If the events are received in 
a different order after a restart, is there any chance that the wallet 
misses certain transaction ? Thanks !
On Monday, November 12, 2018 at 6:36:00 PM UTC+8, Mike Lawrence wrote:
>
> The wallet connects to a bitcoind node and receives tx updates as blocks 
> get added to the bitcoind's blockchain.
>
> If you use a persistent wallet then the wallet uses a block level to 
> resync any missed txs. 
>
> On Sun, Nov 11, 2018 at 11:13 PM oat cookies <oatcoo...@gmail.com 
> <javascript:>> wrote:
>
>> I plan to set up a payment detection system using the SPV wallet of 
>> BitcoinJ on cloud (so resource is not a problem) and set up my own bitcoind 
>> full node. My question is, how does the wallet class keep track on the 
>> progress of synchronisation ? If the application crash somewhere and 
>> restart again, how can I make sure I won't miss any transactions ? Thanks !
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "bitcoinj" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to bitcoinj+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Mike Lawrence
>

-- 
You received this message because you are subscribed to the Google Groups 
"bitcoinj" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bitcoinj+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to