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

Pages: [1] 2 3 4 5 6 7 8 ... 133
Technical Support / Re: Error claiming balance
« on: December 11, 2017, 12:46:19 pm »
Getting the following error when trying to claim balance;
Error claiming balance: TypeError: e is undefined

Also, the unclaimed amount of BTS shown is lower than the asset totals I see after importing keys.

Anyone have any ideas as to what is going on here?

Was there another error message included, something starting with "claimBalance" ?

General Discussion / Re: [ANN] Bitshares gateway GDEX is launching
« on: December 05, 2017, 02:08:21 pm »
I can also do a pull request to have your access node added (wss:// to bitshares-ui if you are ok with it?

please don't, this node is planned for GDEX use only to ensure quick processing without jam, later we will build some other nodes for public use.
OK, no problem.

we now have built an API server wss:// for public use, please add this to bitshares-ui access nodes list. [member=43537]sahkan[/member]

Where's this API server hosted?

Stakeholder Proposals / Re: Compliance Work
« on: October 19, 2017, 07:09:12 am »
This is confused - there is very little about 'compliance' ie TXSRB/STOKENs that Michael/Stan are working on, and a lot on getting listed on exchanges.

I would suggest dropping the compliance and focus just on getting listed.

The TXSRB is a joke that so far has only served to degrade the image of Bitshares.

I think you're all being naive in your thinking about the amount of harm governments and regulatory bodies can do to Bitshares, even Satoshi was worried about that and we're not Bitcoin.. In my opinion we need this worker desperately.

Technical Support / Re: Desktop Wallet Backup
« on: August 11, 2017, 05:11:07 am »
You are using the account model so there is no wallet for you to backup, just make sure you remember your account name and password.

Technical Support / Re: Account password in wallet model
« on: August 11, 2017, 05:07:55 am »
Try switching to wallet mode.

Technical Support / Re: Failed to broadcast transaction
« on: August 11, 2017, 05:06:19 am »
I get the same problem.

I get the following message:

bitshares-crypto digest 3bc2af1c6a26b87f122878fbc37caf3bdb8e975954217bccd7502f8ece084a8b transaction 289c42a6e500ba9465590101bd0400000000000000f39c16bd963f0000000000c10bd4e1d6180000000000a4e7cc62000000 {"ref_block_num":39976,"ref_block_prefix":15050306,"expiration":"2017-07-12T03:17:14","operations":[[1,{"fee":{"amount":"1213","asset_id":"1.3.0"},"seller":"1.2.364147","amount_to_sell":{"amount":"4167357","asset_id":"1.3.1473"},"min_to_receive":{"amount":"416735700","asset_id":"1.3.0"},"expiration":"2022-07-12T03:16:52","fill_or_kill":false,"extensions":[]}]],"extensions":[],"signatures":["2059acf486b4a94508246a39d3fb823d6bf87a04fbbcf5596ea293f34c2bff7ded3cc2227042aff1b208dd173a04cdae1eb8e568ea556f6ea34d61080586a71e80"]}

I'm in Japan. I'm not sure if that has to do with anything but clocks are different.

It's a transaction expiration problem, not fee related. I fixed it yesterday in the code and pushed a new version to

I can't find clear target for this worker.
what I concern about the wallet include:
1. efficient.
currently only 100 client support with a 32G mem VPS node.
will this wallet support at least 10K users in the future?
don't told me this is backend guy's work.
if so, you should find partner who can improve backend, and work together.
as share holder, we need a complete solution, not some lego toy.
2. user friendly.
this is very difficult to verify.
but what make user friendly very difficult  because of most ui developer can't follow the wallet.
because the UI code mixed up with  many blockchain code.
will you make the UI completely independency from the blockchain tec?
3. more function
I have no idea why we need a seperate exploere like
all we need can implement in the wallet.
can you expand more function in the wallet? what's the plan?

1.Thats a backend issue so to resolve that we have to depend on Alfredo Garcia and the others working on the backend. That's also the case for [member=23]bitcrab[/member] concerns about GUI performance and api calls:its a backend issue.
2.The code is bog standard react + flux, with most of the blockchain code already split into a separate library (bitsharesjs)
3. A block explorer needs data that's not available from the witness_node, so replacing would require a whole new backend layer.
The current explorer parts could certainly improved however.

Technical Support / Re: Failed to broadcast transaction
« on: July 30, 2017, 02:01:39 pm »
Something must be wrong with the transaction confirmation. See how the fee on my original request window is different than the one on the confirmation window?

.21851 vs .23131

The fee on the confirmation window is greater than what was is auto-calculated on the request window.

Interesting. I'd guess that the fee in the request window does not take the per-kb fee into account. [member=11456]svk[/member]?

Correct, only the confirmation window has the full fee including per-kb fee for the memo.

It will fall back to a working api server from the list of known servers, if you look at the dev console it will tell you which one it connected to.

Technical Support / Re: Changing the brainkey?
« on: June 30, 2017, 02:07:51 pm »
You cannot change the brain key of an existing wallet. If you want to use a custom brain key, create a new wallet and click use custom brain key.

You have my support as well! I can also help out as part of the multisig group.

Thanks so much for your reply :)

Hyptothetical scenario:

1)Someone creates an account with OpenLedger and then backs it up with ONLY the brainkey.

2) Someone then imports a cold storage private key to the account.
         This account now houses (Brain_key seed private keys) + (new unrelated private key)

PCs explanations are perfect, but I'll add some clarifications.

At this point your WALLET contains the keys generated for your account from the brain key, as well as the imported key.

3) Someone then sends ALL FUNDS to themselves
      Does this account now house ONLY (brain_key seed private keys)

In this situation, is a brainkey backup sufficient?
Is a new backup required after every transaction?
In this case your brain key would indeed be sufficient since the unrelated private key contains no funds anymore. If that private key contained unvested balances however you would need to reimport the key in a future wallet restored from the brain key in order to claim those balances.

A new backup is only really needed after importing unrelated keys, transactions don't matter.

General Discussion / Re: Graphene and Protocol questions
« on: June 20, 2017, 06:48:03 am »
Steem mining was removed a few hardforks ago so its pure POS now.

Technical Support / Re: Bitshares account password incorrect error.
« on: June 18, 2017, 12:16:17 pm »
You still create an account even if you use the wallet model, but the private keys of that account are then stored in what we call the wallet, as opposed to the account/password model where the private keys are generated from your password.

The account model let's you login directly from new computers or browsers without using a backup file, that's why it's convenient.

The wallet model is tied to a database stored in the specific browser and computer you first used to create the account. If you want to use it anywhere else, you need to restore from a backup.

Technical Support / Re: Bitshares account password incorrect error.
« on: June 17, 2017, 07:17:02 pm »
In order to move to a new browser you need to restore your wallet using the backup.

A couple of follow up questions for clarification.

So the account model is mutually exclusive and therefore when I created a wallet on my account it deactivated my account model?

I can no longer use the account model if wallet model is activated? I think this has been confusing some people as well and I certainly hope I'm no the only one confused. At some point I did in fact activate and register an account with a password and now the password does not work.

Is this because of my switching to wallet model? If so how would I recover my account? Is it even possible? I've been using the same password for all of these and it only works with the wallet not the account.

Thanks for being active in this forum. Love the community and platform. Don't want people to leave because of technical issues.

I say mutually exclusive because new accounts are only setup to use one or the other, not both.

Nothing is disabled, switching models in the GUI is just a simple interface switch that determines how the GUI lets you login, it has no effect on your account.

Both models use passwords, that doesn't mean your wallet password can be used with the account model without you actively modifying the permissions of your account.

The only way for you to switch from a password model to wallet model is to copy all your private keys (active, owner, memo) and import them into a newly created wallet. If you did not do that, you never switched from password to wallet but always had wallet.

Pages: [1] 2 3 4 5 6 7 8 ... 133