eznode is a docker-based single-container setup for a personal bitcoin node, featuring:

• Bitcoin Core - Pruned by default with optional trusted fast-sync
• Electrum Server - Personal Electrum server powered by BWT
• BTC RPC Explorer - Personal block explorer and node dashboard
• Specter Desktop - Wallet GUI for hardware and multi-sig setups
• Secure remote access using Tor Onion, SSH tunnels or SSL

Why eznode?

• Simple one command setup
• Lightweight (120 MB docker image)
• Pruning-friendly (requires <5GB of storage)
• Suitable for a dedicated box, but doesn't require one
• Supports Linux, macOS, Windows and ARMv7/v8
• Secure transports out-of-the-box

Quickstart for a pruned node with a block explorer and a personal electrum server tracking your <xpub>, available over a Tor Onion service:

Code:

docker run -it --rm --name ez -v ~/eznode:/data eznode/eznode TOR=1 XPUB=<xpub>

User guide available on the website: https://ezno.de

See it in action (with the trusted fast-sync mode): https://twitter.com/shesek/status/1375144468366700550

Github: https://github.com/ez-org/eznode
Twitter: https://twitter.com/eznode_
Telegram: https://t.co/ez_node

CLI tools for insta-dumping bcash on ShapeShift in exchange for bitcoins (bcash-instadump), creating bcash-compatible transactions (bcash-tx), listing unspent bcash outputs (bcash-utxo) and broadcasting raw bcash transactions (bcash-broadcast).

https://github.com/shesek/bcash-instadump

TL;DR

    $ npm install -g bcash-instadump
    $ bcash-instadump --tor --key LmyBcashKeyWIF --payout 1btcAddrGimmeRogersCoins
    # confirm the details and press Y to get your bitcoins

Yes, that's it! But do read the whole thing to fully understand the risks involved. This program deals with private keys and should be used with care. I recommend that you audit the code yourself (<500 SLOC) before using it, or wait until someone you trust does it.

In any case, you SHOULD MOVE OUT YOUR BITCOINS to new keys before using the tool, such that only the bcash remains on the old ones. This ensures that your bitcoins are never at risk.

Good luck, happy dumping!

HODL.voting is a time-lock-weighted voting system that gives provable long-term bitcoin HODLers a way to express their opinion on proposed protocol upgrades.

To vote, users are requested to lock-up bitcoins for some pre-determined amount of time (using CHECKSEQUENCEVERIFY), where each vote is weighted by the number of bitcoins * lock duration. This mechanism lets people who're willing to commit to long-term hodling (and thus have a provable vested interest in bitcoin) get more say.

I built this project for the TLV emBassy 2017 Hackathon (and won the first prize with it!). It is currently running on testnet. Happy to hear your thoughts :-)

Website: https://HODL.voting/

GitHub repo and more info: https://github.com/shesek/proof-of-hodl

Hackathon slides: https://www.docdroid.net/rzFKS1g/proof-of-hodl.pdf.html

Article by Kyle Torpey: https://cryptoinsider.com/new-bitcoin-project-aims-make-online-trolling-expensive/

We're excited to announce the release of Bitrated V2, a trust platform for the Bitcoin ecosystem.

For these not familiar, Bitrated was launched back in '13 as a service that facilitates 2-of-3 multi-signature transactions for the purpose of arbitration (providing buyer protection in case of fraud) and provides a marketplace for arbitration service.

The new version released today is a complete rewrite of the original system, with a brand new identity & reputation management system, as well as improved usability and user experience.

Check it the new release: https://www.bitrated.com/

Explainer video: https://vimeo.com/116507236

CoinTelegraph article: http://cointelegraph.com/news/113535/bitrated-adds-reputation-system-offering-chargeback-like-process-to-bitcoin

If you have any questions, suggestions, or feedback, please don't hesitate contacting us!

I had an idea for a payment scheme that uses key derivation, but instead of the payee deriving the addresses, the payer would do it.

It would work like that:

• The payee publishes his master public key
• The payer generates a random "receipt number" (say, 25 random bytes)
• The payer derives an address from the master public key using the receipt number and pays to it
• The payer sends the receipt to the payee
• The payee derives a private key with that receipt and adds it to his wallet

Advantages:

• It increases privacy by avoiding address reuse
• The process is asynchronous. The payee is completely passive in the payment process and isn't required to provide new addresses before each payment (no payment server required)
• Its usable as a replacement for cases where re-used addresses are the most viable solution (like putting an address in a forum signature or as a development fund in a github readme)
• The receipt also acts as a proof of payment that the payer can provide to the payee
• Also, if the master is known to belong to someone, this also allows the payer prove to a third-party that the payment was made to that someone. If the output was spent, it also proves that he was aware of the payment and has the receipt.
• Its a really thin abstraction layer and doesn't require any protocol changes

Disadvantages:

• Losing the receipt numbers means losing access to your funds, they are random and there's no way to restore them
• It requires sending the receipt to the payee somehow. Email could work for that, but a better defined channel that also can talk to the Bitcoin client and add the receipt would be much better.

What do you think?

I just released Bitrated, an interface for arbitrated transactions and a marketplace for arbitration services.

If you don't know what multisig/m-of-n means, check out the FAQ: https://www.bitrated.com/faq.html

If you want to play with it, there's also a testnet [1] version: http://testnet.bitrated.com/

When it asks you to share the URL with the other party, you can just open that in a new tab.

If you don't want to go through all the process, you can see how the transaction page looks here.

[1] https://en.bitcoin.it/wiki/Testnet, you can get some testnet coins sent to the multisig from a faucet: http://testnet.mojocoin.com/