Author Topic: bitAsset FIAT Gateway  (Read 7275 times)

0 Members and 1 Guest are viewing this topic.

Offline bitmarket

  • Sr. Member
  • ****
  • Posts: 369
    • View Profile
    • BitShares TV
Valuable feedback @btswolf.  Thank you.
Host of BitShares.TV and Author of BitShares 101

Offline mike623317

  • Hero Member
  • *****
  • Posts: 637
    • View Profile
thank you guys for doing this.  +5%

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Exactly.  +5%
We need it here in munich for our point of sale systems too, no more bitpay needed at the kasse if we have the bts api's avail to us.
Would be nice to be able to accept cryptos, bitassets, cash or credit at the kasse. cash register..
i'll help out with the docs if someone directs me to where we can collab on it.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline btswolf

Do we already have Marketing or Bounty delegates that could free up some Money for a bounty to create a perfectly written API Guide?
We have at least one well known direct Gateway possibility in europe that only requires a good API Guide.
Cannot be this complicated...

Offline btswolf

IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json
I totally agree ... we should expose the api "documentation" more in the wiki!

i want to integrate API documentation on bitshares.org

http://swagger.io/

Great whats the timeline? I know you are very busy :)

@Xeroc: Thx for your quick Wiki article

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json
I totally agree ... we should expose the api "documentation" more in the wiki!

i want to integrate API documentation on bitshares.org

http://swagger.io/
I like this .. it's like yunbi's documentation:
https://yunbi.com/documents/api_v2?lang=en

Can we feed swagger with JSON definitions easily to keep integrity?

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json
I totally agree ... we should expose the api "documentation" more in the wiki!

i want to integrate API documentation on bitshares.org

http://swagger.io/
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I don't know why but thats what Toast have told them.
I think he already pointed them to the docs, but don't know which ones.

But is a json file really a good documentation?
Is that all we should be able to offer our potential partners?
APIs are for developers .. when they are called the result will by a JSON object .. so developers should be able to read JSON quit well ..
also, the json codes in the client DEFINES the API calls .. if something is stated there .. the client will do it that way ..
Hence, there will not be any inconsistency ..

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline btswolf

I don't know why but thats what Toast have told them.
I think he already pointed them to the docs, but don't know which ones.

But is a json file really a good documentation?
Is that all we should be able to offer our potential partners?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json
I totally agree ... we should expose the api "documentation" more in the wiki!

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
IMO the BitShares API documentation is much more detailed than for example bitcoin's. What API documentation have they looked at? The wiki only, or the built-in help?

Maybe point them here:

https://github.com/BitShares/bitshares/blob/master/libraries/api/blockchain_api.json
https://github.com/BitShares/bitshares/blob/master/libraries/api/wallet_api.json
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline btswolf

Got another talk with them.
Our "very sparse" API documentation is what prevents them at this point to integrate BitAssets.
"I have talked with the dev and he said that the API documentation is “very sparse”. We implement a lot of things with an API and the main issue is always the bad API documentation.

So to be able to make BitAssets/BitShares widely accepted it might be good to make sure the API documentation is perfect."


If this is the main reason why BitShares is not widely adopted and why we don't have a good FIAT gateway, who is able to write a good API documentation.
I am not sure but I would say even without 1.0 out there, someone should start to do this job now.
We need to enable businesses to integrate our products easily by themself, at least with a good documentation, then it will be only be a matter of time...

Is someone already working on this and needs help?
Who is able to do this?
- only Devs?
- Community members?
- pc?
How long would this take?
Do we need a bounty or delegate?

Offline btswolf

I've connected Toast with them and he offered help and maybe he can provide some experience on how long it would take to implement BitAssets.
I will contact them again on monday and keep you up to date.

BTSwolf is just my project, a german based BitShares promo project in its early stage.

Offline mike623317

  • Hero Member
  • *****
  • Posts: 637
    • View Profile
 Who is this BTSWOLF and what is the expected cost?

This would truely be great news if we could make this happen.

Kudos  +5%