Community Directory


Go back

User Activity

Forum Posts

  • Replies: 33
  • Topics: 5
  • Likes Received: 15
  • Re: How safe is counter wallet

    I'm not a security expert by any means, but I think the short answer is that it's "relatively safe." You are still reliant on third parties and if your computer isn't secure, you could be compromised in some way.

    You might enjoy the Tokenly Pockets chrome extension where you can enter your 12 word passphrase but also add a password for another layer of protection. https://github.com/loon3/Tokenly-Pockets

    Or you can wait for a working version of Counterparty QT (not sure where development on that is right now).

  • Re: [WTB] Empty BTC, LTC and DOGE addresses that were in use on May 12, 2014

    I think the broader point that Adam was asking about is why you need the private keys at all.

    The answer is that CLAMS had an initial distribution to holders of BTC, DOGE, and LTC. They did a snapshot at a certain time a la the BitShares-PTS model and if you held any of those currencies with a non-dust balance at the time of the snapshot, then you would receive some CLAMS.

    If you move your coins to a new address, then you can safely test importing your old private keys into the client.

    I have done this myself with balances in all three of these coins and can verify that it does work. I also immediately sold them on an exchange because I don't really believe the CLAM project adds any new value to the crypto space.

    @bayareacoins

    @adam What exactly are you doing with used, empty addresses whose private keys you don't have exclusive control of?

    We run them through the "CLAM CLIENT" (https://github.com/nochowderforyou/clams.)

    All Bitcoin, Litecoin and Dogecoin addresses share the same private keys. A good example of how addresses have "sister keys" would be http://buttcoins.com/.

    Even though I'm telling you that we do not save the private keys. You should still treat it as if we do. Same goes with us and the "CLIENTS" relationship. I know a site owner who prior to dealing with CLAMS left a 50 BTC block trusting the client and had no issues.

    Toss as much of that "trust" stuff out of the window when dealing with crypto IMO.

    We will NEVER use the addresses in order to spam the Bitcoin network as seen here recently: https://bitcointalk.org/index.php?topic=1175321 (cause we can't for one!)

  • Re: Poloniex delisting LTBC

    I'm going to submit a request to keep it up on Poloniex as well. Hopefully that could make a difference.... we'll see.

  • Announcing Color Swarm

    I've been working with a couple developers for the last couple of months to create a site called Color Swarm where we deconstruct videos into their individual frames, color them, and reassemble them into a new video. The exciting part of it is that participants will be awarded tokens and if someone chooses to sponsor a project, then the participants will receive dividends proportionate to how much work they have contributed to the project.

    That's the nutshell version of it. I have an early draft of a "white paper" in the following Google Doc link on which I would absolutely LOVE to get any feedback: https://docs.google.com/document/d/1cqJpt3Pik_kdgU78pFIovqhxZ0avydrwJzdXHwQr4Ls/edit?usp=sharing

    The site http://colorswarm.com is currently just a landing page with a little information and a form to sign up for email update (I quickly set it up in WordPress, though the new site is Drupal).

    Looking forward to hearing any thoughts from this wonderful community.

  • Re: LTBCOIN for Ads on On The Cusp Podcast

    Thanks for your help, @deweller and @adam!!

  • Re: 30 Second Spot for On the Cusp Podcast

    I had some small challenges troubleshooting a Counterwallet bug, but now everything has been worked out and the auction is live! Thanks in advance for your interest!

    http://auction.letstalkbitcoin.com/auction/30-second-advertising-spot-for-on-the-cusp-podcast

  • Re: LTBCOIN for Ads on On The Cusp Podcast

    @adam

    @cc5alive I created the asset on Thursday and was checking on Sunday. I just checked again and I still don't see it in Counterwallet, though it is showing up on the blockchain explorer. Strange, right?

    Actually one of the projects we're working on had exactly the same problem, apparently it's a known bug. Try loading the passphrase in your LTB companion and the asset should be sendable although you wont be able to issue or do anything like that until counterwallet recognizes

    Thanks, @adam! When I used the LTB companion, I was able to send the token. Strange bug, but it's very cool that the LTB companion allows a workaround!

    And now the auction is finally live! :)

  • Re: LTBCOIN for Ads on On The Cusp Podcast

    I created the asset on Thursday and was checking on Sunday. I just checked again and I still don't see it in Counterwallet, though it is showing up on the blockchain explorer. Strange, right?

  • Re: LTBCOIN for Ads on On The Cusp Podcast

    I'm noticing a strange issue now... I created the asset ONTHECUSPAD (http://blockscan.com/assetInfo/ONTHECUSPAD) but it is not appearing in my Counterwallet. I am unable to send the asset to the auctioneer as a result.

    Any thoughts on this? Is there a limit to how many assets one can have appear at a single address in Counterwallet?

  • Re: LTBCOIN for Ads on On The Cusp Podcast

    Got it -- didn't see the part where I needed to send 0.005 BTC to activate the auction! Thank you.

    @deweller @cc5alive

    The service is still running.

    You will need to fund this auction. Here are the instructions:

    To begin this auction you must send 0.005 BTC, 1,000 LTBCOIN and the prize tokens listed below to 1Pt74RBfd4pMbyrmLt1NmXtRgfcWnR42T6. After these have been received, your auction will begin no earlier than 5.15.2015 8:00 PM -05:00.

    These instructions should appear at the secret URL you received when you created the auction. If you don't have that URL, PM me and I can send it to you.

Pages 1 2 3 4

© Copyright 2013–2016 The LTB Network. All rights reserved .