Community Directory


Go back

User Activity

Forum Posts

  • Replies: 217
  • Topics: 26
  • Likes Received: 154
  • Re: How safe is my LTB Companion Wallet?

    Whoop, thought I had answered this. This answers below...

    @avarice

    Where exactly does my new LTB Companion wallet (which I created through a Chrome extension) reside at the moment?

    The wallet data (passphrase, address labels, etc.) is stored locally on your hard drive. The actual location of the files is in the Chrome Application folder if you download from the Chrome Web Store.

    On the wallet settings tab there is a button that says "encrypt wallet". This seems to imply to me that currently it is sitting around on my PC somewhere unencrypted - and vulnerable... is my understanding correct? Should I encrypt my wallet if I intend to store any amount of value in it?

    It's up to you to encrypt your wallet if you want that layer of protection. The passphrase is on your computer and never leaves your computer (transactions are constructed and signed locally, then sent to the bitcoin network). The encryption layer is primarily for a physical intrusion (someone at your computer trying to access your wallet). It's something you need to remember, so keep that in mind. If you forget the encryption password, you will not have access to your wallet.

    I've often heard that you should treat online wallets similar to real wallets - and only carry around pocket change in them; is this still the case?

    Analogies aside; the thing that you need to keep safe is your 12-word passphrase. If you think you can do that by keeping your computer itself safe, then you can keep more than pocket change in your wallet.

    Consider trying Tokenly Pockets (http://pockets.tokenly.com). It has all the same functionality as LTB Companion and is more up to date.

  • Re: How safe is counter wallet

    Calling it a second "layer of protection" makes it sound more secure than Counterwallet, but I think you can only say that if you're comparing leaving your Counterwallet active on your browser, vs. using Tokenly Pockets with a password.

    This isn't really a fair comparison. Data stored in a Chrome extension is sandboxed from the rest of the web (and other browser extensions), and data in a browser (i.e. Counterwallet) does not have that level of security. Since Counterwallet requires you to enter your 12-word passphrase every time, unless you've memorized it, you'll need to have it written down somewhere either on paper or on your computer which are both less secure than having it encrypted in the local storage of Tokenly Pockets. There's also the option to download the Tokenly Pockets source which would prevent you from receiving updates but would be much more secure than Counterwallet running on a web server since the code is stored and served locally and can easily be audited before using.

  • Re: Missing the Junseth and Chris DeRose Chit Chat recap on the XCP Community Update show?

  • Re: Using Counterwallet for Proof Of Existence?

    @rob Is there a good way to embed a hash in the blockchain using Counterwallet (with similar results to ProofOfExistence.com, but I'll provide the hash value)? I've heard that it's doable, and someone mentioned using the Broadcast function. I see Address Action>Feed Broadcast, but it doesn't scream as an obvious way to do it, with the various fields that pop up. Anyone know?

    Select Feed Broadcast and just paste your hash into the broadcast text field. You can leave all the other fields as is.

  • Re: Mobile Counterparty Wallet is available for both Android and iOS!

    @cointea1121

    Hey sorry for the really late response.

    I talked with Yuta about this and we will go along with the standardized QR code scheme following the model of bip. Or indieSquare can provide a JS-based SDK for compatible QR code creation.

    We would love to talk about the technical spec with the Tokenly team and other Counterparty folks about this anytime, so please keep us in loop. Thanks!

    I think the consensus is to use the following payment URI...

    counterparty:[address]?asset=&amount=&label=&message=

    so, for example, if you're sending 3 TOKENLY to 1GcFhAQGFZVDAr4jiR2tKwisHcgNUjhGNC then the payment URI would show...

    counterparty:1GcFhAQGFZVDAr4jiR2tKwisHcgNUjhGNC?asset=TOKENLY&amount=3&label=example&message=this%20is%20an%20example

  • Re: Mobile Counterparty Wallet is available for both Android and iOS!

    @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.

  • Re: Mobile Counterparty Wallet is available for both Android and iOS!

    @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.

  • Re: Mobile Counterparty Wallet is available for both Android and iOS!

    @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=

  • Re: LTB Redesign and Upcoming Changes

    Looks great! The recent posts appearing on the home page is a nice touch.

Pages 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25