BitShares Forum
Main => General Discussion => Topic started by: bytemaster on October 12, 2015, 03:42:55 pm
-
Here is a screenshot showing the deposit / withdraw interface
https://slack-files.com/T04MJ0W5X-F0CA1QX98-a705cfc235
https://slack-files.com/T04MJ0W5X-F0C9Y3E9L-4d95d638c7
-
wow +5% +5% +5% +5% +5%
-
awesome!
-
+5%
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
-
Excellent! Looking really clean!!
-
Good stuff +5%
-
+5% +5% nice.
by the way , when will 2.0 build be available?
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
he said: any
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
he said: any
Blocktrades and ccedk are built in.
-
Blocktrades and ccedk are built in.
Have you asked to be included?
Or do you know what criteria you must met to get included?
-
Is there any sample of fiat deposit page?
-
Have you asked to be included?
Or do you know what criteria you must met to get included?
Last thing I heard was that we were being integrated.
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
he said: any
Blocktrades and ccedk are built in.
We will be more than happy to add support for your gateway. Support for Blocktrades was "last second" and CCEDK is using the same backend as Blocktrades so they got it for free. I just haven't had the time to do custom development to support others yet.
-
Here is a screenshot showing the deposit / withdraw interface
https://slack-files.com/T04MJ0W5X-F0CA1QX98-a705cfc235
https://slack-files.com/T04MJ0W5X-F0C9Y3E9L-4d95d638c7
When I bought my first Bitcoin / Altcoin on Cryptsy it took me quite a while to figure out what "generate" has to do with the depositing process because I didnt know anything about Bitcoin. Maybe the Button could be "Deposit / Generate" instead of "Generate" only?
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
he said: any
Blocktrades and ccedk are built in.
We will be more than happy to add support for your gateway. Support for Blocktrades was "last second" and CCEDK is using the same backend as Blocktrades so they got it for free. I just haven't had the time to do custom development to support others yet.
the point is we were delegated to valentine to talk to him. we did a short skype talk in JUNE. We left the conversation that he will look into it and will talk to us if he needs anything from us. So now on launch time we are not integrated and it seems we have to do the work by ourself. Fine, maybe we are not important etc. but this is not a good way to support the only open-source community supported exchange.
-
Will blocktrade reduce the fee on btc to trade.btc conversion since they can generate income from trading in graphene?
-
We will add support for any exchanges / gateways / bridges that define a React JS component and give us a pull request.
The excuse for not integrating metaexchange into 1.0 was that you didn't want to show favouritism to any one service, so for 2.0 you go and integrate your business partners only?
Nice.
he said: any
Blocktrades and ccedk are built in.
We will be more than happy to add support for your gateway. Support for Blocktrades was "last second" and CCEDK is using the same backend as Blocktrades so they got it for free. I just haven't had the time to do custom development to support others yet.
the point is we were delegated to valentine to talk to him. we did a short skype talk in JUNE. We left the conversation that he will look into it and will talk to us if he needs anything from us. So now on launch time we are not integrated and it seems we have to do the work by ourself. Fine, maybe we are not important etc. but this is not a good way to support the only open-source community supported exchange.
If you have an API for generating a deposit address and can accept withdraws by having the BTC address in the memo then I can probably get you integrated today.
-
If you have an API for generating a deposit address and can accept withdraws by having the BTC address in the memo then I can probably get you integrated today.
https://metaexchange.info/apiDocs#api/1/submitAddress
Withdrawals would be bitshares asset to native asset? Use the function above to get a destination address + memo; the memo is customised to suit the order, its not a plain BTC address. Any questions please give me a shout and thank you for considering us :)
-
Nice, but these dialogs are not clear at all. When I "withdraw" Bitcoin it doesnt show the conversion rate from CORE to Bitcoin (from looking at graphene.bitshares.org)
Also depositing Bitcoin gives TRADE.BTC - why should I prefer that over BitBTC? And the dialog should have a risk disclaimer about the TRADE.BTC UIA being vulnerable to couterparty risk.
+5% for Metaexchange integration - competition is good escpecially because Meta seems to give tighter spreads!
-
Guys .. please calm down .. we are talking about an MVP!! I know people are expecting wonders .. but there is alot (and I really mean alot) of development ongoing (not to say the last few weeks have been VERY productive from the webdev team) .. please give them some little time to implement your feature request ..
This is still 2015 and many months to go to release the kraken (phun intended)
-
Guys .. please calm down .. we are talking about an MVP!! I know people are expecting wonders .. but there is alot (and I really mean alot) of development ongoing (not to say the last few weeks have been VERY productive from the webdev team) .. please give them some little time to implement your feature request ..
This is still 2015 and many months to go to release the kraken (phun intended)
^^^ This... for those of you who are not programmers.. MVP means Minimum Viable Product.. note the Minimum. :) It's like getting a car without the leather bucket seats.. it will get you from point A to B. Which is what we really want here.
-
Guys .. please calm down .. we are talking about an MVP!! I know people are expecting wonders .. but there is alot (and I really mean alot) of development ongoing (not to say the last few weeks have been VERY productive from the webdev team) .. please give them some little time to implement your feature request ..
This is still 2015 and many months to go to release the kraken (phun intended)
And being a web wallet, releases / fixes can be made faster...