Other > DevShares

DevShares 0.6.3 Feedback

<< < (2/7) > >>

xeroc:

--- Quote from: sudo on February 21, 2015, 10:00:50 am --->> wallet_account_vesting_balances myid

[[
    "ags",[{
        "balance_id": "DVSGydR………………",
        "sharedrop_address": "PruU…………………………",
        "start_time": "2014-01-05T00:00:00",
        "duration": 5184000,
        "asset_id": 0,
        "original_balance": 193383135,
        "vested_balance": 193383135,
        "claimed_balance": 193383135,
        "available_balance": 0

all unlocked  ?

--- End quote ---
Yep .. DVS are all unlocked ... IIRC there was a hickup in the code that made the vested balance be claimable after 2 weeks instead of 2 years .. but that's just for DVS!

kokojie:
For some reason my 0.6.3 DVS windows gui client can not be unlocked, I'm sure the password is correct, but when I click on unlock, nothing happens, no error or anything. I tried deleting my "chain" folder re-download blockchain, and it didn't help. I'm running it on windows 7 64bit with 4GB ram. Also this only happened since yesterday, but I've had this client for several weeks, and it was working previously, I didn't change anything with the client, but I did have a unscheduled sudden reboot just before yesterday.

sudo:
>> wallet_account_vesting_balances myid

[[
    "ags",[{
        "balance_id": "DVSGydR………………",
        "sharedrop_address": "PruU…………………………",
        "start_time": "2014-01-05T00:00:00",
        "duration": 5184000,
        "asset_id": 0,
        "original_balance": 193383135,
        "vested_balance": 193383135,
        "claimed_balance": 193383135,
        "available_balance": 0

all unlocked  ?

liondani:
can't burn messages with the gui on account walls !
when the window appear to confirm the burn message it sais everytime that 0 DVS will get burn...
when clicking on "details" to see the error , nothing happens (the same thing for any error)

graffenwalder:
Just started DevShares gui on windows.
But it opened without asking for a password, at the same time I wasn't connected to the network.

After 30 secs, the login window showed up, and everything worked fine.

Not sure if this is a potential security threat

Navigation

[0] Message Index

[#] Next page

[*] Previous page