by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ankit Yadav
    @ankit-yadv

    Hi Everyone,

    Welcome to OST Platform's new chat room. This chat room is intended for enabling communication and help to solve technical issues faced by OST Platform developers.

    Below you can find some frequently asked questions.
    Benjamin Bollen
    @benjaminbollen
    Hi đź‘‹
    Ankit Yadav
    @ankit-yadv

    FAQs

    Question-1. Is it possible for a user to create a wallet in the web browser? Or do you need a mobile app to confirm transactions?

    Question-1. Is it possible for a user to create a wallet in the web browser? Or do you need a mobile app to confirm transactions?

    The OST Wallet SDKs support non-custodial wallets, where users hold their keys and can transact with Brand Tokens using their mobile devices.
    The mobile-first approach takes advantage of the security features of modern mobile devices to securely generate the required keys on the user's mobile device and encrypt them using the secure enclave (on iOS) or key store (on Android)
    There are a number of security advantages to building the wallets into Android and iOS mobile apps and using the security on the devices.
    Browser-based solutions are less secure unless implementing a browser extension/plug-in like Metamask does. We have looked at potentially adding something like that in the future but it is not on the near term roadmap since it's a more clumsy user experience, and most companies are very comfortable with and have existing Android and iOS apps, or can launch a new one. In the future we can also look at providing a standalone OST wallet, however our clients tell us they care more about having Brand Tokens in their own apps, so that has not been prioritised at this time.

    Question-2. Can you split Brand Tokens into small units?

    Question-2. Can you split Brand Tokens into small units?

    Brand Tokens are ERC20 based tokens, so they support division up to 18 decimals. Following the SI-naming conventions the smallest denomination is referred to as atto Brand Tokens on the OST Platform.
    The denominations are explained further on dev website.
    https://dev.ost.com/platform/docs/guides/execute_transaction/#conversions-to-atto

    Ankit Yadav
    @ankit-yadv
    Question-3. Do we have to buy OST and mint all BTs in advance or can we buy OST as the users obtain more and more BTs?

    Question-3. Do we have to buy OST and mint all BTs in advance or can we buy OST as the users obtain more and more BTs?

    The smart contract to create branded tokens requires the full value of all minted tokens to be backed by the stake. There is no way around that requirement.

    However, you can mint tokens as you go, so you can start with the minimum required amount and mint more as needed for distribution.

    Question-4. How should we calculate the value of a BT? is 1 OST = 1 BT? Or should it be calculated in USD?

    Question-4. How should we calculate the value of a BT? is 1 OST = 1 BT? Or should it be calculated in USD?

    You set the conversion rate between BT and OST before launching the economy. OST Platform sets a default conversation rate of 1OST=1BT. If you like, you can choose to set an alternative conversion rate. Once you mint your token, the conversion rate is fixed and cannot be changed.
    Two things to consider when setting the conversion rate:

    1. Order of magnitude of token rewards: do you wish to reward single digit, 10s, 100s, 1000s of tokens per incentive?
    2. Fiat value of each token
    Anders
    @andersalm
    hi. im using php sdk for the first time. every request i do ends up with "SOMETHING_WENT_WRONG".
    im using the API keys from dashboard and copied the simple code from the getting started guide
    running on windows and wamp
    Ankit Yadav
    @ankit-yadv
    Hi @andersalm, we will need the following details to look into the error:
    1. Code snippet (Remove your API Secret, don’t remove your API KEY as we will need for debugging, Code snippet should have SDK instantiation code + API call code)
    2. PHP SDK Version
    3. PHP Version
    4. Complete Error response (as returned from the API)
    Anders
    @andersalm

    <?php
    require 'vendor/autoload.php';

    $params = array();
    $params['apiKey']='xxx';
    $params['apiSecret']='xxx';
    $params['apiBaseUrl']='https://api.ost.com/testnet/v2/';

    // The config field is optional
    $configParams = array();
    // This is the timeout in seconds for which the socket connection will remain open
    $configParams["timeout"] = 30;
    $params["config"] = $configParams;

    $ostObj = new OSTSdk($params);

    $userService = $ostObj->services->users;

    $createParams = array();
    $response = $userService->create($createParams)->wait();
    echo json_encode($response, JSON_PRETTY_PRINT);
    ?>

    PHP Version 5.6.31 (WAMP 3.1.0)

    { "success": false, "err": { "code": "SOMETHING_WENT_WRONG", "internal_id": "SDK(g_1)", "msg": "", "error_data": [] } }

    Ankit Yadav
    @ankit-yadv

    Hi @andersalm,
    We were not able to reproduce the error on our side. We have updated the PHP SDK code (dev-debug_v2.0.0 branch) to print a detailed error object.

    To install and use the updated SDK follow these steps:

    1. curl -sS https://getcomposer.org/installer | php
    2. php composer.phar require ostdotcom/ost-sdk-php:dev-debug_v2.0.0
    3. Rerun your API call snippet.
    4. This time you will get a detailed error. Send us that error object along with your API call snippet.
    Anders
    @andersalm
    private 'handlerContext' =>
    array (size=28)
    'errno' => int 60
    'error' => string 'SSL certificate problem: self signed certificate in certificate chain' (length=69)
    'url' => string 'https://api.ost.com/testnet/v2/users/' (length=37)
    'content_type' => null
    'http_code' => int 0
    'header_size' => int 0
    'request_size' => int 0
    'filetime' => int -1
    'ssl_verify_result' => int 19
    'redirect_count' => int 0
    'total_time' => float 0.766
    'namelookup_time' => float 0.172
    'connect_time' => float 0.453
    'pretransfer_time' => float 0
    'size_upload' => float 0
    'size_download' => float 0
    'speed_download' => float 0
    'speed_upload' => float 0
    'download_content_length' => float -1
    'upload_content_length' => float -1
    'starttransfer_time' => float 0
    'redirect_time' => float 0
    'redirect_url' => string '' (length=0)
    'primary_ip' => string '' (length=13)
    'certinfo' =>
    array (size=0)
    empty
    'primary_port' => int 443
    'local_ip' => string '' (length=13)
    'local_port' => int 55108
    protected 'message' => string 'cURL error 60: SSL certificate problem: self signed certificate in certificate chain (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)' (length=140)
    is there a way to do bypass this for development? i tried adding CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST to false in vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php
    Ankit Yadav
    @ankit-yadv

    Hi @andersalm,

    It looks like an issue with the outdated certificates or with the php.ini file. A workaround for wamp is given in this StackOverflow thread. Let us know if you are still facing any issues.

    Klaus Alfert
    @alfert
    I have got conceptional questions. How can I access the transactions of the sidechain for my Brand Token? And who is operating the sidechain?
    The reasoning behind my questions: if I can only access any information about the sidechain, its transactions and balances via your API, then I have to trust you that you manage the sidechain properly. In that case, the entire blockchain and token approach would be a very complicated system with the same security/trust features as a central database operated by you. The whitepapers seem to be outdated regarding the current software release, if I understand them right. Did I miss something? Thanks in advance for clarifying!
    Ankit Yadav
    @ankit-yadv

    Hi @alfert ,
    Thanks for asking this question.

    First, please note that the OST sidechains are public. All transactions recorded on OST sidechains are on public sidechains that anyone can view and audit. So, it’s not a private chain in any way. You can view the OST sidechains at https://view.ost.com. You can also sync and run OpenST Mosaic (alpha) nodes yourself: https://github.com/OpenST/mosaic-chains

    In the current version of OST Platform (for public pilots), transactions will be validated through a Proof of Authority (PoA) consensus mechanism. Under PoA, the network consists of a permissioned set of trusted validators approved by OST to verify transactions. Under PoA, OST approves validators to join the network based on an assessment of how much skin in the game they have to run a secure and trusted network. The OST Platform is starting with PoA, first with OST as the only validator and then expanding to other permissioned validators, to provide for initial platform stability and to kick off the network and the economic incentives needed for validators to participate.

    We are planning to decentralize the network in phases. Once the network is well established, we will transition validation to a completely decentralized Proof of Stake consensus mechanism as part of OpenST Mosaic. More details on OpenST mosaic can be found in its whitepaper here: https://github.com/OpenST/mosaic-contracts/blob/develop/docs/mosaicv0.pdf

    daan-ost
    @daan-ost
    Hi question. I currently looking into the mobile apps / wallet SDK. In the demo IOS app it seems you don't need the store / use the service side API key / secret. Is that correct? If you want to show transactions of that user in a wallet in your IOS app, you use only the wallet SDK methods?
    Anders
    @andersalm
    what is Mappy? i cant find any information other than https://en.mappy.com/
    the demo app needs a base url for mappy
    Ankit Yadav
    @ankit-yadv
    Hi @andersalm, Mappy is your application server. You will have to setup one server, it can be a local server as well. You can then use Server Side SDKs on this server.
    Ankit Yadav
    @ankit-yadv

    Hi @daan-ost,

    1. That’s correct you don’t need API KEY and API Secret in Wallet SDK. Wallet SDK uses a different auth mechanism. Read more about Wallet SDK Authentication here: https://dev.ost.com/platform/docs/sdk/getting_started/authentication/#wallet-sdk-authentication

    2. Using Wallet SDK, you can only fetch information that is related to the user using mobile application. Transaction information has addresses of receiver and sender. You cannot get more details about these addresses as Wallet SDK can’t fetch that information. So, It is recommended that you use Server Side SDK (available in PHP, Ruby, Node.js and JAVA) to get the transaction information.
      Read more about transaction API here: https://dev.ost.com/platform/docs/api/#transactions

    daan-ost
    @daan-ost
    @ankit-yadv ok tnx
    daan-ost
    @daan-ost
    Other question, when I register the device using the device API on my server, should you save the 'address' and 'api_signer_address' in my (service side) database or in the mobile app?
    daan-ost
    @daan-ost
    And another: In the register device paragraph on this page https://dev.ost.com/platform/docs/guides/create_wallet/ the device_name and device_UUID is mentioned. I don't those fields/parameters in the register device API. How do you set the device_name?
    Rachin Kapoor
    @rachinkapoor
    Hi @daan-ost
    You should store at-least store device address on server-side as it is primary key of device entity.
    Rachin Kapoor
    @rachinkapoor

    We removed device_name & device_uuid from the Mobile SDK.

    However, for providing better UX, you can choose to capture and store them on YOUR server.

    If you do capture them, please make sure that your application’s GDPR complience is not violated.

    We shall update the documentation soon. Thanks for pointing it out

    Mario Jefferson
    @Orami

    quick question in building up the test sdk on this part of the instructions to build build a demo wallet where does this file go

    v). Adding SDK configuration file
    Create OstWalletSdk.plist file. This file has configuration attributes used by OstWalletSdk. You should copy paste the configuration values from below snippet.

    does it go into xcode as a snipet or am i making a plist file to go in a folder somewhere.
    im sure its me i just need to be clear

    Ankit Yadav
    @ankit-yadv
    Hi @Orami, You need to create a OstWalletSdk.plist file in main bundle of your application.
    Mario Jefferson
    @Orami
    in the same location of the OstWalletSdk.framework files ?
    or the same location of the cartfile?
    Ankit Yadav
    @ankit-yadv
    Hi @Orami, you need to create the file in root folder of your application in xcode.
    CryptoNoob
    @CryptoNoob2020_twitter
    Hey! I wish to find out how stable coin staking will work for minting BTs.
    Will I be able to stake the chosen stable coin directly on OST platform via metamask, just how I can with OST?
    Or will I need to have the equivalent $ worth in OST tokens?
    Benjamin Bollen
    @benjaminbollen
    The specifics which OST platform will support are still being worked on, ie. which stablecoins we ll support; but when staking with stablecoins, you have to come with the supported stable coin directly
    OST remains the underlying token to run transactions on the sidechains - that doesnt change
    CryptoNoob
    @CryptoNoob2020_twitter
    Thanks @benjaminbollen
    ldumaine
    @ldumaine
    Hi @benjaminbollen .. What stable(s) coin(s) will be supported ? USDT ?
    alanroza4
    @alanroza4
    So just to clarify we dont have to start by purchasing OST and then the OST company will acquire stable coins for us to stake. Approved stable/other tokens can be directly staked.
    Benjamin Bollen
    @benjaminbollen
    We ll make announcements when we re closer to launching the new feature
    @alanroza4 correct, OST.com will not exchange your tokens. All contracts are built non-custodially. It’s always your money in your contracts; OST just provides the technology
    So to stake OST, you have to have OST; to stake stable coin, you’ll have to have stable coin
    and, to deploy your own custom contracts and execute transactions on the sidechains you have to have OST to pay gas fees