The LTB Network Forum


Mobile Counterparty Wallet is available for both Android and iOS!

Back to General

Jump to bottom
Pages: 1234567

Comments

  • cointea1121

    @adam Thanks, I tested it out. Two things I noticed.

    1. The QR code screen is not sized properly. Shoud make the screen a bit bigger so that I can't scroll up and down or sideways

    2. I could read the address perfectly into IndieSquare Wallet but not with the amount. I think we need to do a bit of work on our side as well so I am going to have our engineer look at this and reply to you regarding this.

    Thanks so much for doing this, Adam. I think this is a really great little integration that improve the user experience significantly.

    Permalink
    0 likes
  • adam

    @cointea1121 Yeah I noticed that about the QR code window being sized too small and mentioned it to Devon, we'll fix that.

    Regarding the amount and type of token, we created the "pay with pockets" protocol that is how we allow users to pre-load their wallet with the right token, address and amount. You can find documentation on the schema here, what do you think about making your wallet able to recognize the protocol and respond as you see fit?

    https://github.com/loon3/Tokenly-Pockets/blob/master/Pockets%20Payment%20Button.md

    Permalink
    1 like
  • cointea1121

    Thanks for the info.

    yeah I think it's almost a necessity that IndieSquare Wallet is able to recognize the protocol and read both the address and amount.

    We are focused on the release of the next update(ShapeShift integration and etc) but we will definitely look into this and probably make it happen sometime later. Hope it won't require a lot of work (I'm not a dev myself...)

    Permalink
    0 likes
  • adam

    @cointea1121 Thanks for the info.

    yeah I think it's almost a necessity that IndieSquare Wallet is able to recognize the protocol and read both the address and amount.

    We are focused on the release of the next update(ShapeShift integration and etc) but we will definitely look into this and probably make it happen sometime later. Hope it won't require a lot of work (I'm not a dev myself...)

    Type of token is actually one of the biggest things it does. When we were working just with bitcoin URI's it became obvious that making all the information machine readable would really simplify the payment process and it does, takes like 10 seconds to complete a purchase if you just have to load the wallet, select the address and click "send" without having to select type of token, quantity of token or destination address.

    The "Pay with Pockets" nomenclature has more to do with the text we use on our buttons than anything else, I'd imagine you guys would just need to create some recognizable button art (Pay with IndieSquare) and connect the dots. This is already live on all our services except the auctioneer prototype and also this website.

    Permalink
    1 like
  • loon3

    @adam

    @cointea1121 Thanks for the info.

    yeah I think it's almost a necessity that IndieSquare Wallet is able to recognize the protocol and read both the address and amount.

    We are focused on the release of the next update(ShapeShift integration and etc) but we will definitely look into this and probably make it happen sometime later. Hope it won't require a lot of work (I'm not a dev myself...)

    Type of token is actually one of the biggest things it does. When we were working just with bitcoin URI's it became obvious that making all the information machine readable would really simplify the payment process and it does, takes like 10 seconds to complete a purchase if you just have to load the wallet, select the address and click "send" without having to select type of token, quantity of token or destination address.

    The "Pay with Pockets" nomenclature has more to do with the text we use on our buttons than anything else, I'd imagine you guys would just need to create some recognizable button art (Pay with IndieSquare) and connect the dots. This is already live on all our services except the auctioneer prototype and also this website.

    I don't thing Pay with Pockets is going to help @cointea1121 with the QR code. It would make sense to take this opportunity to standardize a URI scheme for Counterparty payments. This is how it's currently done for bitcoin QR codes... (see https://en.bitcoin.it/wiki/BIP_0021)

    bitcoin:[bitcoin address]?amount=&label=&message=

    I imagine Counterparty should follow a similar scheme and just include the token parameter, like this...

    cntrprty:[Counterparty address]?token=&amount=&label=&message=

    Permalink
    1 like
  • adam

    @loon3

    @adam

    @cointea1121 Thanks for the info.

    yeah I think it's almost a necessity that IndieSquare Wallet is able to recognize the protocol and read both the address and amount.

    We are focused on the release of the next update(ShapeShift integration and etc) but we will definitely look into this and probably make it happen sometime later. Hope it won't require a lot of work (I'm not a dev myself...)

    Type of token is actually one of the biggest things it does. When we were working just with bitcoin URI's it became obvious that making all the information machine readable would really simplify the payment process and it does, takes like 10 seconds to complete a purchase if you just have to load the wallet, select the address and click "send" without having to select type of token, quantity of token or destination address.

    The "Pay with Pockets" nomenclature has more to do with the text we use on our buttons than anything else, I'd imagine you guys would just need to create some recognizable button art (Pay with IndieSquare) and connect the dots. This is already live on all our services except the auctioneer prototype and also this website.

    I don't thing Pay with Pockets is going to help @cointea1121 with the QR code. It would make sense to take this opportunity to standardize a URI scheme for Counterparty payments. This is how it's currently done for bitcoin QR codes... (see https://en.bitcoin.it/wiki/BIP_0021)

    bitcoin:[bitcoin address]?amount=&label=&message=

    I imagine Counterparty should follow a similar scheme and just include the token parameter, like this...

    cntrprty:[Counterparty address]?token=&amount=&label=&message=

    Pay with Pockets wasn't supposed to help them with the QR code, that was a seperate part of the conversation. I was proposing they make their wallet able to recognize the same code we use for Pay with Pockets, which would let them then insert a button that could copy that identified information into the right parts of the app, which then becomes the focus of the window.

    Or am I totally wrong?

    Permalink
    1 like
  • loon3

    @adam

    Pay with Pockets wasn't supposed to help them with the QR code, that was a seperate part of the conversation. I was proposing they make their wallet able to recognize the same code we use for Pay with Pockets, which would let them then insert a button that could copy that identified information into the right parts of the app, which then becomes the focus of the window.

    Or am I totally wrong?

    No way for them to insert a button. If anything, Tokenly would need to serve the code with the button and customized link, which Indiesquare would recognize. I think it's better to go the univeral route and establish a URI scheme for any counterparty transaction and encode it into the qr code, which would be inline with what's done in bitcoin.

    Permalink
    1 like
  • adam

    @loon3

    @adam

    Pay with Pockets wasn't supposed to help them with the QR code, that was a seperate part of the conversation. I was proposing they make their wallet able to recognize the same code we use for Pay with Pockets, which would let them then insert a button that could copy that identified information into the right parts of the app, which then becomes the focus of the window.

    Or am I totally wrong?

    No way for them to insert a button. If anything, Tokenly would need to serve the code with the button and customized link, which Indiesquare would recognize. I think it's better to go the univeral route and establish a URI scheme for any counterparty transaction and encode it into the qr code, which would be inline with what's done in bitcoin.

    So should we schedule a call with someone technical on the indiesquare team and talk about this, or do you just want to write up a document when you get time?

    Permalink
    0 likes
  • loon3

    @adam

    @loon3

    @adam

    Pay with Pockets wasn't supposed to help them with the QR code, that was a seperate part of the conversation. I was proposing they make their wallet able to recognize the same code we use for Pay with Pockets, which would let them then insert a button that could copy that identified information into the right parts of the app, which then becomes the focus of the window.

    Or am I totally wrong?

    No way for them to insert a button. If anything, Tokenly would need to serve the code with the button and customized link, which Indiesquare would recognize. I think it's better to go the univeral route and establish a URI scheme for any counterparty transaction and encode it into the qr code, which would be inline with what's done in bitcoin.

    So should we schedule a call with someone technical on the indiesquare team and talk about this, or do you just want to write up a document when you get time?

    I think if we just agree on the scheme here in this thread that would be enough to get started. It's pretty straightforward if we use bip0021 as a model. Devon can then generate the qr codes from the new payment URI and Indiesquare can parse it. I don't think there is any other wallet that can take advantage of the qr code so now would be the time to do it.

    Permalink
    0 likes
  • adam

    @loon3

    @adam

    @loon3

    @adam

    Pay with Pockets wasn't supposed to help them with the QR code, that was a seperate part of the conversation. I was proposing they make their wallet able to recognize the same code we use for Pay with Pockets, which would let them then insert a button that could copy that identified information into the right parts of the app, which then becomes the focus of the window.

    Or am I totally wrong?

    No way for them to insert a button. If anything, Tokenly would need to serve the code with the button and customized link, which Indiesquare would recognize. I think it's better to go the univeral route and establish a URI scheme for any counterparty transaction and encode it into the qr code, which would be inline with what's done in bitcoin.

    So should we schedule a call with someone technical on the indiesquare team and talk about this, or do you just want to write up a document when you get time?

    I think if we just agree on the scheme here in this thread that would be enough to get started. It's pretty straightforward if we use bip0021 as a model. Devon can then generate the qr codes from the new payment URI and Indiesquare can parse it. I don't think there is any other wallet that can take advantage of the qr code so now would be the time to do it.

    I pinged devon and asked him to put together a spec, thanks for correcting me Joe!

    Permalink
    1 like
Jump to top
Pages: 1234567

Post Reply

Please Login to post a reply to this thread.