Logged Conversation (all times UTC)
[02:01] <stellar-slack> 2015-04-16T22:09:12.655 8837d6 [Ledger] INFO Got consensus: [seq=3436, prev=b765e8, time=1429222147, txs=0, txhash=9e42c8, fee=10]
[02:01] <stellar-slack> 2015-04-16T22:09:12.655 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3436
[02:01] <stellar-slack> 2015-04-16T22:09:12.655 8837d6 [Ledger] WARN this round of catchup will fail.
[02:01] <stellar-slack> stellar-core: src/scp/Slot.cpp:235: void stellar::Slot::bumpToBallot(const stellar::SCPBallot &): Assertion `!mIsCommitted && !mIsExternalized' failed.
[02:01] <stellar-slack> Aborted
[02:02] <stellar-slack> 2015-04-16T22:08:52.421 8837d6 [Ledger] INFO Got consensus: [seq=3431, prev=443748, time=1429222128, txs=0, txhash=cf5511, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:08:52.422 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3431
[02:02] <stellar-slack> 2015-04-16T22:08:52.422 8837d6 [Ledger] WARN this round of catchup will fail.
[02:02] <stellar-slack> 2015-04-16T22:08:57.622 8837d6 [Ledger] INFO Got consensus: [seq=3432, prev=fad5fc, time=1429222132, txs=0, txhash=ae013b, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:08:57.623 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3432
[02:02] <stellar-slack> 2015-04-16T22:08:57.623 8837d6 [Ledger] WARN this round of catchup will fail.
[02:02] <stellar-slack> 2015-04-16T22:09:01.243 8837d6 [Herder] ERROR HerderImpl::valueExternalized@dac306 Externalized txSet not found: 5ef653 [HerderImpl.cpp:685]
[02:02] <stellar-slack> 2015-04-16T22:09:01.951 8837d6 [Ledger] INFO Got consensus: [seq=3433, prev=890287, time=1429222137, txs=0, txhash=5ef653, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:09:01.951 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3433
[02:02] <stellar-slack> 2015-04-16T22:09:01.951 8837d6 [Ledger] WARN this round of catchup will fail.
[02:02] <stellar-slack> 2015-04-16T22:09:03.587 8837d6 [Ledger] INFO Got consensus: [seq=3434, prev=2171db, time=1429222138, txs=0, txhash=16ab34, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:09:03.588 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3434
[02:02] <stellar-slack> 2015-04-16T22:09:03.588 8837d6 [Ledger] WARN this round of catchup will fail.
[02:02] <stellar-slack> 2015-04-16T22:09:08.175 8837d6 [Ledger] INFO Got consensus: [seq=3435, prev=c0fd7e, time=1429222143, txs=0, txhash=cf6322, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:09:08.175 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3435
[02:02] <stellar-slack> 2015-04-16T22:09:08.175 8837d6 [Ledger] WARN this round of catchup will fail.
[02:02] <stellar-slack> 2015-04-16T22:09:12.655 8837d6 [Ledger] INFO Got consensus: [seq=3436, prev=b765e8, time=1429222147, txs=0, txhash=9e42c8, fee=10]
[02:02] <stellar-slack> 2015-04-16T22:09:12.655 8837d6 [Ledger] INFO Out-of-order close during catchup, buffered to 38 but network closed 3436
[02:03] <stellar-slack> nice to see two people hit the same error. Should be reproducable :simple_smile:
[08:13] <stellar-slack> @matschaffer: thanks for fixing the friend bot. I'm onto stage 3 of the tutorial now :wink:
[10:25] <stellar-slack> This morning in Aussie (~12h ago)
[10:25] <stellar-slack> ```2015-04-17T07:37:12.696 1e6e68 [Ledger] INFO Got consensus: [seq=3410, prev=62e9bd, time=1429222029, txs=0, txhash=17378a, fee=10]
[10:25] <stellar-slack> 2015-04-17T07:37:12.696 1e6e68 [Ledger] INFO Catchup awaiting checkpoint (ETA: 0 seconds), buffering close of ledger 3410
[10:25] <stellar-slack> 2015-04-17T07:37:17.143 1e6e68 [Ledger] INFO Got consensus: [seq=3411, prev=4b1bfb, time=1429222032, txs=0, txhash=8bb149, fee=10]
[10:25] <stellar-slack> 2015-04-17T07:37:17.143 1e6e68 [Ledger] INFO Catchup awaiting checkpoint (ETA: 0 seconds), buffering close of ledger 3411
[10:25] <stellar-slack> 2015-04-17T07:37:23.253 1e6e68 [Overlay] ERROR TCPPeer::writeHandler error to 54.225.54.235:39133 [TCPPeer.cpp:194]
[10:25] <stellar-slack> 2015-04-17T07:37:23.290 1e6e68 [Overlay] ERROR TCPPeer::drop shutdown failed: shutdown: Transport endpoint is not connected [TCPPeer.cpp:413]```
[10:53] <stellar-slack> @paulfurley: any time. Sorry it took awhile. Had to get our friend bit surgeon a_ndrew on the job
[13:31] <stellar-slack> So, moving my question over from newcomers. So I understand there's a public/private key pair called `public_key`, `master_seed` respectively
[13:32] <stellar-slack> But what's the relation to the `account_id` (which I think is synonymous with `address`?) and my username? Where are these relationships stored, if anywhere? Can I make a wallet that's *only* a public/private keypair and no account_id (a la bitcoin) or does that not make sense in Stellar?
[13:34] <stellar-slack> for 2.0 I think the public key is the same as your account_id (in 1.0 it was hashed first)
[13:35] <stellar-slack> the username -> account_id is in stored in a db
[13:35] <stellar-slack> and that’s mostly for convenience
[13:36] <stellar-slack> Ahh
[13:36] <stellar-slack> it’s perfectly fine to create a keypair on your own, without registering a username
[13:36] <stellar-slack> And I can derive an account ID from the public key
[13:36] <stellar-slack> (are we on 2.0 or 1.0 currently?)
[13:36] <stellar-slack> I got back a different account id / public key from the dev tutorial thing
[13:36] <stellar-slack> well, both :simple_smile:
[13:37] <stellar-slack> the dev tutorial is about 2.0
[13:38] <stellar-slack> OK, so doing `curl -X POST https://test.stellar.org:9002 -d '{"method":"create_keys"}'` gave me a different account id and public key
[13:38] <stellar-slack> so maybe still a hash happening?
[13:39] <stellar-slack> that’s still running on 1.0
[13:39] <stellar-slack> Ah
[13:39] <stellar-slack> account_id’s in 2.0 are longer
[13:42] <stellar-slack> Is there a 2.0 test endpoint I can play with?
[13:44] <stellar-slack> hmmm, strange… maybe they’ve changed things up.
[13:45] <stellar-slack> I'm glad I'm not the only one who's baffled :simple_smile:
[13:45] <stellar-slack> a couple of days ago the account_id’s where longer
[13:45] <stellar-slack> Oh right
[13:49] <stellar-slack> stellar addresses are not fixed size (can be between 32-35 characters as far as I can remember). to be honest, I’m not sure how address generation looks in 2.0 but in tutorial at: https://www.stellar.org/galaxy/ keys are generated using old stellar-lib (https://github.com/stellar/stellar-lib) what makes me think that address generation hasn’t changed (yet?)
[13:50] <stellar-slack> @bartek: I got a 256-bit address when I went through the tutorial some days ago
[13:51] <stellar-slack> gihTP3fQgvqZ8eCg5Lt1ZWqLwy554vMgP75sYNyug9V56zn8nV
[13:52] <stellar-slack> https://stellar-public.slack.com/archives/dev/p1429023150000994
[13:54] <stellar-slack> Now I’m confused.. somehow I got a 256-bit account_id.. I might have curl:ed something manually, but I’m not running any stellar-core myself
[13:54] <edubai0> hi guys.. i signed for stellar and linked my facebook account.. but i didnt get any stellars ?
[13:56] <stellar-slack> @dzham: I was wrong - check scott’s message from above
[13:56] <stellar-slack> > The only reason account addresses will change is because we’re no longer running the public key through `SHA256 * RIPEMD160` before encoding to base58check.
[13:57] <edubai0> it says Oops!
[13:57] <edubai0> You've already claimed this reward.
[13:57] <edubai0> current balance 0
[13:57] <edubai0> why ?
[13:58] <stellar-slack> @edubai0 what’s your username?
[13:58] <edubai0> ddxxbb
[13:59] <stellar-slack> @bartek: yeah, I was talking with Scott about that last week, so I know there’s a change… I’m just trying to figure out how I generated a 2.0-style account_id if it wasn’t through the galaxy tutorial
[14:02] <stellar-slack> @dzham: it seems it’s generated using UInt256 class:
[14:02] <stellar-slack> ```
[14:02] <stellar-slack> var address = stellar.UInt256.from_bits(bits);
[14:02] <stellar-slack> var outputAddress = stellar.Base.encode_check(stellar.Base.VER_ACCOUNT_ID, address.to_bytes());
[14:02] <stellar-slack> ```
[14:02] <stellar-slack> and not using "normal” method:
[14:02] <stellar-slack> ```
[14:02] <stellar-slack> var seed = seed = new Seed().random();
[14:02] <stellar-slack> var address = keyPair.get_address();
[14:02] <stellar-slack> ```
[14:02] <stellar-slack> (`get_address` runs SHA256_RIPEMD160 on public key)
[14:04] <stellar-slack> So, if I generated a keypair offline and (like a cold Bitcoin wallet), is it still possible to send to it? Or does the public key need to be stored by Stellar somewhere?
[14:04] <stellar-slack> eg I never tell anyone the public key / address until I try to send to it from another wallet
[14:06] <stellar-slack> you can send to it. however a network will take a creation fee (20 STR) https://www.stellar.org/faq/#_Why_is_there_a_minimum_balance
[14:08] <stellar-slack> Ah cool, and thanks for the FAQ which I clearly should have read
[14:08] <stellar-slack> :thumbsup:
[14:10] <stellar-slack> (Although the FAQ seems like a well-kept secret- I can't find any link to it :stuck_out_tongue: )
[14:15] <stellar-slack> Oh, Its supposed to be in the footer - it might have gotten moved, let me make sure someone puts it back. Thanks for pointing that out!
[14:16] <stellar-slack> no worries :simple_smile:
[14:39] <stellar-slack> So @gmarceau : we should not download txsets and quorum slices upfront, this at worst opens an amplification attack on the network, at best causes nodes to download a lot of information they don't need (stuff from parts of the network they don't care about).
[14:45] <stellar-slack> sorry I didn't realize this earlier, I am kinda heads down in the SCP library rework
[14:50] <stellar-slack> @paulfurley: are you particularly interested in the unreleased iteration, or happy to get onto the current ("live" / "working") version?
[14:50] <stellar-slack> If the latter, I could send you some STR for testing purposes.
[14:51] <stellar-slack> @epsilon: Happy with current - I'm just trying to figure out what I can actually do. Thanks, that'd be cool
[14:52] <stellar-slack> have you created a keypair on the live system? If so, bump me your gXXXX addie
[14:52] <stellar-slack> Yep, one sec
[14:53] <stellar-slack> epsilon: gL5sofBS89DewSz2bu6xek9whkhaFcjT5u
[14:53] <stellar-slack> and you;ve saved your sXXX secret, correct?
[14:54] <stellar-slack> epsilon Excellent question. hold fire.
[14:54] <stellar-slack> kk
[14:54] <stellar-slack> we don;t need to see it -- just you *will* need it :simple_smile:
[14:55] <stellar-slack> epsilon: This is the "secret key" field that I can reveal at https://launch.stellar.org/#/settings ... right?
[14:55] <stellar-slack> yes.. seems you;re good to go
[14:55] <stellar-slack> brb
[14:55] <stellar-slack> you should see a transfer within 30s if you have that screen up
[14:55] <stellar-slack> Magic, thanks
[14:56] <stellar-slack> no worries
[14:57] <stellar-slack> epsilon: Cha-ching
[14:57] <stellar-slack> fast, eh?
[14:57] <stellar-slack> Not too shabby :simple_smile:
[14:57] <stellar-slack> these blokes know what they're doing, mate
[14:57] <stellar-slack> lol
[14:58] <stellar-slack> And a good few ladies too apparently! Which is great to see :simple_smile:
[14:59] <stellar-slack> yeah it's a bit matriarchal
[14:59] <stellar-slack> keeps the blokes honest, I s'pose
[14:59] <stellar-slack> :simple_smile:
[14:59] <stellar-slack> Where are y'all based?
[15:00] <stellar-slack> Australia here
[15:00] <stellar-slack> Oh cool
[15:00] <stellar-slack> only in winter
[15:00] <stellar-slack> :wink:
[15:01] <stellar-slack> As in, you go to Australia during its cold bit? (Damn, the southern hemisphere confuses me :P)
[15:01] <stellar-slack> no, we're only cool in winter
[15:01] <stellar-slack> Ah OK
[15:04] <stellar-slack> So who / how many does Stellar employ?
[15:05] <stellar-slack> no clue mate, I'm a blow-in
[15:05] <stellar-slack> (fly on the wall)
[15:05] <stellar-slack> newcomers and general will answer
[15:05] <stellar-slack> Gotcha
[15:07] <stellar-slack> Cheers for the Stellars @epsilon. Not sure what to do with them but I'm sure that won't last long :simple_smile:
[15:07] <stellar-slack> Their website had 17 people on it when I checked a few weeks ago
[15:10] <stellar-slack> they're a bit of a machine 'tho, so that figure equates to 28 or more if comparing to less adept gangs (like Google, et al)
[15:11] <stellar-slack> Awesome
[16:00] <stellar-slack> @monsieurnicolas: i share your concern, my sense was that jed disagrees or otherwise prefers this route for now.
[16:01] <stellar-slack> @paulfurley: FAQ should be back in the footer now:)
[16:05] <stellar-slack> I don't see why we'd do throw away work if we think it's wrong. I guess it depends if it takes us further or closer to where we want to be in terms of code organization. Is your branch in a semi reviewable state?
[16:10] <stellar-slack> yes, more or less. you should be able see where I'm headed, broadly: https://github.com/gmarceau/stellar-core/tree/item-fetching-cleanup
[16:11] <stellar-slack> I pull out the `mFutureEnvelope` into a `PendingEnvelopes` class: https://github.com/gmarceau/stellar-core/blob/item-fetching-cleanup/src/herder/PendingEnvelopes.h
[16:13] <stellar-slack> will take on the additional responsibility of fetching all dependent items before release the envelope to Herder
[16:18] <stellar-slack> you need to check the txset when you get in a ballot. otherwise you don't know if you should forward the ballot on or not.
[16:20] <stellar-slack> I could see waiting to ask for the qset but it also makes it way simpler to just fetch it before you send it into SCP
[16:24] <stellar-slack> not fetching the qset doesn't really limit peoples ability to dos the network. There are plenty of other ways. General prevention of that is slated for a bit later.
[17:01] <stellar-slack> my point is exactly this: with nodes that are behaving well, we download a bunch of useless stuff. the txset is likely going to be quite different across the network so we're coupling things that should not be coupled at a global level.
[17:01] <stellar-slack> if we were to download only when we think the value is interesting, the network will already have eliminated a bunch of redundant ones (if we keep the way we have it right now, we can at least not download old tx sets for old statements). same with the quorum sets: if I can reach quorum without knowing about certain nodes's setup in the corner of the galaxy, then we don't need to download it.
[17:06] <stellar-slack> @guillaume: I think you're pulling too much logic into the this fetching code. It should not have to deal with any of the subtleties of the queue management that feeds into SCP. Herder is the one dealing with SCP.
[17:18] <stellar-slack> `PendingEnvelope` _is_ that queue management code. The fetching code is getting moved to ItemFetcher.
[17:19] <stellar-slack> Herder is getting big, so I'm cutting the queue management section of it into its own class.
[17:21] <stellar-slack> @monsieurnicolas: if we are only flooding ballots with valid txsets. then we shouldn't be downloading a bunch of useless stuff
[17:23] <stellar-slack> whether we prefetch or not, the itemfetcher / pendingenvelop work will be useful. it's cleaning up lots of loose code.
[17:49] <stellar-slack> under what constraint is there loose code that should need cleaning?
[19:00] <stellar-slack> i'm not sure what you mean by constraints
[19:01] <stellar-slack> following the paper
[19:01] <stellar-slack> @jed in `checkFutureCommitted` : "we probably want to fetch the txset here to save time"
[19:01] <stellar-slack> what does it mean?
[19:21] <stellar-slack> this is obsolete, we'll fetch them right away as soon as we try to externalize
[19:21] <stellar-slack> and this triggers externalize
[20:24] <stellar-slack> it is obsolete if we fetch all of them when we get the ballot in. But not if we don't fetch till we want to externalize
[20:28] <stellar-slack> I think you mean this https://github.com/stellar/stellar-core/issues/441 ; the code for downloading is still in externalize
[20:33] <stellar-slack> that'll be easy to address in the code i'm writing now.
About StellarVerse IRC Logger
StellarValue IRC Logger
is part of