166
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.
167
General Discussion / Re: I want to contribute
« on: September 27, 2016, 03:00:10 pm »
Hi,
You could start here: https://github.com/cryptonomex/graphene-ui
You could start here: https://github.com/cryptonomex/graphene-ui
168
Technical Support / Re: Can't access my account Failed to sync with the API server
« on: September 27, 2016, 02:57:22 pm »
Try here: https://bitshares.org/wallet or download client: https://bitshares.org/download/
Most likely it's not your fault.
Most likely it's not your fault.
169
Technical Support / Re: Failed to sync with the API server
« on: September 27, 2016, 02:53:04 pm »
Works great, thank you.
170
Technical Support / Re: Failed to sync with the API server
« on: September 26, 2016, 07:33:31 pm »171
Technical Support / Re: Failed to sync with the API server
« on: September 26, 2016, 04:57:42 pm »
@svk,
Same here.
http://localhost:8080/#/ works fine until i choose Exchange tab - then
Same happen when I go to http://localhost:8080/#/explorer/blocks:
Tested with Firefox 47.0 (i know) and Chrome 52.0.2743.82 (64-bit)
No issues with web hosted clients.
Same here.
http://localhost:8080/#/ works fine until i choose Exchange tab - then
Code: [Select]
TypeError: c is null
C/e()
/:9
C/e()
/:9
C()
/:9
B.stockChart/e.xAxis<()
/:438
va()
/:27
B.stockChart()
/:438
t.exports/a<.renderChart()
/:1
bound ()
self-hosted:752
t.exports/a<.componentDidMount()
/:1
ReactCompositeComponentMixin.mountComponent/</<()
/:264
measureLifeCyclePerf()
/:74
ReactCompositeComponentMixin.mountComponent/<()
/:263
.notifyAll()
/:67
ON_DOM_READY_QUEUEING.close()
/:81
Mixin.closeAll()
/:204
Mixin.perform()
/:151
Mixin.perform()
/:138
.perform()
/:90
flushBatchedUpdates()
/:173
bound ()
self-hosted:752
Mixin.closeAll()
/:204
Mixin.perform()
/:151
ReactDefaultBatchingStrategy.batchedUpdates()
/:63
batchedUpdates()
/:98
ReactEventListener.dispatchEvent()
/:150
bound ()
self-hosted:792
Same happen when I go to http://localhost:8080/#/explorer/blocks:
Code: [Select]
Error in BlockchainActions.getLatest: TypeError: c is null
Stack trace:
C/e@webpack:///./~/highcharts/highstock.js?:9:17
C/e@webpack:///./~/highcharts/highstock.js?:9:46
C@webpack:///./~/highcharts/highstock.js?:9:159
B.stockChart/e.xAxis<@webpack:///./~/highcharts/highstock.js?:438:450
va@webpack:///./~/highcharts/highstock.js?:27:12
B.stockChart@webpack:///./~/highcharts/highstock.js?:438:412
t.exports/a<.renderChart@webpack:///./~/react-highcharts/dist/ReactHighstock.js?:1:1387
t.exports/a<.shouldComponentUpdate@webpack:///./~/react-highcharts/dist/ReactHighstock.js?:1:1701
ReactCompositeComponentMixin.updateComponent/shouldUpdate<@webpack:///./~/react/lib/ReactCompositeComponent.js?:622:20
measureLifeCyclePerf@webpack:///./~/react/lib/ReactCompositeComponent.js?:74:12
ReactCompositeComponentMixin.updateComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:621:26
ReactCompositeComponentMixin.receiveComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:544:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactCompositeComponentMixin._updateRenderedComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:751:7
ReactCompositeComponentMixin._performComponentUpdate@webpack:///./~/react/lib/ReactCompositeComponent.js?:721:5
ReactCompositeComponentMixin.updateComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:642:7
ReactCompositeComponentMixin.receiveComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:544:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactChildReconciler.updateChildren@webpack:///./~/react/lib/ReactChildReconciler.js?:110:9
ReactMultiChild.Mixin._reconcilerUpdateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:210:11
ReactMultiChild.Mixin._updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:314:26
ReactMultiChild.Mixin.updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:301:7
ReactDOMComponent.Mixin._updateDOMChildren@webpack:///./~/react/lib/ReactDOMComponent.js?:942:7
ReactDOMComponent.Mixin.updateComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:760:5
ReactDOMComponent.Mixin.receiveComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:718:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactChildReconciler.updateChildren@webpack:///./~/react/lib/ReactChildReconciler.js?:110:9
ReactMultiChild.Mixin._reconcilerUpdateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:210:11
ReactMultiChild.Mixin._updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:314:26
ReactMultiChild.Mixin.updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:301:7
ReactDOMComponent.Mixin._updateDOMChildren@webpack:///./~/react/lib/ReactDOMComponent.js?:942:7
ReactDOMComponent.Mixin.updateComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:760:5
ReactDOMComponent.Mixin.receiveComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:718:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactChildReconciler.updateChildren@webpack:///./~/react/lib/ReactChildReconciler.js?:110:9
ReactMultiChild.Mixin._reconcilerUpdateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:210:11
ReactMultiChild.Mixin._updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:314:26
ReactMultiChild.Mixin.updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:301:7
ReactDOMComponent.Mixin._updateDOMChildren@webpack:///./~/react/lib/ReactDOMComponent.js?:942:7
ReactDOMComponent.Mixin.updateComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:760:5
ReactDOMComponent.Mixin.receiveComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:718:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactChildReconciler.updateChildren@webpack:///./~/react/lib/ReactChildReconciler.js?:110:9
ReactMultiChild.Mixin._reconcilerUpdateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:210:11
ReactMultiChild.Mixin._updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:314:26
ReactMultiChild.Mixin.updateChildren@webpack:///./~/react/lib/ReactMultiChild.js?:301:7
ReactDOMComponent.Mixin._updateDOMChildren@webpack:///./~/react/lib/ReactDOMComponent.js?:942:7
ReactDOMComponent.Mixin.updateComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:760:5
ReactDOMComponent.Mixin.receiveComponent@webpack:///./~/react/lib/ReactDOMComponent.js?:718:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactCompositeComponentMixin._updateRenderedComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:751:7
ReactCompositeComponentMixin._performComponentUpdate@webpack:///./~/react/lib/ReactCompositeComponent.js?:721:5
ReactCompositeComponentMixin.updateComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:642:7
ReactCompositeComponentMixin.receiveComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:544:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactCompositeComponentMixin._updateRenderedComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:751:7
ReactCompositeComponentMixin._performComponentUpdate@webpack:///./~/react/lib/ReactCompositeComponent.js?:721:5
ReactCompositeComponentMixin.updateComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:642:7
ReactCompositeComponentMixin.receiveComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:544:5
ReactReconciler.receiveComponent@webpack:///./~/react/lib/ReactReconciler.js?:126:5
ReactCompositeComponentMixin._updateRenderedComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:751:7
ReactCompositeComponentMixin._performComponentUpdate@webpack:///./~/react/lib/ReactCompositeComponent.js?:721:5
ReactCompositeComponentMixin.updateComponent@webpack:///./~/react/lib/ReactCompositeComponent.js?:642:7
ReactCompositeComponentMixin.performUpdateIfNecessary@webpack:///./~/react/lib/ReactCompositeComponent.js?:558:7
ReactReconciler.performUpdateIfNecessary@webpack:///./~/react/lib/ReactReconciler.js?:158:5
runBatchedUpdates@webpack:///./~/react/lib/ReactUpdates.js?:151:5
Mixin.perform@webpack:///./~/react/lib/Transaction.js?:138:13
Mixin.perform@webpack:///./~/react/lib/Transaction.js?:138:13
.perform@webpack:///./~/react/lib/ReactUpdates.js?:90:12
flushBatchedUpdates@webpack:///./~/react/lib/ReactUpdates.js?:173:7
Mixin.closeAll@webpack:///./~/react/lib/Transaction.js?:204:11
Mixin.perform@webpack:///./~/react/lib/Transaction.js?:151:11
ReactDefaultBatchingStrategy.batchedUpdates@webpack:///./~/react/lib/ReactDefaultBatchingStrategy.js?:63:7
enqueueUpdate@webpack:///./~/react/lib/ReactUpdates.js?:201:5
enqueueUpdate@webpack:///./~/react/lib/ReactUpdateQueue.js?:25:3
ReactUpdateQueue.enqueueSetState@webpack:///./~/react/lib/ReactUpdateQueue.js?:210:5
ReactComponent.prototype.setState@webpack:///template_of_302_referencing_?:64:3
AltContainer/this.altSetState@webpack:///./~/alt-container/lib/AltContainer.js?:167:7
push/<@webpack:///../dl/~/transmitter/dist/transmitter.js?:21:14
push@webpack:///../dl/~/transmitter/dist/transmitter.js?:20:5
AltStore/this.emitChange@webpack:///../dl/~/alt/lib/store/AltStore.js?:50:14
AltStore/this.dispatchToken<@webpack:///../dl/~/alt/lib/store/AltStore.js?:98:56
Dispatcher.prototype.$Dispatcher_invokeCallback@webpack:///../dl/~/flux/lib/Dispatcher.js?:220:5
Dispatcher.prototype.dispatch@webpack:///../dl/~/flux/lib/Dispatcher.js?:195:9
dispatch/<@webpack:///../dl/~/alt/lib/index.js?:89:16
Alt/this.batchingFunction<@webpack:///../dl/~/alt/lib/index.js?:56:14
dispatch@webpack:///../dl/~/alt/lib/index.js?:72:7
dispatch@webpack:///../dl/~/alt/lib/actions/index.js?:38:7
getLatest/<@webpack:///../dl/src/actions/BlockchainActions.js?:40:21Tested with Firefox 47.0 (i know) and Chrome 52.0.2743.82 (64-bit)
No issues with web hosted clients.
173
Technical Support / Re: Minimal required changes to revive an MPA after a black swan event?
« on: September 18, 2016, 12:53:42 pm »
Great lesson, indeed... and very cheap.
I was unable to close my position when market moves my direction, so I set my collateral as low as possible when BTS jumped to 1300 sat. If we didn't stop there I could be even at profit while margin called. (bolded one).
Anyway, my position is closed, orderbook is empty - I had also buy order which I've been canceled by hand after black swan event. I suppose others done the same.
What we've got now is 1,472 BTS in Setllement fund which could be used to cover holders ( some may be at loos, some not - relative to BTS) with 1: 1,47 ratio
I think proper way to resolve black swan event is:
1 auto-cancel all orders
2.refund holders - they should be aware what is their risk before the trade.
3. Restart market and expect different results ?
I was unable to close my position when market moves my direction, so I set my collateral as low as possible when BTS jumped to 1300 sat. If we didn't stop there I could be even at profit while margin called. (bolded one).
Anyway, my position is closed, orderbook is empty - I had also buy order which I've been canceled by hand after black swan event. I suppose others done the same.
What we've got now is 1,472 BTS in Setllement fund which could be used to cover holders ( some may be at loos, some not - relative to BTS) with 1: 1,47 ratio
I think proper way to resolve black swan event is:
1 auto-cancel all orders
2.refund holders - they should be aware what is their risk before the trade.
3. Restart market and expect different results ?
Quote
kezzik121 bought 1,000 GRIDCOIN at 1.471823 BTS/GRIDCOIN
kezzik121 bought 1,110.59 BTS at 0.85 GRIDCOIN/BTS
kezzik121 bought 11.76 BTS at 0.8499997 GRIDCOIN/BTS
kezzik121 bought 6 BTS at 0.83333333 GRIDCOIN/BTS
kezzik121 bought 6.5 BTS at 0.76923077 GRIDCOIN/BTS
kezzik121 bought 7 BTS at 0.71428571 GRIDCOIN/BTS
kezzik121 bought 15 BTS at 0.66666667 GRIDCOIN/BTS
kezzik121 bought 16 BTS at 0.625 GRIDCOIN/BTS
kezzik121 bought 20 BTS at 0.50 GRIDCOIN/BTS
kezzik121 bought 1.17 BTS at 0.85655306 GRIDCOIN/BTS
174
Technical Support / Re: Questions about shorting
« on: September 18, 2016, 10:25:17 am »
I'm not an expert, actually I'm a noob, but i know that margin trading is very risky game. Shorter must be sure that he can open or close his position at any time with fair price. What he need is fat orderbook (on both side) and tight spread, otherwise he can lose even if was right.
This leads to question who could provide that?
Isn't Smartcoins answer for lack of stability in crypto world, so why almost nobody wants make use of it?
ANTSHARE did by selling their UIA primarily with bitCNY
CONSTRUCTION did by selling his UIA only for bitUSD ( actually I'm the only sucker(?) who bought a bit just because this.)
Would be very awesome if BLOCKPAY, PEERPLAYS and so on did the same - but it's to late for that and probably not in their best interest.
Any decent project doing/done the same? I'm quite new here.
This leads to question who could provide that?
Isn't Smartcoins answer for lack of stability in crypto world, so why almost nobody wants make use of it?
ANTSHARE did by selling their UIA primarily with bitCNY
CONSTRUCTION did by selling his UIA only for bitUSD ( actually I'm the only sucker(?) who bought a bit just because this.)
Would be very awesome if BLOCKPAY, PEERPLAYS and so on did the same - but it's to late for that and probably not in their best interest.
Any decent project doing/done the same? I'm quite new here.
175
Technical Support / Re: Questions about shorting
« on: September 17, 2016, 11:28:35 am »
Because at the end you have more BTS... if lucky.
What you do while shorting is playing with borrowed money. Borrow => sell high => buy low => pay your debt = difference is yours.
What you do while shorting is playing with borrowed money. Borrow => sell high => buy low => pay your debt = difference is yours.
176
General Discussion / Re: BTS tranfer to poloniexwallet went wrong
« on: September 16, 2016, 04:14:58 am »
You can send him 1 BTS and put message in memo field, but Chronos is right.
178
General Discussion / Re: Cryptofresh API
« on: September 13, 2016, 04:40:15 pm »
Yes, noticed that Openledger working on their own gui and i like those changes. What about @svk? Do you know his plans?
179
General Discussion / Re: Cryptofresh API
« on: September 13, 2016, 04:11:21 pm »
BTW we have 0 zero active workers right now.
180
Openledger / Re: Open.xxx assets withdrawal not working
« on: September 12, 2016, 10:33:38 pm »
http://cryptofresh.com/u/openledger-wallet
For me works fine. Track this account.
For me works fine. Track this account.
