sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
[7] has quit [Disconnected by services]
TheSeven has joined #stellar-dev
<stellar-slack>
<buhrmi> morning
<stellar-slack>
<sacarlson> yo yo
<stellar-slack>
<sacarlson> I just published my updated stellar_utility that is now setup to be able to send to horizon (but fails to do so) https://github.com/sacarlson/stellar_utility
<stellar-slack>
<sacarlson> as noted above I've tried both hex and base64 so maybe the problem is in the documented method to interface to horizon
<stellar-slack>
<sacarlson> or horizon interface is broken. so now it's time maybe to try the js-lib to see if it works?
<stellar-slack>
<buhrmi> sacarlson i just made a tx to your account GAJYPMJOWAAGCXMB7UYP63LIMTYPXMGIBMYGQRW7QBF5AVSO7S3IRKIP
<stellar-slack>
<buhrmi> using master jslib and master stellar-base
<stellar-slack>
<sacarlson> cool so I assume it works? I'll check my account
<stellar-slack>
<buhrmi> yeah i checked your account, seems to work :)
<stellar-slack>
<buhrmi> wonder if i can send you sausage-assets
<stellar-slack>
<sacarlson> no not until I setup my account to trust yours
<stellar-slack>
<buhrmi> right
<stellar-slack>
<buhrmi> we need an easy UI for that
<stellar-slack>
<sacarlson> but we should now document all the commits at this point that this is the most stable branch at this point
<stellar-slack>
<sacarlson> yes maybe next step start working on user interface
<stellar-slack>
<buhrmi> yeah ... i hope they keep the 4 main repos (stellar-core (master), horizon (master), jslib (master), jsbase (master)) compatible with each other from now on...
<stellar-slack>
<sacarlson> we also need some kind of matrix that shows what all tests have been performed between each set of code I would think
<stellar-slack>
<buhrmi> nah don't think that's required
<stellar-slack>
<sacarlson> we haven't tested multi sign yet
<stellar-slack>
<sacarlson> that's about the only part left that I know of that I haven't seen work
<stellar-slack>
<buhrmi> i think i gonna try to work on a simple UI today evening
<stellar-slack>
<sacarlson> cool
<stellar-slack>
<sacarlson> can you send us the commit codes of js-base and js-lib you just used?
<stellar-slack>
<sacarlson> for js-stellar-base I show present master at 17328b04687cdf35f5132443d04b3e5c13399d87
<stellar-slack>
<sacarlson> for js-stellar-lib I show at present master at 4042b169b24c83f25f822a63f3846d5bfaeb88b6
<stellar-slack>
<buhrmi> that's the ones
<stellar-slack>
<sacarlson> ok
<stellar-slack>
<sacarlson> so now I have a list of all the parts that work together at least with native tx
<stellar-slack>
<buhrmi> so in order to establish trust the private seed is somehow required
<stellar-slack>
<buhrmi> don't know how to build that into the UI ... prompt for it?
<stellar-slack>
<sacarlson> ya I guess gray it out if not needed?
<stellar-slack>
<sacarlson> for a trustline from me to you only my secrete key is needed
<stellar-slack>
<buhrmi> yeah
<stellar-slack>
<sacarlson> but then your secret key is needed for you to issue me the asset
<stellar-slack>
<sacarlson> you might look at the ripple site that has an interface already setup I think
<stellar-slack>
<sacarlson> maybe I'm wrong on that?
<stellar-slack>
<buhrmi> let's see
<stellar-slack>
<buhrmi> well they have a nice office
<stellar-slack>
<sacarlson> I have an account on ripple maybe you might need that to look at the interface?
<stellar-slack>
<buhrmi> i can't find anything useful on ripple's site
<stellar-slack>
<buhrmi> ah, it's http://rippletrade.com|rippletrade.com ... so they give u the option to let them store your secret key for u
<stellar-slack>
<buhrmi> yeah i wanna do something similar
<stellar-slack>
<buhrmi> just have it based on stellar-core/open-core
<stellar-slack>
<sacarlson> ya I'm looking at the interface now they just have a botton called "add gateway" that provides you with a page asking for needed info to add trustlines
<stellar-slack>
<buhrmi> that's dumb
<stellar-slack>
<sacarlson> why?
<stellar-slack>
<sacarlson> that's what trustlines are in most cases I guess is a gateway to assets
<stellar-slack>
<buhrmi> well as @jed said a few days ago, gateways are just a business concept
<stellar-slack>
<buhrmi> not really needed
<stellar-slack>
<buhrmi> LOOOL in order to use rippletrade u have to have a mobile phone for identification and provide full name and address LOOL
<stellar-slack>
<buhrmi> fuck those guys
<stellar-slack>
<buhrmi> "in order to activate your wallet, .... [blablabla] GIEF US MONEY"
<stellar-slack>
<sacarlson> yes that's why I opted for stellar, they are way too tight now on ripple
<stellar-slack>
<sacarlson> but I like there interface
<stellar-slack>
<sacarlson> graphs of any trade you want like a real exchange
<stellar-slack>
<buhrmi> no thank you
<stellar-slack>
<sacarlson> and yes gateway is just another name they have for trustlines that can be just people not just banks or institutions
<stellar-slack>
<sacarlson> but if you want screen shots I have them for you to look at
<stellar-slack>
<matschaffer> @buhrmi: I'm sure you haven't seen the doc yet, but comments like "fuck those guys" are probably not in the spirit of https://www.stellar.org/community-guidelines/
<stellar-slack>
<sacarlson> oh ya edit that out
<stellar-slack>
<buhrmi> let me retract the comment
<stellar-slack>
<buhrmi> *retracts comment*
<stellar-slack>
<matschaffer> thanks. Let's try to keep this a welcoming space, even to rippletrade
<stellar-slack>
<buhrmi> sry :O
<stellar-slack>
<buhrmi> sacarlson u got XRP ?
<stellar-slack>
<sacarlson> yes I have a few
<stellar-slack>
<buhrmi> can u send a few to my acc? (buhrmi)
<stellar-slack>
<sacarlson> I only have 30 xrp just enuf to keep my account open
<stellar-slack>
<buhrmi> ah, okay
<stellar-slack>
<sacarlson> sorry I very poor
<stellar-slack>
<sacarlson> I think I had to spend $3 usd to get it
<stellar-slack>
<buhrmi> yeah it's okay just wanted to look at how they do the UI/UX without putting money in or giving anyone banking info
<stellar-slack>
<sacarlson> I can send you the screen shots of every page, I'll post them to you pm
<stellar-slack>
<buhrmi> nah, it's fine
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<sacarlson> too late already done
<stellar-slack>
<sacarlson> it has no key info in them
<stellar-slack>
<buhrmi> got them
<stellar-slack>
<sacarlson> I'm adding a few more shots
<stellar-slack>
<buhrmi> lol it's okay i don't need them lol
<stellar-slack>
<buhrmi> what i wanna do is fundamentally different
<stellar-slack>
<sacarlson> well other people may want them so I'm trying to collect them all
<stellar-slack>
<sacarlson> put that $3 investment to good use ha ha
de_henne has joined #stellar-dev
<stellar-slack>
<buhrmi> stellar-core & horizon already support creation of trustlines?
<stellar-slack>
<buhrmi> can't find docs for an endpoint on horizon
<stellar-slack>
<sacarlson> it requires a transaction to setup a trustline
<stellar-slack>
<buhrmi> ah, i see
<stellar-slack>
<sacarlson> my code has examples of how to set it up
<stellar-slack>
<sacarlson> in ruby
<stellar-slack>
<buhrmi> cool can i look at it?
<stellar-slack>
<buhrmi> so, creation of trustlines require native currency fee, huh?
<stellar-slack>
<buhrmi> whoa what's axios and bluebird
<stellar-slack>
<sacarlson> this looks to be the line I was looking for submitTransaction(transaction) { var promise = http://axios.post|axios.post(URI(this.serverURL).path('transactions').toString(), { tx: transaction.toEnvelope().toXDR().toString("base64")
<stellar-slack>
<sacarlson> in that I found I was missing "transactions" but when I add this to my code now I just get error 500
<stellar-slack>
<sacarlson> I'm guessing my problem is on or near this line in my code response = http://RestClient.post|RestClient.post @configs["url_horizon"]+"/transactions", values, headers
<stellar-slack>
<sacarlson> I thought it was changed to base64 but I could try it
<stellar-slack>
<sacarlson> as from the working code in js-stellar-lib shows it sends transaction in base64
<stellar-slack>
<buhrmi> so, in theory, when using the jslib to build a transaction, i should be able to feed that transaction blob directly to stellar-core, without going through horizon
<stellar-slack>
<buhrmi> via HTTP
<stellar-slack>
<sacarlson> I would guess you would use js-stellar-base to get a tx blob that you could send direct to stellar-core
<stellar-slack>
<buhrmi> yeah
<stellar-slack>
<sacarlson> I've tried several trail and error methods but can't find a solution. I guess I need to see what the server is seeing as the error I'm creating
<stellar-slack>
<sacarlson> any posibility of that matschaffer?
<stellar-slack>
<sacarlson> @matschaffer:
<stellar-slack>
<sacarlson> or point it at @fredolafritte horizion server and see what he see's in the error I create
<stellar-slack>
<sacarlson> other option is I setup the same horizion and point it at myself
<stellar-slack>
<buhrmi> maybe don't even need horizon ...
<stellar-slack>
<sacarlson> I already have that working without horizon, that I have tested already as working
<stellar-slack>
<sacarlson> but not with the presently known version now running on horizon so that's another step I could try and need to do anyway
edubai_ has quit [Quit: Connection closed for inactivity]
<stellar-slack>
<buhrmi> trying to send tx to stellar-core via HTTP i get { data: { exception: 'bad value of type in _body_t' },
<stellar-slack>
<buhrmi> hmmm...
<stellar-slack>
<sacarlson> to your localy running core?
<stellar-slack>
<buhrmi> yeah
<stellar-slack>
<fredolafritte> right now, the only way to make it work is to have everything built locally: js-stellar-base, horizon, go-horizon and stellar-core
<stellar-slack>
<buhrmi> @fredolafritte: shouldn't it be possible to skip horizon and go directly js-stellar-base -> core?
<stellar-slack>
<buhrmi> isn't the base64 encoded transaction the same?
<stellar-slack>
<sacarlson> fredolafritte: maybe you missed it that buhrmi was able to do a native transaction with all stellar code erlier today
<stellar-slack>
<fredolafritte> sending a transaction is not enough, you would need to check the state of the transaction to find out if it succeeds or not
<stellar-slack>
<fredolafritte> getting the list of transactions is the job of horizon, not stellar-core
<stellar-slack>
<sacarlson> buhrmi: you also need to get the nextsequence transaction number that my code does in two ways depending on weather it does the transaction from horizon or local
<stellar-slack>
<buhrmi> but *in theory*, posting a tx blob to [horizon]/transactions or [stellar-core]/tx?blob= should be the same, right?
<stellar-slack>
<sacarlson> in local I look direct at the stellar-core database file and find the sequence for the account needed
<stellar-slack>
<sacarlson> they aren't the same in my case as I run standalone nothing in the database is the same
<stellar-slack>
<buhrmi> i mean the format of the base64 is the same, now?
<stellar-slack>
<sacarlson> yes but if you were running from a node that was in sync they should be able to use the same blob
<stellar-slack>
<buhrmi> right
<stellar-slack>
<sacarlson> I think so yes I use base64 with success in my direct stellar-core transactions
<stellar-slack>
<sacarlson> there just seems to be no reason they would have to change that
<stellar-slack>
<sacarlson> ok I've already checked out stellar-core version b179493a328955f8927d367c712bf0dd7341f3e7 that I will setup and check to see if it works for me
<stellar-slack>
<sacarlson> seems to take as long to compile this as a new kernel
<stellar-slack>
<buhrmi> can u send me an example blob that you were able to successfully send to your local core?
<stellar-slack>
<sacarlson> I can send you a failed blob of what I last tried to send to horizon
<stellar-slack>
<buhrmi> for example, if i post the following to horizon on testnet, it behaves fine ... but if i send it to stellar-core/tx?blob= it errors out
<stellar-slack>
<sacarlson> is your stellar-core in sync?
<stellar-slack>
<buhrmi> no idea
<stellar-slack>
<sacarlson> look at the output at the term you should intermitently see the word sync
<stellar-slack>
<sacarlson> or you used to
<stellar-slack>
<sacarlson> at the term running your core
<stellar-slack>
<sacarlson> with the old stellard I ran all night and still never got in sync
<stellar-slack>
<sacarlson> but I think that was due to not enuf mem?
<stellar-slack>
<matschaffer> the /info endpoint shows sync status too
<stellar-slack>
<matschaffer> That ledger age is in seconds
<stellar-slack>
<sacarlson> so state is joining at some point I guess it will be synced
<stellar-slack>
<sacarlson> how long has it been running?
<stellar-slack>
<matschaffer> The logs will have some info about what's up. More if you use the /ll endpoint to set debug log level (or set it via the config)
<stellar-slack>
<matschaffer> With an age that old it probably failed very early on in the process
<stellar-slack>
<matschaffer> If it's working the logs will show ETA
<stellar-slack>
<matschaffer> Should only take ~5 min or so I think. Probably bandwidth depending
<stellar-slack>
<sacarlson> with 5min maybe for you that's due to being hooked to the few running nodes over lan that runs at 100meg/s or 1G/s
<stellar-slack>
<sacarlson> oh and my stellar-core compile completed
<stellar-slack>
<buhrmi> how do i "tell" my local stellar core to sync?
<stellar-slack>
<buhrmi> should it do it automatically?
<stellar-slack>
<sacarlson> yes in theory in time if configured correctly it should sync
<stellar-slack>
<sacarlson> I think in that "state": "Joining SCP" it should be seen
<stellar-slack>
<sacarlson> instead of joining
<stellar-slack>
<sacarlson> when I get my new one up and running in a bit I'll verify, but at first I will run standalone. with that it syncs in secounds
<stellar-slack>
<sacarlson> you might also try standalone to verify yourself
<stellar-slack>
<buhrmi> maybe i should try different config file
<stellar-slack>
<buhrmi> ah, there we go... my config was bad
<stellar-slack>
<sacarlson> there ya go
<stellar-slack>
<buhrmi> now i always get
<stellar-slack>
<buhrmi> 2015-08-24T09:55:26.099 e27586 [] [Ledger] INFO Out-of-order close during catchup, buffered to 350405 but network closed 350421 2015-08-24T09:55:26.099 e27586 [] [Ledger] WARN this round of catchup will fail.
<stellar-slack>
<sacarlson> I'm not sure you did the reset stuf
<stellar-slack>
<sacarlson> I have scripts to do reset and startup I should share with you
<stellar-slack>
<sacarlson> I'm presently rewriting them
<stellar-slack>
<sacarlson> not sure these are still needed with newer builds or not
<stellar-slack>
<sacarlson> a copy of these will be kept in my stellar_utilities package
<stellar-slack>
<buhrmi> are we still going to the moon?
<stellar-slack>
<sacarlson> ??
<stellar-slack>
<sacarlson> ya I'm about to blast off man
<stellar-slack>
<buhrmi> 15-08-24T10:06:29.159 936689 [] [Ledger] INFO Out-of-order close during catchup, buffered to 350595 but network closed 350609 2015-08-24T10:06:29.159 936689 [] [Ledger] WARN this round of catchup will fail.
<stellar-slack>
<buhrmi> the "buffered to XXXX' number doesn't increase :O
<stellar-slack>
<sacarlson> is this with running my reset script?
<stellar-slack>
<buhrmi> partly ... i dont wanna run standalone
<stellar-slack>
<sacarlson> you can try run standalone for 20 secounds and see if it works or not and go back to try to sync
<stellar-slack>
<sacarlson> but no need I'll be running standalone in about 2 min
<stellar-slack>
<sacarlson> just have to see about a new config file
<stellar-slack>
<sacarlson> FATAL Got an exception: invalid quorum set
<stellar-slack>
<sacarlson> my old config is no good
<stellar-slack>
<buhrmi> gonna leave a core node with public HTTP for now
<stellar-slack>
<buhrmi> in sync with testnet
<stellar-slack>
<sacarlson> so you have 2 clouds running now then?
sacarlson has quit [Ping timeout: 246 seconds]
<stellar-slack>
<matschaffer> buhrmi: have you tested port level access from the local one?
<stellar-slack>
<sacarlson> port level? is that were I did the transactions? if so then yes
<stellar-slack>
<sacarlson> oh not me
<stellar-slack>
<matschaffer> buhrmi said "my core hosted in the cloud is syncing .... my local one doesn't" - curious if the local one can actually access http://core-testnet1.stellar.org:(whatever-the-new-peer-port-is)|core-testnet1.stellar.org:(whatever-the-new-peer-port-is) and http://s3-eu-west-1.amazonaws.com:443|s3-eu-west-1.amazonaws.com:443
<stellar-slack>
<matschaffer> I know virtualbox for example makes it really easy to make a VM with limited internet access
<stellar-slack>
<matschaffer> was sort of the default a few years ago
<stellar-slack>
<sacarlson> well if what I looked at was his only cloud then it's not in sync it's in "state" : "Catching up"
<stellar-slack>
<matschaffer> that's good though
<stellar-slack>
<matschaffer> means it's actually moving
<stellar-slack>
<matschaffer> an ETA in the logs is promising too
<stellar-slack>
<matschaffer> especially if it's going down
<stellar-slack>
<matschaffer> buhrmi: oh btw, watch out having that http port open. There are some commands that you don't really want other people hitting
<stellar-slack>
<sacarlson> mine seemed to sync very fast less than 5 min
<stellar-slack>
<sacarlson> in fact it was like less than 2 min
<stellar-slack>
<matschaffer> generateload for example
<stellar-slack>
<matschaffer> I'm sure it varies. when restarting testnet I had a tendency to see ~300s
<stellar-slack>
<sacarlson> well that's not long
<stellar-slack>
<matschaffer> nah, not bad
<stellar-slack>
<sacarlson> but I assume with an older buzy network things will change
<stellar-slack>
<matschaffer> or an underpowered VM
<stellar-slack>
<matschaffer> catch up was pretty I/O heavy last I looked
<stellar-slack>
<sacarlson> I wasn't looking at top when I started, it's very low on resouces now
sacarlson has joined #stellar-dev
<stellar-slack>
<matschaffer> fwiw, my rebuild here is syncing fine now
<stellar-slack>
<matschaffer> just on my mac
<stellar-slack>
<buhrmi> it's synced :P
<stellar-slack>
<matschaffer> just ran ``` > ./src/stellar-core --conf docs/stellar-core_testnet.cfg --newdb > ./src/stellar-core --conf docs/stellar-core_testnet.cfg ```
<stellar-slack>
<matschaffer> my guess is that'll fail if you followed the same process there
<stellar-slack>
<matschaffer> why would be a networking question (vm selinux or fw rules, vm network, host network, lan, etc.)
<stellar-slack>
<buhrmi> finally this works 'http://open-core.org/tx?blob=';+encodeURIComponent(transaction.toEnvelope().toXDR().toString("base64"))
<stellar-slack>
<buhrmi> sick encoding chain
<stellar-slack>
<matschaffer> You saw my note about generateload right?
<stellar-slack>
<buhrmi> would generateload propagate to the entire testnet ?
<stellar-slack>
<matschaffer> Not sure. Hopefully not :)
<stellar-slack>
<buhrmi> yeah i don't really care about load on that instance, can restart it easily
<stellar-slack>
<matschaffer> Try it and see, SF should be awake soon :-p
<stellar-slack>
<buhrmi> haha, nah
<stellar-slack>
<matschaffer> Thx ;)
<stellar-slack>
<buhrmi> so.. uhm ... in order for horizon to show account info ... what is it accessing? ledger SQL?
<stellar-slack>
<buhrmi> what's that
<stellar-slack>
<buhrmi> ah, it's just a whatever-database ... postgres or sqlite
<stellar-slack>
<sacarlson> ya that's what my code does. it just gets info from sqlite
<stellar-slack>
<buhrmi> k... wanna built my infrastructure without depending on horizon
<stellar-slack>
<sacarlson> main missing thing is the sequence number that I didn't see a way to get it from the port interface on stellar-core
<stellar-slack>
<buhrmi> that's probably stored in the database, no?
<stellar-slack>
<sacarlson> seems like a minimal horizon like interface would only need to provide you a way to lookup the sequence number, do the rest from the stellar-core
<stellar-slack>
<sacarlson> yes it's in the sqlite database
<stellar-slack>
<buhrmi> anyway, gonna throw this one into the public testnet pool for now http://open-core.org ... main difference being the HTTP ports being open for submitting transactions without horizon. but want to bootstrap my own disjointed network later so keep that in mind ^^
<stellar-slack>
<sacarlson> why not just add a way to lookup the sequencenumber with the stellar-core code? ore maybe it's there and I just can't find it
<stellar-slack>
<buhrmi> but ... for testing .. i guess it's fine
<stellar-slack>
<buhrmi> heading home
<stellar-slack>
<buhrmi> yeah maybe it could be possible to add sequence number to /info
<stellar-slack>
<sacarlson> but yours is synced with testnet? if so then they can just get the sequence code from there and send transaction to yours
<stellar-slack>
<buhrmi> yes
<stellar-slack>
<sacarlson> ok it's been fun
<stellar-slack>
<buhrmi> can't wrap my head around this quorum stuff
<stellar-slack>
<sacarlson> that's above my paygrade
<stellar-slack>
<buhrmi> @matschaffer: the telnet stuff worked btw ...
gst has quit [Ping timeout: 246 seconds]
gst has joined #stellar-dev
gst has quit [Changing host]
gst has joined #stellar-dev
<stellar-slack>
<buhrmi> can somebody quickly explain what is stored in the buckets and what in the database?
<stellar-slack>
<buhrmi> oh man i just got the best domain for the core-based social network
<stellar-slack>
<buhrmi> can't believe it wasnt taken
<stellar-slack>
<eva> what's the domain? @buhrmi
<stellar-slack>
<eva> or is it a surprise? :)
<stellar-slack>
<buhrmi> gonna be surprise :P
<stellar-slack>
<eva> awesome, can't wait :)
de_henne has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
Vinnie_win_r has joined #stellar-dev
Vinnie_win has quit [Ping timeout: 250 seconds]
de_henne has quit [Remote host closed the connection]
DomKM has joined #stellar-dev
Vinnie_win has joined #stellar-dev
Vinnie_win_r has quit [Ping timeout: 250 seconds]
<stellar-slack>
<sacarlson> I'm making an attempt to install a local copy of horizon today
<stellar-slack>
<sacarlson> first problem rake db:create && rake db:migrate fe_sendauth: no password supplied . so I'm sure I can figure this one out but I thought I had it set to no password
samuelharden has quit [Read error: Connection reset by peer]