16
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.
17
Technical Support / Re: Do we have mobile infrastructure for iOS and Android?
« on: March 01, 2016, 09:44:23 pm »The answer to your question is: Yes.
The current web wallet does it the same way. The private key never leaves the browser on the clientside
I think we'd better have native library for Android and iOS. If we restrict ourselves in "wallet", current state is okay IMO. But if we want to expand our services to the blue ocean, we need native libraries.
18
General Discussion / Graphene Library for Java?
« on: March 01, 2016, 06:31:40 pm »
Mobile app market is very large and have great potentials. It's a key of success -- without having mobile apps, Uber-like services couldn't succeed.
I saw Ken's mobile wallet uses JS library, and maybe the development was little difficult because he has to import JS into Android Java structure.
But what if we had Java library for Graphene? Anyone can easily subscribe blockchain using websocket, and send transactions without storing their private keys in the server, like current Javascript wallet does. This will bolster Bitshares as a platform.
I saw Ken's mobile wallet uses JS library, and maybe the development was little difficult because he has to import JS into Android Java structure.
But what if we had Java library for Graphene? Anyone can easily subscribe blockchain using websocket, and send transactions without storing their private keys in the server, like current Javascript wallet does. This will bolster Bitshares as a platform.
19
General Discussion / Re: [ANN] Kkachi Service is Opened to the Community
« on: February 28, 2016, 06:58:28 am »Very nice clayop. What kind of profit have you been running so far?
Please see this link:
https://bitsharestalk.org/index.php/topic,21221.msg281259.html#msg281259
Kkachi mainly made some profits in BTC, in short.
20
General Discussion / [ANN] Kkachi Service is Opened to the Community
« on: February 28, 2016, 02:01:38 am »
Kkachi has been providing liquidity into DEX by copying orderbooks from outside and performed well during the last month. (https://bitsharestalk.org/index.php/topic,21221.msg281259.html#msg281259)
I decided to open Kkachi service to the community in order to anyone can provide liquidity to DEX using Kkachi and make a profit.
To use Kkachi service, please read the following instructions and conditions:
1) Operation Period: 2016/3/4 ~ 2016/4/3. You cannot withdraw fund during the period.
2) All your principals are protected in terms of quantity.
3) Minimum investment is 0.5 BTC worth. (e.g. 0.25 BTC, 25k BTS)
4) Your fund shoud be a combination of BTC and Non-BTC. The ratio between BTC and non-BTC should be greater than 1.
(e.g. 2 BTC and 100k BTS - Okay / 1 BTC and 200k BTS - Not Acceptable)
FYI: This is due to the slowness of BTC transfer. To be agile, Kkachi must have more BTC than BTS.
5) Fee is proportional to profit rate with maximum of 20%. The fee does not applied to your principal, but only to your profit.
(e.g. 1% profit - 1% fee / 30% profit - 20% fee from the profit)
6) If the connected exchange is compromised (I will inform the exchange's name to users), 50% of your fund can be haircut.
7) Supported currencies and rates:
a) BTS: 1 BTC = 100,000 BTS
b) ETH: 1 BTC = 70 ETH
Please PM me before 2016/3/4 if you're interested in. Please include your planned amounts and currency and send them before the beginning date after confirmation from me. If you have questions, please let me know.
Lastly, I want to remind you that this service is based on trust (in me and the external exchange) so don't put too much fund into this service.
I decided to open Kkachi service to the community in order to anyone can provide liquidity to DEX using Kkachi and make a profit.
To use Kkachi service, please read the following instructions and conditions:
1) Operation Period: 2016/3/4 ~ 2016/4/3. You cannot withdraw fund during the period.
2) All your principals are protected in terms of quantity.
3) Minimum investment is 0.5 BTC worth. (e.g. 0.25 BTC, 25k BTS)
4) Your fund shoud be a combination of BTC and Non-BTC. The ratio between BTC and non-BTC should be greater than 1.
(e.g. 2 BTC and 100k BTS - Okay / 1 BTC and 200k BTS - Not Acceptable)
FYI: This is due to the slowness of BTC transfer. To be agile, Kkachi must have more BTC than BTS.
5) Fee is proportional to profit rate with maximum of 20%. The fee does not applied to your principal, but only to your profit.
(e.g. 1% profit - 1% fee / 30% profit - 20% fee from the profit)
6) If the connected exchange is compromised (I will inform the exchange's name to users), 50% of your fund can be haircut.
7) Supported currencies and rates:
a) BTS: 1 BTC = 100,000 BTS
b) ETH: 1 BTC = 70 ETH
Please PM me before 2016/3/4 if you're interested in. Please include your planned amounts and currency and send them before the beginning date after confirmation from me. If you have questions, please let me know.
Lastly, I want to remind you that this service is based on trust (in me and the external exchange) so don't put too much fund into this service.
21
Technical Support / Do we have mobile infrastructure for iOS and Android?
« on: February 27, 2016, 10:37:28 pm »
Can mobile users connect any graphene websocket server, and send transactions with having their private keys only in their devices?
Do we have such APIs? (or kind of develop infrastructures)
Do we have such APIs? (or kind of develop infrastructures)
22
General Discussion / Why No 160225 Windows/Mac Binaries Uploaded?
« on: February 27, 2016, 06:02:57 am »
I was tagged yesterday, but so far there's no binaries on github. Who will upload them and when?
23
General Discussion / Re: Annoying problem matching orders
« on: February 25, 2016, 08:02:03 pm »I had the same problem. I wondered why there is so little information on the internet about bitshares. I guess I found out why. This kind of things are unacceptable.
I deposited some bitcoins, then I realized that there is nothing called bitUSD I can buy anywhere, and there is 25% difference from other markets price for something called USD (what the heck). I decided to withdraw my bitcoins but I did't have any BTS to cover the fee. It didn't want to mach the orders. After some tries I realized there is 9,9BTS fee return, and that way I managed to collect the fee for withdrawal. Meanwhile I got a headache. It looked so good...
This tells a lot...
24
General Discussion / Re: Poloniex Deposit
« on: February 25, 2016, 12:34:29 am »
The real problem is polo mods and supports don't realize this issue for 24 hours. If this happens again, run to polo trollbox and complain about it (after creating a ticket)
25
General Discussion / Re: NXT forks BitShares 2.O mojo! goes for scalability
« on: February 24, 2016, 11:45:47 pm »Same procedure as every year ..
While we are sitting here in a circle jerk arguing about dilution, other people are taken our ideas and running with them.
At least we wont have much money to spend innovating in future
Shame...
Where does NXT get the money for innovating? They have no dilution right.
Not against diluting for good/profitable development obviously, just slightly ironic/humorous we're attempting to justify dilution for development using a competitor innovating/developing with no dilution
IMO the motivation is NXT price increase, and that's the win-win for shareholders and workers.
If a worker declares that he won't get paid until the price doubled, he may get voted in
26
General Discussion / Re: Poloniex Deposit
« on: February 24, 2016, 04:53:42 pm »If there's a lot of txs it misses some txs.works for meThe one get fixed is another issue. I think it's not high priority and few people using cli_wallet or that API and many people (for example roadscape) already know that, so didn't bother open an issue.Afaik that issue jas been fixed withblatest releaseI'm having this problem again.
And FYI, they missed some deposited because of broken "get_account_history" API. I sent them a simple script to detect them.
If it's can be fixed, please open the issue at github: https://github.com/cryptonomex/graphene/issues
@xeroc you can simply try these commands in cli_wallet to see if it's buggy:Code: [Select]get_account_history in.abit 100
get_account_history in.abit 101
27
General Discussion / Re: Poloniex Deposit
« on: February 24, 2016, 03:53:32 am »It's dead again.
withdrawal issues?
Deposit at least.
28
General Discussion / Re: Poloniex Deposit
« on: February 24, 2016, 01:07:56 am »
It's dead again.
29
General Discussion / Re: Market making bot "Kkachi" is on testing in the DEX (OPENBTC-BTS)
« on: February 23, 2016, 07:13:27 am »
After over 100k transactions and about 500 filled orders, Kkachi needs some rest for a while (to payback to investors)
Here's a short summary,
Operation day: 25 days
Principal: 1.37 BTC, 81000 BTS, 75 ETH
Result: 1.79 BTC, 84500 BTS, 79 ETH
Profit: 0.42 BTC (30.6%) , 3500 BTS (4.3%), 4 ETH (5.3%)
Kkachi will be back soon!
Here's a short summary,
Operation day: 25 days
Principal: 1.37 BTC, 81000 BTS, 75 ETH
Result: 1.79 BTC, 84500 BTS, 79 ETH
Profit: 0.42 BTC (30.6%) , 3500 BTS (4.3%), 4 ETH (5.3%)
Kkachi will be back soon!
30
Stakeholder Proposals / Re: [Worker Proposal] Blockchain maintenance developer
« on: February 22, 2016, 11:17:00 pm »Here's a list of issues handled by this worker to date. Most of these were done by theoretical, other than #251 and the ones related to Windows builds, since BlockTrades has been tied up with other work for most of the period.Great. I will vote for you when voting bug is fixed.
https://github.com/cryptonomex/graphene/issues/251
https://github.com/cryptonomex/graphene/issues/514
https://github.com/cryptonomex/graphene/issues/516
https://github.com/cryptonomex/graphene/issues/542
https://github.com/cryptonomex/graphene/issues/549
https://github.com/cryptonomex/graphene/issues/550
https://github.com/cryptonomex/graphene/issues/553
https://github.com/cryptonomex/graphene/issues/555
https://github.com/cryptonomex/graphene/issues/556
https://github.com/cryptonomex/graphene/issues/559
https://github.com/cryptonomex/graphene/issues/562
https://github.com/cryptonomex/graphene/issues/566
https://github.com/cryptonomex/graphene/issues/572
https://github.com/cryptonomex/graphene/issues/586
