Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    another-hodler
    @another-hodler
    Now to the risk of having keys written to usbs:
    1. I am not sure whether boot USB is required after the boot. It needs to be tried.
    2. You can create several sets of usbs during setup and then use them just once and destruct them physically after each use.
    BTC1776
    @BTC1776
    so i see that blockchain.info is no longer showing unspent outputs. i used the link https://blockchain.info/unspent?active=$address for my address. it is unclear to me what is the transaction ID. I used 2 numbers( transaction id's?) but was unable to access my entire wallets funds with those numbers. Some assistant would be greatly appreciated
    for further clarification: I must be missing some of the transaction id's using that page because only a fraction of the bitcoin was available to me to spend
    bitcoinhodler
    @bitcoinhodler
    @another-hodler the protocol would need to explain safe destruction methods. And are you going to destroy the quarantined laptops after each use, too? They have many persistent data stores inside them that malware might use. I filed an issue on this, let's move the discussion there: GlacierProtocol/GlacierProtocol#51
    bitcoinhodler
    @bitcoinhodler
    @BTC1776 The txid is listed as "tx_hash" in that output. You should be able to search blockchain.info for each of those txids and see the full balance of your cold storage address. When you say you were unable to access your entire wallet's funds, you mean that the total was not as large as expected? You think there should have been more BTC?
    bitcoinhodler
    @bitcoinhodler
    @BTC1776 nevermind I saw your clarification. I don't know why blockchain.info would be missing UTXOs but that wouldn't be the first time its data was unreliable. Unfortunately I don't know of any other online service that will report unspent outputs. If you run a Bitcoin Core full node, there is a way.
    I added my cold storage address to by Bitcoin Core full node as a watch-only address. Unfortunately, I don't remember how I did that. But now I can run "listunspent" (in the console window) and it will list all the UTXOs.
    bitcoinhodler
    @bitcoinhodler
    @BTC1776 another idea: go to blockstream.info, paste your address, then click the Details button next to each txid. Within each transaction, find the output to your cold storage address, and look at the "Spending Tx" field. It will tell you if it's spent or unspent. Manually collate the txid for each unspent output.
    BTC1776
    @BTC1776
    @bitcoinhodler Thank you I was able to access all of my balance. On that blockchain page the transaction id was actually "tx_hash_big_endian". above it on the page was "tx_hash" and that resulted in nothing when using the the value associated with it
    @BTC1776 everything worked out. Thanks especially for the timely response. Cheers
    bitcoinhodler
    @bitcoinhodler
    Interesting. Glad you figured that out.
    Jernej
    @jazarija
    Hm... the protocol document is clearly broken if people are not able to perform withdrawals by following it
    isn't it due time that it gets corrected?
    Jernej
    @jazarija
    Perhaps relevant for the future of Glacier bitcoin-core/bitcoincore.org#635
    bitcoinhodler
    @bitcoinhodler
    I have some significant changes & bug fixes to GlacierScript that I'll be submitting over the next few days.
    Reviewers requested: GlacierProtocol/GlacierProtocol#58
    Several more PRs to come, but they each build on the previous one, so I plan to submit them one at a time after each gets merged.
    bitcoinhodler
    @bitcoinhodler
    Thank you @jazarija for the review. My next PR cleans up some of the developer tests which will let me move forward with some bug fixes: GlacierProtocol/GlacierProtocol#60
    bitcoinhodler
    @bitcoinhodler
    My last (for now) PR will bring GlacierScript into the modern world of Python 3: GlacierProtocol/GlacierProtocol#61
    I've got much more to come in the future, but I have to wait for the release of Bitcoin Core v0.18 to get their bug fixes!
    Jernej
    @jazarija
    Is it OK not to have the initial line invoking python3?
    bitcoinhodler
    @bitcoinhodler
    No. That's called the shebang line, and it tells the shell what program to use to execute this file
    Without that line, you'd have to run it like: python3 glacierscript.py (instead of the documented ./glacierscript.py
    Or perhaps you're talking about base58.py...in that case it's fine since that file is an imported module, not a directly executed file
    iharokus
    @iharokus
    Guys, is the latest version of Glacier 0.93 compatible with Bitcoin Core 0.17.1? I want to set up my cold storage.
    bitcoinhodler
    @bitcoinhodler
    @iharokus yes it is
    iharokus
    @iharokus
    Thanks
    bitcoinhodler
    @bitcoinhodler
    @diogomonica we need a new release of Glacier for compatibility with the upcoming v0.18 release of Bitcoin Core. We need at least up through PR #50 if you don't want to review anything beyond that.
    I've also tested up through my latest PR (#61) and it also works with v0.18.
    bitcoinhodler
    @bitcoinhodler
    Otherwise anyone creating new App USBs will see GlacierScript die with cryptic error messages because the signrawtransaction and getaddressesbyaccount RPCs have both been removed from Bitcoin Core.
    Note, all these versions of GlacierScript are also compatible with today's v0.17.1, so you can do a Glacier release today and it will work.
    bitcoinhodler
    @bitcoinhodler
    Can someone who is on Twitter ping @RobertStigler and point him to the issue I just filed based on his suggestions: GlacierProtocol/GlacierProtocol#64
    Jernej
    @jazarija
    Pinging him right now
    bitcoinhodler
    @bitcoinhodler
    Thank you @jazarija . Perhaps you could also ping @GlacierProtocol and/or @diogomonica to get Diogo to give us a new Glacier release for v0.18 compatibility. It seems he's not paying attention here on Gitter
    Jernej
    @jazarija
    For sure
    is it ok to write "@GlacierProtocol , @diogomonica the developers of glacier need you to pay attention to the recent v0.18 compatibility issue that would break glacier" ?
    if not, just write whatever text you want me to dispatch
    bitcoinhodler
    @bitcoinhodler
    sounds good to me
    Jernej
    @jazarija
    Do you perhaps also have a relevant ticket link?
    iharokus
    @iharokus
    Do you know when they are planning to release Bitcoin Core 0.18??
    bitcoinhodler
    @bitcoinhodler
    no to both of you :)
    Diogo Mónica
    @diogomonica_twitter
    Just caught up on the messages.
    Will try to schedule a release for the upcoming weeks.
    Diogo Mónica
    @diogomonica_twitter
    We'll tweet about it tomorrow, let us know if you find anything wrong in the meantime.
    iharokus
    @iharokus
    What are the most significant improvements in this release?
    Sorry, got the answer via link)))
    iharokus
    @iharokus
    It says: "This version is compatible with Bitcoin Core v0.18. Earlier versions are not." But Core v0.18 hasn't been released yet.
    bitcoinhodler
    @bitcoinhodler
    @iharokus it has not. So what? We're ready for it, when it is. Which is better than the last two Core releases, where we didn't get a Glacier release out in time.
    This Glacier version is also compatible with Core v0.17.1 and v0.17, if that wasn't clear.