<stellar-slack>
<sacarlson> but at present you can only lookup what is already in the stellar database as I can't get stellar-core to come up today
de_henne has joined #stellar
<stellar-slack>
<dzham> @sacarlson: on the surface, it looks quite like a payment channel
<stellar-slack>
<dzham> ```
<stellar-slack>
<sacarlson> what does?
<stellar-slack>
<dzham> your offline transactions
<stellar-slack>
<dzham> ```Payment Channels in Stellar producer, consumer setup: - create a joint 2-of-2 multi-signature account, with consumer and producer as signers - producer sends consumer a tx that sends all the funds back to consumer, valid only after a certain time - consumer funds account w/ a certain amount while running: consumer consumer a service consumer sends producer a tx that: * sends the balance to the produc
<stellar-slack>
consumer (if asset other than XLM) * merges account w/ consumer to cash out, producer signs the most recent tx, and submits it to the network```
<stellar-slack>
<sacarlson> accept here you have to trust that the producer will send back the money. in my method you already have your money back without the producer sending it back
<stellar-slack>
<sacarlson> but that would also work I think
<stellar-slack>
<dzham> both actors have to sign, otherwise no one will get any money, plus.. producer has already signed the “refund”-tx
<stellar-slack>
<sacarlson> no I think this might be even better
<stellar-slack>
<sacarlson> I knew you guys would figure it out
<stellar-slack>
<dzham> There’s a blog post in there somewhere, that’s just the rough outline
<stellar-slack>
<sacarlson> but I think the producer would have to be my trust gateway redirector so you don't need as many 2 of 2 accounts
<stellar-slack>
<dzham> they’re all temporary anyways, so it doesn’t matter much.. the refund -tx would normally kick in after the duration of a normal interaction. If you’re having a paid phone consultation with someone, maybe that’s a an hour or two. For a night out, w/ you and your buddy, 8-12 hours
<stellar-slack>
<sacarlson> but I think this is way better than my original idea with the trust bot signer. that wouldn't be needed
<stellar-slack>
<sacarlson> yes I understand how this would work
<stellar-slack>
<sacarlson> I like it
<stellar-slack>
<sacarlson> lets add this one to the android app
<stellar-slack>
<sacarlson> I still want the auto detect if internet is available to send the transaction normally on stellar network if so. but this might make transactions faster also
<stellar-slack>
<sacarlson> this service could and should be provided by most any gateway, I hope gateways also provide auto redirect of payments to other gateways
<stellar-slack>
<sacarlson> how can we make that safe? to have a gateway redirect payment to anther gateway without this gateway running off with the original funds?
<stellar-slack>
<sacarlson> oh I think this method might not even need a redirector, this is looking better all the time
<stellar-slack>
<sacarlson> no I guess it still does
<stellar-slack>
<sacarlson> I see a problem with your method as you can't use a gateway redirector in your case as you don't have the key seed to sign to return the change for the address of a gateway redirector. so in your case you would be force to have prelocked accounts for every shop and store you planed to deal with before hand.
Azitrex has joined #stellar
<stellar-slack>
<dzham> but that’s the whole point.. you set them up, figure out how much to pay, then close them
<stellar-slack>
<sacarlson> yes but what about the 100's of shops on the street you want to deal with on the fly? I would have to setup prelocked funds for all of them?
<stellar-slack>
<sacarlson> how would I know ahead of time what shop I was going to get thirst at?
<stellar-slack>
<sacarlson> with your method you can't setup a group of shops to work from a single trust account that the funds would be locked on
<stellar-slack>
<sacarlson> but maybe mine can't eather?
<stellar-slack>
<sacarlson> I don't think mine would work with groups since if more than one shop accepted to the same account then again you could double spend so I guess your method is still as good or better than mine
Mr_SeLeNiO has quit [Ping timeout: 244 seconds]
<stellar-slack>
<dzham> @sacarlson: one quickie about "account B”: just make it a keypair, and just make sure that it’s not registered as an account in the ledger. I think that’s a bit simpler than to deal with the thresholds.
<stellar-slack>
<sacarlson> if it's not already an account then it could be created as an account and start receiving the funds. in this case if was already created and then locked it could never collect funds
<stellar-slack>
<sacarlson> I thought I got that idea from you?
<stellar-slack>
<dzham> ah, gotcha, good point
<stellar-slack>
<dzham> well, I do something similar, but for a different effect
<stellar-slack>
<dzham> I should write it up, but I just hate technical writing
<stellar-slack>
<sacarlson> I've already updated it with your idea above added I'll go ahead and publish it if you want to reread it.
<stellar-slack>
<sacarlson> I published the update
Azitrex has quit [Read error: Connection reset by peer]
Mr_SeLeNiO has joined #stellar
<stellar-slack>
<dzham> It would be interesting to know the stats.. I’m in a 4k member slack, and it’s got a daily average around 300 users
<stellar-slack>
<lab> !here
<stellar-slack>
<lab> <here>
<stellar-slack>
<sacarlson> I'm not sure this is related but I already added broadcast on mss-websocket that would allow chat with filters for stellar keypair holders to prove that they who they are and can add filters for any new members
Azitrex_ has quit [Read error: Connection reset by peer]
Azitrex_ has joined #stellar
<stellar-slack>
<buhrmi> whats with all the inflation transactions happening on livenet atm
<stellar-slack>
<sacarlson> in theory it should happen every week i guess
<stellar-slack>
<sacarlson> but I thought there would just be one
<stellar-slack>
<jed> anyone can inject the tx
<stellar-slack>
<jed> at any time
<stellar-slack>
<jed> it will only work though if it is time for it