Logged Conversation (all times UTC)
[00:55] <stellar-slack> LOL https://github.com/stellar/stellar-core/blob/master/src/ledger/LedgerManagerImpl.cpp#L152
[00:55] <stellar-slack> ok...
[01:03] <stellar-slack> https://github.com/buhrmi/stellar-core/commit/d0de430c98edc22b708d8b24049f590ca9e7ccc7
[01:05] <stellar-slack> buhrmi: are you not going to charge tx fees?
[01:06] <stellar-slack> no
[01:07] <stellar-slack> how can i charge tx fee if there's no currency to charge it in ^_^
[01:07] <stellar-slack> what will prevent people from dos'ing the network?
[01:07] <stellar-slack> nothing
[01:08] <stellar-slack> common sense?
[01:08] <stellar-slack> i dunno
[01:09] <stellar-slack> I'm like ¯_(ツ)_/¯
[01:13] <stellar-slack> @lab: please tell china not to ddos me :O
[01:14] <stellar-slack> no. because ddos cost much than simple spamming..
[01:14] <stellar-slack> i don't know, i never ddos anyone lol
[01:16] <stellar-slack> i'd like store wikipedia in your ledger.
[01:16] <stellar-slack> why
[01:16] <stellar-slack> anyone else do it, why not be the first.
[01:16] <stellar-slack> :)
[01:17] <stellar-slack> you'd have to disect it into transactions
[01:17] <stellar-slack> will do it.
[01:17] <stellar-slack> LOL
[01:18] <stellar-slack> no god, no peace
[01:26] <stellar-slack> i bet this reset is the last before production.
[01:33] <stellar-slack> @sacarlson: i added history to the config file. it might work now https://github.com/buhrmi/stellar-core/blob/master/docs/stellar-core_testnet.cfg
[01:57] <stellar-slack> tokyo-stellar-history.json does not exist...
[02:00] <stellar-slack> ah, stellar-core -newhist tokyo
[02:09] <stellar-slack> @jed: is the -forcescp option needed? or are all nodes supposed to run without that option? if running without it the ledger number doesn't increase
[02:11] <stellar-slack> should only be necessary on the first N nodes if starting a network from nothing (N = quorum threshold)
[02:11] <stellar-slack> ah, okay... so after a while, (supposing the number of nodes gets larger), the -forcescp nodes can quit the network?
[02:13] <stellar-slack> what if N=0
[02:14] <stellar-slack> no idea what that would imply
[02:15] <stellar-slack> lowest I've used is 1
[02:15] <stellar-slack> but yes, so long as you have enough nodes to achieve quorum any should be able to leave the network, even the forcescp ones
[02:16] <stellar-slack> there's nothing really special about the forcescp nodes either though. It just tells them to kickstart the SCP event loop instead of letting it get triggered by seeing messages from peers
[02:16] <stellar-slack> with N=0 quorum is always achieved lol
[02:16] <stellar-slack> no idea ¯_(ツ)_/¯
[02:17] <stellar-slack> try it and see :)
[02:17] <stellar-slack> lol let's try
[02:19] <stellar-slack> need a peer
[02:20] <stellar-slack> the minimal to bootstrap need 3 nodes: start node1(forcescp), start node2(forcescp), start node3, restart node1, restart node2
[02:21] <stellar-slack> k
[02:22] <stellar-slack> lab: shouldn't need the restarts at the end
[02:26] <stellar-slack> if somebody wants to join the experiment, please compile from my sources and use this config https://github.com/buhrmi/stellar-core/blob/master/docs/open-core.cfg ^^
[02:38] <stellar-slack> ok buhrmi I'm now awake and will soon be ready to take a wack at it
[02:39] <stellar-slack> cool ... gonna work on the UI
[02:47] <stellar-slack> ETA: 379 seconds so it says @buhrmi
[02:47] <stellar-slack> excite ...
[02:47] <stellar-slack> what is it you have to put at this history place?
[02:47] <stellar-slack> amazon s3 tokyo region
[02:48] <stellar-slack> what is that some free storage or something?
[02:49] <stellar-slack> no
[02:54] <stellar-slack> ok I'm now synced
[02:54] <stellar-slack> Active Peers Address: 124.122.212.164:11625
[02:54] <stellar-slack> must be
[02:54] <stellar-slack> sweet
[02:55] <stellar-slack> now i wanna trust you with some beer
[02:55] <stellar-slack> I can try a transaction but not sure how it will work
[02:55] <stellar-slack> I'll try native first
[02:55] <stellar-slack> native won't work
[02:58] <stellar-slack> can't something that doesn't exist
[03:01] <stellar-slack> but trust should work
[03:01] <stellar-slack> this is my address GCICXSZOM7GE2KML5MN7VKQCSJJ3CEKGBFNJABPHTYTT5DDD5UTYMC7K
[03:13] <stellar-slack> I'm getting this error : /home/sacarlson/.bundle/gems/json-1.8.3/lib/json/common.rb:155:in `parse': 757: unexpected token at '{"exception": "sqlite3_statement_backend::prepare: near "WITH": syntax error"}' (Faraday::ParsingError)
[03:13] <stellar-slack> no idea what that is
[03:13] <stellar-slack> is that what your sending me?
[03:13] <stellar-slack> ah.... right ... it doesnt work with sqlite 3
[03:14] <stellar-slack> why is that?
[03:14] <stellar-slack> because the query i added isn't supported by sqlite 3
[03:14] <stellar-slack> on my side or your side?
[03:14] <stellar-slack> on your side... gonna change the config file and say that it requires postgres
[03:15] <stellar-slack> oh that sucks, that requires me to setup another postgress db
[03:16] <stellar-slack> sorry :(
[03:17] <stellar-slack> but it shoulb be enough if u just update the config ... it should create the DB by itself, no?
[03:17] <stellar-slack> u already got postgres running right?
[03:17] <stellar-slack> and the database browser for postgresql is not a cool as the one for sqlite
[03:18] <stellar-slack> no I think I have to create the db or I should say give it access to a db it will auto fill it with the tables
[03:18] <stellar-slack> ah
[03:21] <stellar-slack> but on the positive side with postgres I can also support horizon that as far as I know also doesn't support sqlite
[03:21] <stellar-slack> that I was able to finally get working last night with the help of scott
[03:21] <stellar-slack> wait, is horizon accessing the ledger db directly?
[03:22] <stellar-slack> it does yes
[03:23] <stellar-slack> you want to run horizon on your side? then I won't even need to change much of anything
[03:23] <stellar-slack> no i'm not touching horizon
[03:23] <stellar-slack> you need it at some point on the network
[03:24] <stellar-slack> why?
[03:24] <stellar-slack> to support the libs that pass between it
[03:24] <stellar-slack> stellarbase does not require horizon
[03:24] <stellar-slack> unless you want all clients to run cores
[03:25] <stellar-slack> yeah everybody should have a core :)
[03:25] <stellar-slack> I don't think you want to run a core on your android phone
[03:25] <stellar-slack> haha
[03:25] <stellar-slack> but it might work who knows
[03:26] <stellar-slack> i'm sending transactions directly to stellar-core via HTTP
[03:26] <stellar-slack> no need for horizon
[03:26] <stellar-slack> yes that's what I was doing but my goal is to have clients go to a horizon entity
[03:27] <stellar-slack> a minimal horizon doesn't do much
[03:27] <stellar-slack> yeah well u can still do that
[03:28] <stellar-slack> but i won't officially "recommend" using horizon"
[03:28] <stellar-slack> yes but to do it I will need to move to postgres as if you run it then I wouldn't have to
[03:28] <stellar-slack> i won't be running horizon, sorry
[03:28] <stellar-slack> what do you have against horizon ?
[03:28] <stellar-slack> nothing
[03:28] <stellar-slack> just don't need it
[03:29] <stellar-slack> ok I'll set it up then
[03:29] <stellar-slack> I don't know why we didn't have 2 horizon on testnet to start with
[03:30] <stellar-slack> what about the js-libs that use horizon? you have something to replace those?
[03:31] <stellar-slack> like my work around on ruby you must have that on js?
[03:41] <stellar-slack> wasn't as hard as expected, I moved to postgress for opencore
[03:42] <stellar-slack> I'll have the horizon hooked to it in a bit, last thing to figure out is how to make horizon public
[04:16] <stellar-slack> @buhrmi: I'm now getting {"status"=>"ERROR", "error"=>"AAAAAAAAAAD////7AAAAAA=="}
[04:17] <stellar-slack> probly lack of funds
[04:20] <stellar-slack> @fredolafritte: how do I get horizon to listen on all addresses not just localhost?
[04:35] <stellar-slack> I must be close with this sudo script/server -b 10.0.2.1 -p 3000 ; is that my only option to run as sudo?
[04:36] <stellar-slack> AAAAAAAAAAD////7AAAAAA== means bad sequence
[04:37] <stellar-slack> StellarBase.xdr.TransactionResult.fromXDR(new Buffer('AAAAAAAAAAD////7AAAAAA==', 'base64'))._attributes.result._switch.name => txBadSeq
[04:39] <stellar-slack> @sacarlson: try script/server -b 124.122.212.164 -p 3000 ? lol
[05:19] <stellar-slack> @bartek: i think it's impossible to delete a trustline with the js-stellar-base https://github.com/stellar/js-stellar-base/blob/master/src/operation.js#L138
[05:20] <stellar-slack> "0" and 0 are both falsey in JS so it would always create a line with in64 as limit
[05:20] <stellar-slack> should i file an issue?
[05:22] <stellar-slack> I've never tried to delete a trustline, I'll have to give it a try some time
[05:22] <stellar-slack> mhh, it works when the string "0", but not integer 0
[05:23] <stellar-slack> oh and I did try your above but it still comes out with localhost:3000 every time not sure why
[05:23] <stellar-slack> I don't see anything in config that controls it
[05:24] <stellar-slack> oh bad sequence your your thing is broken?
[05:24] <stellar-slack> no, but since there is no "createAccount" tx anymore, you don't know your sequence...
[05:25] <stellar-slack> so if you use "0" as the sequence it should work
[05:25] <stellar-slack> yes so it's broken
[05:25] <stellar-slack> if no sequence is returned just use 0 that might work
[05:25] <stellar-slack> 0 or 1, depending on whether the library you're using automatically adds +1
[05:26] <stellar-slack> wow have to try both if first fails
[05:26] <stellar-slack> or i don't know... maybe the core adds +1
[05:26] <stellar-slack> i don't know who does it... lol
[05:26] <stellar-slack> yes for nextseq I guess you add 1
[05:27] <stellar-slack> I'll try manualy seq 1 2 3 if they all fails then it's >>>>>>you
[05:28] <stellar-slack> just try 0 and 1 ^^
[05:30] <stellar-slack> I think it would have worked out of the box if you just set the configs to require zero and fee zero
[05:30] <stellar-slack> you still create accounts but with no balance
[05:31] <stellar-slack> so they will still have the start seqnum
[05:31] <stellar-slack> that way no changes needed on the client pointing side
[05:32] <stellar-slack> I think they also have the config for the master account start amount that you can also still set to zero
[05:33] <stellar-slack> mhh I get "txInsufficientBalance" when trying to changeTrust ..
[05:34] <stellar-slack> maybe you still have fee's set
[05:35] <stellar-slack> with just config changes you can also upgrade your core with off the shelf stellar-core pulls
[05:35] <stellar-slack> I'll make a config file for you to check out if it's all posible
[06:21] <stellar-slack> found a method to change listen bind to 0.0.0.0 for me I had to add this to config/boot.rb
[06:22] <stellar-slack> so with that I should assume you can now access your new network with horizon from http://stellar.ddns.net:3000|stellar.ddns.net:3000
[06:27] <stellar-slack> cool... but it's down atm, i'm fixing bugs
[07:02] <stellar-slack> oh mine wasn't working also I forgot to forward the port
[07:02] <stellar-slack> mine should be working now when yours starts again
[07:18] <stellar-slack> yeah i'm having some troubles with the implicit account creation
[07:18] <stellar-slack> when adding a row to the accounts table within a transaction, it's not available for update further down the transaction
[07:19] <stellar-slack> cause the transaction can only perform changes on rows that existed before it started
[07:21] <stellar-slack> so what's the plan then?
[07:27] <stellar-slack> working on it..
[08:06] <stellar-slack> it's running ... no idea if it's working tho
[08:07] <stellar-slack> it's not
[08:12] <stellar-slack> okay.. made some changes... looks good
[08:12] <stellar-slack> i can make trustlines on my fork
[08:12] <stellar-slack> Hey guys- i'm a non technical guy looking to learn more about stellar, if i could maybe pay someone as a consultant to answer some questions cheers!
[08:13] <stellar-slack> @alekar: will you pay me in sacarlson/beer ?
[08:13] <stellar-slack> if you lived in berlin hell yer
[08:14] <stellar-slack> haha
[08:14] <stellar-slack> re beer
[08:14] <stellar-slack> best beer in germany
[08:14] <stellar-slack> Erdinger?
[08:14] <stellar-slack> Schöfferburger Weizen?
[08:16] <stellar-slack> @alekar: best bet is to ask your questions here
[08:16] <stellar-slack> no need to pay anyone...
[08:22] <stellar-slack> augustiner helles
[08:23] <stellar-slack> Are you involved in building gateways here?
[08:26] <stellar-slack> yeah kinda
[08:26] <stellar-slack> basically the gateways provide the access to the stellar network? do they issue the user IOU's and then communicate with other gateways to trade based on a users request?
[08:27] <stellar-slack> i'm making a website where everybody can act as gateway
[08:27] <stellar-slack> gateways physically hold a users currency though right?
[08:28] <stellar-slack> so basically you get around any legal issues because each person just holds their own $
[08:33] <stellar-slack> but on a super basic level user X wants 100USD they have 80 Euro ( whatever the Forex rate is) they have to use a US gateway which communicates with an EU one? Then the euros are on you stellar wallet? Who provides the liquidity if there is no peer interested in selling those euros?
[08:38] <stellar-slack> @alekar: liquidity would come from independent market makers, who put up offers either directly USD/EUR or using XLM as a bridge currency
[08:42] <stellar-slack> so if you wanted to make a larger trade say 200,000k and it was relatively urgent you'd be at their mercy re-rates? What kind of competition exists or rules to stop market makers selling the currency at a poor rate?
[08:46] <stellar-slack> hard to say anything about competition… but poor rates (large spread) would attract other market makers
[08:48] <stellar-slack> what if.... nobody trusts anyone
[08:48] <stellar-slack> lol
[08:50] <stellar-slack> MM’s are there to make money, so they would have to trust some gateways
[09:04] <stellar-slack> man i suck at c++
[09:05] <stellar-slack> anybody can find out why getIsNew() always returns "368" (seems so random) allthough it should be either 0 or 1 ?
[09:05] <stellar-slack> https://github.com/buhrmi/stellar-core/blob/master/src/ledger/AccountFrame.cpp#L371
[09:05] <stellar-slack> maybe i'm declaring the variable in the wrong place... no clue.
[09:19] <stellar-slack> that’s a bit weird. you don’t ever modify it after setting to one :S
[09:19] <stellar-slack> i'm modifying it here https://github.com/buhrmi/stellar-core/blob/master/src/ledger/AccountFrame.cpp#L226
[09:19] <stellar-slack> but 10 lines further down i'm debugging and the output is "1"
[09:20] <stellar-slack> ah, references :)
[09:21] <stellar-slack> yeah ..... :O don't quite understand why it's "1" there and "368" somewhere else
[09:22] <stellar-slack> c++ has changed a lot since I used to use it
[09:26] <stellar-slack> thanks guys
[09:29] <stellar-slack> how much would a gateway cost to build? Aside from the compliance issues? pretty keen to get one made if possible
[09:31] <stellar-slack> depends on a lot of things.. the very simplest gateway wouldn’t cost anything, you can run it all manually
[09:35] <stellar-slack> if you want a gateway for fiat currencies, you have to decide if you want the bank account transfers automated, and then figure out how to integrate that with your bank. you’d want notifications for inbound transactions, and ability to send outbound transfers too
[09:48] <stellar-slack> I’m doing one for a custom asset right now, that’s a bit different.
[10:06] <stellar-slack> I basically want to create a gateway for people (like me) who find the process now a bit technical. I'm an expat and getting money from NZ to Germany is slow and costly.. Ideally it would be for fiat currencies initially in say 3 countries.. The hurdle is KYC/ Anti money laundering law and the amount each jurisdiction requires you hold in physical cash
[10:10] <stellar-slack> You wouldn’t be a bank, so you’d be full reserve. 1 NZD in the bank = 1 NZD in the network.
[10:11] <stellar-slack> Money transfers and being an expat sucks. That’s one of the big reasons I got into cryptocurrencies.
[10:11] <stellar-slack> If it helps the unbanked too, I’m all for it :)
[10:20] <stellar-slack> How can it be 368
[10:21] <stellar-slack> @alaka: lol fund me I'm building exactly that open source
[10:21] <stellar-slack> Alekar
[10:22] <stellar-slack> @buhrmi: are you assigning this variable somewhere?
[10:24] <stellar-slack> Just the initial one at declaration and then I pass a reference to the prepared statement
[10:25] <stellar-slack> where exactly?
[10:29] <stellar-slack> @dzham: so are you saying you the legal requirement is fulfilled as you hold every dollar you give out an IOU for? (not the KYC /AML)
[10:32] <stellar-slack> Legal requirement... good one
[10:32] <stellar-slack> well, this banking law stuff is complicated
[10:33] <stellar-slack> i know if you issue an IOU / digital money you are required to keep a large amount in physical bank accounts
[10:35] <stellar-slack> @buhrmi: i'd love to see what you're doing- so you're project is really giving people like me the ability to send money to themselves/others?- if you aren't making money from it either your KYC/AML requirements aren't there? Whats the sign up process and have you designed the interface etc? from my research of all the money transfer and crypto gateways the biggest barriers are the sign ups-it takes quite a
[10:35] <stellar-slack> company that is clearly killing it in this area ( great rates- super easy sign up- free debit card and withdrawals)
[10:35] <stellar-slack> Yeah well if u hold trust from someone for usd as long u actually possess the usd at any point in time so you can trade it back then there should be no problem
[10:35] <stellar-slack> Legally
[10:42] <stellar-slack> yep, its just if you wanted to provide a more federated gateway service- so you also operate the EUR end, and they trade that USD to Euro, you would either need liquidity or to have a relationship with a marker maker..
[10:46] <stellar-slack> "Relationship" is hard to define in that context
[10:46] <stellar-slack> But yes
[10:48] <stellar-slack> That relationship would have to mean "entitlement"
[10:51] <stellar-slack> @alekar: yeah, that *ought* to be the case.
[10:54] <stellar-slack> As long as you’re not selling air to anyone, there’s a clean record of who holds the titles to the funds
[10:54] <stellar-slack> But you should probably run it by a lawyer :)
[10:58] <stellar-slack> Unless u issue air as asset
[10:58] <stellar-slack> I’ve actually put some thought into carbon credits, that’s pretty close :)
[11:07] <stellar-slack> If someone trades some usd for your air u can legally sell air
[11:08] <stellar-slack> lol
[11:15] <stellar-slack> @alekar u can see progress on http://github.com/buhrmi/open-core|github.com/buhrmi/open-core
[11:15] <stellar-slack> It's supposed to run on my own core network tho but it would work with all stellar core networks
[11:50] <stellar-slack> > i think it's impossible to delete a trustline with the js-stellar-base @buhrmi: it expects strings. I updated stellar-base to throw an error when `limit` is not a string (version 0.3.11)
[13:02] <stellar-slack> I assume from what I see after failing to connect to stellar-core testnet is that it got reset
[13:03] <stellar-slack> I think scott mentioned yestarday he was planing on upgradeing horizon but didn't hear anything about a stellar-core reset
[13:07] <stellar-slack> oh no it's seem i'm in "state" : "Catching up"
[13:09] <stellar-slack> this is after I did a full reset cleaned out the db to start again
[13:13] <stellar-slack> sacarlson: note that you cannot connect to an official testnet core with my version of the core
[13:14] <stellar-slack> i made changes to the consensus protocol on my fork
[13:14] <stellar-slack> (dont know if you're still running my core)
[13:14] <stellar-slack> no I shut yours down
[13:15] <stellar-slack> I was testing my last change of get_lines_balance expecting to find the lines I already created but they aren't there
[13:15] <stellar-slack> k
[13:16] <stellar-slack> i'm resetting often before the launch
[13:27] <stellar-slack> I'm getting a new error now even if I run standalone
[13:38] <stellar-slack> I have to go back to fred's 0c4c858... to get anything to even come up
[13:40] <stellar-slack> maybe something to do with files intermigled with your new version @buhrmi ? I checked /tmp and don't see any files there
[13:41] <stellar-slack> the error message looks like you dont have a validation_seed in your config
[13:51] <stellar-slack> it has one, I even took it out thinking if not there it would autocreate one. maybe it's mispelled
[13:51] <stellar-slack> but this was working with this same config before
[15:05] <stellar-slack> possible my first accepted pr, https://github.com/stellar/stellar-core/pull/723 @monsieurnicolas @jed :)
[15:59] <stellar-slack> lab: I don't get it? cfg.load(cfgFile); will cfg.load("-") ?
[16:50] <stellar-slack> as buhrmi said seems my validation_seed must have been the last error as I put it back in with a new validation_seed and reset I get the original fault
[16:52] <stellar-slack> as far as I know it was running the same code with same configs. When it failed to come up I tried full reset and still stuck.
[16:55] <stellar-slack> I'm still running stellar-core commit b179493a328955f8927d367c712bf0dd7341f3e7
[16:56] <stellar-slack> @sacarlson: I’m running 5182572c7cbe76a76ef444682e7213e6e273c7e1 and it works
[16:57] <stellar-slack> testnet was reset to 5182572c7cbe76a76ef444682e7213e6e273c7e1 yesterday… I wouldn’t expect any prior version to be able to catchup. The XDR definitions changed
[17:01] <stellar-slack> oh thanks for telling us, I'll update
[17:02] <stellar-slack> @sacarlson: https://stellar-public.slack.com/archives/dev/p1441062491000371
[17:06] <stellar-slack> man i'm getting really weird random behaviour with AccountFrame
[17:09] <stellar-slack> c++ isn't my strength
[17:12] <stellar-slack> ya c++ is not as much fun
[17:22] <stellar-slack> ok I now have steller-core 51825... running ok
[23:02] <stellar-slack> If anyone wants to do some review:
[23:02] <stellar-slack> https://github.com/stellar/horizon/pull/49
[23:03] <stellar-slack> https://github.com/stellar/go-horizon/pull/81
[23:03] <stellar-slack> The above pull requests implement the API change proposed in: https://github.com/stellar/stellar-protocol/issues/20
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of