04:45 <stellar-slack> <jed> lab: what does your history scanning tool do?

06:27 <stellar-slack> <lab> jed, it generates a sequence of 0x40*n -1 and check whether the files are in history/transactions/results/ folders

06:29 <stellar-slack> <lab> notice, it doesn't check the contents nor buckets folder.

06:55 <stellar-slack> <sacarlson> ok I suck at java script so sue me ha ha

06:57 <stellar-slack> <sacarlson> at least I have basic control of the multi-sign-websocket from the browser now. as before I used ruby websocket clients. I guess I'll need to learn a bit more about using the js. libs and also port some of my basic message signing and verify tools into js

06:57 <stellar-slack> <buhrmi> i think sucking at javascript is not breaking any laws

06:58 <stellar-slack> <sacarlson> I was just hoping someone else would figure it out long before me

08:19 <stellar-slack> <raymens> How do you, as Stellar, manage/upgrade/run your core and horizon services?

09:58 <stellar-slack> <sacarlson> ok not that it maters but what is the difference in features bettween stellar-sdk.js and stellar-sdk.min.js besides being about 1/3 the size?

09:58 <stellar-slack> <sacarlson> I guess at full version only 1.7mb it's small enuf already

10:00 <stellar-slack> <dzham> @sacarlson: they’re the same thing. .min.js is just whitespace optimized/obfuscated

10:01 <stellar-slack> <sacarlson> so you use the min.js then?

10:01 <stellar-slack> <dzham> yeah

10:01 <stellar-slack> <dzham> only use the other one for reading

10:01 <stellar-slack> <sacarlson> as I just started to read the docs I'm seeing things I didn't know existed. looks cool

10:02 <stellar-slack> <sacarlson> oh ic

10:59 <stellar-slack> <sacarlson> of my first error after I installed stellar-sdk I put the native_payment.js example in the dir that has the dir js-stellar-sdk when I run node native_payment.js the Error: Cannot find module 'js-stellar-sdk'

10:59 <stellar-slack> <sacarlson> I must be running from the wrong base dir

11:02 <stellar-slack> <sacarlson> I assumed it was the file in the dist

11:02 <stellar-slack> <sacarlson> but I also tried making a symbolic link to that in the dir I was running from

11:02 <stellar-slack> <dzham> just run `npm install stellar-sdk`

11:02 <stellar-slack> <sacarlson> already did that

11:03 <stellar-slack> <sacarlson> it creates the dir with the modules

11:03 <stellar-slack> <dzham> you’re doing `require ‘stellar-sdk’`in your .js file?

11:03 <stellar-slack> <sacarlson> I think so

11:04 <stellar-slack> <sacarlson> I just copied the sample that I thought was already setup with that

11:04 <stellar-slack> <dzham> oh, wait.. where did you put native_payment.js? in node_modules?

11:05 <stellar-slack> <sacarlson> var StellarSdk = require('js-stellar-sdk')

11:05 <stellar-slack> <sacarlson> so that's not name correctly in the example?

11:05 <stellar-slack> <dzham> the folder you have native_payments.js in should have a node_modules folder

11:06 <stellar-slack> <dzham> Ah! no, it’s called stellar-sdk only

11:08 <stellar-slack> <sacarlson> oh so none of the example work out of the box then

11:11 <stellar-slack> <sacarlson> ok that fix the missing file part

11:12 <stellar-slack> <sacarlson> { type: 'https://stellar.org/horizon-errors/not_found', title: 'Resource Missing', status: 404,

11:12 <stellar-slack> <sacarlson> this might be what you get when the account is bad?

11:15 <stellar-slack> <sacarlson> if this is the source account in this file server.loadAccount("GCEZWKCA5VLDNRLN3RPRJMRZOX3Z6G5CHCGSNFHEYVXM3XOJMDS674JZ") were does it get the seed for this account?

11:16 <stellar-slack> <sacarlson> best I find a create account example in js maybe that might work

11:22 <stellar-slack> <sacarlson> (function (exports, require, module, __filename, __dirname) { let StellarLib = ^^^^^^^^^^ SyntaxError: Unexpected identifier

11:23 <stellar-slack> <sacarlson> I'm not sure there are any working example in here

11:33 <stellar-slack> <sacarlson> I'm not sure there are any working examples. this one has at least 2 errors I can see and I can't even read js

11:34 <stellar-slack> <sacarlson> ReferenceError: server is not defined

11:34 <stellar-slack> <dzham> loadAccount uses the address to check with Horizon what the sequence number is, that’s all… no seed needed (yet)

11:34 <stellar-slack> <sacarlson> it helps when I start from at least one working example, from there I can move on

11:35 <stellar-slack> <sacarlson> well that was a payment transaction so at some point it will need a seed

11:37 <stellar-slack> <dzham> ``` /* global require, console, Buffer */ (function () { 'use strict'; var stellar = require('stellar-sdk'); var server = new stellar.Server({ hostname: 'http://horizon-testnet.stellar.org|horizon-testnet.stellar.org', port: 443, secure: true }); stellar.Network.useTestNet(); var seed = 'SBADPREUF6NNS3LXLLSRN6YJZT3VQRKFQLWUAA2YKPCCA4FJSWZRLWJW'; var key = stellar.Keypair.fromSeed(seed); funct

11:37 <stellar-slack> server.loadAccount(key.address()) .then(function (account) { var transaction = new stellar.TransactionBuilder(account) .addOperation(stellar.Operation.setOptions({ signer: { address: 'GDXWWC643RSHGPUEGTIGYBLUMWON3WZXXURDEWJC7DSGKK74ME3YQSAZ', weight: 1 } })) .addOperation(stellar.Operation.setOptions({ signer: { address: 'GBSJBNTNW57LDIRCUE7A6KFNFQ437PVOBBUCANVDYHWONWOTIAR3TRK

11:37 <stellar-slack> .addOperation(stellar.Operation.setOptions({ signer: { address: 'GBZJW4L54EOKYPRA5M2APJJKBY2GRMJQCCXWFEI4QMQBQIH7AB53ZMXW', weight: 1 } })) .addOperation(stellar.Operation.setOptions({ masterWeight: 0, lowThreshold: 2, medThreshold: 2, highThreshold: 2 })) .addSigner(key) .build(); return server.submitTransaction(transaction); }) .then(console.log) .catch(c

11:37 <stellar-slack> createContractAccount(key); })(); ```

11:38 <stellar-slack> <dzham> @sacarlson: ^^that should work, that’s what I use to set up my multi-sig contract accounts...

11:38 <stellar-slack> <sacarlson> well that looks like it might work but I prefer starting from simple. but I'll add that to my example files I'm collecting

11:39 <stellar-slack> <dzham> just change the operation to a payment, and you’re set

11:41 <stellar-slack> <sacarlson> well for the most basic example I guess I'll makes two accounts and and send native from one to the other. for others to get the idea

11:42 <stellar-slack> <sacarlson> then I'm going to replace this line return server.submitTransaction(transaction); to send it to mss-server instead as another simple example

11:43 <stellar-slack> <dzham> ``` var tx = new stellar.TransactionBuilder(account) .addOperation(stellar.Operation.payment({ destination: msg.destination, amount: msg.amount, asset: stellar.Asset.native() })) .addSigner(signer) .build(); ```

11:43 <stellar-slack> <dzham> ^^^ for a payment

11:45 <stellar-slack> <sacarlson> that can't be complete

11:45 <stellar-slack> <dzham> it’s not.. but replace the transaction in the first example with this

11:52 <stellar-slack> <raymens> Shouldn't the mention at https://github.com/stellar/docker-stellar-core#single-node-configurations me removed now?

12:00 <stellar-slack> <sacarlson> we aren't far now with your added transaction [ReferenceError: msg is not defined]

12:01 <stellar-slack> <dzham> oh, yeah, you’d have to change amount and destination

12:02 <stellar-slack> <sacarlson> yes I can see that

12:02 <stellar-slack> <sacarlson> for this it will just be hard coded to test

12:06 <stellar-slack> <sacarlson> boy I'm going to stick with ruby ha ha. with error they don't give line numbers

12:06 <stellar-slack> <sacarlson> undefined

12:06 <stellar-slack> <sacarlson> what might be undefined now?

18:50 <stellar-slack> <scott> FYI: if anyone is building horizon themselves, we’re about to remove go 1.4 support (https://github.com/stellar/horizon/pull/160) so that we can surface database connection metrics.

21:04 <stellar-slack> <scott> Is anyone here GAB2KFKTAQWHWZAUHC6AEGX5MPVIOLMGZT4BLB6O7LCA43VBYPOJIYTQ? Could you please stop spamming horizon-testnet, if so? I’d prefer to leave rate limiting off for the time being but won’t really have a choice if it doesn’t stop

23:10 <stellar-slack> <sacarlson> darn and I missed the activity, seems my stellar-core wasn't running at the time

23:11 <stellar-slack> <sacarlson> my last window of running only showed 27 transactions

23:13 <stellar-slack> <sacarlson> but I do see there are over 400k accounts on the ledger

23:15 <stellar-slack> <scott> oh, this person isn’t spamming the core network, they’re just loading https://horizon-testnet.stellar.org/accounts/GAB2KFKTAQWHWZAUHC6AEGX5MPVIOLMGZT4BLB6O7LCA43VBYPOJIYTQ over and over again

23:15 <stellar-slack> <scott> It’s not really hurting anything.. it’s just making the logs annoying to watch

23:24 <stellar-slack> <sacarlson> and thanks @bartek you read my mind as I couldn't figure out how to change base fee in the js-stellar-sdk I see you now have that fixed so I don't need this line var transaction = new stellar.TransactionBuilder(account,{fee:100})

23:41 <stellar-slack> <sacarlson> how would I translate this line to what's used in js-stellar-sdk from ruby b64 = tx.to_envelope(funder).to_xdr(:base64), I want the base64 string

23:45 <stellar-slack> <sacarlson> when I view it with this console.log(transaction) it's broken into what's seen in the structure

23:48 <stellar-slack> <sacarlson> never mind I found it: console.log(transaction.toEnvelope().toXDR().toString("base64"))