03:23 <stellar-slack> <meetreks> sacarlson

03:23 <stellar-slack> <meetreks> Hi

03:23 <stellar-slack> <meetreks> I tried static_path_find

03:24 <stellar-slack> <meetreks> following are the info

03:24 <stellar-slack> <meetreks> issuer_account = "gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE" From Account = set_account("gBuYT5AQpjw1mEiDBJNJshtV3GyV5A2UKA") Destination Account = stellar.set_destination("gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE")

03:24 <stellar-slack> <meetreks> so the result I got was

03:24 <sacarlson> I also wrote a test for static_path_find and published it

03:24 <stellar-slack> <meetreks> source to send 1.4444444 to receive 1

03:25 <sacarlson> ya that sounds correct

03:25 <sacarlson> so that's the price you get with that volume of an order that's on the books

03:26 <sacarlson> oh your destination account is the issuer

03:26 <sacarlson> normaly you send it to someone

03:26 <stellar-slack> <meetreks> yes

03:26 <sacarlson> or maybe I don't understand the destination value

03:27 <stellar-slack> <meetreks> before that

03:27 <stellar-slack> <meetreks> one simple querry

03:27 <sacarlson> I don't see the amount value

03:28 <stellar-slack> <meetreks> can you run this?

03:28 <stellar-slack> <meetreks> !/usr/bin/ruby require 'yaml' require './class_payment' issuer_account = "gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE" stellar = Payment.new # my test account gHVS... that has trust and ballances on issuer gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE # in static_path_find account is used for source_account stellar.set_account("gBuYT5AQpjw1mEiDBJNJshtV3GyV5A2UKA") #gBuY... is meetreks users account we will play w

03:28 <stellar-slack> trust from issuer gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE # and will use it as our destination address here stellar.set_destination("gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE") stellar.set_issuer(issuer_account) stellar.set_currency("USD") stellar.set_value(1) results = stellar.static_path_find puts "#{results}"

03:28 <stellar-slack> <meetreks> I just checked your source

03:29 <sacarlson> what is that?

03:29 <stellar-slack> <meetreks> can you execute and see if you are getting an exchange value?

03:29 <sacarlson> I should see the same thing as you

03:30 <stellar-slack> <meetreks> yes

03:31 <sacarlson> did you see this https://github.com/sacarlson/pokerth_accounting/blob/master/static_path_find.rb

03:31 <sacarlson> {"result"=>{"alternatives"=>[{"paths_computed"=>[[{"account"=>"gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE", "type"=>1}]], "source_amount"=>{"currency"=>"USD", "issuer"=>"gHVS8kkZVfhUcbv11hpRVGMB7r8gEwhzKm", "value"=>"1"}}], "destination_account"=>"gBuYT5AQpjw1mEiDBJNJshtV3GyV5A2UKA", "destination_currencies"=>["GPB", "JPN", "USD", "AUS", "EUR", "CHP", "STR"], "status"=>"success"}}

03:31 <stellar-slack> <meetreks> Yes I did

03:32 <stellar-slack> <meetreks> but

03:32 <sacarlson> so I"m not sure how to read those results

03:32 <sacarlson> other than value 1

03:32 <stellar-slack> <meetreks> Can you try the one I sent

03:32 <stellar-slack> <meetreks> then we can discuss

03:32 <stellar-slack> <meetreks> please

03:33 <sacarlson> if I put in a large amount like 100000 as amount I get no results as there are no open orders for that ammount

03:33 <stellar-slack> <meetreks> Yes

03:33 <stellar-slack> <meetreks> thats correct

03:34 <sacarlson> again I don't think you want the destination to be the issuer or am I wrong?

03:34 <sacarlson> I don't know what values you want me to try

03:35 <sacarlson> but they should come out the same as yours

03:35 <sacarlson> it doen't require secreet to view the results

03:36 <stellar-slack> <meetreks> yes

03:36 <stellar-slack> <meetreks> no secret is required

03:39 <sacarlson> did you look at the book orders?

03:40 <sacarlson> did you setup any orders?

03:41 <sacarlson> {"result"=>{"ledger_current_index"=>1020514, "offers"=>[{"Account"=>"gBuYT5AQpjw1mEiDBJNJshtV3GyV5A2UKA", "Sequence"=>10, "TakerGets"=>{"currency"=>"EUR", "issuer"=>"gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE", "value"=>"100"}, "TakerPays"=>{"currency"=>"USD", "issuer"=>"gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE", "value"=>"140"}, "quality"=>"1.4"}], "status"=>"success"}}

03:42 <sacarlson> so this is the order you now have on the books

03:44 <sacarlson> {"result"=>{"ledger_current_index"=>1020514, "offers"=>[{"Account"=>"gHVS8kkZVfhUcbv11hpRVGMB7r8gEwhzKm", "Sequence"=>16, "TakerGets"=>{"currency"=>"USD", "issuer"=>"gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE", "value"=>"90"}, "TakerPays"=>{"currency"=>"EUR", "issuer"=>"gpHUkTY9c7qviqSbAkPMm5v9ZyTDho9GAE", "value"=>"130"}, "quality"=>"1.444444444444444"}, {"Account"=>"gHVS8kkZVfhUcbv11hpRVGMB7r8gEwhzKm", "Sequence"=>18, "TakerGets

03:44 <sacarlson> these are the orders I now have setup on my account

03:50 <sacarlson> so I guess all the static_path_find is telling us is there is liquidity for that order and at this time it only requires one account "gBuYT5AQpjw1mEiDBJNJshtV3GyV5A2UKA" it seems to get the price you have to look at the book offers from that account

03:57 <stellar-slack> <meetreks> Yes

03:57 <stellar-slack> <meetreks> thats what we are supposed to get

03:57 <stellar-slack> <meetreks> now

03:57 <stellar-slack> <meetreks> if we say

03:57 <stellar-slack> <meetreks> set up 6 orders

03:57 <stellar-slack> <meetreks> then I expect 6 paths to be returned

03:57 <stellar-slack> <meetreks> also

03:57 <sacarlson> ok setup 6 orders and find out

03:57 <stellar-slack> <meetreks> the orders can in in other currencies as well

03:58 <stellar-slack> <meetreks> for ex

03:58 <stellar-slack> <meetreks> A demands B

03:58 <sacarlson> yes the chain I explained before

03:58 <stellar-slack> <meetreks> Yes

04:00 <stellar-slack> <meetreks> will set up different orders and I will try again

04:07 <sacarlson> so A wants EUR to USD B wants USD to JPN C wants JPN to AUS D wants AUS to USD, I would assume that would create a chain event

04:07 <sacarlson> I guess to be simple you could just setup 1 to 1 trades for each

05:19 <sacarlson> meetreks seems our issuer account has run out of STR and I can't seem to refill it as I get this error tefDST_TAG_NEEDED" not sure what this is

05:20 <sacarlson> this didn't seem to help https://ripplelabs.atlassian.net/browse/RIPD-574

05:27 <sacarlson> "Destination tag required." is the error but I do have a destination address so not sure what it wants

06:01 <sacarlson> {"result"=>{"engine_result"=>"tefDST_TAG_NEEDED", "engine_result_code"=>-190, "engine_result_message"=>"Destination tag required.", "status"=>"success", "tx_blob"=>"12000022800000002400000001614000000039D1068068400000000000000A7320E19267EFE79689788EF51292E3313E6A7EE246AD78B3DB4D873026EECD310D29744017A493878E98CD7E842D7B9934B79A88C7115FA826A6E93DCD037030221F6945B87CADFFC0DE2E18E494E1474DA94A74DBD982E6D5C419F49242B6906E4B1B0

06:01 <sacarlson> no clue

12:39 <Kwelstr> sacarlson, a destination tag is different than an address, as in: a gateway can have one address and each of their customers will have a different destination tag to send funds into the gateway's address

12:41 <sacarlson> kwelstr I'm not sure how this tag got set and how it is that I can deposit STR into the account because of it

12:44 <sacarlson> as I am not the only human with this accounts number and secreet key, I have to assume one of the other holders may have changed the destination tag address making it imposible to deposit STR?

12:45 <sacarlson> is there a way to list these tag numbers?

12:47 <sacarlson> I would also like to add that I just tested my software on live.stellar.org and it's working there just the same as it has on test.stellar.org

12:47 <stellar-slack> <eno> you can deposit with a random DT IMO

12:48 <sacarlson> eno oh ok so how do I add this random tag? just add it to the address string?

12:49 <stellar-slack> <eno> There is a flag that if enabled the issuer can't receiving deposit without DT in ripple ,so maybe it's similar in stellard

12:50 <sacarlson> eno yes that sounds like a posibility but I haven't found the documents to correct it

12:52 <stellar-slack> <bartek> @sacarlson @eno you’re looking for this: https://www.stellar.org/api/#api-accountset SetFlag 1- Require Destination tag flag. This flag is a hint to the client that this account only wants transactions with a destination tag.

12:52 <sacarlson> bartek perfect that sounds like we have a solution then

12:54 <stellar-slack> <eno> yes you're the best @bartek

12:55 <sacarlson> bummer my ruby lib isn't setup to support this part of the api so I'll have to use curl

12:57 <sacarlson> so this looks like the flag that can also be used to freeze accounts from the issuer I think

12:58 <sacarlson> I saw this feature was added on Ripple and I guess used to freeze the assets of someone

13:17 <sacarlson> I found the other solution worked to add a random number to destination tag in a payment transaction

13:17 <sacarlson> I don't know how the setting was changed but that works

15:59 <stellar-slack> <priyav_shah> Hey, was looking for some advice. I'm currently working on university project

16:00 <sacarlson> and? so what is the question? just ask

16:02 <stellar-slack> <priyav_shah> sorry ended up half typing up question and pressed enter, and then editted

16:05 <stellar-slack> <priyav_shah> Or would it be ok to use inactive stellar-lib and stellard?

16:05 <stellar-slack> <priyav_shah> just for 2 months, would ideally like to b eable to keep working on this after university anyways

16:05 <sacarlson> ??? or

16:07 <sacarlson> very cryptic

16:08 <stellar-slack> <scott> @priyav_shah: Given a 2 month timeline, I personally wouldn’t build your project on top of the new stellar core

16:09 <stellar-slack> <scott> Whether you choose ripple or the legacy stellard is up to you. either way significant work would be needed if you wanted to move to the new stellar system in the future

16:10 <sacarlson> <scott> how difficult would it be to port from old to new? can't we build a bridge lib

16:10 <stellar-slack> <naumenkogs> Do u have any idea about why I get 0 peers while connecting to core-testnet using Validators from https://www.stellar.org/galaxy/getting-started? I've waited for years and got "Lost consensus".

16:12 <stellar-slack> <jed> naumenkogs: testnet is on an old version. We are reving it to master shortly

16:14 <stellar-slack> <priyav_shah> @scott: yea that helps actually. makes me sad not to be using stellar, but guess can do so after :)

16:16 <stellar-slack> <jed> I'd build on stellar-core fwiw :)

16:17 <sacarlson> I guess focus is on the server side interface not on the api side for client side apps?

16:19 <stellar-slack> <priyav_shah> haha, I was thinking about it jed, but makes me a bit too nervous :scream_cat:

16:19 <stellar-slack> <eva> @priyav_shah: what's your project? :)

16:20 <stellar-slack> <scott> sacarlson: while the concepts are very similar between the old and the new, there’s enough difference that migration won’t be trivial.

16:21 <sacarlson> I have to assume they will have the basic features of the old but a superset, I haven't looked at differences other than different length account strings

16:22 <sacarlson> so a simple payment api bride must be posible

16:24 <stellar-slack> <priyav_shah> The idea is to try to find a way to allow for people without a bank account to be able to buy stuff online. I like the idea of stellar and issuances, because then people can also transfer money between themselves, or even abroad. Was gonna connect it up to paypal, so they would send money to me in stellar, and i'd set up a way to send money into paypal account that they had/have/gets created when they s

16:24 <stellar-slack> <priyav_shah> send money to me or gateway

16:24 <stellar-slack> <priyav_shah> my* gateway

16:28 <stellar-slack> <eva> that's an awesome concept, and very much in line with Stellar's ethos, IMO.

16:29 <stellar-slack> <eva> in terms of financial inclusion (economic access for the 2 billion unbanked people worldwide)

16:30 <stellar-slack> <priyav_shah> Thanks eva :)

16:31 <stellar-slack> <eva> :thumbsup::skin-tone-2: whatever you decide to use, I'm sure folks here would be happy to help if you run into snags :)

16:55 <stellar-slack> <jed> ok testnet is on the latest master

16:56 <stellar-slack> <jed> horizon is down till it gets updated to deal with the latest changes in stellar-core

16:57 <sacarlson> <jed> testnet seems to be still working

16:58 <sacarlson> still have my original accounts

17:11 <stellar-slack> <scott> it’s lying to you, and showing the old ledger. Horizon doesn’t yet have a system in place that detects when the stellar network has it’s history replaced from underneath, as it will only really happen during the lead up to launch.

17:20 <stellar-slack> <eno> i think sacarlson is talking about http://test.stellar.org|test.stellar.org

17:22 <stellar-slack> <naumenkogs> In this case what I should use instead of testnet? Do I have any possibility to connect to stellar network? Or I should just wait until the new version will be released?

17:24 <stellar-slack> <scott> Oh, i’m sorry. the legacy testnet on http://test.stellar.org|test.stellar.org is still running… I was referring to the stellar-core testnet that jed was referring to.

17:56 <stellar-slack> <jed> naumenkogs: you are trying to use the new network right?

18:29 <stellar-slack> <naumenkogs> I'm trying to launch stellar-core and connect to stellar-network via it (not stellard)

18:30 <stellar-slack> <jed> it should work now

18:30 <stellar-slack> <jed> is it not?

18:30 <stellar-slack> <naumenkogs> Let me check it

18:30 <stellar-slack> <naumenkogs> It didnt work 3 hours ago. Has something changed?

18:32 <stellar-slack> <naumenkogs> Maybe the mistake is in my config but I cant figure out where exactly so I wonder if the problem is in testnet or validator address or my config

18:32 <stellar-slack> <jed> yeah I moved the testnet to master

18:32 <stellar-slack> <jed> it should work now

18:32 <stellar-slack> <jed> it was out of date when you tried before

18:33 <stellar-slack> <naumenkogs> I'll check it in 5 mins

18:37 <stellar-slack> <naumenkogs> Everything seems to be fine except one warn

18:37 <stellar-slack> <naumenkogs> [History] WARN failed to get history/00/00/05/history-000005bf.json from history archive 'vs'

18:38 <stellar-slack> <naumenkogs> But thank you anyway. Does it mean anytime I need to launch stellar-core I should ask you to move testnet to master?

18:49 <stellar-slack> <naumenkogs> Or maybe give me a link how to launch non-test version if it is possible.

19:01 <stellar-slack> <jed> no in general you should always be able to connect. We just had some protocol churn that never made it onto the testnet until today