pigeons_ is now known as pigeons
pigeons is now known as Guest21333
Guest21333 is now known as pigeons
victortyau has joined #stellar-dev
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
de_henne_ has quit [Ping timeout: 250 seconds]
<stellar-slack> <steelheaddigital> Is the stellar-wallet project dead? I'm guessing so since the build is failing and it hasn't been touched in 6 months. https://github.com/stellar/stellar-wallet
<stellar-slack> <steelheaddigital> If so, is there a replacement or another reference implentation? Thanks
<stellar-slack> <sacarlson> steelheaddigital: that looks to be some kind of server based walled. what kind of a wallet are you looking for? there is the https://github.com/TbLtzk/Centaurus that I would recomend as a client side wallet
<stellar-slack> <sacarlson> it's also available as an android app on google playstore
<stellar-slack> <jed> the stellar-wallet was a way to store people's private keys such that the server didn't have access to them. They were retrievable by username/password. Is that what you need?
victortyau has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
victortyau has joined #stellar-dev
victortyau has quit [Client Quit]
<stellar-slack> <steelheaddigital> yeah, that's what I'm looking for. I've got my own implementation in the works, but if there's something out there already I'd rather use that. In my experience it's best not to roll your own when it comes to security/cryptography. I'm not a complete neophyte when it comes to those things, but they aren't my specialty either.
<stellar-slack> <steelheaddigital> Thanks @sacarlson, that looks promising. At least a good reference
<stellar-slack> <sacarlson> so client side then?
<stellar-slack> <sacarlson> and yes Centaurus is simple and basic and is what I've also used as my reference
<stellar-slack> <steelheaddigital> yes, for a web app, but with encrypted seed stored on the server. All encryption happens in the browser based on user's password so the server never knows the actual seed. That's the idea anyway. Obviously kind of scary since it needs to be done right to be secure.
<stellar-slack> <steelheaddigital> That's basically what stellar-wallet did from what I can tell.
<stellar-slack> <sacarlson> IC ya people are used to being able to reset there password if they loose it, but the standard case with stellar if you loose the secret seed, you have permanetly lost the account
<stellar-slack> <sacarlson> so good to hear you are working on this case method. I just backup my keys
koolhead17 has joined #stellar-dev
<stellar-slack> <steelheaddigital> I guess I'll keep on with my implementation. It will be open source, so hopefully I can just get a lot of eyes on it to make sure I don't make any mistakes with the crypto or design. What do you say @jed, would you be willing to take a look?
<stellar-slack> <jed> steelheaddigital: you might just want to bring the stellar-wallet up to date then. It shouldn't be too hard to get it working.
<stellar-slack> <jed> it is the server side of what you need
<stellar-slack> <steelheaddigital> Hmmm... OK, I'll give that a go. Thanks
<stellar-slack> <jed> bartek is probably the most familiar with how it was left I'll ask him what it would take
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
TheSeven has quit [Ping timeout: 245 seconds]
TheSeven has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
<stellar-slack> <steelheaddigital> Great, thanks a lot
bit2017 has quit [Ping timeout: 245 seconds]
bit2017 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
<stellar-slack> <bartek> @steelheaddigital: it's not a problem with `stellar-wallet` itself but with dependencies we use. a few months ago node 4.x was released thus all packages that are using node bindings must be updated. I tried to upgrade all of deps we're using in stellar-wallet to the versions that support node 4.x but there's at least one that hasn't been updated yet: https://github.com/schamane/node-syslog/pull/49 (it's used
<stellar-slack> stellar-wallet). so if you want to use it, switch to node 0.10 - I've just confirmed it's working (nvm can help you a lot). I subsribed to `node-syslog` PR so I will updated our deps when it's merged.
koolhead17 has quit [Remote host closed the connection]
nivah has joined #stellar-dev
bit2017 has quit [Ping timeout: 240 seconds]
nivah has quit [Ping timeout: 272 seconds]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
stadja has joined #stellar-dev
<stadja> Hello guys :)
<stellar-slack> <jed> hi stadja
<stadja> just to know: is the horizon-testnet down ?
<stadja> I mean
<stadja> can you do transactions ?
<stadja> Right now, all my transactions get me a "Transaction Failed The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html"
<stadja> but it is possible that I am the one failing :)
<stellar-slack> <bartek> can you post extras here?
<stellar-slack> <jed> what is the result_code
<stadja> tx_bad_seq
<stellar-slack> <jed> yeah how are you making the tx?
<stadja> my envelope is
<stadja> AAAAAKBW/Lr6XtWHZFarEXil1+1Aw1wqBGAKnt7ddpMZFw26AAAD6AAgdbQAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAAGEs9pYm5PTJxNK5qUGzH3hmfWyb2EMTj3Kif0vOxHGMAAAAAAAAAAAvrwgAAAAAAAAAAARkXDboAAABAghFFjsoJCrNzkw/dStY1FWV7cctc5UO+QO1fASq4OPMb9c0GZYmM3ENLdgfA8WDxACkM0S8TIo70t5dHKmpmAA==
<stadja> envelope_xdr :"AAAAAKBW/Lr6XtWHZFarEXil1+1Aw1wqBGAKnt7ddpMZFw26AAAD6AAgdbQAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAAGEs9pYm5PTJxNK5qUGzH3hmfWyb2EMTj3Kif0vOxHGMAAAAAAAAAAAvrwgAAAAAAAAAAARkXDboAAABAghFFjsoJCrNzkw/dStY1FWV7cctc5UO+QO1fASq4OPMb9c0GZYmM3ENLdgfA8WDxACkM0S8TIo70t5dHKmpmAA=="
<stellar-slack> <jed> your seq num needs to be 1 higher
<stadja> result_xdr :"AAAAAAAAAAD////7AAAAAA=="
<stadja> hmmm
<stadja> my seq num ...
<stadja> what is it ?
<stellar-slack> <bartek> @stadja hold on
<stadja> ok
<stellar-slack> <jed> stadja: how are you making this tx?
stadja has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
stadja2 has joined #stellar-dev
<stadja2> I had a connection problem
<stadja2> did you send me anything the last 2 minutes ?
<stellar-slack> <jed> yeah how are you making this tx?
<stadja2> with the sdk
<stadja2> I show you
<stellar-slack> <jed> ok in JS
<stadja2> server.loadAccount(senderPublicAddress)
<stadja2> .then(function (account) {
<stadja2> // create a new transaction using StellarSdk's TransactionBuilder
<stadja2> var transaction = new StellarSdk.TransactionBuilder(account, {
<stadja2> // add a memo to the transaction if they gave one
<stadja2> memo: ""
<stadja2> })
<stadja2> // add a "payment" operation to the transaction
<stadja2> .addOperation(StellarSdk.Operation.payment({
<stadja2> destination: recipientPublicAddress,
<stadja2> asset: new StellarSdk.Asset('xlm'),
<stadja2> amount: amountToBeSent
<stadja2> }))
<stadja2> // sign the transaction with the account's secret key
<stellar-slack> <jed> there is a bug that we fixed yesterday. We need to roll it out.
<stellar-slack> <jed> doing that now
<stellar-slack> <bartek> @stadja please upgrade to stellar-sdk ver. 0.4.0 and it should work
<stadja2> ok...
<stadja2> did you update the bower version ?
<stellar-slack> <bartek> yes
<stadja2> ok, because with the last version on bower I couldn't do StellarSdk.Keypair.random().address()
<stadja2> because address() was undefined
<stadja2> (it wasd this morning, I am in france, so 10 hours ago)
<stellar-slack> <bartek> address is depreciated and we removed it in the last minor release (0.4.0), you accountId instead
<stellar-slack> <bartek> use*
<stadja2> cool
<stadja2> and uuuuh
<stadja2> .addSigner(StellarSdk.Keypair.fromSeed(senderPrivateKey))
<stadja2> addSigner is deprecated too ?
<stellar-slack> <bartek> yes, please use transaction.sign(keypair)
<stadja2> keypair ?
<stellar-slack> <bartek> `senderPrivateKey` in your case
<stadja2> uuuh ok :)
<stellar-slack> <bartek> I mean `transaction.sign(StellarSdk.Keypair.fromSeed(senderPrivateKey))`
<stadja2> where can I find the changelod (i know, on the github, right ?)
<stellar-slack> <bartek> there is no changelog in js libs (yet) but here you can see diff between new minor and the last 0.4.x: https://github.com/stellar/js-stellar-base/compare/v0.4.22...v0.5.0
<stadja2> hmmmm transaction.sign is not a function
<stellar-slack> <bartek> can you share your code?
<stadja2> yes
<stadja2> server.loadAccount(senderPublicAddress)
<stadja2> .then(function (account) {
<stadja2> var transaction = new StellarSdk.TransactionBuilder(account, {
<stadja2> // create a new transaction using StellarSdk's TransactionBuilder
<stadja2> memo: ""
<stadja2> // add a memo to the transaction if they gave one
<stadja2> })
<stadja2> // add a "payment" operation to the transaction
<stadja2> .addOperation(StellarSdk.Operation.payment({
<stadja2> destination: recipientPublicAddress,
<stadja2> asset: new StellarSdk.Asset('xlm'),
<stadja2> amount: amountToBeSent
<stadja2> }))
<stadja2> // sign the transaction with the account's secret key
<stadja2> and if I do
<stadja2> var transaction = new StellarSdk.TransactionBuilder(account, {
<stadja2> // add a memo to the transaction if they gave one
<stadja2> memo: ""
<stadja2> });
<stadja2> // add a "payment" operation to the transaction
<stadja2> transaction.addOperation(StellarSdk.Operation.payment({
<stadja2> destination: recipientPublicAddress,
<stadja2> asset: new StellarSdk.Asset('xlm'),
<stadja2> amount: amountToBeSent
<stadja2> }));
<stadja2> // sign the transaction with the account's secret key
<stadja2> transaction.sign(StellarSdk.Keypair.fromSeed(senderPrivateKey));
<stadja2> transaction.build();
<stadja2> TypeError: transaction.sign is not a function
<stellar-slack> <bartek> ``` server.loadAccount(senderPublicAddress) .then(function (account) { // create a new transaction using StellarSdk's TransactionBuilder var transaction = new StellarSdk.TransactionBuilder(account, { memo: "" // add a memo to the transaction if they gave one }) // add a "payment" operation to the transaction .addOperation(StellarSdk.Operation.payment({ destination: recipientPublicAddress, asset: new StellarS
<stellar-slack> amountToBeSent })) .build(); // sign the transaction with the account's secret key transaction.sign(transaction.sign(StellarSdk.Keypair.fromSeed(senderPrivateKey))) ```
<stellar-slack> <jed> stadja: have you tried slack. This channel is also there http://slack.stellar.org|slack.stellar.org and the UI is a bit better
<stadja2> yes but whenever I send a request it doesn't answer me :)
<stadja2> stadja@gmail.com
<stadja2> I never receive that email
<stellar-slack> <bartek> oops, copy paste bug. should be: ``` transaction.sign(StellarSdk.Keypair.fromSeed(senderPrivateKey)) ```
<stadja2> so what is the difference between your snippet and mine ? You build first and then you sign it right ?
<stellar-slack> <bartek> yes, you sign a built transaction
<stadja2> but I have the feeling that it is still the same problem... is the .min.js up to date there
<stadja2> ?
<stadja2> TypeError: transaction.sign is not a function
<stellar-slack> <bartek> are you sure you have `build()` before `sign()`? as in my snippet?
<stadja2> server.loadAccount(senderPublicAddress)
<stadja2> .then(function (account) {
<stadja2> // create a new transaction using StellarSdk's TransactionBuilder
<stadja2> var transaction = new StellarSdk.TransactionBuilder(account, {
<stadja2> // add a memo to the transaction if they gave one
<stadja2> memo: ""
<stadja2> });
<stadja2> // add a "payment" operation to the transaction
<stadja2> transaction.addOperation(StellarSdk.Operation.payment({
<stadja2> destination: recipientPublicAddress,
<stadja2> asset: new StellarSdk.Asset('xlm'),
<stadja2> amount: amountToBeSent
<stadja2> }));
<stadja2> transaction.build();
<stellar-slack> <bartek> change the last 2 lines to: ``` })).build(); ```
<stadja2> Yep, that the same problem
<stadja2> (hey, can you send me a slack invite ?)
<stadja2> I have transaction.signers
<stadja2> but not transaction.sign in my debugger
<stellar-slack> <bartek> @stadja, it should work, just like in tests: https://github.com/stellar/js-stellar-base/blob/master/test/unit/transaction_test.js#L38-L41 (just change `StellarBase` to `StellarSdk`.
<stadja2> I KNOW !
<stadja2> haha :)
<stadja2> found it
<stadja2> it's transaction = transaction.(...).build();
<stadja2> that was missing
<stellar-slack> <bartek> yeah...
<stadja2> it's not updating the transaction object
<stadja2> it's returning a new transaction object with another signature
<stadja2> cool
<stadja2> And so,
<stadja2> now,
<stadja2> it works !
<stadja2> THAT IT GREAT :)
<stadja2> thank's guys
<stellar-slack> <bartek> :thumbsup:
<stadja2> yeah
<stadja2> a new happy futur stellar dev
<stadja2> well not stellar dev, but dev using stellar :)
<stellar-slack> <jed> cool. and we'll try to figure out what is happening with your slack invite
<stellar-slack> <jed> stadja2: " I double checked and Slack does have him as a member. This means that if he logs into https://stellar-public.slack.com and clicks “forgot password” he should be able to reset it."
<stadja2> Hey that worked !
stadja2 has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
<stellar-slack> <stadja> and now, from inside slack: that worked
<stellar-slack> <stadja> cool.
koolhead17 has quit [Remote host closed the connection]
<stellar-slack> <eva> whoo welcome @stadja, and sorry for the trouble. Great to have you :)
bit2017 has joined #stellar-dev
bit2017 has quit [Ping timeout: 240 seconds]
<stellar-slack> <brian.ebert> I have some code that has been running for the last couple of months. A few days ago I opened a client session and everything was fine. Yesterday I got an error from horizon with result_codes:
<stellar-slack> <brian.ebert> transaction: "tx_bad_seq"
<stellar-slack> <brian.ebert> Does anyone have an idea what might have changed?
<stellar-slack> <bartek> @brian.ebert please upgrade to stellar-sdk 0.4.0. It's a bug on our side, sorry. @eva will send (sent?) email to our dev mailing list about this.
<stellar-slack> <eva> (will send, it’s on its way :) )
<stellar-slack> <bartek> @channel >If you are actively developing on the Stellar network, please subscribe to the official http://Stellar.org|Stellar.org releases mailing list (https://www.freelists.org/list/sdf-releases) to make sure you receive future update notices. > > Due to a few recent updates, you will need upgrade your JavaScript libraries to stellar-sdk 0.4.0 and to stellar-base 0.5.0 as soon as possible. Please note that
<stellar-slack> of js sdks may fail. > > These releases also remove the following deprecated methods: > * Account.isValidAddress (replaced by Account.isValidAccountId) > * Account.getSequenceNumber (replaced by Account.sequenceNumber) > * Keypair.address (replaced by Keypair.accountId) > * Network.usePublicNet (now Network.usePublicNetwork) > * Network.useTestNet (now Network.useTestNetwork) > * Removed TransactionBuilder.addSigner (
<stellar-slack> sure to update your code before deploying an updated version. > > Thank you, and apologies for any inconvenience, > > Team Stellar
stellar-slack has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
edubai__ has quit [Quit: Connection closed for inactivity]
victortyau has joined #stellar-dev
<stellar-slack> <brian.ebert> Thanks for fixing. If that email was sent from Eva, I haven't received a copy.
<stellar-slack> <eva> @brian.ebert: best way to be sure to get software updates like this is to sign up for this list: https://www.freelists.org/list/sdf-releases
<stellar-slack> <brian.ebert> @eva: I've signed up for the list twice, with two different email addresses. I haven't received any mail yet.
<stellar-slack> <eva> when did you sign up @brian.ebert ?