smartstellar

What's your plan to deal with failed transactions?

It seems like there are so many ways this can fail, especially with surge pricing, and the network downtime we have experienced just this week.

    tallship- Hi, thanks for voting for our project. Yes,, as dzham writes, for this round only accounts created in March 2019 or earlier are counted. You can vote for the next round. If you have feedback on our project or have suggestions let us know :-) This will help us to know more about the requirements/usecases and further improve our product.

    dzham Hi, thanks for your feedback. You are addressing two important points

    Failed Transactions

    We implemented a retry process, so even downtimes of over an hour as we had this week can be handeled. In the worst case, if a transaction could't be submitted, you will see that on our monitoring page. See a screenshot below. For a first hand experience you also can signin on our web wallet with a testaccount: https://blueorion.cc/testaccount

    Surge Pricing/Volatility

    This is true for XLM and all non-stable tokens.

    • We still see a range of usecases with stable tokens. E.g. tokens from stronghold can enable an easy way to payout US$-Tokens worldwide with minimal costs.
    • and also with utility tokens which are purly used for internal company purposes a timed payment model can be useful.

    If anybody has more use cases let us know or also join our open meeting every month to see in detail how we work. You can contact us via contact[at]blueorionDOTcc.

    View Payment Schedules

      bkolobara changed the title to Timed Transactions API - Schedule payments on the Stellar network! .

      Hi all,

      as I mentioned above, we have monthly open meetings. The next one is next Thursday, on 30th of May. Everybody who has interest in our activities is welcome.

      Send me a note at contact[at]blueorionDOTcc to get the conferencelink. Looking forward to have you in the call.

      International Times are:
      20:30 IST (New Dehli, India)
      17:00 CEST (Munich / Europe)
      11:00 EDT (New York, USA)
      08:00 PDT (Los Angeles, USA)

      7 days later

      Hi all,

      thanks to everybody who joined our meeting yesterday. We agreed to proceed with promoting the project within the Stellar Community and also will provide specific slides.

      Thanks for the community news from Mexico, Malta and Chicago. It was also good to hear more projects are moving towards Stellar.

      As always, if there are questions on the project or want to join the team let us know.

      smartstellar

      The problem with failed transactions is that they may fail and still get included in a ledger, thereby consuming a sequence number. Now you can't retry it in a simple way without re-signing that one, and all the consecutive transactions you've set up for scheduling.

        dzham Yes, we ran into that with our first version. We now found a solution for that without having to resign all following transactions. You can check that with any stellar account and create a schedule or use our testaccount on: https://blueorion.cc/testaccount.

        See also a sample screenshot below.

        I know you developed the stargazer wallet. I already installed it a while ago.
        Are you possibly interested on a cooperation and implement our future API with your wallet?

        View Payment Schedules

          4 days later

          smartstellar Is this open source? I saw your Reddit post which said it was but then theres no mention here or your site and I couldn't find the source to check out

            tmacshaq Hi, no our service platform is not open source. If you have more detailed questions you can contact us via blueorion.cc. We are currently also running a test program, if you are intersted.

            smartstellar Are you possibly interested on a cooperation and implement our future API with your wallet?

            I think it would be more useful for me to implement support for SEP-0007, or at least parts of it, and go that route instead of a direct integration. Integrations with new APIs are always tricky, since it increases the number of external dependencies you have, and the amount of maintenance you're exposed to.

              dzham I also guess its good to start with SEP-0007.

              With that our users could sign transactions using your wallet. If you want to integrate our timed payments in your wallet you also need to transfer data to us. This would be another step.

              Hi all,

              we are announcing our next monthly meeting on Thursday, 27th of June. Everybody who has interest in our activities is welcome. Send me a note at contact[at]blueorionDOTcc to get the conferencelink. Looking forward to have you in the call.

              International Times are:
              19:30 IST (New Dehli, India)
              16:00 CEST (Munich / Europe)
              10:00 EDT (New York, USA)
              07:00 PDT (Los Angeles, USA)

              Hi all, just an update on the ongoing work. Currently we are doing some Beta tests on the MultiSend module. You find a more detailed testing description on our subreddit account: Multisend Testing

              If I have a subscription service can I have Stellar users subscribe and the payment will be sent automatically every month?

                deylandra We are working on a subscription solution. Yes, the payment will be sent automatically every month.

                Could you please explain to me about connecting with another wallet just for an example with satoshipay wallet (micropayment) ?

                  bostravel Hi BOSTRAVEL, a wallet like SatoshiPay, for example, could use our Timed Transactions feature (and API when it becomes available) to sell digital content on a recurring basis. The entire flow is non-custodial on Blue Orion's part, so we never handle secret keys. Once integrated, instead of a consumer paying every time they want content, they could subscribe to a monthly magazine, or to an annual newspaper subscription. The future payments would automatically be billed. And if the consumer wallet were empty, the access could be restricted again. This could also be used for Software as a service subscriptions.

                    carriere

                    The limitation is still that any payment going out of an account needs to be signed for -> all your subscription payments have to be signed in advance -> you can't really keep it going forever