Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jamesc

Pages: 1 2 3 4 [5] 6 7 8 9 10 11 12 ... 22
Code: [Select]
"connecting to wss://" app.js:2:183711
Configured for BitShares Object { core_asset: "BTS", address_prefix: "BTS", chain_id: "4018d7844c78f6a6c41c6a552b898022310…" } app.js:2:189461
db init done app.js:2:69245
ChainStore Init app.js:12:9104
synced and subscribed, chainstore ready app.js:12:9589
Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. vendors.js:1:20286
GenesisFilterWorker start 1ae2f77e0472c8b52ebd.worker.js:1:560
GenesisFilterWorker InvalidStateError: An attempt was made to use an object that is not, or is no longer, usable 1ae2f77e0472c8b52ebd.worker.js:1:786

A problem appeared under Firefox, I see the error and I'm working on it.. thank you

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.

I adding to the web wallet so it will run automatically.   It is not ready yet.

If you have the CS degree and want to try it that is what the script is for.
Web release for importing large wallets (testers needed),

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

** this is temporary, later you'll file the same wallet under the typical place:
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:

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,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.

Technical Support / Re: Are 2.0 wallets deterministic when claiming keys?
« on: October 28, 2015, 05:19:21 pm »
When keys are imported and claimed, their ownership goes to a new address which is derived from the wallet key (as I understand). So can those private keys be re-generated deterministically from the wallet key? Or after every address import do we have to make a new backup?

Thats what these docs seem to imply:

After importing your accounts and balances, we recommend to make a new backup of your wallet that will then contain access to your newly imported accounts and corresponding balances.

If thats the case then the docs should be more explicit. I wonder if this is where I messed up...

Newly created keys are deterministic.  The old brain keys are not compatible so you need to save your backups...  Improvements to this process is in progress.

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...

I adding to the web wallet so it will run automatically.   It is not ready yet.

If you have the CS degree and want to try it that is what the script is for.

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

    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.

Technical Support / Re: Loading stalls for OpenLedger web wallet
« on: October 23, 2015, 12:07:36 am »
When you see the Loading... Message can you open a console and see if there is any error?

I have heard of the backup download problem on Safari. I wonder did it download and just not notify you and you might find it saved on your computer?

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. 

General Discussion / Re: Reducing Bitshares Supply : A different approach
« on: October 22, 2015, 07:10:45 pm »
Another poll option? Yes with serious collaboration with community exchanges..

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

This is from Step 1:
The sha1 sum will print when you run step two... It should print:
Code: [Select]
bloom.dat (1048576 bytes) sha1 3cee441d8d28ab3b26aea149630fa2a96a91845c

Technical Support / Re: usd-collateral-holder
« on: October 20, 2015, 08:08:23 pm »
This should fix the issue in the repo as of Oct 14th...

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

Can anyone confirm the fix at open ledger?

Technical Support / Re: no balance claims
« on: October 20, 2015, 07:24:27 pm »
I have been updating this ticket with comments as I go:

Their has been progress and it is being tested now.  It is not perfect and I don't believe it will be, there are some quarks in the browser making this very difficult.  We have lots of options and I'll make sure we get this running smoothly.

Pages: 1 2 3 4 [5] 6 7 8 9 10 11 12 ... 22