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

Pages: [1]
Technical Support / Neo; fractional amounts, where do they go?
« on: April 27, 2018, 10:37:21 pm »
I wanted to transfer the 1.1 open.Neo I had in my Bitshares account to my Neon wallet. This being my first ever transfer of Neo I wanted to be cautious and sent 0.2 Neo via Openledger, being unaware at that time that Neo has to be transferred in whole number units; neither my Bitshares account, Openledger or the Neon wallet warned me about this.

Obviously the 0.2 never arrived in my Neon wallet but the Neo in my Bitshares account was reduced to 0.9 Neo.
Hence my question is where do the fractional units of Neo go?

Reading this web page, dated 28 February 2018, states:
Coin fractions at exchanges. How do they do it?
Exchanges are currently trying to figure a way around the problem of NEO being indivisible. The answer they have might not be the best one but it’s the best we have: You’ll be allowed to trade fractions of NEO as long as you keep them inside your exchange wallet. If you transfer them to your NEO wallet, those fractions will remain on the exchange and won’t be moved to your private wallet.

For example, you are not technically allowed to own 5.32 NEO. You either have 5 NEO or 6. But exchanges will let you exchange BTC for 5.32 NEO without issue. If you keep those 5.32 NEO in your exchange wallet, you should have no problem exchanging them for another cryptocurrency. However, if you transfer the 5.32 NEO you own to your actual NEO wallet, you will end up with 5 NEO, and the 0.32 NEO will stay on the exchange.

In view of that comment, should the 0.2 Neo have remained in my Bitshares account?
Should this have been enabled programmatically but has been overlooked?
Can I recover my 0.2 Neo?

Any feedback would be appreciated. Thanks.

... I would like to withdraw some of my coins and transfer them to an external wallet, in particular my Gridcoins, GRC, to my GridcoinResearch wallet. However I can find no options to withdraw them either in my Dashboard > Portfolio or in the page.

I discovered the main source of this problem was the settings for the Privacy Badger web browser add on which was blocking some needed content from OpenLedger, I have adjusted the settings now so the content is displayed giving me many more deposit-withdraw options. I have made a separate post about the Privacy Badger settings in case others have been caught by the same problem.

However, regarding GRC, this remains the most recent OpenLedger blog entry:
... A relatively recent OpenLedger blog entry, 8th December 2017, says the "GRC, EMC, DASH, ETP gateways have been opened" ...
Contrary to that, selecting GRC to deposit or withdraw results in the following message being displayed:
which appears to have been the case for a few months, hence my original two questions remain mostly valid should anyone wish to comment.

Technical Support / Privacy Badger, check the settings.
« on: February 01, 2018, 10:38:57 am »
I have the Privacy Badger add on, from the the Electronic Frontier Foundation, installed in my main web browsers. It does a good job working quietly in the background helping to maintain privacy.

However unrealised by me for a few months it was blocking some needed content on the deposit-withdraw web page, namely there were no coins and content displayed for the OpenLedger Transfer Service. At last I noticed I needed to adjust the Privacy Badger settings to disable the blocking of any content for the site, I now have many more deposit-withdraw options available!

I hope that will be useful information to anyone else who may have omitted to check their Privacy Badger settings.

I use with a local wallet.

I would like to withdraw some of my coins and transfer them to an external wallet, in particular my Gridcoins, GRC, to my GridcoinResearch wallet. However I can find no options to withdraw them either in my Dashboard > Portfolio or in the page.

Several months ago (August or September 2017?) I was able to withdraw and transfer GRC using the OpenLedger gateway, but for a few months now no OpenLedger gateway withdraw options have been available. A relatively recent OpenLedger blog entry, 8th December 2017, says the "GRC, EMC, DASH, ETP gateways have been opened" but still no options appear within

Hence a couple of questions:
  • Are any OpenLedger gateway options going to become available anytime soon so I can withdraw and transfer Gridcoin or other coins?
  • In the absence of any current withdraw options can anyone suggest alternative ways I may transfer my Gridcoins to my GridcoinResearch wallet?
Otherwise it seems some coins are trapped within the Bitshares wallet.

This information may be useful for anyone wondering where the backup options are for their local wallet prior to using the new address:

I use the Google Chromium web browser on a Manjaro Linux system, when I first display the page only the following text is displayed:
In an effort to provide enhanced security for the web-based wallet, we are migrating it, effective immediately to the address below. Please be sure to update any bookmarks you may have.
Please use from now on, your existing credentials will let you login there as well.
But if that page is refreshed, using the page reload button in the browser tool bar or menu option, additional important text is displayed:
Local wallet detected
Please backup your wallet now and restore the backup file to, which will be your new address for the web wallet. Thanks for your continued support
followed by more information, instructions and wallet settings and backup options.

I discovered I needed to refresh the page by accident, I do not know if the problem applies to other browsers or operating systems, but as a precaution try refreshing the page to see if more text and options appear for you. I hope that information may be of help to some.

Technical Support / Re: pybitshares, historic trades() data & 100 limit?
« on: September 27, 2017, 09:23:13 am »
This is exactly what you need to do ...
Thank you for your guidance, much appreciated.

if you want the data for a chart, you may want to look into another call that uses "buckets" ..
I tried searching for the "buckets" you refer to but without success, could you give a URL for the information on the buckets and call to which you refer?

Technical Support / pybitshares, historic trades() data & 100 limit?
« on: September 24, 2017, 12:09:41 pm »
I am having my first venture into using pybitshares. I would like to obtain the historic market trade data for a trading pair, eg. BTS:ETH or other pairs, for up to their entire trading history.

The trades(limit=25, start=None, stop=None) function from the class provides the data I am interested in, however it appears there is an internal limit of 100 on the limit= parameter as if I try anything larger I get the following error:

Code: [Select]
RPCError                                  Traceback (most recent call last)
/usr/lib/python3.6/site-packages/bitsharesapi/ in rpcexec(self, payload)
     41             # Forward call to GrapheneWebsocketRPC and catch+evaluate errors
---> 42             return super(BitSharesNodeRPC, self).rpcexec(payload)
     43         except exceptions.RPCError as e:

/usr/lib/python3.6/site-packages/grapheneapi/ in rpcexec(self, payload)
    159             else:
--> 160                 raise RPCError(ret['error']['message'])
    161         else:

RPCError: Assert Exception: limit <= 100:

During handling of the above exception, another exception occurred:

UnhandledRPCError                         Traceback (most recent call last)
<ipython-input-6-7d79ce4640e5> in <module>()
      2 t2 = datetime(2017, 8, 12)  # to stop time
----> 4 market.trades(start=t1, stop=t2, limit=101)

/usr/lib/python3.6/site-packages/bitshares/ in trades(self, limit, start, stop)
    269             formatTime(stop),
    270             formatTime(start),
--> 271             limit)
    272         return list(map(
    273             lambda x: FilledOrder(

/usr/lib/python3.6/site-packages/grapheneapi/ in method(*args, **kwargs)
    193                      "jsonrpc": "2.0",
    194                      "id": self.get_request_id()}
--> 195             r = self.rpcexec(query)
    196             return r
    197         return method

/usr/lib/python3.6/site-packages/bitsharesapi/ in rpcexec(self, payload)
     48                 raise exceptions.NoMethodWithName(msg)
     49             elif msg:
---> 50                 raise exceptions.UnhandledRPCError(msg)
     51             else:
     52                 raise e

UnhandledRPCError: Assert Exception: limit <= 100:

I could put the trades() function in a loop and repeatedly call it for different start= and stop= datetimes until I have all the trade data, but that seems a crude workaround, so I was wondering if those with more knowledge and experience in this area could suggest any better approaches?  Is it possible to adjust the internal limit of 100 to a much higher value?

Also I was wondering if the internal 100 limit was a legacy of the development process and someone forgot about it, as I might do, or if it was to limit server load, though it does seem a low value to limit it to?

Pages: [1]