sv-logger has quit [Remote host closed the connection]
sv-logger has joined #stellar-dev
<stellar-slack>
<sacarlson> as I look at https://github.com/stellar/horizon/pull/49 it seems to look ok as far as 7 digits for amounts. but I note the conversion is done only at the horizon level. so this I take it will make it match for any asset other than native as seen from ruby-stellar-base already. but I think we have to remember at base level we still do native in integer but beyond after horizion it will be seen as de
<stellar-slack>
<sacarlson> if so no bigy
TheSeven has quit [Disconnected by services]
[7] has joined #stellar-dev
<stellar-slack>
<buhrmi> woohoo my core is finally working
<stellar-slack>
<sacarlson> I had a thought maybe we could add tags to stellar-core git that would indicate what is now running on horizon. I added some local tags just to reference my points to find none already there
<stellar-slack>
<sacarlson> dam postres 9.5 I just installed 9.4.4 a few days ago and that was just an upgrade from 9.3
<stellar-slack>
<sacarlson> sure you don't mean libpq5 that is install version 9.4.4-1...? as far as I know this is most resent you can get that with prebuild binary deb packages
<stellar-slack>
<buhrmi> no i mean postgres 9.5
<stellar-slack>
<buhrmi> check it out... trustlines now update in real time when a tx is received
<stellar-slack>
<sacarlson> looks good
<stellar-slack>
<raybesiga> Looking good @buhrmi just curious as to why you moved away from the native currency..
<stellar-slack>
<dzham> @buhrmi: what do you mean by ‘federated'?
<stellar-slack>
<buhrmi> federated ... storing secret seed on the server
<stellar-slack>
<buhrmi> need to work on wording etc
<stellar-slack>
<buhrmi> @raybesiga: cause with a native currency it can not be truly open
<stellar-slack>
<sacarlson> there is no secret seeds on the server but it's own
<stellar-slack>
<buhrmi> yeah well "server" meaning in this context the server that serves the web application. not the core node server
<stellar-slack>
<sacarlson> horizon also doesn't hold any secret seeds
<stellar-slack>
<raybesiga> Looking forward to seeing how it develops @buhrmi
pixelb has joined #stellar-dev
<stellar-slack>
<sacarlson> the signing of transactions are performed in js on the local computer before it is seen by horizon
<stellar-slack>
<buhrmi> @sacarlson: yes
<stellar-slack>
<buhrmi> storing it on the server is just "for convienience"
<stellar-slack>
<buhrmi> not really recommended if concerned with security
<stellar-slack>
<sacarlson> it's not stored there it can't
<stellar-slack>
<sacarlson> or I should say it's not setup to do so
<stellar-slack>
<buhrmi> if you sign up at http://open-core.meteor.com|open-core.meteor.com it gives you the option to store your secret seed for you
<stellar-slack>
<buhrmi> so it can sign transactions for you
<stellar-slack>
<sacarlson> oh that should be nesesary if we figure out how to use the js scripts to do it on the user side on the browser
<stellar-slack>
<buhrmi> yes
<stellar-slack>
<buhrmi> @sacarlson: do you have an address i can trust with some beer?
<stellar-slack>
<sacarlson> no I see no addreses in your database so something must be wrong
<stellar-slack>
<sacarlson> do you see any on your side?
<stellar-slack>
<buhrmi> you generate your own address
<stellar-slack>
<buhrmi> any address works
<stellar-slack>
<buhrmi> as long as you have the secret seed for it
<stellar-slack>
<sacarlson> yes I did but they didn't show up on your database
<stellar-slack>
<sacarlson> do yours?
<stellar-slack>
<sacarlson> if yours show up then I have a problem on my side
<stellar-slack>
<sacarlson> I only show ledger headers
<stellar-slack>
<sacarlson> you would have to pass me your address first but it still won't work since I can't setup trust on an account that doesn't exist yet
<stellar-slack>
<buhrmi> it won't work on your side if you're not running pg 9.5
<stellar-slack>
<buhrmi> you're probably out of sync now
<stellar-slack>
<buhrmi> @sacarlson: yes you can.. that's the whole point
<stellar-slack>
<buhrmi> you can send transactions from accounts that don't exist
<stellar-slack>
<sacarlson> your correct I'm "state" : "Catching up"
<stellar-slack>
<sacarlson> ok what apt get libs exactly do I need for dependancies in debian ubuntu
<stellar-slack>
<sacarlson> just the newer version of libpq?
<stellar-slack>
<sacarlson> the don't seem to be seen in any of the repository I now have
<stellar-slack>
<fredolafritte> @buhrmi: use valgrind to catch these kind of errors
<stellar-slack>
<buhrmi> @sacarlson: so if i trust you with beer, and you trust me with sausage, we can make a multisign transaction that credits me with your beer, and you with my sausage ^^
<stellar-slack>
<sacarlson> need a 3rd party for multisign
<stellar-slack>
<buhrmi> no, two is enough
<stellar-slack>
<sacarlson> not sure how that would work with 2
<stellar-slack>
<sacarlson> I think I found a way to delete 9.4
<stellar-slack>
<buhrmi> that's an example with two signers
pixelb has quit [Quit: Leaving]
pixelb has joined #stellar-dev
pixelb has quit [Quit: Leaving]
pixelb has joined #stellar-dev
<stellar-slack>
<sacarlson> ok we got the first transaction sent on @buhrmi open-core of qty 3 BEER's with no native fee's
<stellar-slack>
<sacarlson> oh and yes an exchange of two different assets, that's a good example of a 2 party multi-sign transaction
<stellar-slack>
<dzham> using offers or just two ops?
<stellar-slack>
<buhrmi> Just two ops
<stellar-slack>
<sacarlson> for the beer?
<stellar-slack>
<dzham> yeah.. I mean, you could’ve just used the exchange to do that
<stellar-slack>
<buhrmi> Have Sacarlson beer credits. Want: wine
<stellar-slack>
<dzham> but multiple ops per tx is a really convenient thing
<stellar-slack>
<sacarlson> yes that's why I didn't understand what good a 2 party multi-sign was for but at least it's easiest to test something
<stellar-slack>
<sacarlson> with only 3 beer how much wine were you hoping to get? and with me backing them no less
<stellar-slack>
<buhrmi> I would assume you are a trustworthy beer gateway
<stellar-slack>
<buhrmi> hmmm how would a good UI for a 2 party multi sign transaction look like
_whitelogger has joined #stellar-dev
<stellar-slack>
<buhrmi> @dzham: what exchange?
<stellar-slack>
<sacarlson> there is the built in exchange system built into stellar
<stellar-slack>
<sacarlson> really no need for 2 party exchange but good to practice
<stellar-slack>
<buhrmi> the offer system?
<stellar-slack>
<buhrmi> yeah i think i gonna do offers next
<stellar-slack>
<sacarlson> or three party multi-sign would be good for payment for goods that are delivered then signed for after recieveing
<stellar-slack>
<buhrmi> i see
<stellar-slack>
<sacarlson> hay I just had an idea @buhrmi, we could make a gateway direct 1 to 1 from open-core to stellar and stellar to open-core. just deposit the money at a decided gateway address and it apears on the other network as a deposit to that same address
<stellar-slack>
<sacarlson> in the same asset with the same issuer addresses
<stellar-slack>
<sacarlson> since they keys are the same on both sides it might work
<stellar-slack>
<buhrmi> that address would have to give trust on the one side and receive trust on the other side before deposits could be made, no?
<stellar-slack>
<buhrmi> mhh i don't think i gonna explore that idea
<stellar-slack>
<buhrmi> wanna do offers instead and trade some beer
<stellar-slack>
<sacarlson> the gateways would have to exist on both networks I guess for it to work
<stellar-slack>
<sacarlson> gateways I should mean the issuers
<stellar-slack>
<sacarlson> I'm not totaly sure I thought this thrue. it would be easy with native but not totaly sure with non native for this
<stellar-slack>
<sacarlson> the issuers would have to trust that when deposits are recieved on one side it will spit out the other side. maybe your 2 person multi-sign trade would even be needed in this case
<stellar-slack>
<sacarlson> wow I think you can even pass multi-sign through the gateway
<stellar-slack>
<sacarlson> it's still all the same key sets so maybe it would work. need smarter people than me to think about it ha ha
<stellar-slack>
<buhrmi> haha
<stellar-slack>
<buhrmi> having the stellar-core friendbot issuing XLM as a regular asset from the same address on open-core would be super feasible tho.
<stellar-slack>
<sacarlson> oh I think I have it figured out. each participating gateway issuer would just have the same address on both networks. if the holder of the asset wanted to move it to the other network they would simply send it back to the same issuer with a memo indicating they want to transfer to the other side
<stellar-slack>
<sacarlson> it would then show up on the other side at the same address and same issuer
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<sacarlson> oh this is to look at historic trades that already happened @scott?
<stellar-slack>
<scott> yep
<stellar-slack>
<scott> you could, for example, drive a real-time stream of trades from the endpoint
<stellar-slack>
<sacarlson> sounds useful but I'm not sure how it would be done
<stellar-slack>
<sacarlson> the data I look at in the present core database is of what is to be or could be now what was
<stellar-slack>
<sacarlson> so some kind of event recorder would have to exist on every trade event and as you say streamed to some buffer for some time window that others could capture and hold longer windows
<stellar-slack>
<scott> so, we already import “trades” and it works quite well. This specific issue is in regards to indexing that data from the order books viewpoint.
<stellar-slack>
<sacarlson> well the only way that is simple for me to understand is more like your solution #2 that just adds a new table with every trade. with that it's simple you just data search for the pair your looking for and even the time window you want
<stellar-slack>
<sacarlson> and price range if you like
<stellar-slack>
<sacarlson> maybe I just didn't look at what the horizon data base already has in it
<stellar-slack>
<scott> You’ll notice the `type` is `33`, which is the trade effect constant. Solution number one is basically "maintain a partial index where `type == 33` that indexes the “bought_*” and “sold_*” columns"
<stellar-slack>
<sacarlson> ok so this is history on every trade event that is already captured?
<stellar-slack>
<scott> yep
<stellar-slack>
<sacarlson> the format is unclear as to what I'm looking at but I think the info must be there
<stellar-slack>
<scott> that’s a pg_dump formatted sql file
<stellar-slack>
<sacarlson> yes in some spread sheet it might be more clear
<stellar-slack>
<sacarlson> I know nothing of partial index, I would use the most inefficient method and reformat it in a new table with just the data I want to see and can work from.
<stellar-slack>
<sacarlson> sorted by time
<stellar-slack>
<sacarlson> but as things get big better to find a better way than what I would try to do
de_henne has quit [Remote host closed the connection]