11:21 <stellar-slack> <veerasarma> Hi i am using stellar api its working fine

11:21 <stellar-slack> <veerasarma> but i have one problem

11:21 <stellar-slack> <veerasarma> var StellarSdk = require('stellar-sdk') var server = new StellarSdk.Server('https://horizon-testnet.stellar.org'); var accountId = 'GBBORXCY3PQRRDLJ7G7DWHQBXPCJVFGJ4RGMJQVAX6ORAUH6RWSPP6FM'; server.transactions() .forAccount(accountId) .call() .then(function (page) { console.log('Page 1: '); console.log(page.records); return page.next(); }) .then(function (page)

11:21 <stellar-slack> console.log(page.records); }) .catch(function (err) { console.log(err); });

11:22 <stellar-slack> <veerasarma> i am using the above code get transactions but it have only 10 records in the page so i got only 20 records

11:22 <stellar-slack> <veerasarma> how can i get more records

11:22 <stellar-slack> <veerasarma> please help me

11:22 <stellar-slack> <veerasarma> awaiting for your response

11:23 <stellar-slack> <veerasarma> Or give the way to remove this pagewise record option

13:08 <stellar-slack> <powderfan> by default, transactions for account is limited to 10 records: https://www.stellar.org/developers/horizon/reference/transactions-for-account.html try '`.limit(30)

13:17 <stellar-slack> <powderfan> How are you guys dealing with the tests? I just run `stellar-core --test` and it runs all testcases as expected. However, when finished, I find it hard to determine the outcome. The console closes immediately. My current workaround (on a windows machine) is to pipe the console output into a file `stellar-core --test > testslog.txt` and later search that file for `FAILED`. Any better suggestion?

13:21 <stellar-slack> <powderfan> Furthermore 5 tests keep failing (both on my fork/branch but also on the original code base)

16:58 <stellar-slack> <chretien> @bartek: never mind for the charge-back question. I see how to now.

17:11 <pigeons> chretien: how?

17:17 <stellar-slack> <chretien> I guess, two ways: 1. In case funds are on hold for a cc charge, use the transaction-multisig mechanism to release the hold when the charge is not validated and 2) if the charge has been validated, simply initiate a "reverse" payment

17:41 <stellar-slack> <chretien> guys, how to issue credits or update account balance with a non-native currency?

17:44 <stellar-slack> <chretien> in the case of a gateway, how does one create a "hot wallet" linked to a bank account though the bank API and then issue credits in the bank account's currency?

17:44 <stellar-slack> <irisli> @chretien: to issue a credit, you simply send the credits using the gateway account

17:45 <stellar-slack> <irisli> and to create a "hot wallet" linked to your bank API, you would have to write code connecting your Stellar accounts to your bank API

17:46 <stellar-slack> <chretien> from what I see here https://www.stellar.org/developers/learn/integration-guides/building-blocks/account-management.html at the account creation, I can only populate it with lumens. How to populate it with a different currency?

17:47 <stellar-slack> <irisli> Funding an account can only be done with lumens because it is required for the account be on the network

17:47 <stellar-slack> <irisli> only after you have created the account can you send a payment of an asset

17:48 <stellar-slack> <irisli> This is because accounts need to fulfill the minimum balance to be allowed on the network: https://www.stellar.org/developers/learn/concepts/fees.html#minimum-balance

17:48 <stellar-slack> <irisli> Once you have the account, you can use a Payment operation: https://www.stellar.org/developers/learn/concepts/list-of-operations.html#payment

17:50 <stellar-slack> <chretien> @irisli: any guide on how to go about this? >and to create a "hot wallet" linked to your bank API, you would have to write code connecting your Stellar accounts to your bank API

17:51 <stellar-slack> <irisli> Some of it is code you would have to write on your own

17:51 <stellar-slack> <irisli> This would be helpful to you: https://www.stellar.org/developers/learn/integration-guides/gateway.html

17:53 <stellar-slack> <chretien> @irisli: yeah I've been looking at that gateway integration guide, but I don't see how to issue new assets in the network

17:55 <stellar-slack> <irisli> @chretien: To issue a new asset to the network, you need 2 steps: 1. Have the receiver submit a transaction with a `Change Trust` operation to trust the gateway account 2. Have the gateway account submit a transaction with a `Payment` operation sending the specified asset to the receiver

17:56 <stellar-slack> <chretien> @irisli: Oh ok that simple :P, thanks

17:59 <stellar-slack> <irisli> yeah its kinda so simple that it throws people off

17:59 <stellar-slack> <chretien> @irisli: so as a gateway, while creating stellar account on behalf of users, how to get the minimun lumens required?

17:59 <stellar-slack> <irisli> to get lumens, you would have to buy them on an exchange

17:59 <stellar-slack> <irisli> though another thing you may consider is not having an account for each user

18:00 <stellar-slack> <irisli> and just having a few gateway accounts operated on behalf of the user

18:00 <stellar-slack> <irisli> this would save you the trouble of managing many accounts and funding them

18:01 <stellar-slack> <chretien> makes sense, thanks

18:03 <stellar-slack> <chretien> @irisli: any other best practices like that one, while creating a gateway?

18:04 <stellar-slack> <irisli> We are still working on guides on how to do that. You might also want to take a look at the compliance protocol

18:05 <stellar-slack> <chretien> cool

18:05 <stellar-slack> <irisli> the compliance protocol will help you be able to interact with other gateways

18:05 <stellar-slack> <irisli> but that is for when you seriously operate a gateway

18:06 <stellar-slack> <irisli> As in, it is very useful for if you were running a gateway following regulations. But while you're exploring the Stellar protocol, you don't need it to learn about how it work

18:07 <stellar-slack> <eva> @chretien: I’d also highly recommend subscribing to the releases mailing list, where we send any important software update info https://www.freelists.org/list/sdf-releases

18:10 <stellar-slack> <chretien> for a payment processor, that uses stellar as a backend, what's the "best" scenario to make a payment from clientA to merchantA assuming we have API access to bank APIs of clientA and merchantA?

18:10 <stellar-slack> <chretien> I mean what would be the appropriate design of that backend?

18:15 <stellar-slack> <chretien> would it be as simple as creating one stellar account for each of those banks and use one "hot wallet" for all transactions of the same bank?

18:16 <stellar-slack> <chretien> and in case clientA and merchandA are both using the same bank, what's the advantage of going through the stellar network to make a payment?

18:18 <stellar-slack> <irisli> well, if you have API access to the banks of client A and merchant A. You could just send a bank transfer and not need Stellar

18:19 <stellar-slack> <irisli> Alternatively, if client A and merchantA are going to be on the Stellar network, you could send credits rom one to another

18:20 <stellar-slack> <irisli> The advantage of going through the Stellar network is that it is a lot faster and cheaper to send the transaction

18:21 <stellar-slack> <irisli> if you used a bank transfer, that could take several hours or a day and cost a lot of fees

18:25 <stellar-slack> <chretien> I see. So then I would need to create a stellar account for clientA and merchantA in addition to the the bankA hot wallet if both are using bankA, right?

18:27 <stellar-slack> <chretien> or I should simply use only the bankA hot wallet and the bank API?

18:28 <stellar-slack> <irisli> just a nit pick is that you wouldn't have a account called `bankA` but rather `gatewayA` unless you ARE the bank

18:28 <stellar-slack> <chretien> (y)

18:28 <stellar-slack> <irisli> It depends on how you want to do the accounting. If you're doing transfers from yourself to yourself, you don't need to use Stellar

18:29 <stellar-slack> <irisli> and by yourself to yourself, I mean if all your customers are managed by you and you have one Stellar account, then all it takes to send from merchantA and clientA (both registered under you) would be to subtract some balance from merchantA and add some to clientA in your database

18:30 <stellar-slack> <irisli> I think the confusing part is that here we are talking about combining the gateway and the payment processor

18:30 <stellar-slack> <irisli> they are actually 2 separate things

18:30 <stellar-slack> <chretien> yes

18:32 <stellar-slack> <irisli> A close analogy would be Gateway is a bank while the processor is like Stripe

18:33 <stellar-slack> <chretien> exactly. How would Stripe work if it was using stellar?

18:34 <stellar-slack> <irisli> in this hypothetical situation, lets say you are a merchant using Stripe (with Stellar support). A user that has an account with another processor would be able to send a transaction to your account at Stripe paying you credits in SomeBank

18:35 <stellar-slack> <irisli> Stripe would accept SomeBank credits and then once Stripe has received them, they can go to SomeBank and change it for cash

18:39 <stellar-slack> <chretien> great

18:41 <stellar-slack> <irisli> but the thinking here is that who you are receiving payments from or sending to do NOT have to be with the same processor as you

18:41 <stellar-slack> <irisli> or even with the same gateway

18:41 <stellar-slack> <irisli> and this is where Stellar shines the most: interoperability

18:43 <stellar-slack> <irisli> The sender's payment processor doesn't have to hold credits issued by the gateway of another processor. They can just buy them just for the duration of the transaction and never actually hold them.

18:46 <stellar-slack> <chretien> got it