<stellar-slack>
<sacarlson> I do note that my stellar-core has died at 20/10/2015 09:39 __core out of sync detected
<stellar-slack>
<sacarlson> and failed to restart with my auto reset program
<stellar-slack>
<sacarlson> strange when the other day I couldn't get it to fail even if I tried so something on the stellar end node set might be mest up?
<stellar-slack>
<jojopoper> ......,:(
<stellar-slack>
<sacarlson> but your account shows a return from the tools site\
<stellar-slack>
<jojopoper> I see. I'm debugging my program , connect to the horizon, but always returns timeout.
<stellar-slack>
<jojopoper> testnet and livenet
<stellar-slack>
<sacarlson> I'll give horizon a try from here to verify
<stellar-slack>
<jojopoper> ...I'm going to do some other things....,:(
<stellar-slack>
<sacarlson> horizon works ok from thailand at this time, performed transactions on this account GDSKZBPN7CHBHEIFHSDEDUOWJHTW5W6SNWTZMDWAK7OM6V5XMPXXTN5S ok
<stellar-slack>
<sacarlson> after manually reseting my stellar-core it is now also working
de_henne has quit [Remote host closed the connection]
Kwelstr has joined #stellar-dev
caseyj has joined #stellar-dev
<stellar-slack>
<sacarlson> ya jojopoper sometimes it's location specific for failures for me with some websites
<stellar-slack>
<sacarlson> all that I know is that it was working here at the time
<stellar-slack>
<sacarlson> oh and sometimes vpn around my problem works for me. as I think it's my ISP that sometimes filters stuf from me for reason I don't know
<bittrex-richie>
guys i'm playign with this right now
<bittrex-richie>
tryign to send a test payment
<bittrex-richie>
what is the "asset code"?
<stellar-slack>
<richiela> meh.. i guess i should jsut talk in here..
pixelb has joined #stellar-dev
<stellar-slack>
<scott> richiele: The asset system in the network has three types: native, “credit alphanum 4” and “credit alphanum 12”, the two credit types have an alphanumeric code and an issuer associated with them used to identify the asset
<stellar-slack>
<scott> for example
<stellar-slack>
<scott> take the “USD” asset issued by address “G123"
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack>
<richiela> hmm .. wth
<stellar-slack>
<richiela> sec trying again
<stellar-slack>
<richiela> hm i used memo as wel
<stellar-slack>
<richiela> did the exact same thing but got an error.. meh
<stellar-slack>
<jed> your error is that the destination doesn't exist
<stellar-slack>
<jed> you need to create the destination account first
<stellar-slack>
<richiela> erm... does it have to be "funded" to be created?
<stellar-slack>
<richiela> i mean i have the secret for it already
<stellar-slack>
<richiela> it was the root account that was created...
<stellar-slack>
<jed> yeah there is a separate tx to create an account now
<stellar-slack>
<scott> apparently that tool doesn’t really have a facility for creating arbitrary accounts
<stellar-slack>
<richiela> ok simple enough.. i can just create another oen and have the bot fund it i suppose
<stellar-slack>
<scott> yep
rejon has joined #stellar-dev
<stellar-slack>
<irisli> I have a question about the history store disk usage. How many GB of data do we expect stellar-core to save into the history? How big would it be if we had usage similar to the stellard network?
<stellar-slack>
<scott> it’ll be much smaller than the legacy network, given the inefficiencies of the SHAMap
<stellar-slack>
<irisli> but is there an estimate on the disk size a history store would likely want to have just in case?
<stellar-slack>
<jed> you mean for complete history?
<stellar-slack>
<irisli> i wonder if there is data on the current test net with stress test numbers
<stellar-slack>
<irisli> yea
<stellar-slack>
<irisli> if someone were to host a validator, how much disk space should they prepare to allocate?
<stellar-slack>
<jed> you don't need complete history to do that though
<stellar-slack>
<irisli> allocation (and requesting it in the beginning) is often easier than upsizing
<stellar-slack>
<irisli> Oh, i thought it was mandatory that a validator host history
<stellar-slack>
<jed> but you can look at how much testnet is taking up now: s3://history.stellar.org/prd/core-testnet/core_testnet_001
<stellar-slack>
<jed> no you don't need it
<stellar-slack>
<scott> I thought a validator needed to post/have available it’s own history
<stellar-slack>
<eva> that’s what Gr-aydon said in the preso, I thought
<stellar-slack>
<eva> (trying not to tag him cause he’s on vacation)
<stellar-slack>
<jed> no it needs to be able to get it form somewhere to be able to catch up. but once it is caught up it doesn't need to write it
<stellar-slack>
<jed> it will have the bucketlist and the SQL DB
<stellar-slack>
<scott> @irisli: the on-disk growth of history will be very predictable, anything over 10GB of space should last quite a long time
<stellar-slack>
<irisli> oh what about the history store size?
<stellar-slack>
<irisli> if someone wanted to host the store on their own server. If someone at a university wanted to run a node, they would need to figure out how to get these resources and it's just kinda hard to ask for a blank check from administration. Though i do understand this question is difficult to answer. Also, how do i see the size of that s3 folder?
<stellar-slack>
<jed> iris on testnet now a stellar-core would need 1.6GB of space for SQL and bucketlist
<stellar-slack>
<jed> there are maybe around 1M accounts there
<stellar-slack>
<scott> And that’s _with_ all the scrubbable data in txhistory and txfeehistory
<stellar-slack>
<jed> iris I'd just say 10GB + another 40GB if they want to store hsitory
rejon has quit [Read error: Connection reset by peer]
<stellar-slack>
<irisli> ok thanks for the more concrete numbers. It's a good start to have rough stats that can help guide things in the right direction
rejon has joined #stellar-dev
<stellar-slack>
<scott> horizon testnet may be rocky for a bit… I will be running some schema migrations and then updating history
<stellar-slack>
<eva> @jojopoper: really excited to see your go-stellar-wallet for Windows and Linux! Were you able to work out your timeout issues?