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.

Topics - svk

Pages: [1] 2
Stakeholder Proposals / [Worker Proposal] New GUI development worker
« on: January 03, 2017, 07:29:11 am »
I've just created a new worker for another 3 month period starting on Monday the 9th of January 2017. As part of the worker I will be making new releases of the light wallets and updating, and making improvements to the wallet as outlined here:

Your support is much appreciated!

General Discussion / [ANN] Bitshares simple wallet template
« on: June 14, 2016, 12:59:38 pm »
Using my graphenejs-lib I've made a new very basic wallet template. This wallet makes use of a new feature I've added to the graphenejs-lib: Account login. This is the same type of login used by Steemit, where a private key is generated on the fly from your account name and password. This means nothing is stored in your browser, and no private data is sent over the wire. This login feature could be reused by any number of wallets and you could then login everywhere using the account name and password.

Since your account name and password become your brain key in this case, it is important that you use a very long password, 16 characters at least. Remember: there's no centralised method of recovery so make sure you remember your password!

For more info, please see this post on steemit:[member=11456]svk[/member]/new-simple-wallet-template

You can find the source here:

And a live preview on the testnet here:

I've extracted the websocket rpc connection code from my graphenejs-lib in order to provide a minimal rpc library for graphene chains. In doing so I've made some improvements to the original code, and I've managed to reduce the dependencies so that the minified browser build is now only 12kb.

The library does one thing: lets you open a websocket connection to a BTS or other graphene node, and perform api calls. There are examples included in the github repo as well as several tests that show how the library can be used.

In an attempt to make Bitshares/Graphene development more accessible for JavaScript developers, I've extracted the api and crypto libraries from the graphene-ui repo into a separate package. This package will allow anyone to easily connect to and interact with the Bitshares blockchain through either a public or local API server.

All the transaction creation/signing code used by graphene-ui is included, which means you can easily create a trading bot in node.js for example using this library. That bot would only need access to a private key and an api server, no cli_wallet required. This library should also make it very easy to implement alternative front-ends for Bitshares.

The library is available through NPM using
Code: [Select]
npm install graphenejs-lib.

The open source code is available here, this repo also includes some basic examples:

I intend to expand on the examples, so if there's anything you'd like to see an example for let me know.

Stakeholder Proposals / [Worker Proposal] GUI development
« on: June 06, 2016, 10:32:35 am »
I've decided to continue working on the Bitshares GUI for the time being, so I've made another worker proposal that will last three months, starting Sunday 12th of June. Details can be found here:

As always, your support is much appreciated.

Stakeholder Proposals / GUI development worker - svk
« on: December 15, 2015, 11:24:22 pm »
As hinted to by Bytemaster in last week's hangout, I've now made a worker proposal for working on the Bitshares GUI as an independent contractor. You can find the details here:

I appreciate your votes, the proposal is open for voting until and including Sunday this week.

Thanks to awesome work by theoretical and jcalfee we now have two simple command line tools that will remove keys that are not in the Bitshares 2 genesis file from your keys json file generated by the wallet_export_keys command. I've just tested it on a wallet with 95k keys (16MB) and it was reduced to 375 keys (64kB). This might get embedded in the Bitshares 2 wallet and in a future 0.9.4 release of legacy Bitshares, but I wanted to share it with those of you who are struggling with importing your keys.

DISCLAIMER: try at your own risk, I'm not responsible for any loss of keys or balances, etc. Instructions are for *nix/OSX
DISCAIMER 2: Please backup and keep safe your original keys file first

The tools were written using Python and Nodejs so you'll need those installed.

Step 1: Generate a bloom filter file from Bitshares 2 genesis file
Code: [Select]
python -i ./genesis.json --o bloom.dat
Step 2: Filter your old wallet.json using the bloom filter
  • Clone the graphene-ui repo: "git clone"
  • In a terminal, go inside the cloned repo: "cd graphene-ui/dl/" and install dependencies "npm install"
  • Copy the bloom.dat file you generated as well as your wallet.json file to "graphene-ui/dl/programs"
  • From inside the folder "graphene-ui/dl/programs", apply the filter to your wallet.json using:
Code: [Select]
cat OLD_WALLET_NAME.json | node ./bloom_filter_wallet.js > NEW_WALLET_NAME.json
The script will run, telling you as it goes how many keys it's removed and has processed.

Step 3: Profit
Once that's done, you should have a MUCH smaller json file containing the keys you need to import in the Bitshares 2.0 wallet of your choice, light wallet, OpenLedger, localhost, etc.

General Discussion / Graphene GUI testing and feedback
« on: September 24, 2015, 03:36:34 pm »
Please use this thread for feedback on the new GUI as well as issues related to

The GUI is available here:

If you notice a bug or anything that needs changing, please create an issue for it here if you can:

DAC PLAY / Bitsharesblocks for Play
« on: April 06, 2015, 03:18:44 pm »
In case you're not following the forum, I've made Bitsharesblocks available for Play here:

General Discussion / Reworking the wallet trading interface
« on: March 16, 2015, 10:41:01 am »
I've made some initial progress on reworking the trading interface of the wallet, I would like to get some feedback and for us to do some brainstorming on features. I've used the coinbase interface as inspiration, but due to the complexity of Bitshares trading with shorts/margin calls etc you end up having to display more info resulting in a more cramped interface, so it's hard to get it as nice as theirs.

The biggest changes so far are:
  • Buy/Sell/Short section is now fixed on the left side and always visible
  • The order book is displayed vertically next to the orderbook chart (sorting is weird because of ui-grid table)
  • Open orders for the currently selected tab are displayed immediately below in order to always be visible
  • Removed the price history chart
  • Removed grid lines from plots
  • Open orders other than the currently selected tab shown below the orderbook chart
  • Table headings are now black and bolded instead of grey (this applies elsewhere too, the old one was hardly visible imo)
  • Less paddings and margins to fit everything
Improvements I'd like to make still:
- Ideally I'd prefer to use standard tables instead of ui-grid but they do offer speed compared to standard angular.
- Put daily range, volume etc on top of orderbook chart like on bitsharesblocks
- Unify open order tables to contain buy, sell and shorts
- Split order history and price history chart into separate tab

You can check this out by using the web_wallet in a browser, simply checkout the branch newlayout_market, then follow the standard procedure for running the web wallet.

Here are some screenshots:

General Discussion / Stellar/Ripple consensus issues
« on: December 10, 2014, 10:48:57 am »
Interesting story that I didn't see mentioned here about a potential fault in Ripple's consensus mechanism:

Stellar's Jed McCaleb has issued a statement on the issue. While he does not deny that the code has been changed since its fork from Ripple, he does maintain that the Ripple protocol could be at risk.

Despite all that, both Ripple and Stellar are up today, go figure..

Marketplace / bitsharesblocks Logo and Favicon - 3500 BTS [CLOSED]
« on: November 26, 2014, 12:09:31 pm »
I'd like to propose a bounty for an icon competition for

What I'd like to have is:
  • A logo to replace Bitsharesblocks here:

  • A favicon to replace this:

Both and have logos that I quite like, especially blockr, if you're wondering what type of logo I'm looking for.

I'll pay 3500 BTS to the winner, with another 1500 BTS to be distributed as I see fit to any worthy runners-up.

Stakeholder Proposals / Please downvote delegate*.svk31
« on: November 25, 2014, 10:28:48 am »
I would like to retire my two delegates who are currently in the top 101 in favour of my new delegate:


If you want to support me, please remove your votes for the delegates "delegate.svk31" and "delegate2.svk31" and vote for dev.bitsharesblocks instead!

Thanks, svk

中文(Chinese) / Translation bounty
« on: November 24, 2014, 10:12:48 pm »
Hey, just a heads up that I'm looking for someone to translate Bitsharesblocks from English to Chinese, I've posted a 500 BTS + 10 bitUSD bounty here:

I've recently added a translation framework to Bitsharesblocks, and as a result I need some more translations!

I'm offering a bounty of 10 bitUSD + 500 BTS per major language translation. The ones I'd like to have are:
  • Chinese Done, thanks to btswildpig
  • Spanish Done, thanks to fran2k
  • German Done, thanks to xeroc
  • Russian Done, thanks to rootbear
I've created a github repo just for this, in it you'll find the locale_en.json file that needs to be translated.

Simply make a pull request with your translated file: locale-es.json for Spanish, locale-zh for Chinese, locale-de.json for Germany or locale-ru.json for Russian. Include the account to which you want the bounty sent in your pull request and I'll send it right over.

If you really don't want to use github, you can simply download the file from there and then e-mail your translation to [email protected]

Pages: [1] 2