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 @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
    alanroza4
    @alanroza4
    What are the pros and cons to staking OST or a Stable coin
    Benjamin Bollen
    @benjaminbollen
    I wont comment on that here
    ldumaine
    @ldumaine
    Thank you @benjaminbollen
    alanroza4
    @alanroza4
    Makes sense thanks!
    Benjamin Bollen
    @benjaminbollen
    Mostly because it depends on your use-case, you can reach out to partners@ost.com and they ll happily listen and share insight
    godman84
    @godman84
    Hi @benjaminbollen - in the AMA earlier this year, the OST Company provided a different position on how a company would purchase stable coins. Are you confirming that the OST Company is now moving in a different direction and that companies that wish to launch a branded token economy, they can purchase ANY token and stake it? i.e. the OST Company is no longer the middle man...
    I quote from the AMA on Reddit "Under the OST company's implementation of OpenST, in which the OST company provides APIs, SDKs, SaaS dashboards, wallets, and a redemption platform on top of OpenST to its clients, the base (default) staking token will be the OST token. The OST company is going to accept software fees paid in the OST token for using its proprietary OST KIT software and for funding the stakes. If a OST client prefers to stake stablecoins, they will still pay the OST company in OST tokens first. All sidechain gas and Mosaic staking/validating will still always be paid in OST. We anticipate that the OST token will thus be used similar to BNB (Binance coin) in that respect."
    Jason Goldberg
    @betashop_twitter

    Hi, we've been working on making Brand Token setup minting and distributing as easy possible for OST Platform customers, including ways to make it risk free to get started with minimal investment. This involves both technology and business/financial decisions. We've also been gathering direct input and feedback from OST clients and prospects on various facets Brand Token minting. And, we've been developing token rules and logic to help aid this, to accomplish the needs and desires of real clients.

    As @benjaminbollen points out, we'll release specs when ready. And, OST will not be a custodial service.

    Jason Goldberg
    @betashop_twitter
    Friendly reminder that this is a developers forum and only development related questions will be answered here
    godman84
    @godman84
    Thanks Jason - have a great weekend
    daan-ost
    @daan-ost
    Hi in the demo IOS app, func login in CurrentUser.swift I see that you retrieve user_pin_salt (or passphrasePrefix) from the API. Why do you want todo that on login. You only need it as an active user when you like to recover your wallet? tnx Daan
    Daniel Pham
    @danielpham_gitlab
    Hi guys,
    What are txs under tab "Latest Transactions" on https://view.ost.com/?
    There are 4 tokens on mainnet, however those txs under "Latest Transactions" are unlikely belong to those 4?
    Willy
    @shenwilly
    Hi OST team, just read the latest update. Awesome stuffs :)
    the React Native SDK caught my interest. Is the team considered developing another SDK for Flutter?
    it's also a cross platform framework, backed by google and currently growing very fast
    Ankit Yadav
    @ankit-yadv

    Hi @daan-ost,
    Yes, you are correct. The passphrasePrefix must only be fetched when needed.
    The security guidelines are provided here:
    https://dev.ost.com/platform/docs/sdk/getting_started/security_guidelines/

    On a side note, all device-manager operations need user authentication.
    User is authenticated using biometric OR they can enter the active pin.
    As pin is never (and should never be) stored in it's raw form even in the application, we need need passphrasePrefix to regenerate the pin to key to authentication.

    In current state, the demo-app is only meant for testing the Sdk.

    Ankit Yadav
    @ankit-yadv
    Hi @danielpham_gitlab,
    Those transactions are related to price oracle contract. The conversion value between OST and USD needs to be updated in price oracle.
    Hi @shenwilly,
    We have flutter in our list but looking at our current partners, no one is using it so it's not on priority. If we get enough interest from partner companies for flutter then it would make a lot of sense to develop it.
    Daniel Pham
    @danielpham_gitlab
    @ankit-yadv Thank you
    daan-ost
    @daan-ost
    I am currently working on the ios app, and first using the demoapp OST provided to get things working .
    The signup of the user us done right now in the website (not the app). User on OST is created with an UUID and I have an API to retrieve the app_user_id and UUID in the IOS app.
    So in the the demoapp I don't use the signup but the login. After login the device is setup succesfully and also retrieves the passphrase from the website. But then a problem we have we don't understand. We get an error when activate the user (userActivate). No recovery address is set for this user, this address should be set during useractivation...".
    Seems like the demoapp thinks this is a user that is already activitated or what could this be?
    Can you help with this problem?
    Rachin Kapoor
    @rachinkapoor

    Hi @daan-ost ,
    Thanks for reporting the issue.
    I request you to kindly send us the parameters of OstWalletSdk.activateUser method.

    In general, this error signifies that the device failed to create a recovery key based on given inputs.
    The recovery key is never stored anywhere and only created when needed.
    To create recovery key, we use:
    userPin - from user
    passphrasePrefix - this should come from your server (associated with the user and must not change/rotate)
    SCrypt salt - This is provided by Ost Platform

    daan-ost
    @daan-ost
    @rachinkapoor user id -->af648400-96cc-47dd-be34-426e937ddcf3
    userPin -->123456
    passphrasePrefix -->"comfort parade license deer differ please pudding gesture swap clock inspire something else"
    spendingLimit -->1000000000000000000000000
    expireAfterInSec -->1209600.0
    POB
    daan-ost
    @daan-ost
    @daan-ost POB coin on sandbox
    daan-ost
    @daan-ost
    @rachinkapoor We tried the signup today. Same result, device is registered successfully, but activateUser fails on the recovery address creation . Please help, we are stuck for now...
    Owais Vaiyani
    @OsVaiyani_twitter
    is there plan to release C# SDK
    Ankit Yadav
    @ankit-yadv

    Hi @OsVaiyani_twitter,

    We don't have any plans to launch C# SDK in near future.

    daan-ost
    @daan-ost
    Hi Guys, the IOS demo app does not have an example to show the token balance of the loggedin user . Can you provide some example code? Tnx Daan
    Ankit Yadav
    @ankit-yadv

    Hi @daan-ost,

    We have added balance API in version 2.2.0, more detail here: https://github.com/ostdotcom/ost-wallet-sdk-ios#user-balance

    daan-ost
    @daan-ost
    @ankit-yadv Tnx, my developer is looking for an example in the demo-app for iOS. Do you have that already?
    Shinto2000
    @Shinto2000_twitter

    Hello, i'm using the key/secret directly from my platform.ost.com but am getting the following error. Expired API key & secret?

    $ node test.js
    {"success":false,"err":{"code":"UNAUTHORIZED","msg":"Access denied due to using expired API key and secret. You can check the active API Key and secret on developer's page in OST Platform.","error_data":[{"parameter":"api_key","msg":"The API Key is not entered correctly. Please inspect for what is being sent, verify it against the API KEY shown on developer's page in OST Platform and re-submit."}],"internal_id":"scm_ac_1"}}

    $ npm --version
    6.9.0

    Shinto2000
    @Shinto2000_twitter
    const ostObj = new OSTSDK({
    "apiKey": 'caae229c48a515dc5368acb1b3e2cddf',
    "apiSecret": ‘xxxxx’,
    "apiEndpoint": "https://api.ost.com/mainnet/v2/",
    "config": {"timeout": 15}
    });