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] 9 10 11 12 13 14 15 ... 133
106
General Discussion / Re: Pegged Cryptocurrencies for Remittances
« on: January 29, 2017, 06:40:26 pm »
Welcome!

I'm surprised you mention Nubits since I thought it died when the peg failed,  is it still operational?

The main problem we've had with smart coins is as you mention liquidity.  It's a chicken and egg problem where we need liquidity to attract traders,  and traders to create liquidity. Last I checked the supply of BitUSD  was only around 100k, and with BTS in a long downtrend it's a hard sell for shorters to take the risk of creating more,  and without liquidity its even riskier since you may not be able to close your positions.

There's some initiatives at the moment to incentivize smart coin creation so maybe that will help,  but it's hard to say for sure.

107
General Discussion / Re: Things that needs to be fixed with bitshares
« on: January 29, 2017, 06:32:29 pm »
Quote from: oakmaster on January 29, 2017, 05:20:27 pm
I have a question this might be off topic but when I try to collect vesting balance I'm being charged a 200 and something bts transaction fee does anyone know why Thanks

Sent from my SAMSUNG-SM-N900A using Tapatalk

The fees are set by the committee and at one point they set that one really high for unknown reasons.  I complained at the time but the high fee still remains.

108
Technical Support / Re: Where are the collateral positions on the wallet gone?
« on: January 29, 2017, 06:30:54 pm »
Quote from: JonnyBitcoin on January 29, 2017, 05:27:08 pm
excuse my ignorance but can someone tell me more about these bitshares nodes?

I assume a full node is someone running a full copy of the bitshares blockchain requiring a good spec machine in a data centre with lots of ram?

Is a seed node the same as a full node?

Is the light wallet just a GUI for talking to these hosted full nodes?

do witnesses have to be running a full node?

In the GUI where I can select my API connection, am I selecting which full node I want my light wallet to talk to?

thanks in advance.

Yes,  yes and yes.

The node doesn't need much in terms of specs though,  a witness needs 4-5 gigs I think.

A public node needs better specs though.

The advantage of the light wallet is that the javascript is fixed,  it is not downloaded every time you open it so there's  one attack vector less than a website like bitshares.openledger.info

109
General Discussion / Re: Where exactly is the DEX?
« on: January 29, 2017, 06:26:52 pm »
Quote from: Voyager_8 on January 29, 2017, 05:00:49 pm
Hi, I am just trying our BItshares, I downloaded the client on bitshares.org and am looking at the integrated exchange feature. Is this just connecting to Openledger.info on the backend? From my understanding Openledger is a counterparty like any old exchange, the assets they issues like OPEN.BTC have no proof of reserves or anything you just trust they have the equivalent amount of OPEN.BTC to support trades, is this correct? The bitshares website talks alot about the DEX so does it exist on the client I downloaded and when I place trades I am trading with others using the client or how does it work? Thanks!

The backend is the Bitshares blockchain,  that is also the case for Openledger.  The OPEN. X assets have the problems you mention,  but other assets like bitUSD or bitCNY  are free of counterparty risk.

All trades also happen in a decentralized manner on the blockchain, no matter who the issuer is.

110
Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
« on: January 24, 2017, 11:52:43 am »
Quote from: Bitshiz on January 23, 2017, 05:45:10 pm
Instructions for the novice Windows user:

You will need to download nodejs, git, and Python 3 first and foremost.

  • Open a command prompt by typing "cmd" in your windows search in the start menu
  • Clone the graphene-ui repoby typing "git clone https://github.com/cryptonomex/graphene-ui.git" in the cmd window. (remember that what ever directory/file location is showing on the prompt is where the graphen-ui download will be located
  • Now change the directory to the graphene-ui file location, type
Code: [Select]
cd C:\your\file\location\graphene-ui\bloom_filter
  • then type
Code: [Select]
npm install
  • Now find the wallet file you downloaded from Bitshares 0.93 and change the wallet name to
Code: [Select]
wallet.json
  • Copy the newly named wallet.json file
  • open the graphene-ui file location (the actual file, not in the cmd). Then open the "bloom_filter" file and paste the new wallet.json file inside
  • Go back to the command prompt and type
Code: [Select]
npm run start-windows

    In the cmd window you will see it start to run and depending on how many keys you have it could take a little while. Also you should see the sha 1 sum at the beginning too (3cee441d8d28.......)
    When it is finished you will have the a file with only the necessary keys linked to accounts and balances.

    The new key file is in the graphene-ui/bloom_filter file and it is called
    Code: [Select]
    filtered_wallet.json
    This just worked for me again to make sure my directions were correct. Unless someone changes things in the graphene-ui file you download from git.

    Thanks for the write-up!

    111
    General Discussion / Re: Graphene vs. BitShares in GitHub
    « on: January 19, 2017, 07:00:54 am »
    Quote from: Brekyrself on January 19, 2017, 06:02:24 am
    I do not see the ability to open issues within bitshares/bitshares-2-ui.  It still requires us to go into cryptonomex/graphene-ui to open a UI issue.  Should this be changed as well?

    It will be changed soon.

    112
    Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
    « on: January 18, 2017, 06:55:27 pm »
    Quote from: Bitshiz on January 18, 2017, 05:16:55 pm
    Well I just got this error now:
    Quote
    C:\Users\skysc\graphene-ui\bloom_filter>npm run start-windows

    > bitshares-keys-bloom-filter@1.0.0 start-windows C:\Users\skysc\graphene-ui\bloom_filter
    > type wallet.json | node bloom_filter_wallet.js > filtered_wallet.json

    bloom_bitshares.dat (1048576 bytes) sha1 3cee441d8d28ab3b26aea149630fa2a96a91845c

    C:\Users\skysc\graphene-ui\bloom_filter\bloom_filter_wallet.js:59
            var inputJSON = inputChunks.join("")
                                        ^

    RangeError: Invalid string length
        at Array.join (native)
        at Socket.<anonymous> (C:\Users\skysc\graphene-ui\bloom_filter\bloom_filter_wallet.js:59:37)
        at emitNone (events.js:91:20)
        at Socket.emit (events.js:185:7)
        at endReadableNT (_stream_readable.js:974:12)
        at _combinedTickCallback (internal/process/next_tick.js:74:11)
        at process._tickCallback (internal/process/next_tick.js:98:9)

    npm ERR! Windows_NT 10.0.14393
    npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start-windows"
    npm ERR! node v6.9.4
    npm ERR! npm  v3.10.10
    npm ERR! code ELIFECYCLE
    npm ERR! bitshares-keys-bloom-filter@1.0.0 start-windows: `type wallet.json | node bloom_filter_wallet.js > filtered_wallet.json`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the bitshares-keys-bloom-filter@1.0.0 start-windows script 'type wallet.json | node bloom_filter_wallet.js > filtered_wallet.json'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the bitshares-keys-bloom-filter package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     type wallet.json | node bloom_filter_wallet.js > filtered_wallet.json
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs bitshares-keys-bloom-filter
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls bitshares-keys-bloom-filter
    npm ERR! There is likely additional logging output above.

    npm ERR! Please include the following file with any support request:
    npm ERR!     C:\Users\skysc\graphene-ui\bloom_filter\npm-debug.log



    I deleted graphene-ui and cloned it again before I ran this. I then ran "npm install" and copied my wallet.json(I changed the name to wallet.json) file to the bloom_filter folder.

    I figured it out! Kind of. My json file is over a 1,013,686KB. So it is too big of a json file. I tried on another wallet file that is only 90,252KB and it is working. Is there any way to get this to work on a larger file? I don't think I am missing any balances but just curious what the limit or why there would be a limit on the json file size?

    Quote
    kept 2099 of 534165 keys

    kept 2102 of 534168 keys

    kept 2103 of 534169 keys
    Thanks @svk

    Wow that is a lot of keys! I have a 16MB json file myself but it only has around 85k keys.

    If you're able to edit the file it's certainly possible to cut and paste the keys inside and assemble multiple smaller files. You'll have to do that by hand though, I recommend sublime editor for big JSON files like that.

    113
    Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
    « on: January 18, 2017, 10:28:59 am »
    Quote from: Bitshiz on January 13, 2017, 07:18:29 pm
    Quote from: svk on January 13, 2017, 08:25:59 am
    Quote from: Bitshiz on January 12, 2017, 02:51:41 am
    Any help with this error. I cant upload my .json to the web client because I have too many keys and it crashes every fucking time. been trying to access my BTS for over a year and finally tried this manual but am getting this error. ANyone know what this is? And how to fix? This happens after I run
    Code: [Select]
    OLD_WALLET_NAME.json | node ./bloom_filter_wallet.js > NEW_WALLET_NAME.json but with my wallet names. Doing this through windows 10 64 and I have downloaded everything this tutorial says.


    Code: [Select]
    module.js:471
        throw err;
        ^

    Error: Cannot find module '../web/lib/common/hash'
        at Function.Module._resolveFilename (module.js:469:15)
        at Function.Module._load (module.js:417:25)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (C:\Users\skysc\graphene-ui\programs\bloom_filter_wallet.js:20:9)
        at Module._compile (module.js:570:32)
        at Object.Module._extensions..js (module.js:579:10)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.runMain (module.js:604:10)
        at run (bootstrap_node.js:394:7)
        at startup (bootstrap_node.js:149:9)
        at bootstrap_node.js:509:3

    Ok I had a look and it was indeed trying to load modules that no longer exist. I pushed an update and also included a bloom_bitshares.dat file that you can use if don't want to compile your own.

    To run the filter now, just go to the "bloom_filter" folder, run "npm i" to get the dependencies, name your old wallet file "wallet.json" then  do "npm start". The output will be in a file called "filtered_wallet.json"

    I didn't have an old wallet.json file to test it with so the npm start method might not work properly, if so just run it manually like the original instructions said.

    so I tried it and got this error because of the 'cat' command:
    Code: [Select]
    'cat' is not recognized as an internal or external command,
    operable program or batch file.

    npm ERR! Windows_NT 10.0.14393
    npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
    npm ERR! node v6.9.4
    npm ERR! npm  v3.10.10
    npm ERR! code ELIFECYCLE
    npm ERR! bitshares-keys-bloom-filter@1.0.0 start: `cat wallet.json | node bloom_filter_wallet.js > filtered_wallet.json`
    npm ERR! Exit status 255
    npm ERR!
    npm ERR! Failed at the bitshares-keys-bloom-filter@1.0.0 start script 'cat wallet.json | node bloom_filter_wallet.js > filtered_wallet.json'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the bitshares-keys-bloom-filter package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     cat wallet.json | node bloom_filter_wallet.js > filtered_wallet.json
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs bitshares-keys-bloom-filter
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls bitshares-keys-bloom-filter
    npm ERR! There is likely additional logging output above.

    npm ERR! Please include the following file with any support request:
    npm ERR!     C:\Users\skysc\graphene-ui\bloom_filter\npm-debug.log

    C:\Users\skysc\graphene-ui\bloom_filter>

    I then tried to follow instructions from the original post and got error:

    Code: [Select]
    C:\Users\skysc\graphene-ui\bloom_filter>wallet.json | node ./bloom_filter_wallet.js > filtered_wallet.json'
    C:\Users\skysc\graphene-ui\bloom_filter\bloom_filter_wallet.js:29
        if (err) throw err
                 ^

    Error: ENOENT: no such file or directory, open 'C:\Users\skysc\graphene-ui\bloom_filter\bloom.dat'
        at Error (native)


    So then i decided to switch out my original bloom.dat file I created yesterday instaed of using the bloom_bitshares.dat and then got this error:

    Code: [Select]
    C:\Users\skysc\graphene-ui\bloom_filter>wallet.json | node ./bloom_filter_wallet.js > filtered_wallet.json
    bloom_bitshares.dat (1048576 bytes) sha

    undefined:1



    SyntaxError: Unexpected end of JSON input
        at Object.parse (native)
        at Socket.<anonymous> (C:\Users\skysc\graphene-ui\bloom_filter\bloom_filter_wallet.js:59:27)
        at emitNone (events.js:91:20)
        at Socket.emit (events.js:185:7)
        at endReadableNT (_stream_readable.js:974:12)
        at _combinedTickCallback (internal/process/next_tick.js:74:11)
        at process._tickCallback (internal/process/next_tick.js:98:9)

    Those instructions assume a Linux environment, the cat command is not available on Windows. You also need to fetch the latest version, there is no long a reference to web/lib/common/hash so apparently you're not using the latest release.

    I've identified a bug however so I've pushed a new version just now, and this time I've tested it with an old wallet.json I had lying around so I know it works. I've also added a npm script for windows that you can use, try this in your node console:

    Code: [Select]
    npm run start-windows
    Your wallet  json file must be called wallet.json for this to work.

    114
    General Discussion / Re: Brainstorm - Bit20 MSSR / margin call
    « on: January 18, 2017, 09:30:43 am »
    @EstefanTT I've confirmed your findings and updated the GUI accordingly, it will be included in the next release coming later today.

    I've also taken the time to update my Google doc explaining margin call mechanics, I believe it's now in sync with the current rules. Please review here: https://docs.google.com/document/d/1h9E6N9VECh48NKRQGFoPQsSwfZXT4p_TD3LT3CqeTYk/edit?usp=sharing

     @xeroc  Could you update the docs.bitshares.eu documentation to reflect my changes?

    115
    Stakeholder Proposals / Re: [Worker Proposal] New GUI development worker
    « on: January 18, 2017, 09:27:13 am »
    Quote from: Brekyrself on January 17, 2017, 02:48:32 am
    @svk

    Anything specific we should be testing in this RC?

    https://github.com/bitshares/bitshares-2/releases

    Order matching is the big thing to test. I have identified a couple issues after making this release so there will be another one today, most likely this will not be a RC but a final release.

    116
    General Discussion / Re: Brainstorm - Bit20 MSSR / margin call
    « on: January 15, 2017, 11:37:36 pm »
    Quote from: EstefanTT on January 15, 2017, 02:51:42 pm
    @svk , when would be the next gui release ? Would you consider to rectify this issue ?

    Sent from my SM-G935F using Tapatalk

    Sure. I suspected this needed to be changed so thanks for doing the testing. I intend to release new light wallets either tomorrow or Tuesday, will try to squeeze this in too.

    117
    Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
    « on: January 13, 2017, 08:25:59 am »
    Quote from: Bitshiz on January 12, 2017, 02:51:41 am
    Any help with this error. I cant upload my .json to the web client because I have too many keys and it crashes every fucking time. been trying to access my BTS for over a year and finally tried this manual but am getting this error. ANyone know what this is? And how to fix? This happens after I run
    Code: [Select]
    OLD_WALLET_NAME.json | node ./bloom_filter_wallet.js > NEW_WALLET_NAME.json but with my wallet names. Doing this through windows 10 64 and I have downloaded everything this tutorial says.


    Code: [Select]
    module.js:471
        throw err;
        ^

    Error: Cannot find module '../web/lib/common/hash'
        at Function.Module._resolveFilename (module.js:469:15)
        at Function.Module._load (module.js:417:25)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (C:\Users\skysc\graphene-ui\programs\bloom_filter_wallet.js:20:9)
        at Module._compile (module.js:570:32)
        at Object.Module._extensions..js (module.js:579:10)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.runMain (module.js:604:10)
        at run (bootstrap_node.js:394:7)
        at startup (bootstrap_node.js:149:9)
        at bootstrap_node.js:509:3

    Ok I had a look and it was indeed trying to load modules that no longer exist. I pushed an update and also included a bloom_bitshares.dat file that you can use if don't want to compile your own.

    To run the filter now, just go to the "bloom_filter" folder, run "npm i" to get the dependencies, name your old wallet file "wallet.json" then  do "npm start". The output will be in a file called "filtered_wallet.json"

    I didn't have an old wallet.json file to test it with so the npm start method might not work properly, if so just run it manually like the original instructions said.

    118
    Technical Support / Re: GUIDE: How to remove unneeded keys from Bitshares 0.9.3 export_keys json
    « on: January 13, 2017, 07:48:50 am »
    Quote from: Bitshiz on January 12, 2017, 02:51:41 am
    Any help with this error. I cant upload my .json to the web client because I have too many keys and it crashes every fucking time. been trying to access my BTS for over a year and finally tried this manual but am getting this error. ANyone know what this is? And how to fix? This happens after I run
    Code: [Select]
    OLD_WALLET_NAME.json | node ./bloom_filter_wallet.js > NEW_WALLET_NAME.json but with my wallet names. Doing this through windows 10 64 and I have downloaded everything this tutorial says.


    Code: [Select]
    module.js:471
        throw err;
        ^

    Error: Cannot find module '../web/lib/common/hash'
        at Function.Module._resolveFilename (module.js:469:15)
        at Function.Module._load (module.js:417:25)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (C:\Users\skysc\graphene-ui\programs\bloom_filter_wallet.js:20:9)
        at Module._compile (module.js:570:32)
        at Object.Module._extensions..js (module.js:579:10)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.runMain (module.js:604:10)
        at run (bootstrap_node.js:394:7)
        at startup (bootstrap_node.js:149:9)
        at bootstrap_node.js:509:3

    Like Chris mentioned you could try the light wallet as it includes the bloom filter directly, as does https://bitshares.org/wallet I believe.

    The bloom filter program in the graphene-ui repo is probably out of sync with the location of files in the repo right now after I moved a lot of things around, I'll have a look and update it if necessary.

    119
    General Discussion / Re: Distinguish asset types from API
    « on: January 08, 2017, 07:14:55 pm »
    You can identify smartcoins by a field called bitasset_id, only they have it. For each smartcoin you then need to fetch that object with get_objects, and it will contain a boolean field is_prediction_market.

    120
    General Discussion / Re: Brainstorm - Bit20 MSSR / margin call
    « on: January 07, 2017, 11:46:08 pm »
    Quote from: yvv on January 07, 2017, 11:08:20 pm
    Quote from: svk on January 07, 2017, 09:44:19 pm
    No he's correct, margin calls only happen once the call price goes below the feed price.


    Then documentation should be corrected, because it says that margin call is triggered when the call price is between feed price and SQPP.


    The documentation is a copy paste of a write up that I did before BM changed the mechanics to make it so that margin calls are only triggered when the call price goes below the feed price, there's a github issue for this in the graphene repo.

    Call price is DEBT * MCR / COLLATERAL.

    Pages: 1 2 3 4 5 6 7 [8] 9 10 11 12 13 14 15 ... 133

    Page created in 0.029 seconds with 23 queries.