Not sure how long it should take.

I'm using a 15MB keys.json from 0.9.3c in Firefox, with roughly 90k keys. I selected the file and now 15mins in.  Still have the spinning circle, not sure if its doing anything.

I've already imported these key with another method, just testing.

It should spin when downloading the 1MB filter.. There is probably a console error that caused it to be stuck in the spinning state.  Can you please send me any errors if you see them.

TEST COMPLETE.. the filter is in the main wallets now.

   https://bitshares.org/worker

** this is temporary, later you'll file the same wallet under the typical place:  https://bitshares.org/wallet
EDIT: please post browser name and version

This uses the BitShares 2.0 Genesis bloom filter to reduce the size of wallets when importing BTS 0.9.x key files.  The filter is applied to all BTS 0.9.x exported keys (by file format) upon import.  Also "worker" refers to the HTML5 worker threads...

The /worker release has a 1MB file in it (a bloom filter) that was built using all public keys and public addresses used in the BTS 2.0 genesis.json file.  When you import a BTS 0.9.x keys file (or backup), the public keys and addresses are checked against the filter.  With 100% certainty any private key has a public key or address in the genesis block will be included.  Almost all keys that do not appear in the genesis block will be filtered out and do not import..

If you have a small wallet and all the keys are used you may not even notice it happened..  We are mostly interested in: did it work?

This will remove any spent TITAN addresses and remove any unused keys that were created by BTS < 2.0 generate key commands, etc..  You should save and backup your original BTS 0.9.x keys export file as that contains all your keys.

Typically you will use this url or a partner's URL instead:
  https://bitshares.org/wallet

Both /wallet and /worker share the same local storage
(after we remove the /worker directory you will will remain at /wallet)

This release is not available in an installer yet.  You may wait or try to filter yourself:
  GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
  https://bitsharestalk.org/index.php/topic,19390.0.html

I'm doing a separate temporary release because I need to know if the HTML5 worker threads are going to work for most browsers.  There are varying degrees of support so I tried to stick to the very basic stuff.  Worker threads lets us get into multi-core processing so this is a good thing to know about...

EDIT:  Filtering 130K keys started almost instantly (about 1 sec to download the filter as shown in the network tab) and took 3 minutes to filter.  In my case about 500 keys remained.  After clicking import the wallet was ready in about 5 seconds.

I'm not sure if I wait a simpler solution or I dig into this one.

Anyone knows how much time it could take to have a wallet base simpler solution ?

Anyone could give me an estimation of the time it could takes to me to acheive it with the explanations above ? I've wrote a few lines of html, css and autohotkey but my code knowledge is not very deep. I'm on windows 10 / light client.

Thanks

Today for notes and tomorrow to test it.  So tomorrow or the day after...

made it to step 2

Code: [Select]

merockstar@merockstar-HP-Pavilion-dv6-Notebook-PC:~/Desktop/key pruning$ cat mig6.json | node ./bloom_filter_wallet.js > pruned1.json

module.js:340
    throw err;
          ^
Error: Cannot find module '../src/common/hash'
  at Function.Module._resolveFilename (module.js:338:15)
  at Function.Module._load (module.js:280:25)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/home/merockstar/Desktop/key pruning/bloom_filter_wallet.js:20:9)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  at startup (node.js:119:16)
  at node.js:902:3

coffee script is installe

The instructions do not give you all the files you need. One way is to clone the repository. I have a sample maybe by for Monday so you can do this in the web wallet instead.

Where is the new wallet file in Bitshares 2?  I compiled a local wallet on a linux machine.

It is in the browser's local storage... I have been fussing with large test wallets trying to get the browser to work well for weeks now.  I am fresh with knowledge but I'm believing this it is not something that can be fixed over-night and would require improvements in the browser.

Your best bet is to run the filter on the wallet file to get rid of a bunch of those unused keys (in the future we should not save unused generated keys!).  So, there will be constant issues with insanely large wallets some of which I believe are in Chrome and FF and out of my control.  I have seen decent performance with up to 10K keys which is very large for normal usage.

We are considering options to streamline the process and your feedback helps. 

...backup your original key file as it contains all your keys.

This should fix the issue in the repo as of Oct 14th...
https://github.com/cryptonomex/graphene-ui/issues/330

It is running at openledger.  However, the last release v2.15.286 happened on Oct 13th.

Can anyone confirm the fix at open ledger?