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

Pages: 1 ... 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82
1126
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 18, 2014, 03:30:34 pm »
What's meaning of wallet_set_delegate_trust_level  number ? For example , what does 1and 5 and 10 stands for?
Is there any rule or guide about trust_level when we want to give someone trust? I see somebody give others  trust_level 5 or  10 or 1. What's the difference?
After using  this command, why we need to transfer XTS to our account?

Code: [Select]
xeldal-w (unlocked) >>> help wallet_set_delegate_trust_level
Usage:
wallet_set_delegate_trust_level <delegate_name> [trust_level]                                         Updates the trust placed in a given delegate
Updates the trust placed in a given delegate

Parameters:
  delegate_name (account_name, required): the name of the delegate to set trust level on
  trust_level (int32_t, optional, defaults to 0): Positive for Trust, Negative for Distrust, 0 for Neutral

Returns:
  void

aliases: trust, set_trust

Im not sure 10 is any different that 1, perhaps someone can clarify that.

Currently, all positive integers are treated the same, and all negative integers are treated the same. See: https://github.com/BitShares/bitshares_toolkit/blob/63798df7ca63f18e1face9ae87b42a9ee00a1383/libraries/wallet/wallet.cpp#L2717-L2723

We should probably restrict the input to only {-1,0,1}.

1127
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 18, 2014, 12:29:26 am »
blockchain_list_forks not work
Code: [Select]
(wallet closed) >>> blockchain_list_forks
6 key_not_found_exception: Key Not Found
unable to find key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:74 fetch
error fetching key f54461de391b568340f93083999858a32613a438
    {"key":"f54461de391b568340f93083999858a32613a438"}
    th_a  level_map.hpp:84 fetch
Unable to find block f54461de391b568340f93083999858a32613a438
    {"block_id":"f54461de391b568340f93083999858a32613a438"}
    th_a  chain_database.cpp:1574 get_block_num

    {}
    th_a  common_api_client.cpp:222 blockchain_list_forks

    {"command":"blockchain_list_forks"}
    th_a  cli.cpp:570 execute_command
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "d6efe05763d10bc274b37e84d626ede07373d964",
  "bitshares_toolkit_revision_age": "18 hours ago",
  "fc_revision": "6ef1c3e5d915cd655cf1f8727e35d52b64ee196a",
  "fc_revision_age": "25 hours ago",
  "compile_date": "compiled on Jun 17 2014 at 14:06:33"
}
(wallet closed) >>>

Should be fixed for now: https://github.com/BitShares/bitshares_toolkit/commit/909323ea5e1ed6287f6ca5900d135771e2fa7564

1128
General Discussion / Re: Dry Run 2: The Real Deal
« on: June 18, 2014, 12:04:15 am »
load config from .BitSharesXTS or .BitShares\ XTS ?
this is the output from latest version .
Code: [Select]
Creating default config file "/home/alt/.BitSharesXTS/config.json"

Default directory was restored to the ~/.BitSharesXTS on Linux per: https://github.com/BitShares/bitshares_toolkit/issues/291

Linux users will want to move their wallets from ~/.BitShares\ XTS to ~/.BitSharesXTS.

1129
General Discussion / Re: Market Report
« on: June 17, 2014, 07:40:53 pm »

A couple of months it was way too buggy and non friendly for non tech guys and their progress now is outstanding...

"The question is did we missed that boat and initial investors will soon start to dump at some point"? Or do you guys believe that it will overtake litecoin and could reach the 1/2 bil market cap?

NXT is a currency first of all, with added on features.  Their AE is pretty cool.  It is not something that can't be easily overtaken.   NXT also isn't as successful as people think it is.  Look at Cryptsy volumes.

CRYPT/BTC    CryptCoin    1012 BTC   
LTC/BTC    LiteCoin    181 BTC   
DRK/BTC    DarkCoin    176 BTC   
DOGE/BTC    Dogecoin    151 BTC
POT/BTC    PotCoin    67.5 BTC   
NXT/BTC    Nxt    47.0 BTC   

So Dogecoin has 3x the volume (unspecified timeframe) and even PotCoin beats NXT.

I wish coinmarketcap would adjust NXT's supply to exclude the unclaimed genesis addresses. They did adjust Ripple's supply, after all. Anyone want to send them that suggestion? Use words like "misleading" and "would be more accurate"

These are kinds of messes we get without inactivity fees and BIPS.

1130
how do you register a delegate?

wallet_register_delegate name ""

But the default wallet just picks random delegates at the moment, no way for people to vote for you

Just opened an issue about it here: https://github.com/BitShares/bitshares_toolkit/issues/140

1131
General Discussion / Re: r/BitShares @ reddit
« on: May 16, 2014, 04:45:59 pm »
We've just been added to the sidebar in /r/CryptoCurrency. Woohoo!

1132
Until Dan chimes in, there is some sparse documentation at: http://bitshares.org/documentation/namespacefc.html

1133
General Discussion / Re: Testing BitShares XT Launch...
« on: May 09, 2014, 06:13:18 pm »
I just added some extra code to save the wallet on Ctrl+C. 

The key generation algorithm is deterministic so you you can always regenerate your change addresses.

can your exception handling cater for the scenarios that the client crashed or computer power off suddenly?

power failure cannot be handled. Only way to is to sync wallet changes immiediently on disk

It should be saving after every major wallet operation...   One thing that I have realized is that we need to switch to using a database for the wallet so that we can do partial saves with proper logging without the performance hit of having to encrypt / save the entire wallet.

Now automatically saves after every command that would require the wallet to be unlocked: https://github.com/BitShares/bitshares_toolkit/commit/1300929e64bed39f24e4f137bc2171dda9af2758

We may want to save on other big operations as well, e.g. rescan.

1134
General Discussion / Re: Testing BitShares XT Launch...
« on: May 08, 2014, 05:00:04 pm »
Change the bts total share to 80 trillion for what?

The exact value of the constant isn't particularly important, as your assets are best measured in bips. The share supply just needs to be scaled so that it is sufficiently divisible, but not overly divisible that it requires excessive storage. Bitcoin has 2.1 quadrillion shares; we are currently using 80 trillion.

1135
General Discussion / Re: How is BitShares capitalized?
« on: May 07, 2014, 04:37:03 am »
It seems to me we are trying to establish bitshares as a broadly used and adopted almost generic term for the inevitable wave of profitable DACs.  For this use I think all lower case makes the most sense.

I could see an argument to referring to the name of a particular DAC like "Bitshares X" with capital B because it is almost like the name of a company, but when used in the generic sense it is all lowercase.

Seconded. I think we can treat bitshares as if it is already a common English word, and use it all lowercase in normal sentences. When referring to a particular entity/product/etc. (e.g. Bitshares X) or at the start of sentences/in titles/whatever we can use Bitshares, capitalized like a proper noun. Similar to the way bitcoin/Bitcoin is used now. I'm not a fan of the camelcase BitShares as I think it's harder on the eyes and people will be lazy/ignorant about the extra capitalization anyway.

Quote
But there should be a consensus among the whole team. Then it should be changed on every single web page now, and on every document going forth, to all read the same way. It looks kind of disjointed. That will undermine the overall confidence people have in the Bitshares ecosystem, even if they don't catch it consciously.

+1 I definitely get this vibe looking at bitshares.org, hence why I made this post.

1136
General Discussion / Re: Testing BitShares XT Launch...
« on: May 06, 2014, 10:44:12 pm »
Having problems sending..

Code: [Select]
>>> getbalance
180499303231
>>> sendtoaddress BvoktQoKdxB6AjZabBkxGret12rMUsJ2s 180499303231
assert
!"Unable to collect sufficient unspent inputs":
    {"requested_amount":{"amount":180499304884,"unit":0},"total_collected":{"amount":180499303231,"unit":0}}
    th_a  wallet.cpp:315 collect_inputs
{"amount":180499303231,"unit":0} to BvoktQoKdxB6AjZabBkxGret12rMUsJ2s
    {"amnt":{"amount":180499303231,"unit":0},"to":"BvoktQoKdxB6AjZabBkxGret12rMUsJ2s"}
    th_a  wallet.cpp:771 send_to_address

You cannot send your full balance, as a transaction fee is required.

Perhaps we need some mechanism to adjust the amount downward by the necessary amount and ask for confirmation if it's okay.

1137
General Discussion / How is BitShares capitalized?
« on: May 06, 2014, 12:23:35 pm »
bitshares.org seems to use 'BitShares', 'Bitshares', and 'bitshares' in different places.

1138
How do I import the data?

also while I was changing the client funds where sent from cryptsy that hadnt yet hit the old wallet ??? I have already downloaded the new and it has overridden the old. The funds transfer was not on the backup ......what do i do?

I think there might be some misunderstanding. It seems you were using an old version of the PTS/Protoshares client. You then downloaded and installed the most recent version from: https://github.com/BitShares/BitShares-PTS/releases.

After doing this, there is another step. You need to copy the 'wallet.dat' file from a particular application folder corresponding to the older client to the appropriate application folder corresponding with the most recent version of the client. This is what toast means by "exporting" and "importing".

These folder locations depend on your operating system--Mac or Windows. Which are you using?

Here is what the appropriate folders should look similar to for Windows: http://www.reddit.com/r/protoshare/comments/1youib/caution_watch_for_falling_pts/cfmtvgh

1139
General Discussion / Re: Testing BitShares XT Launch...
« on: May 05, 2014, 04:52:10 am »
Import private key does not work with btc or pts keys


Sent from my iPhone using Tapatalk

Why not?

https://github.com/BitShares/bitshares_toolkit/blob/master/libraries/rpc/rpc_server.cpp#L1147

Looks like the wallet has the private key so it should know that it can spend the output in the genesis block when it rescans. We shouldn't have to do a separate "sweep" transaction for the balance to show.

WIF private keys (like from doing 'dumpprivkey' from the PTS console) can now be imported using 'importprivkey'.

1140
General Discussion / Re: Testing BitShares XT Launch...
« on: May 05, 2014, 02:27:53 am »
I just added some extra code to save the wallet on Ctrl+C. 

The key generation algorithm is deterministic so you you can always regenerate your change addresses.


Same problem with your recent changes

Code: [Select]
creating default config file /home/alexxy/.bitsharesxt/config.json
>>> open_wallet
bad_cast
Invalid cast from type '5' to Object
    {"type":5}
    th_a  variant.cpp:498 get_object
unable to load /home/alexxy/.bitsharesxt/default_wallet.dat
    {"wal":"/home/alexxy/.bitsharesxt/default_wallet.dat"}
    th_a  wallet.cpp:442 open
>>>

@bytemaster

i created new wallet, stopped client with quit and started it again

Code: [Select]
$ ./bts_xt_client --trustee-address 9gWvCSLaAA67Rwg9AEvPAttUrdr9pXXKk --connect-to 107.170.30.182:8765
================================================================
=                                                              =
=             Welcome to BitShares XT                          =
=                                                              =
=  This software is in alpha testing and is not suitable for   =
=  real monetary transactions or trading.  Use at your own     =
=  risk.                                                       =
=                                                              =
=  Type 'help' for usage information.                          =
================================================================
$

Now it doesnt even start. its latest build of git master

I was having these problems as well. Just pushed a fix it may work for you now. I guess you would have to manually test (http://bitshares.org/documentation/group__manual__testing.html) if the server has been taken down.

Pages: 1 ... 69 70 71 72 73 74 75 [76] 77 78 79 80 81 82