Logged Conversation (all times UTC)
[02:49] <stellar-slack> 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
[02:52] <stellar-slack> if so no bigy
[05:00] <stellar-slack> woohoo my core is finally working
[05:00] <stellar-slack> 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
[05:00] <stellar-slack> i think ^^
[05:00] <stellar-slack> i gonna set up two websites ... http://stellar-core.meteor.com|stellar-core.meteor.com and http://open-core.meteor.com|open-core.meteor.com ^^
[05:00] <stellar-slack> same app, different networks
[05:01] <stellar-slack> oh I didn't see that. ready for me to try it? I'll pull the changes
[05:01] <stellar-slack> i think so
[05:01] <stellar-slack> either it's working or i just got lucky with the random behaviour
[05:02] <stellar-slack> ha ha well we will see
[05:08] <stellar-slack> mhh it's still random sometimes ...
[05:09] <stellar-slack> what's a good place to set up a programming bounty? 20 bucks or so...
[05:09] <stellar-slack> this line sometimes outputs a random integer even tho isnew is a bool .... just can't find out what's happening here https://github.com/buhrmi/stellar-core/blob/master/src/ledger/AccountFrame.cpp#L376
[05:10] <stellar-slack> here to start if it's stellar code otherwise you could try maybe one of the many http://frelance.com|frelance.com
[05:11] <stellar-slack> they have lots of indians that do almost anything for $5
[05:12] <stellar-slack> my c++ is probly even worse than yours ha ha
[05:13] <stellar-slack> anyway, i take it back, it still produces txInternalError sometimes
[05:13] <stellar-slack> my thing was instrument, ad prints everyplace to get a clue
[05:13] <stellar-slack> just sent lots of transactions...
[05:13] <stellar-slack> oh wow and I was just about to start compile ha ha
[05:21] <stellar-slack> https://bountify.co/find-source-of-random-behavior-in-c-code
[05:23] <stellar-slack> sounds good
[05:37] <stellar-slack> @burhmi: have you stepped through it with a debugger? Try setting a memory breakpoint on the variable
[05:39] <stellar-slack> i don't even know to do that :O
[05:39] <stellar-slack> do i use visual studio for that? no clue
[05:41] <stellar-slack> dzham $50 bucks has your name on it
[05:51] <stellar-slack> You could use visual studio
[05:51] <stellar-slack> https://msdn.microsoft.com/en-us/library/350dyxd0%28v=vs.90%29.aspx
[05:51] <stellar-slack> k maybe when i'm at home. don't have windows here
[05:52] <stellar-slack> this standalone config doen't seem to work as it still trying to connect to other nodes
[05:53] <stellar-slack> I was going to just try set all fee's to zero to see what that does in standalone
[05:53] <stellar-slack> @buhrmi: OK… What platform are you on?
[05:57] <stellar-slack> ubuntu ^^
[05:57] <stellar-slack> but i can just google ubuntu c++ debugger ide or something
[05:57] <stellar-slack> alright, so you know gdb?
[05:57] <stellar-slack> just don't have much time atm so i rather give some money away
[05:58] <stellar-slack> i've heard the term "gdb" before
[05:59] <stellar-slack> opps I was pointing at wrong config file in my script
[05:59] <stellar-slack> but now the real problem as seen when you add these values
[06:00] <stellar-slack> so I guess even with it in the comments of the stellar-core example configs they are not really setup to work
[06:23] <stellar-slack> okay lets try that gdb thing
[07:19] <stellar-slack> i think i figured it out
[07:19] <stellar-slack> i didn't initialize the variable in all possible constructors
[07:20] <stellar-slack> so that why it's just random
[07:20] <stellar-slack> there ya go
[07:44] <stellar-slack> k it's finally working
[07:44] <stellar-slack> but i also upgraded the dependencies to postgres 9.5 :P
[07:44] <stellar-slack> (fixes the doc)
[07:56] <stellar-slack> updated readme https://github.com/buhrmi/core
[09:46] <stellar-slack> dam postres 9.5 I just installed 9.4.4 a few days ago and that was just an upgrade from 9.3
[10:01] <stellar-slack> 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
[10:26] <stellar-slack> no i mean postgres 9.5
[10:26] <stellar-slack> check it out... trustlines now update in real time when a tx is received
[10:27] <stellar-slack> looks good
[10:50] <stellar-slack> Looking good @buhrmi just curious as to why you moved away from the native currency..
[10:51] <stellar-slack> @buhrmi: what do you mean by ‘federated'?
[10:52] <stellar-slack> federated ... storing secret seed on the server
[10:53] <stellar-slack> need to work on wording etc
[10:54] <stellar-slack> @raybesiga: cause with a native currency it can not be truly open
[10:54] <stellar-slack> there is no secret seeds on the server but it's own
[10:55] <stellar-slack> yeah well "server" meaning in this context the server that serves the web application. not the core node server
[10:55] <stellar-slack> horizon also doesn't hold any secret seeds
[10:55] <stellar-slack> Looking forward to seeing how it develops @buhrmi
[10:56] <stellar-slack> the signing of transactions are performed in js on the local computer before it is seen by horizon
[10:56] <stellar-slack> @sacarlson: yes
[10:56] <stellar-slack> storing it on the server is just "for convienience"
[10:57] <stellar-slack> not really recommended if concerned with security
[10:57] <stellar-slack> it's not stored there it can't
[10:57] <stellar-slack> or I should say it's not setup to do so
[10:58] <stellar-slack> 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
[10:58] <stellar-slack> so it can sign transactions for you
[10:59] <stellar-slack> 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
[10:59] <stellar-slack> yes
[10:59] <stellar-slack> @sacarlson: do you have an address i can trust with some beer?
[11:00] <stellar-slack> no I see no addreses in your database so something must be wrong
[11:00] <stellar-slack> do you see any on your side?
[11:00] <stellar-slack> you generate your own address
[11:00] <stellar-slack> any address works
[11:00] <stellar-slack> as long as you have the secret seed for it
[11:00] <stellar-slack> yes I did but they didn't show up on your database
[11:00] <stellar-slack> do yours?
[11:01] <stellar-slack> if yours show up then I have a problem on my side
[11:01] <stellar-slack> I only show ledger headers
[11:02] <stellar-slack> i've just added one http://open-core.meteor.com/accounts
[11:03] <stellar-slack> nope nothing seen on my side
[11:03] <stellar-slack> in table accounts is empty
[11:04] <stellar-slack> yes
[11:04] <stellar-slack> cause it didnt make any transaction yet
[11:04] <stellar-slack> it should show up as soon as it makes a trust transaction
[11:04] <stellar-slack> just need your address
[11:04] <stellar-slack> ok
[11:05] <stellar-slack> GBZH6Z74OWID6ZP67KYNF7T5ES4APLZSISYO7GZGXW7PJNMFL4XNV3PT
[11:05] <stellar-slack> 3 beers please
[11:06] <stellar-slack> spelled BEER
[11:06] <stellar-slack> done
[11:06] <stellar-slack> don't I need to add trust for you to send them to me?
[11:06] <stellar-slack> no i just made the trustline
[11:07] <stellar-slack> in this case I think the trustline would be on my side to hold BEER from you but I could be wrong
[11:07] <stellar-slack> yeah i don't know... as long as there's beer. lol
[11:08] <stellar-slack> nope nothing seen in the database
[11:09] <stellar-slack> select * from trustlines => accountid | assettype | issuer | assetcode | tlimit | balance | flags | lastmodified ----------------------------------------------------------+-----------+----------------------------------------------------------+-----------+--------+---------+-------+--------------
[11:09] <stellar-slack> GD5GK7WBU27XXAGD6J75JOLF7WVFGH2RXEBLOQ6OCVJTIA2JZDJLXAJ3 | 1 | GBZH6Z74OWID6ZP67KYNF7T5ES4APLZSISYO7GZGXW7PJNMFL4XNV3PT | beer | 100 | 0 | 1 | 363
[11:09] <stellar-slack> 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
[11:09] <stellar-slack> it won't work on your side if you're not running pg 9.5
[11:09] <stellar-slack> you're probably out of sync now
[11:10] <stellar-slack> @sacarlson: yes you can.. that's the whole point
[11:10] <stellar-slack> you can send transactions from accounts that don't exist
[11:10] <stellar-slack> your correct I'm "state" : "Catching up"
[11:11] <stellar-slack> ok what apt get libs exactly do I need for dependancies in debian ubuntu
[11:11] <stellar-slack> just the newer version of libpq?
[11:12] <stellar-slack> the don't seem to be seen in any of the repository I now have
[11:12] <stellar-slack> @buhrmi: use valgrind to catch these kind of errors
[11:13] <stellar-slack> http://raonyguimaraes.com/installing-postgresql-9-5-on-linux/
[11:36] <stellar-slack> @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 ^^
[11:37] <stellar-slack> need a 3rd party for multisign
[11:37] <stellar-slack> no, two is enough
[11:37] <stellar-slack> not sure how that would work with 2
[11:38] <stellar-slack> I think I found a way to delete 9.4
[11:38] <stellar-slack> https://github.com/stellar/stellar-core/tree/master/src/transactions
[11:39] <stellar-slack> that's an example with two signers
[13:51] <stellar-slack> ok we got the first transaction sent on @buhrmi open-core of qty 3 BEER's with no native fee's
[14:01] <stellar-slack> oh and yes an exchange of two different assets, that's a good example of a 2 party multi-sign transaction
[14:03] <stellar-slack> using offers or just two ops?
[14:04] <stellar-slack> Just two ops
[14:04] <stellar-slack> for the beer?
[14:06] <stellar-slack> yeah.. I mean, you could’ve just used the exchange to do that
[14:06] <stellar-slack> Have Sacarlson beer credits. Want: wine
[14:06] <stellar-slack> but multiple ops per tx is a really convenient thing
[14:07] <stellar-slack> 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
[14:08] <stellar-slack> with only 3 beer how much wine were you hoping to get? and with me backing them no less
[14:11] <stellar-slack> I would assume you are a trustworthy beer gateway
[14:38] <stellar-slack> hmmm how would a good UI for a 2 party multi sign transaction look like
[16:28] <stellar-slack> @dzham: what exchange?
[16:30] <stellar-slack> there is the built in exchange system built into stellar
[16:30] <stellar-slack> really no need for 2 party exchange but good to practice
[16:31] <stellar-slack> the offer system?
[16:32] <stellar-slack> yeah i think i gonna do offers next
[16:33] <stellar-slack> or three party multi-sign would be good for payment for goods that are delivered then signed for after recieveing
[16:34] <stellar-slack> i see
[16:46] <stellar-slack> 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
[16:47] <stellar-slack> in the same asset with the same issuer addresses
[16:48] <stellar-slack> since they keys are the same on both sides it might work
[16:51] <stellar-slack> that address would have to give trust on the one side and receive trust on the other side before deposits could be made, no?
[16:52] <stellar-slack> mhh i don't think i gonna explore that idea
[16:53] <stellar-slack> wanna do offers instead and trade some beer
[16:54] <stellar-slack> the gateways would have to exist on both networks I guess for it to work
[16:55] <stellar-slack> gateways I should mean the issuers
[16:56] <stellar-slack> I'm not totaly sure I thought this thrue. it would be easy with native but not totaly sure with non native for this
[16:58] <stellar-slack> 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
[16:59] <stellar-slack> wow I think you can even pass multi-sign through the gateway
[17:00] <stellar-slack> it's still all the same key sets so maybe it would work. need smarter people than me to think about it ha ha
[17:01] <stellar-slack> haha
[17:02] <stellar-slack> having the stellar-core friendbot issuing XLM as a regular asset from the same address on open-core would be super feasible tho.
[17:13] <stellar-slack> 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
[17:14] <stellar-slack> it would then show up on the other side at the same address and same issuer
[17:19] <stellar-slack> If anyone would like to contribute some discussion to a technical problem I’ve encountered in go-horizon: https://github.com/stellar/go-horizon/issues/86
[17:34] <stellar-slack> oh this is to look at historic trades that already happened @scott?
[17:34] <stellar-slack> yep
[17:35] <stellar-slack> you could, for example, drive a real-time stream of trades from the endpoint
[17:36] <stellar-slack> sounds useful but I'm not sure how it would be done
[17:37] <stellar-slack> the data I look at in the present core database is of what is to be or could be now what was
[17:41] <stellar-slack> 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
[17:41] <stellar-slack> 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.
[17:43] <stellar-slack> 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
[17:44] <stellar-slack> and price range if you like
[17:49] <stellar-slack> maybe I just didn't look at what the horizon data base already has in it
[17:49] <stellar-slack> You can see an example of a trade effect here: https://github.com/stellar/horizon/blob/master/spec/fixtures/scenarios/trades-horizon.sql#L345
[17:51] <stellar-slack> 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"
[17:55] <stellar-slack> ok so this is history on every trade event that is already captured?
[17:56] <stellar-slack> yep
[17:56] <stellar-slack> the format is unclear as to what I'm looking at but I think the info must be there
[17:56] <stellar-slack> that’s a pg_dump formatted sql file
[17:56] <stellar-slack> yes in some spread sheet it might be more clear
[18:02] <stellar-slack> 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.
[18:03] <stellar-slack> sorted by time
[18:04] <stellar-slack> but as things get big better to find a better way than what I would try to do
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of