slippy has quit [Ping timeout: 246 seconds]
graydon has quit [Quit: Leaving.]
<stellar-slack> <meetreks> @scott: will do as suggested. Will run it past you before I post it in git
DomKM has quit [Quit: Connection closed for inactivity]
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> <sacarlson> what is the RUN_STANDALONE=true mode suposed to do? when I tried setting it to true on commit 69ec10e5aa0da004d8f3f047f0dcfb60ddb2c107, I note that stellar-core no longer listens on any ports. So I put it back to RUN_STANDALONE=false to get it to listen again.
<stellar-slack> <jed> it wont listen on the peer port
<stellar-slack> <jed> should still on the http port
<stellar-slack> <sacarlson> it shuts both down
<stellar-slack> <sacarlson> so I guess that's why we were setting THRESHOLD=1 was that was the only working way at present to run a standalone system
<stellar-slack> <jed> yeah it looks like it is blocking it. I made an issue
<stellar-slack> <jed> but I want to check with people before fixing it
<stellar-slack> <sacarlson> cool thanks
cagedwisdom has joined #stellar-dev
<stellar-slack> <sacarlson> is there a utility in stellarbase to decode a txbody to a json string? so I can decode this: AAAAALMgie+jwmYSUlBzCsqNJnJSx38YyZ3XTKMoCVhuZLr2AAAACgAABpYAAAARAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAA00QQywROdnkVaUjK9PG+waFCvMVjigelIccg1AUjXqgAAAAAAAAAAAL68IAAAAAAAAAAAW5kuvYAAABA/5EBKIR2v7qGnCIWL0WPwnxZ2r4N0/ye04hhgtPUs0R8rlBxDJZQ5G7XUo6WWx0BR3Xgzsl40tQoLpfSDy8HAA==
<stellar-slack> <sacarlson> this might help me figure out why I can't add the trustlines I'm attempting to add
<stellar-slack> <alex3000> on step two of the api guide and I'm getting internal server error
<stellar-slack> <sacarlson> ya I think the demo api is still set at base58 and they now run base32
<stellar-slack> <sacarlson> I've mentioned that here before @alex3000 , not sure when they will get around to fixing i
<stellar-slack> <sacarlson> it
<stellar-slack> <alex3000> oh, do you know how to generate stellars or lumens or whatever the internal currency is called? I am going to be build my own stellar network while I work through the paper in more detail.
<stellar-slack> <sacarlson> yes I also run a standalone stellar-core to allow working around the present development
<stellar-slack> <sacarlson> if you want to try that method I can try to help you set it up
<stellar-slack> <alex3000> that would be great
<stellar-slack> <sacarlson> we can try the present origin master on stellar-core and see how that works for you. if that fails we can try move down to what I now run that is older
<stellar-slack> <alex3000> my first build failed (on the tip of master) .. Stopping at 'lib/libsodium'
<stellar-slack> <alex3000> what commit are you on?
<stellar-slack> <sacarlson> ok well that's due to you not having libsodium installed
<stellar-slack> <sacarlson> what platform system are you running on
<stellar-slack> <alex3000> oops fedora 20... It downloaded something into lib/libsodium.
<stellar-slack> <alex3000> anyway i installed the package...trying again
<stellar-slack> <sacarlson> ok
<stellar-slack> <alex3000> sorry for the delay, i am on gcc 4.8 and it wants 4.9
<stellar-slack> <alex3000> gonna try building it on my server
<stellar-slack> <sacarlson> by the way @fredolafritte as your the only one I know that has had success as of late with trustlines, what commit of stellar-core are you running?
<stellar-slack> <sacarlson> ok @alex3000 and what language of development do you plan to use with stellar?
<stellar-slack> <alex3000> sacarlson: tend to write most of my stuff in java/python/scala/clojure ...and javascript ofc
<stellar-slack> <sacarlson> good since we have more support for java or nodejs. but I mostly write ruby
<stellar-slack> <alex3000> sacarlson: okie dokie thats building now
samuelharden has quit [Ping timeout: 244 seconds]
<stellar-slack> <alex3000> getting stuck at: g++: error: xdrc/scan.cc: No such file or directory (http://pastie.org/10345258)
<stellar-slack> <alex3000> pretty sure all my duck deps are in a row
<stellar-slack> <alex3000> sacarlson: i have tried a few random commits and none of them are building. what commit are you on?
<stellar-slack> <sacarlson> @alex3000: I presently run commit 69ec10e5aa0da004d8f3f047f0dcfb60ddb2c107
<stellar-slack> <sacarlson> I run it on Mint 17 a dirivitive of Ubuntu
de_henne has joined #stellar-dev
<stellar-slack> <alex3000> cool, i'll "check it out". your proj looks interesting btw
<stellar-slack> <alex3000> sacarlson: thats all built now
<stellar-slack> <alex3000> sorry for the delays, i had to resize my cloud vm
<stellar-slack> <sacarlson> so the origin master won't build but my commit 69ec... does?
<stellar-slack> <alex3000> sacarlson: i havent tested origin master recently. i think g++ was running out of memory at one stage, hence the vm resize.
<stellar-slack> <sacarlson> ok
<stellar-slack> <alex3000> the original error message i got though (if it was caused by that) was pretty opaque...see the pastie above
<stellar-slack> <sacarlson> yes I looked but haven't seen that before
<stellar-slack> <alex3000> are stellars and lumens the same thing?
nivah has quit [Ping timeout: 265 seconds]
samuelharden has joined #stellar-dev
<stellar-slack> <sacarlson> well I guess on the new network they will be lumens, they do much the same thing with them
<stellar-slack> <alex3000> sacarlson: how do I make my stellar standalone & generate lumens
<stellar-slack> <alex3000> ?
<stellar-slack> <sacarlson> at the bottom of that I added the config file that has mine setup as standalone
<stellar-slack> <sacarlson> you don't generate lumens, your build has the preminted money already in it, you just need to create an account using funds from master that has all the money that you now have the key for
nivah has joined #stellar-dev
<stellar-slack> <sacarlson> I've only gone as far as being able to create accounts and send lumens from master myself
nivah has quit [Read error: Connection reset by peer]
nivah has joined #stellar-dev
nivah has quit [Read error: Connection reset by peer]
nivah has joined #stellar-dev
nivah has quit [Read error: Connection reset by peer]
<stellar-slack> <sacarlson> for stellar_utilities_local and other examples you can look at my files in slack. I haven't yet published them on github
<stellar-slack> <alex3000> [stellar@f21-tester stellar-core]$ stellar-core ./stellar-core.cfg 2015-08-12T07:05:36.038 startup [140617019205696] [default] FATAL Got an exception: invalid quorum set, should be a group while parsing 'THRESHOLD_PERCENT' while parsing '1' while parsing '2' [main.cpp:405]
<stellar-slack> <alex3000> that's pretty much the verbatim stellar-example.cfg
<stellar-slack> <sacarlson> did you use my config file? what commit are you running
<stellar-slack> <alex3000> no i didnt. still on the commit you suggested.
<stellar-slack> <alex3000> where is your cfg file?
<stellar-slack> <sacarlson> the config file can be anyplace but were you run it will be the location that all the db files will reside
<stellar-slack> <alex3000> I mean did you paste yours in slack?
<stellar-slack> <sacarlson> yes the config file was pasted just above
<stellar-slack> <alex3000> sry. i see what u did now
<stellar-slack> <sacarlson> it was apart of the "to build, ...." I paisted
<stellar-slack> <alex3000> yay ive got it started at least :)
<stellar-slack> <sacarlson> :+1:
<stellar-slack> <alex3000> ehehehe
<stellar-slack> <alex3000> maybe we should bind ours together in a little network off testnet. not today, but once i know a bit more
<stellar-slack> <sacarlson> sure we can try that, remind you I've never done it
<stellar-slack> <alex3000> could you elaborate on this comment: you don't generate lumens, your build has the preminted money already in it, you just need to create an account using funds from master that has all the money that you now have the key for I've only gone as far as being able to create accounts and send lumens from master myself
<stellar-slack> <alex3000> what do you mean from master
<stellar-slack> <sacarlson> if you browse the sqlite database you will see at reset there is one first account that has like 1billion lumens in it. this is the master account they key is shown in the example ruby file above
<stellar-slack> <alex3000> ahhh i c. thats great information ty
<stellar-slack> <sacarlson> @alex3000: so now with all that find out how to get trustlines to apear in the database. when you figure that out tell me.
<stellar-slack> <alex3000> absolutely. thx for your help
<stellar-slack> <alex3000> ( i don't know what trustlines are yet - I
<stellar-slack> <alex3000> 'm assuming they are a datastructure related to the / a merkle tree?
<stellar-slack> <sacarlson> well they have to do with when you start sending and trading other currencies other than lumens
<stellar-slack> <sacarlson> with them being for example USD or EUR or YEN....
<stellar-slack> <alex3000> okie dokie, hopefully i will know more as i get deeper into the publication.
DomKM has joined #stellar-dev
de_henne has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
<stellar-slack> <sacarlson> @fredolafritte: good news! I got my trustlines now working when I used your stellar-core commit 0c4c858124e0bb32efda1e26fae7c9bc5b396f6d, not sure why it wasn't working on my build
<stellar-slack> <sacarlson> also note that I can create 4 letter assets names like "ABCD" instead of just 3 like "USD" I guess that's what :alphanum4 mean? and with :alphanum12 I'm guessing you can have asset names with 12 letters?
cagedwisdom has quit [Ping timeout: 264 seconds]
<stellar-slack> <fredolafritte> the asset name is padded with \0, 3+1 = 4
<stellar-slack> <sacarlson> I took the pad out and seems it allow 4 letter. as strings always end in \0 I guess?
<stellar-slack> <fredolafritte> in the C language yes, they end with \0
<stellar-slack> <sacarlson> so now I guess I can setup a gateway for nasdaq assets that normaly have 4 letters
<stellar-slack> <sacarlson> with 12 letters I guess you can combine all the different trading centers assets with nyse.IBM nasdaq.MSFT
<stellar-slack> <fredolafritte> the magic number 12 comes from https://en.wikipedia.org/wiki/International_Securities_Identification_Number
<stellar-slack> <sacarlson> ok so I wasn't far off then
<stellar-slack> <sacarlson> ok I can now send non native currency including "CHP" so tomaro I should have stellar-core integrated into pokerth_accounting, only thing left is to figure out multi-sign
ultrashag has quit [Ping timeout: 244 seconds]
ultrashag has joined #stellar-dev
<stellar-slack> <fredolafritte> anyone got the trading working properly ? it partially work on my side, only when the price and quantity are set to 1
<stellar-slack> <sacarlson> no I haven't tried it yet but could give it a wak
<stellar-slack> <sacarlson> I'm having problems with transaction merge b64 = tx1.merge(tx2).to_envelope(account).to_xdr(:base64)
<stellar-slack> <sacarlson> I get this returned on attempt to send {"status"=>"ERROR", "error"=>"AAAAAAAAAAD////3AAAAAA=="}
<stellar-slack> <sacarlson> I think I'll give up on it but it would make some of my transactions faster I think as now I have to wait 11 secounds each time
<stellar-slack> <fredolafritte> { "_attributes": { "feeCharged": { "low": 0, "high": 0, "unsigned": false }, "result": { "_switch": { "name": "txInsufficientFee", "value": -9 }, "_arm": {}, "_armType": {} }, "ext": { "_switch": 0, "_arm": {},
<stellar-slack> <sacarlson> txInsufficientFee cool! wonder how I set it up to pay?
<stellar-slack> <sacarlson> it was suposed to be combined to native send transactions
de_henne has quit [Remote host closed the connection]
sacarlson has joined #stellar-dev
sacarlson1 has quit [Ping timeout: 250 seconds]
slippy has joined #stellar-dev
slippy has quit [Ping timeout: 244 seconds]
slippy has joined #stellar-dev
slippy has quit [Quit: Leaving]
DomKM has quit [Quit: Connection closed for inactivity]