Thanks for the response! Yes ive recently found this to be the case, but lets imagine 10k user wallets, i cant keep those listeners running 24/7.
so i decide to try and write a rpelay method that when a wallet is added to the chain again it will catchup by manually pulling, block by block from the blockstore and alerting the wallet via its listener methods. Is this in any way viable? or are there some further issues that make this impossible? I dont see the point of having a relational block store if i cant use it for anything other than pulling balance for a specific address. the goal is 1 peer group, one block chain and 1 store for 10k wallets (just an example number). the functionality is there, the chain is downloaded, i have the resources to handle that many sql queries, i dont however have the bandwidth to constantly reset and download the chain (plus a full blockchain download can take days if its not spv it seems) what can be done? -- 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.
