<stellar-slack1>
<dzham> @jed: yeah, but who gets the inflation? ;)
<stellar-slack1>
<sacarlson> by what I see the time stamps on the posts here and what I see on github I'm not sure what the horizon stellar-core is running. should I assume dcda8bbbe656122c537097500c7122bcad4e4939
<stellar-slack1>
<dzham> speaking of homeDomain, BTW, is reverse federation documented anywhere? Should I assume it works the same as previously?
<stellar-slack1>
<sacarlson> reverse federation?
<stellar-slack1>
<sacarlson> I'll try change it to verify it works the same. sounds like they might filter to be sure it's lower case or something
<stellar-slack1>
<sacarlson> maybe it has to be in email like format me@atmy.house
<stellar-slack1>
<sacarlson> they took down testnet from 11:24pm - 1:56am my time the last update to stellar-core was at 5:25 am my time so the commit number I just posted can't be correct
<stellar-slack1>
<lab> the threshhold to get inflation is 50 million, i think hulukan has a change to get
<stellar-slack1>
<sacarlson> what is inflation? does that mean that the price of transactions goes up?
<stellar-slack1>
<sacarlson> as from what I just read it already has
<stellar-slack1>
<lab> jed: i don't know which one is correct, base_fee is 1000 or 10?
<stellar-slack1>
<sacarlson> I have my fee set in my code to 10 due to compatibiilty bettween open-core that needed it set to zero
<stellar-slack1>
<sacarlson> thanks eva I'll read it
<stellar-slack1>
<sacarlson> any clue @monsieurnicolas as to what commit code they used on the horizon testnets stellar-core?
<stellar-slack1>
<sacarlson> before I start to compile that take like 20 min on my slow computer I would like to know I'm compiling what's needed
<stellar-slack1>
<monsieurnicolas> we're running "85472c7" on testnet right now
<stellar-slack1>
<jed> lab: 10. I already fixed it
<stellar-slack1>
<sacarlson> thanks that's what I wanted
<stellar-slack1>
<sacarlson> so inflation of 1% per year if the base of the percent is the starting capital of XLM that is 100,000,000,000 would be 1,000,000,000 per year or as paid weekly as noted in your link @eva that would be 19,230,769.23 XLM per week paid to people by inflation?
<stellar-slack1>
<sacarlson> oh maybe I'm still counting in integer
<stellar-slack1>
<sacarlson> that didn't totaly answer my question but added a few more questions. but from the sound of it, it will be some time before the MIN_VOTE will be reached but the first one that gets it will probly get a big one with the all the unallocated lumens inflation being added to the fee pool
<stellar-slack1>
<sacarlson> as jed's link failed to mension what the base distribution of XLM is they left it a mistery
<stellar-slack1>
<sacarlson> and on the good side as far as I am concerned is that the inflation as set by your docs does not change fee's charged. only inflation or deflation in fees we might see is if the value of XLM changes
<stellar-slack1>
<sacarlson> my first error seen in attempted stellar-core compile probly due to only doing make
<stellar-slack1>
<sacarlson> next attempt as I should have done it had I followed the instructions: ./autogen.sh ; ./configure; make
<stellar-slack1>
<sacarlson> ETA 40 sec
<stellar-slack1>
<sacarlson> I hope this stellar-core build has what I needed fixed that is ability to delete signers
<stellar-slack1>
<sacarlson> otherwise you will have many unneeded accounts left on the testnet from my play
<stellar-slack1>
<sacarlson> first attempts at transaction with horizon I can create account ok. but sending a native transaction I get no return from horizon at all
<stellar-slack1>
<sacarlson> I normaly see something like: {"hash":"4d3bc7e9d1faef87e3ab024b993e93d9a3ae186d571480632c3ba92f299ce516","result":"received","error":null}
<stellar-slack1>
<sacarlson> seems to return an empty string
<stellar-slack1>
<sacarlson> I'll try point at my local stellar-core
<stellar-slack1>
<sacarlson> before I did I added some added error capture prints but I ran it a third time and it worked so I must have some problems on my side?
[7] has quit [Disconnected by services]
TheSeven has joined #stellar-dev
<stellar-slack1>
<sacarlson> very strange as it fails most the time but the return when it fails is rescue failure at send_tx_horizon response.class NilClass: e.response.class String: empty string
<stellar-slack1>
<buhrmi> Sacarlson u don't need to set fee to 0 on open-core. Any fee is being ignored.
<stellar-slack1>
<sacarlson> yes I know but if I don't need to change it I don't
<stellar-slack1>
<sacarlson> it's just that it was already changed and set in my default on both networks
TheSeven has quit [Disconnected by services]
[7] has joined #stellar-dev
stellar-slack1 has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<sacarlson> I switch to pointing at my local stellar-core but now that has gone to "state" : "Catching up"
<stellar-slack>
<sacarlson> I'll try soft reset it
<stellar-slack>
<sacarlson> even now that I'm synced it's giving me sequence errors so I'm going to try soft reset stellar-core
<stellar-slack>
<sacarlson> ok after the soft reset of my stellar-core everything seems to work at least on the first try. so maybe the problems on horizon are what I see as sequence failures here
<stellar-slack>
<buhrmi> I wonder if I should submit a PR that turns stellar-core into open-core lol
<stellar-slack>
<buhrmi> might not be the best idea :P
<stellar-slack>
<sacarlson> why not just have 2 cores ha ha
<stellar-slack>
<sacarlson> let the masses decide
<stellar-slack>
<buhrmi> well i'll keep my fork auto-mergeable
<stellar-slack>
<sacarlson> auto-mergeable? cool
<stellar-slack>
<buhrmi> I wanna have the changes I made to the code base professionally audited tho...
<stellar-slack>
<sacarlson> professionally? that means you will have to pay me some more beer
<stellar-slack>
<sacarlson> I found a major bug in my code that must be the cuase of my original problems
de_henne has joined #stellar-dev
<stellar-slack>
<buhrmi> Haha yeah I'd be happy to pay via trustline balance xD
<stellar-slack>
<buhrmi> Actually...
<stellar-slack>
<buhrmi> Actually...
<stellar-slack>
<buhrmi> I think I gonna add passphrase support back in and let it run on the same network as stellar public and leave it in a state of constant disagreement
<stellar-slack>
<sacarlson> I think that's what bitcoin is now doing with block size that is about to or already split
<stellar-slack>
<buhrmi> i think that would be the smart™ thing to do
<stellar-slack>
<sacarlson> no I think it's causing tecnical problems on there network also cuasing devaluation
<stellar-slack>
<buhrmi> but i'm all for bitcoin devaluation
<stellar-slack>
<sacarlson> why would it benifit you that bitcoin is devalued?
<stellar-slack>
<sacarlson> makes your dogcoins more valued?
<stellar-slack>
<buhrmi> not only mine
<stellar-slack>
<sacarlson> hay I have a new idea oposite of yours buhrmi, I'll make a branch of stellar-core that instead of having no native as yours has would instead have a non-native currency as it's method to pay it's fee's that is based on USD
<stellar-slack>
<sacarlson> or beer?
<stellar-slack>
<sacarlson> with me of course being the issuer
<stellar-slack>
<sacarlson> but I think that's the same is stellar?
<stellar-slack>
<sacarlson> so never mind
pixelb has joined #stellar-dev
<stellar-slack>
<buhrmi> lol
<stellar-slack>
<buhrmi> i retired my forks of stellar-base libs as the open-core fork now operates on the exact same parameters as stellar core
<stellar-slack>
<buhrmi> so any transaction sent into stellar-core live net should also be recognized by open-core
<stellar-slack>
<sacarlson> that meaning? you site with the info now displays stellar testnet?
<stellar-slack>
<sacarlson> http://open-core.org|open-core.org is not opening from here today but my network is doing some strange things
<stellar-slack>
<sacarlson> like no longer have access to google from http://google.com.th|google.com.th as the thailand nic is no longer working
<stellar-slack>
<buhrmi> it should open again, was in the middle of a deploy
<stellar-slack>
<sacarlson> ya it now opens but the last transactions show homedomain changes that don't show on stellar-core network so it's not synced
<stellar-slack>
<buhrmi> huh? the networks are not supposed to be synced
<stellar-slack>
<sacarlson> I thought you said they were the same?
<stellar-slack>
<buhrmi> open-core and stellar-core will live in a state of constant disagreement
<stellar-slack>
<sacarlson> oh I think IC
<stellar-slack>
<buhrmi> like, not only a code-fork but also a network-fork
<stellar-slack>
<sacarlson> well these are things the network should already have expected and should handle it. as I've run older version of stellar-core and it's just ignored
<stellar-slack>
<buhrmi> exactly
<stellar-slack>
<sacarlson> same settings with same fee's now?
<stellar-slack>
<buhrmi> ah well, actually only the pass phrase is the same ... i've updated the readme with all the differencies now
<stellar-slack>
<sacarlson> oh ok all the same but same pass phrase but the genisis will differ
<stellar-slack>
<buhrmi> yes
<stellar-slack>
<sacarlson> what does this mean? Requires axiomatic trust in configured validator nodes
<stellar-slack>
<sacarlson> axiomatic? like aximoron?
<stellar-slack>
<sacarlson> oh but that's what I am so ...
<stellar-slack>
<sacarlson> I looked it up ax·i·o·mat·ic ˌaksēəˈmadik/ adjective adjective: axiomatic self-evident or unquestionable. but I am still a moron so don't get it
<stellar-slack>
<sacarlson> ah and I'm am a self-evident moron as I know I am one?
<stellar-slack>
<buhrmi> it means ... if you configure a node as a trusted validator, you can't blame anything but yourself if that node decides to go mad
<stellar-slack>
<sacarlson> wow ok. but in simple terms I think it mean is needs that big number leter thing in the config
<stellar-slack>
<buhrmi> it means: be careful who you trust
<stellar-slack>
<sacarlson> ah ok, and there is provisions in the config options to place different trust in different nodes
<stellar-slack>
<buhrmi> yeah you can do that via the quorum thresholds
<stellar-slack>
<sacarlson> oh ya that too as they are set very lax now
<stellar-slack>
<sacarlson> how long has your present configured core been running?
<stellar-slack>
<sacarlson> at present when there is any type of failure on horizion it provides little or no info so may have been your cores influence
<stellar-slack>
<buhrmi> just reset it like an hour ago or two
<stellar-slack>
<sacarlson> oh no but it was my problem with my timing error that didn't provide needed time for the sequence number to even advance by one
<stellar-slack>
<buhrmi> lol my core is not configured in SDF's quorum so it can't influence anything
<stellar-slack>
<sacarlson> true
<stellar-slack>
<buhrmi> the three SDF cores look at my core and be like "what the f**k do you want?"
<stellar-slack>
<buhrmi> lol
<stellar-slack>
<sacarlson> I'm not sure they would ever see you unless you added there nodes in your config list
<stellar-slack>
<sacarlson> but even if you did your right they would ignore you
<stellar-slack>
<buhrmi> yup
<stellar-slack>
<monsieurnicolas> Also, in case of a split like this, your node will just stay stuck forever, not closing ledgers
<stellar-slack>
<buhrmi> -forcescp
gst has quit [Quit: leaving]
gst has joined #stellar-dev
gst has joined #stellar-dev
pixelb has quit [Ping timeout: 240 seconds]
<stellar-slack>
<monsieurnicolas> no force scp won't cause it to close ledgers - just to attempt to vote on a ledger from the start
de_henne has quit [Remote host closed the connection]
<stellar-slack>
<buhrmi> vote? vote with who? the SDF nodes aren't even in my quorum.
<stellar-slack>
<jed> yeah that just means you are in a different network
<stellar-slack>
<buhrmi> yeah
<stellar-slack>
<buhrmi> it's running, ledgers are being closed. the contents of the ledgers is not the same among the network forks but that shouldn't be an issue. that's... "by design" i guess