Logged Conversation (all times UTC)
[04:12] <stellar-slack> morning
[04:12] <stellar-slack> yo yo
[04:39] <stellar-slack> 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
[04:41] <stellar-slack> as noted above I've tried both hex and base64 so maybe the problem is in the documented method to interface to horizon
[04:41] <stellar-slack> or horizon interface is broken. so now it's time maybe to try the js-lib to see if it works?
[04:50] <stellar-slack> sacarlson i just made a tx to your account GAJYPMJOWAAGCXMB7UYP63LIMTYPXMGIBMYGQRW7QBF5AVSO7S3IRKIP
[04:50] <stellar-slack> using master jslib and master stellar-base
[04:51] <stellar-slack> cool so I assume it works? I'll check my account
[04:51] <stellar-slack> yeah i checked your account, seems to work :)
[04:51] <stellar-slack> wonder if i can send you sausage-assets
[04:52] <stellar-slack> no not until I setup my account to trust yours
[04:52] <stellar-slack> right
[04:52] <stellar-slack> we need an easy UI for that
[04:52] <stellar-slack> but we should now document all the commits at this point that this is the most stable branch at this point
[04:53] <stellar-slack> yes maybe next step start working on user interface
[04:54] <stellar-slack> 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...
[04:54] <stellar-slack> we also need some kind of matrix that shows what all tests have been performed between each set of code I would think
[04:54] <stellar-slack> nah don't think that's required
[04:55] <stellar-slack> we haven't tested multi sign yet
[04:55] <stellar-slack> that's about the only part left that I know of that I haven't seen work
[04:56] <stellar-slack> i think i gonna try to work on a simple UI today evening
[04:56] <stellar-slack> cool
[04:57] <stellar-slack> can you send us the commit codes of js-base and js-lib you just used?
[04:58] <stellar-slack> for js-stellar-base I show present master at 17328b04687cdf35f5132443d04b3e5c13399d87
[05:00] <stellar-slack> for js-stellar-lib I show at present master at 4042b169b24c83f25f822a63f3846d5bfaeb88b6
[05:05] <stellar-slack> that's the ones
[05:05] <stellar-slack> ok
[05:06] <stellar-slack> so now I have a list of all the parts that work together at least with native tx
[05:07] <stellar-slack> so in order to establish trust the private seed is somehow required
[05:07] <stellar-slack> don't know how to build that into the UI ... prompt for it?
[05:08] <stellar-slack> ya I guess gray it out if not needed?
[05:08] <stellar-slack> for a trustline from me to you only my secrete key is needed
[05:08] <stellar-slack> yeah
[05:09] <stellar-slack> but then your secret key is needed for you to issue me the asset
[05:10] <stellar-slack> you might look at the ripple site that has an interface already setup I think
[05:10] <stellar-slack> maybe I'm wrong on that?
[05:24] <stellar-slack> let's see
[05:25] <stellar-slack> well they have a nice office
[05:26] <stellar-slack> I have an account on ripple maybe you might need that to look at the interface?
[05:30] <stellar-slack> i can't find anything useful on ripple's site
[05:32] <stellar-slack> ah, it's http://rippletrade.com|rippletrade.com ... so they give u the option to let them store your secret key for u
[05:32] <stellar-slack> yeah i wanna do something similar
[05:33] <stellar-slack> just have it based on stellar-core/open-core
[05:38] <stellar-slack> 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
[05:38] <stellar-slack> that's dumb
[05:38] <stellar-slack> why?
[05:38] <stellar-slack> that's what trustlines are in most cases I guess is a gateway to assets
[05:40] <stellar-slack> well as @jed said a few days ago, gateways are just a business concept
[05:40] <stellar-slack> not really needed
[05:41] <stellar-slack> LOOOL in order to use rippletrade u have to have a mobile phone for identification and provide full name and address LOOL
[05:41] <stellar-slack> fuck those guys
[05:43] <stellar-slack> "in order to activate your wallet, .... [blablabla] GIEF US MONEY"
[05:43] <stellar-slack> yes that's why I opted for stellar, they are way too tight now on ripple
[05:44] <stellar-slack> but I like there interface
[05:44] <stellar-slack> graphs of any trade you want like a real exchange
[05:45] <stellar-slack> no thank you
[05:45] <stellar-slack> and yes gateway is just another name they have for trustlines that can be just people not just banks or institutions
[05:46] <stellar-slack> but if you want screen shots I have them for you to look at
[05:47] <stellar-slack> @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/
[05:48] <stellar-slack> oh ya edit that out
[05:48] <stellar-slack> let me retract the comment
[05:48] <stellar-slack> *retracts comment*
[05:48] <stellar-slack> thanks. Let's try to keep this a welcoming space, even to rippletrade
[05:49] <stellar-slack> sry :O
[05:50] <stellar-slack> sacarlson u got XRP ?
[05:50] <stellar-slack> yes I have a few
[05:50] <stellar-slack> can u send a few to my acc? (buhrmi)
[05:50] <stellar-slack> I only have 30 xrp just enuf to keep my account open
[05:51] <stellar-slack> ah, okay
[05:51] <stellar-slack> sorry I very poor
[05:51] <stellar-slack> I think I had to spend $3 usd to get it
[05:52] <stellar-slack> yeah it's okay just wanted to look at how they do the UI/UX without putting money in or giving anyone banking info
[05:52] <stellar-slack> I can send you the screen shots of every page, I'll post them to you pm
[05:56] <stellar-slack> nah, it's fine
[06:00] <stellar-slack> too late already done
[06:00] <stellar-slack> it has no key info in them
[06:06] <stellar-slack> got them
[06:06] <stellar-slack> I'm adding a few more shots
[06:07] <stellar-slack> lol it's okay i don't need them lol
[06:07] <stellar-slack> what i wanna do is fundamentally different
[06:08] <stellar-slack> well other people may want them so I'm trying to collect them all
[06:09] <stellar-slack> put that $3 investment to good use ha ha
[06:15] <stellar-slack> stellar-core & horizon already support creation of trustlines?
[06:15] <stellar-slack> can't find docs for an endpoint on horizon
[06:16] <stellar-slack> it requires a transaction to setup a trustline
[06:17] <stellar-slack> ah, i see
[06:17] <stellar-slack> my code has examples of how to set it up
[06:17] <stellar-slack> in ruby
[06:17] <stellar-slack> cool can i look at it?
[06:18] <stellar-slack> so, creation of trustlines require native currency fee, huh?
[06:18] <stellar-slack> yes it's in github published https://github.com/sacarlson/stellar_utility
[06:19] <stellar-slack> but my code at present only works on a local stellar-core, I haven't got the horizon api interface working yet
[06:21] <stellar-slack> interesting..........
[06:22] <stellar-slack> there is better examples in stellar-core-commander but I haven't fully got that working ether
[06:37] <stellar-slack> @sacarlson: did u do anything at all with interstellar modules?
[06:37] <stellar-slack> looks like they're using ecmascript and angular
[06:38] <stellar-slack> I'm not sure I know what that is
[06:40] <stellar-slack> oh no that's js stuf, I'm only just barely touched js
[06:46] <stellar-slack> so your stellar utilities they talk to your standalone node direclty?
[06:46] <stellar-slack> in ruby
[06:47] <stellar-slack> yes
[06:47] <stellar-slack> but the goal is it to work with horizon as I don't want to run a stellar-core
[06:48] <stellar-slack> I will leave it as an option of poker players want to try run there own stellar-core nodes
[07:24] <stellar-slack> let's find out how to set up a "create trust" transaction using the js lib
[07:25] <stellar-slack> ok but I can't do it yet with my code as I'm stuck at horizon not working
[07:26] <stellar-slack> oh I might be able to if I setup a stellar-core to be public node instead of a standalone
[07:28] <stellar-slack> yeah u can let it participate in testnet ^^
[07:28] <stellar-slack> yes that's another one of my milestones also
[07:29] <stellar-slack> I'm assuming my problem is at the RestClient interface that's setup wrong as the base64 codes should be the same
[07:29] <stellar-slack> I can't seem to find that part in the js-stellar-base to compare
[07:53] <stellar-slack> So before an account can create a trustline, the other account has to do an "allow trust" transaction first?
[08:19] <stellar-slack> mhh apperently not
[08:26] <stellar-slack> no it seems not, I'm not sure what that allowtrust does yet
[08:45] <stellar-slack> transaction.toEnvelope().toXDR().toString("base64")
[08:46] <stellar-slack> whatever happened to good old json -._
[08:52] <stellar-slack> beware that changing trust on the stellar js-stellar-base is broken
[08:52] <stellar-slack> in what way
[08:54] <stellar-slack> it just doesn't work due to a one line bug
[08:54] <stellar-slack> fixed in my fork BTW
[08:55] <stellar-slack> is there are PR for the fix?
[08:56] <stellar-slack> indeed
[08:57] <stellar-slack> let me vote on it
[09:01] <stellar-slack> can we vote on PR ?
[09:03] <stellar-slack> can write a comment with the content '+1'
[09:03] <stellar-slack> lol
[09:07] <stellar-slack> can u link the PR?
[09:09] <stellar-slack> go the https://github.com/stellar/js-stellar-base and click on "Pull Requests"
[09:10] <stellar-slack> https://github.com/stellar/js-stellar-base/pull/19
[09:10] <stellar-slack> I'm guessing
[09:10] <stellar-slack> that's the one
[09:14] <stellar-slack> whoa what's axios and bluebird
[09:20] <stellar-slack> 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")
[09:20] <stellar-slack> in that I found I was missing "transactions" but when I add this to my code now I just get error 500
[09:34] <stellar-slack> 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
[09:35] <stellar-slack> is this still true? https://github.com/stellar/stellar-core/blob/master/src/main/CommandHandler.cpp#L196
[09:35] <stellar-slack> hex?
[09:36] <stellar-slack> I thought it was changed to base64 but I could try it
[09:36] <stellar-slack> as from the working code in js-stellar-lib shows it sends transaction in base64
[09:39] <stellar-slack> 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
[09:39] <stellar-slack> via HTTP
[09:40] <stellar-slack> I would guess you would use js-stellar-base to get a tx blob that you could send direct to stellar-core
[09:40] <stellar-slack> yeah
[09:41] <stellar-slack> 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
[09:42] <stellar-slack> any posibility of that matschaffer?
[09:42] <stellar-slack> @matschaffer:
[09:43] <stellar-slack> or point it at @fredolafritte horizion server and see what he see's in the error I create
[09:44] <stellar-slack> other option is I setup the same horizion and point it at myself
[09:45] <stellar-slack> maybe don't even need horizon ...
[09:45] <stellar-slack> I already have that working without horizon, that I have tested already as working
[09:47] <stellar-slack> but not with the presently known version now running on horizon so that's another step I could try and need to do anyway
[09:52] <stellar-slack> trying to send tx to stellar-core via HTTP i get { data: { exception: 'bad value of type in _body_t' },
[09:52] <stellar-slack> hmmm...
[09:52] <stellar-slack> to your localy running core?
[09:52] <stellar-slack> yeah
[09:52] <stellar-slack> right now, the only way to make it work is to have everything built locally: js-stellar-base, horizon, go-horizon and stellar-core
[09:53] <stellar-slack> @fredolafritte: shouldn't it be possible to skip horizon and go directly js-stellar-base -> core?
[09:53] <stellar-slack> isn't the base64 encoded transaction the same?
[09:55] <stellar-slack> fredolafritte: maybe you missed it that buhrmi was able to do a native transaction with all stellar code erlier today
[09:55] <stellar-slack> sending a transaction is not enough, you would need to check the state of the transaction to find out if it succeeds or not
[09:56] <stellar-slack> getting the list of transactions is the job of horizon, not stellar-core
[09:56] <stellar-slack> 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
[09:58] <stellar-slack> but *in theory*, posting a tx blob to [horizon]/transactions or [stellar-core]/tx?blob= should be the same, right?
[09:58] <stellar-slack> in local I look direct at the stellar-core database file and find the sequence for the account needed
[09:59] <stellar-slack> they aren't the same in my case as I run standalone nothing in the database is the same
[10:00] <stellar-slack> i mean the format of the base64 is the same, now?
[10:00] <stellar-slack> yes but if you were running from a node that was in sync they should be able to use the same blob
[10:00] <stellar-slack> right
[10:01] <stellar-slack> I think so yes I use base64 with success in my direct stellar-core transactions
[10:02] <stellar-slack> there just seems to be no reason they would have to change that
[10:03] <stellar-slack> ok I've already checked out stellar-core version b179493a328955f8927d367c712bf0dd7341f3e7 that I will setup and check to see if it works for me
[10:14] <stellar-slack> seems to take as long to compile this as a new kernel
[10:15] <stellar-slack> can u send me an example blob that you were able to successfully send to your local core?
[10:16] <stellar-slack> I can send you a failed blob of what I last tried to send to horizon
[10:16] <stellar-slack> 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
[10:17] <stellar-slack> is your stellar-core in sync?
[10:17] <stellar-slack> no idea
[10:18] <stellar-slack> look at the output at the term you should intermitently see the word sync
[10:18] <stellar-slack> or you used to
[10:18] <stellar-slack> at the term running your core
[10:19] <stellar-slack> with the old stellard I ran all night and still never got in sync
[10:19] <stellar-slack> but I think that was due to not enuf mem?
[10:19] <stellar-slack> the /info endpoint shows sync status too
[10:20] <stellar-slack> { "info": { "build": "e8b8598", "ledger": { "age": 1440408627, "closeTime": 0, "hash": "e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1", "num": 2 }, "numPeers": 3, "state": "Joining SCP" } }
[10:20] <stellar-slack> Very not in sync
[10:20] <stellar-slack> lol
[10:20] <stellar-slack> That ledger age is in seconds
[10:21] <stellar-slack> so state is joining at some point I guess it will be synced
[10:21] <stellar-slack> how long has it been running?
[10:21] <stellar-slack> 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)
[10:21] <stellar-slack> With an age that old it probably failed very early on in the process
[10:22] <stellar-slack> If it's working the logs will show ETA
[10:22] <stellar-slack> Should only take ~5 min or so I think. Probably bandwidth depending
[10:23] <stellar-slack> 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
[10:25] <stellar-slack> oh and my stellar-core compile completed
[10:30] <stellar-slack> how do i "tell" my local stellar core to sync?
[10:30] <stellar-slack> should it do it automatically?
[10:31] <stellar-slack> yes in theory in time if configured correctly it should sync
[10:31] <stellar-slack> I think in that "state": "Joining SCP" it should be seen
[10:32] <stellar-slack> instead of joining
[10:32] <stellar-slack> 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
[10:34] <stellar-slack> you might also try standalone to verify yourself
[10:37] <stellar-slack> maybe i should try different config file
[10:40] <stellar-slack> ah, there we go... my config was bad
[10:41] <stellar-slack> there ya go
[10:45] <stellar-slack> now i always get
[10:45] <stellar-slack> 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.
[10:46] <stellar-slack> I'm not sure you did the reset stuf
[10:46] <stellar-slack> I have scripts to do reset and startup I should share with you
[10:47] <stellar-slack> I'm presently rewriting them
[10:50] <stellar-slack> not sure these are still needed with newer builds or not
[10:52] <stellar-slack> a copy of these will be kept in my stellar_utilities package
[10:54] <stellar-slack> are we still going to the moon?
[10:54] <stellar-slack> ??
[10:55] <stellar-slack> ya I'm about to blast off man
[10:55] <stellar-slack> 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.
[10:56] <stellar-slack> the "buffered to XXXX' number doesn't increase :O
[10:56] <stellar-slack> is this with running my reset script?
[10:57] <stellar-slack> partly ... i dont wanna run standalone
[10:57] <stellar-slack> you can try run standalone for 20 secounds and see if it works or not and go back to try to sync
[10:58] <stellar-slack> but no need I'll be running standalone in about 2 min
[10:58] <stellar-slack> just have to see about a new config file
[10:59] <stellar-slack> FATAL Got an exception: invalid quorum set
[10:59] <stellar-slack> my old config is no good
[10:59] <stellar-slack> try this guy https://raw.githubusercontent.com/stellar/stellar-core/master/docs/stellar-core_testnet.cfg
[10:59] <stellar-slack> see if u can get it to sync
[11:00] <stellar-slack> I want to try standalone first that will take too long
[11:00] <stellar-slack> min 5 min to sync
[11:00] <stellar-slack> I can check for other problems long before that
[11:02] <stellar-slack> almost no network activity while it's trying to catch up
[11:06] <stellar-slack> ok mine is now running I guess synced
[11:08] <stellar-slack> what do you get on /info ?
[11:13] <stellar-slack> i'm not sure what happened but after I got this info it crashed
[11:14] <stellar-slack> I'm not sure if getting info did it or not. I'll reset and try it again
[11:15] <stellar-slack> I think my old version is more stable
[11:16] <stellar-slack> maybe the tmp path, I'll change it
[11:29] <stellar-slack> or I erased all the original database and files and reset now it's working
[11:30] <stellar-slack> "state" : "Synced!"
[11:38] <stellar-slack> hmmm
[11:39] <stellar-slack> synced with testnet?
[11:39] <stellar-slack> numPeers 0
[11:39] <stellar-slack> no standalone
[11:39] <stellar-slack> lol
[11:39] <stellar-slack> they also changed the port address
[11:39] <stellar-slack> I'm still working on finding it
[11:39] <stellar-slack> try testnet lol
[11:39] <stellar-slack> this doens't work yet
[11:40] <stellar-slack> need to find ports
[11:40] <stellar-slack> when this works then I'll try it
[11:40] <stellar-slack> there were 2 sets of ports before not sure what I'm suposed to be attached to
[11:42] <stellar-slack> it was http://localhost:39132 I think it's now http://localhost:8080
[11:44] <stellar-slack> now I guess we can try your config
[11:53] <stellar-slack> first attempt with testnet config fails
[11:54] <stellar-slack> !mSCP.getSecretKey().isZero()' failed. ?
[11:54] <stellar-slack> just dont --forcescp when trying to join a network
[11:54] <stellar-slack> ok
[11:59] <stellar-slack> ETA: 65 seconds
[12:00] <stellar-slack> so even if this fails I'm ready to try install a local copy of horizon
[12:03] <stellar-slack> "state" : "Synced!"
[12:04] <stellar-slack> so I guess now I can perform transactions on testnet without horizion
[12:04] <stellar-slack> will try that
[12:06] <stellar-slack> mine won't sync...
[12:06] <stellar-slack> seems to work created new accounts and native transacation GCK4JRZX44275PBWKQWEJ52XWFNOWLW4EFZ7ULTAVEFDBZJ3OJE7OQ56
[12:06] <stellar-slack> I have a new reset script maybe I should send you the new one
[12:06] <stellar-slack> k
[12:07] <stellar-slack> I just took out the -forcescp as you said
[12:08] <stellar-slack> only thing I changed in config was http port
[12:08] <stellar-slack> FATAL Can't initialize unknown history archive 'vs' [HistoryManagerImpl.cpp:48]
[12:08] <stellar-slack> you must manualy delete all the history files and db
[12:08] <stellar-slack> I guess in later version I'll have the script also do that
[12:09] <stellar-slack> i don't see any history files
[12:09] <stellar-slack> what about db files?
[12:09] <stellar-slack> only the one -newdb create
[12:10] <stellar-slack> I also may be running an older version of stellar-core the same as horizion runs
[12:11] <stellar-slack> delete all the db files
[12:11] <stellar-slack> I run these scripts in a bare directory that gets filled with db files and history files after it starts
[12:12] <stellar-slack> maybe thats the reason WARN No writable archives configured, history will not be written.
[12:12] <stellar-slack> I might have had that warn also but it kept running
[12:15] <stellar-slack> ah u need to configure the history "vs" in the config file
[12:16] <stellar-slack> https://github.com/stellar/docker-stellar-core/blob/master/start#L31 might help a bit as far as reset goes
[12:16] <stellar-slack> wasn't it already configured? I didn't change anything
[12:17] <stellar-slack> there's on-disk stuff referenced by BUCKET_DIR_PATH & TMP_DIR_PATH
[12:17] <stellar-slack> then db, depending how you have that set
[12:17] <stellar-slack> then history storage
[12:17] <stellar-slack> wipe all 3 and you've got a clean reset
[12:17] <stellar-slack> ya wipe um
[12:18] <stellar-slack> I'll edit my reset script now so I don't forget
[12:18] <stellar-slack> and your history config (e.g., "vs") needs to match whatever you pass to --newhist
[12:18] <stellar-slack> doesn't matter what you call it
[12:18] <stellar-slack> in prod it matches the internal short hostname (core-001, core-002)
[12:19] <stellar-slack> not sure where "vs" came from
[12:19] <stellar-slack> https://github.com/stellar/docker-stellar-core/blob/master/start#L30 is exactly that but it's psql specific
[12:21] <stellar-slack> https://github.com/stellar/docker-stellar-core/blob/master/confd/templates/stellar-core.cfg.tmpl is what builds the config file for the containers. It's a little gnarly, but shouldn't be too bad to follow. It's a golang template for confd
[12:21] <stellar-slack> just bootstrapped a completely new VM, trying to get core to run and sync...
[12:22] <stellar-slack> (not using docker)
[12:25] <stellar-slack> ndb, this stuff isn't really docker dependent
[12:26] <stellar-slack> hmm yeah, well :O ..
[12:26] <stellar-slack> docker's really just a glorified chroot anyway
[12:27] <stellar-slack> what's your config look like at this point?
[12:27] <stellar-slack> https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_testnet.cfg
[12:30] <stellar-slack> I'll start a source build here to check it out. Could be that works just don't try to call --newhist
[12:30] <stellar-slack> since it doesn't have any writable hist to intialize
[12:30] <stellar-slack> yeah i'm just rebuilding here too
[12:43] <stellar-slack> my core hosted in the cloud is syncing .... my local one doesn't
[12:43] <stellar-slack> grrr
[12:44] <stellar-slack> why is that so bad at least you got one working
[12:44] <stellar-slack> cause i want one local
[12:44] <stellar-slack> overhead looks very small at 10kb/s and only 0.3 mem used by stellar-core
[12:45] <stellar-slack> 0.3%mem 0.3% cpu used
[12:46] <stellar-slack> well maybe my new new reset-core.sh
[12:48] <stellar-slack> if that fails try a differernent version
[12:50] <stellar-slack> it's prob something to do with my local machine ...
[12:50] <stellar-slack> windows?
[12:50] <stellar-slack> ubuntu
[12:51] <stellar-slack> I'm runing ubuntu 14.04 but I've also run in Lubuntu 14.04 in virtualbox
[12:51] <stellar-slack> I'm sorry I'm running Linux Mint 17 but that's the same as Ubuntu 14.04
[12:53] <stellar-slack> http://108.61.160.52:11626/info
[12:53] <stellar-slack> maybe tomaro I'll make a deb file for the version I'm running now that's also running on horizon
[12:53] <stellar-slack> gonna use that one to test against
[12:54] <stellar-slack> "state" : "Catching up"
[12:54] <stellar-slack> is that the cloud?
[12:54] <stellar-slack> yeah
[12:54] <stellar-slack> ETA 250 secs
[12:54] <stellar-slack> oh ok
[12:55] <stellar-slack> gonna leave a core node with public HTTP for now
[12:55] <stellar-slack> in sync with testnet
[12:55] <stellar-slack> so you have 2 clouds running now then?
[12:56] <stellar-slack> buhrmi: have you tested port level access from the local one?
[12:57] <stellar-slack> port level? is that were I did the transactions? if so then yes
[12:57] <stellar-slack> oh not me
[12:58] <stellar-slack> 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
[12:59] <stellar-slack> I know virtualbox for example makes it really easy to make a VM with limited internet access
[12:59] <stellar-slack> was sort of the default a few years ago
[12:59] <stellar-slack> well if what I looked at was his only cloud then it's not in sync it's in "state" : "Catching up"
[12:59] <stellar-slack> that's good though
[12:59] <stellar-slack> means it's actually moving
[13:00] <stellar-slack> an ETA in the logs is promising too
[13:00] <stellar-slack> especially if it's going down
[13:00] <stellar-slack> buhrmi: oh btw, watch out having that http port open. There are some commands that you don't really want other people hitting
[13:00] <stellar-slack> mine seemed to sync very fast less than 5 min
[13:00] <stellar-slack> in fact it was like less than 2 min
[13:01] <stellar-slack> generateload for example
[13:01] <stellar-slack> I'm sure it varies. when restarting testnet I had a tendency to see ~300s
[13:02] <stellar-slack> well that's not long
[13:02] <stellar-slack> nah, not bad
[13:02] <stellar-slack> but I assume with an older buzy network things will change
[13:02] <stellar-slack> or an underpowered VM
[13:02] <stellar-slack> catch up was pretty I/O heavy last I looked
[13:03] <stellar-slack> I wasn't looking at top when I started, it's very low on resouces now
[13:11] <stellar-slack> fwiw, my rebuild here is syncing fine now
[13:11] <stellar-slack> just on my mac
[13:11] <stellar-slack> it's synced :P
[13:11] <stellar-slack> just ran ``` > ./src/stellar-core --conf docs/stellar-core_testnet.cfg --newdb > ./src/stellar-core --conf docs/stellar-core_testnet.cfg ```
[13:11] <stellar-slack> :+1:
[13:11] <stellar-slack> http://open-core.org/info
[13:12] <stellar-slack> ah, DNS is slow again
[13:12] <stellar-slack> I can see it as synced
[13:12] <stellar-slack> I'd try `telnet http://core-testnet1.stellar.org|core-testnet1.stellar.org 11625` and `telnet http://s3-eu-west-1.amazonaws.com|s3-eu-west-1.amazonaws.com 443` on the vm
[13:13] <stellar-slack> my guess is that'll fail if you followed the same process there
[13:13] <stellar-slack> why would be a networking question (vm selinux or fw rules, vm network, host network, lan, etc.)
[13:17] <stellar-slack> finally this works 'http://open-core.org/tx?blob='+encodeURIComponent(transaction.toEnvelope().toXDR().toString("base64"))
[13:18] <stellar-slack> sick encoding chain
[13:18] <stellar-slack> You saw my note about generateload right?
[13:19] <stellar-slack> would generateload propagate to the entire testnet ?
[13:20] <stellar-slack> Not sure. Hopefully not :)
[13:20] <stellar-slack> yeah i don't really care about load on that instance, can restart it easily
[13:20] <stellar-slack> Try it and see, SF should be awake soon :-p
[13:20] <stellar-slack> haha, nah
[13:20] <stellar-slack> Thx ;)
[13:23] <stellar-slack> so.. uhm ... in order for horizon to show account info ... what is it accessing? ledger SQL?
[13:23] <stellar-slack> what's that
[13:25] <stellar-slack> ah, it's just a whatever-database ... postgres or sqlite
[13:26] <stellar-slack> ya that's what my code does. it just gets info from sqlite
[13:26] <stellar-slack> k... wanna built my infrastructure without depending on horizon
[13:28] <stellar-slack> main missing thing is the sequence number that I didn't see a way to get it from the port interface on stellar-core
[13:30] <stellar-slack> that's probably stored in the database, no?
[13:30] <stellar-slack> 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
[13:30] <stellar-slack> yes it's in the sqlite database
[13:31] <stellar-slack> 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 ^^
[13:31] <stellar-slack> 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
[13:31] <stellar-slack> but ... for testing .. i guess it's fine
[13:31] <stellar-slack> heading home
[13:32] <stellar-slack> yeah maybe it could be possible to add sequence number to /info
[13:32] <stellar-slack> but yours is synced with testnet? if so then they can just get the sequence code from there and send transaction to yours
[13:33] <stellar-slack> yes
[13:33] <stellar-slack> ok it's been fun
[13:41] <stellar-slack> can't wrap my head around this quorum stuff
[13:49] <stellar-slack> that's above my paygrade
[13:54] <stellar-slack> @matschaffer: the telnet stuff worked btw ...
[15:32] <stellar-slack> can somebody quickly explain what is stored in the buckets and what in the database?
[15:39] <stellar-slack> buhrmi: does this help https://github.com/stellar/stellar-core/blob/master/docs/architecture.md
[15:41] <stellar-slack> yeah, thanks :)
[15:47] <stellar-slack> oh man i just got the best domain for the core-based social network
[15:47] <stellar-slack> can't believe it wasnt taken
[16:29] <stellar-slack> what's the domain? @buhrmi
[16:29] <stellar-slack> or is it a surprise? :)
[16:30] <stellar-slack> gonna be surprise :P
[16:30] <stellar-slack> awesome, can't wait :)
[23:27] <stellar-slack> I'm making an attempt to install a local copy of horizon today
[23:28] <stellar-slack> 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
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of