Litecoin Miner ☘️ - TOP 7 Modelle unter der Lupe

Bitcoin lingo...lay it on me!

Okay so for fun, for newbies and perhaps even new to some of us more seasoned crypto heads (is that a thing?) how about posting some lingo or terminology that relates to the culture of Bitcoin or even something you may have ‘coined’ yourself?
submitted by bj_d to Bitcoin [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

PSA: Guide on how to recover your lost Segwit coins using Electron Cash

How to get your recovered SegWit funds using Electron Cash

Background

Thousands of BCH on thousands of coins that were accidentally send to Segwit 3xxx addresses were recovered by BTC.TOP in block 582705.
This was a wonderful service to the community. This had to be done quickly as the coins were anyone can spend and needed to be sent somewhere. This all had to be done before thieves could get their dirty paws on them.
So.. How were they recovered? Did BTC.TOP just take the coins for themselves? NO: They were not taken by BTC.TOP. This would be wrong (morally), and would open them up to liability and other shenanigans (legally).
Instead --BTC.TOP acted quickly and did the legally responsible thing with minimal liability. They were sent on to the intended destination address of the SegWit transaction (if translated to BCH normal address).
This means BTC.TOP did not steal your coins and/or does not have custody of your funds!
But this does mean you now need to figure out how to get the private key associated with where they were sent -- in order to unlock the funds. (Which will be covered below).
Discussions on why this was the most responsible thing to do and why it was done this way are available upon request. Or you can search this subreddit to get to them.

Ok, so BTC.TOP doesn't have them -- who does?

You do (if they were sent to you)! Or -- the person / address they were sent to does!

HUH?

The Segwit transactions have a bad/crazy/messed-up format which contains an output (destination) which contains a hash of a public key inside. So they "sort of" contain a regular bitcoin address inside of them, with other Segwit garbage around them. This hash was decoded and translated to a regular BCH address, and the funds were sent there.
Again: The funds were forwarded on to a regular BCH address where they are safe. They are now guarded by a private key -- where they were not before (before they were "anyone can spend"). It can be argued this is the only reasonable thing to have done with them (legally and morally) -- continue to send them to their intended destination. This standard, if it's good enough for the US Post Office and Federal Mail, is good enough here. It's better than them being stolen.

Ok, I get it... they are on a regular BCH address now. The address of the destination of the Tx, is it?

Yes. So now a regular BCH private key (rather than anyone can spend) is needed to spend them further. Thus the Segwit destination address you sent them to initially was effectively translated to a BCH regular address. It's as if you posted a parcel with the wrong ZIP code on it -- but the USPS was nice enough to figure that out and send it to where you intended it to go.

Why do it this way and not return to sender?

Because of the ambiguity present-- it's not entirely clear which sender to return them to. There is too much ambiguity there, and would have led to many inputs not being recovered in a proper manner. More discussion on this is available upon request.

Purpose of this guide

This document explains how to:
Complications to watch out for:

Step 1: Checking where your coins went

To verify if this recovery touched one of your lost coins: look for the transaction that spent your coins and open it on bch.btc.com explorer.

Normal aka "P2PKH"

Let’s take this one for example.
Observe the input says:
P2SH 160014d376cf1baff9eeed943d58551d53c48377adb98c 
And the output says:
P2PKH OP_DUP OP_HASH160 d376cf1baff9eeed943d58551d53c48377adb98c OP_EQUALVERIFY OP_CHECKSIG 
Notice a pattern?
The fact that these two highlighted hexadecimal strings are the same means that the funds were forwarded to the identical public key, and can be spent by the private key (corresponding to that public key) if it is imported into a Bitcoin Cash wallet.

Multisig aka "P2SH"

If the input starts with “P2SH 220020…”, as in this example, then your segwit address is a script -- probably a multisignature. While the input says “P2SH 22002019aa2610492ee2c18605597136294596d4f0f9bc6ce0974ed3a975d65da4ca1e”, the output says “P2SH OP_HASH160 21bdc73fb15b3bb7bd1be365e92447dc2a44e662 OP_EQUAL”. These two strings actually correspond to the same script, but they are different in content and length due to segwit’s design. However, you just need to RIPEMD160 hash the first string and compare to the second -- you can check this by entering the input string (after the 220020 part) into this website’s Binary Hash field and checking the resulting RIPEMD160 hash. The resulting hash is 21bdc73fb15b3bb7bd1be365e92447dc2a44e662, which corresponds to the output hex above, and this means the coins were forwarded to the same spending script but in "non-segwit form". You will need to re-assemble the same multi-signature setup and enough private keys on a Bitcoin Cash wallet. (Sorry for the succinct explanation here. Ask in the comments for more details perhaps.)

No match -- what?!

If the string does not match (identically in the Normal case above, or after properly hashing in the Multisig case above), then your coins were sent elsewhere, possibly even taken by an anonymous miner. :'(

Step 2: How To Do the Recovery

Recover "Normal" address transactions (P2PKH above)

This is for recoveries where the input string started with “160014”.
Option 1 (BIP39 seed):
Option 2 (single key):
Option 3 (xprv -- many keys):
Code:
mkey = "yprvAJ48Yvx71CKa6a6P8Sk78nkSF7iqqaRob1FN7Jxsqm3L52K8XmZ7EtEzPzTUWXAaHNfN4DFAuP4cdM38yrE6j3YifV8i954hyD5rhPyUNVP" from electroncash.bitcoin import DecodeBase58Check, EncodeBase58Check EncodeBase58Check(b'\x04\x88\xad\xe4'+DecodeBase58Check(mkey)[4:]) 
Option 4 (hardware wallet):

How to Recover Multisignature wallets (P2WSH-in-P2SH in segwit parlance)

This is for recoveries where the input string started with "220020.
Please read the above instructions for how to import single keys. You will need to do similar but taking care to reproduce the same set of multisignature keys as you had in the BTC wallet. Note that Electron Cash does not support single-key multisignature, so you need to use the BIP39 / xprv approach.
If you don’t observe the correct address in Electron Cash, then check the list of public keys by right clicking on an address, and compare it to the list seen in your BTC wallet. Also ensure that the number of required signers is identical.
submitted by NilacTheGrim to btc [link] [comments]

BCH sent to P2WPKH-P2SH Address, recovery shows mixed results...

I have a case here where a client of mine used a BitCoin ATM, and inadvertently used the 'BitCoin CASH' option instead of 'BitCoin', when he was using himself a Mycelium HD Wallet on a SegWit Address. Mistakes were made, but we have held onto the hope that at somepoint recovery would be possible.

With the May 15 Fork and the addition of SegWit recovery to the BitcoinABC codebase, recovery became possible, and the BCH chain survived an attempt at a double-spend attack by some thrifty miner(s) who realized that they could swoop in and take some of these trapped coins.

Since then, a couple guides have arisen that give an explanation of how to do a recovery, if those BCH sent to a 3xxxx Segwit address have the correct 'things', primarily a corresponding private key.

Here is my question/problem --- my BCH wallet is an HD Wallet created in Mycellium, and this was the 2nd 'account' in the wallet, and the 'second' key in that account. The BCH Derivation code is m/49'/0'/1'/0/1 . Problem is, I can only find a private key corresponding to the p2wskh-ps2h: key, and the p2sh: key in not importable in to Electron Cash wallet. How can I find a private key that corresponds to that wallet location in Electron Cash?

Here are some details:
3CSUDH5yW1KHJmMDHfCCWShWgJkbVnfvnJ
address the BCH was sent to... now, this address had BCH AND BTC sent to it at some point, and the BTC was spent, revealing the public key hash.
18dWL1ANKPwrhnbvNhrTDy8sxUzDGZ7YH2 is the 'legacy address' that Electron Cash spits out when I put the p2wskh-ps2h:"private key'

bitcoincash:pp67j94cfvnfg727etymlst9jts3uhfdkurqvtj2un is the public key address that Electron Cash shows the transaction occured on. If you put that key into the Electron Cash as a 'watch only' wallet, it still shows a 0.58 BCH Balance.

Problem is, I can't find out how to retrieve the private key for this address... the private key for 3CSUDH5yW1KHJmMDHfCCWShWgJkbVnfvnJ just gives the 18dWL1ANKPwrhnbvNhrTDy8sxUzDGZ7YH2 address in Electron Cash instead of bitcoincash:pp67j94cfvnfg727etymlst9jts3uhfdkurqvtj2un ....

Anyone think that have a hint where to check next? I have tried the BIP39 recovery site and can generate xprv/yprv keys, but none of these seem to be giving me the private key needed for the Derivation set of the HD wallet. Any help would be greatly appreciated!
submitted by sorcererhermes to btc [link] [comments]

Attention, benevolent BCH miners: A BCH segwit-recovery service is sorely needed!

These BCH are now recoverable; please read the update at the end of the post!

 
 

Background

In the short while since segwit activated on the BTC network and segwit addresses even-more-recently became the default for receiving BTC in the Trezor wallet - and perhaps other wallets too (soon?) - people have started accidentally sending their BCH to BTC-segwit addresses.
 
Due to the fact(s) that...
a) the BCH network supports P2SH (i.e. addresses starting with 3), but not segwit
... and ...
b) the sending wallets thus have no way of knowing that P2SH-wrapped segwit addresses really are "hiding" a segwit redeemscript
... people are losing access to their BCH, there's currently no way to prevent this, and it will continue happening.
 

Examples

(These are just the ones that I've noticed, but I'm sure there are many more that go straight to the various wallet service providers' support teams instead of via Reddit.)
 
To add insult to injury, the unlucky BCH owners are routinely told that there's no way to recover the coins (including by myself at the start) due to BCH not supporting segwit. And while that's currently true, it is ultimately only a half-truth.
After all, segwit opponents have often said that the satoshis in segwit addresses would be "anyone-can-spend" if the miners didn't enforce the segwit rules (i.e. ensuring that there's a proper witness/signature in the "segregated" part of the txs).
And on the BCH network the segwit rules aren't being enforced!
 

A Partial Solution

So I did some digging (e.g. in the segwit documentation and P2SH specification, BIP16) and came to the conclusion, which I'm sure that many have before me, that in order to spend money sent to a P2SH-wrapped segwit address, you only need to know the public key of the address (or more precisely: the RIPEMD160 hash of the SHA256 hash of a the public key).
Yes, a hash derived from the public key, not the private key.
Luckily, the 3-addresses don't by themselves reveal this public key hash, or anyone could've made "signed" txs from these "BCH-segwit" addresses - and someone probably already would have.
 

More Problems

So, given that it's relatively easy (for a technically inclined person, anyway) to get the public key corresponding to an address from their BIP39 mnemonic (aka wallet recovery seed), why aren't people re-claiming their BCH from these addresses?
Well, the "signature" that's needed isn't really a digital signature in the normal sense. Regular cryptocurrency transactions include a digital signature that doesn't reveal the private key that was used to make the signature in question. What's needed to "sign" for BCH-segwit addresses, however, is just literally including the public key hash that was mentioned above instead of a proper digital signature.
This means that anyone who sees such a transaction can just extract the public key hash from it - and then go on to create a conflicting transaction, using the same public key hash, that sends the same money elsewhere (to themselves, I would presume).
Technically, the second transaction would be a double-spend of the original and, as with all double-spends, it's the miners that would be the final arbiters of which transaction gets recorded in the block chain.
Additionally, a malicious miner could just create their own version of the transaction, either overtly redirecting the money to themselves, or covertly by changing the transaction to have no monetary outputs (i.e. all the money would go to the miner as "fee").
But the problems don't stop there. These segwit-spending transactions would be non-standard and as such wouldn't be relayed to the miners in the first place, nor would it be mined by miners even if it reached them (provided that the nodes and miners run with the default policy of ignoring non-standard txs, that is).
 

Suggested Solution

What we need is one or more trustworthy (yes, trust would unfortunately be required) miners to step up and make a BCH Segwit-Recovery Service for this particular purpose, in a somewhat similar way that they provided acceleration services for the BTC network (example1 and example2).
 
So... Does anyone know if a) miners are already working on this or b) know how to get in touch with them about this?
Or are there any benevolent miners here, that would like to:
 
/btc users, feel free to notify any miner contacts you may have - let's make this happen!
 
 

Update 1 (2017-09-11)

I made a proof-of-concept frontend to "show" what I'm envisioning such a service would look like for the end users (obviously it's ugly and needs to include javascript for key/hash/address validation, etc., but it should get the intention across), here:
https://btctroubadour.github.io/bch-recovery.html

Update 2 (2017-11-21)

It looks like some greyhat/vigilante, working with an unknown miner, was able to unilaterally claim some of the BCH that were "stuck" in BTC-segwit addresses (namely, the ones for which the public keys were revealed by the owners spending BTC from the same addresses), as explained in this post and comments: https://np.reddit.com/Bitcoin/comments/7eixcu/recovering_bch_sent_to_segwit_addresses/
For those that are affected by this, it means you no longer control your BCH (they were "stolen" by the greyhat), but he seems to be offering to give them back if you agree to letting him keep 30 % for his service (or "service", however you look at it). Either way, and given the alternative (100 % loss), you should certainly check if you're affected and decide how you want to proceed. As if that wasn't enough to deal with, there seems to be a ~2 week deadline, until "December 5th, 2017 at 23:59:59 UTC", after which it seems he's decided he's entitled to keep your money. :(

Update 3 (2017-11-28)

It looks like the greyhat has turned white! He's now offering to give back, for free, any and all BCH that were transferred to him (yes, 100 %!). Read his new update post and check if you were affected by this transfer.

Update 4 (2017-12-05)

Benevolent BCH miner finally found! The good people at btc.com have announced an automated BCH-segwit-recovery service, just as I outlined in my original post. Thanks a lot to Stellaluna19 for bringing it to my attention.
Here are links to btc.com's Twitter announcement as well as the recovery service itself:
https://twitter.com/btccom_official/status/933682190424199169
https://bch.btc.com/docs/help/bch_segwit_recovery
(Note that SatoshiLabs/Trezor developer, and well-known whitehat, -johoe have suggested some improvements to secure the process outlined by btc.com. You can read his suggestions in the last paragraph of this post - or in this one.)
submitted by btctroubadour to btc [link] [comments]

BCH sent to segwit BTC what to do?

Most people have said it's not possible to recover it while I've personally found a few posts explaining how to but which I didn't personally understand.
Example 1: Reddit post on /BTC
Example 2: Post made by Electron Cash.
Here is an image of the transaction on Ledger live. Here is the transaction on blockchair and here it is on bch.btc.
I sent the BCH to a BTC wallet (dropbit coin_ninja_com, contacted them but they said there is nothing to do but contact a miner?). Since I sent the money to myself on a BTC wallet that means I have the word seed but not the private key(?) that I need for recovery on Electron cash. How do I convert the word seed so I can recover it on Electron cash? I've asked similar questions before and people always give me this link: https://iancoleman.io/bip39/ without explaining to me how to use it. Is it possible to recover my BCH? Either by the methods listed in any of the above links or is the only option contacting miners?`
Edit: As for recovery I've found a few options. Not sure which are legit though.
https://bch-recovery.btc.com/
https://docs.google.com/forms/d/1R1zqeLLOynmPiqeqj4p6Ex7vLDbjmLrlE0z97RaSrYs/viewform?edit_requested=true
[email protected]
jtoomim
and people mention this btc.com thing over at this reddit thread but unsure of how to contact.
Also first scam attempt here by Ledgerhelp
submitted by John9tv to ledgerwallet [link] [comments]

Accidentally sent BCH to my BTC wallet, how to recover?

I sent some BCH from my Bitcoin.com wallet on iOS to my Edge wallet (also on iOS), but accidentally copied the BTC receiving address instead of the BCH one. I have the 24-word master seed for the BTC Edge wallet the funds were sent to.
The transaction is here: https://explorer.bitcoin.com/bch/address/3BsGaWzro8XjGun8ZKo7E4AVFcio1HvsPS
I have tried restoring the Edge BTC wallet on the Coinomi app with the 24-word master seed, and added a BCH wallet with the BTC derivation path M/44H/0H/0H instead of Bitcoin cash's default M/44H/145H/0H. I found this technique from this, where it apparently worked for the OP, but this hasn't worked for me so far.
The Coinomi app doesn't promt me on what type of wallet I want to restore, just gives me an option of using a BIP39 passphrase on top of the recovery phrase. After that, I get to select what cryptos I want to use the app for, and after that I can go and add another coin where I then get the advanced option that allows me to add the derivation path. So I add a BCH coin and add the previously mentioned derivation path as an advanced option, and continue to an empty wallet where I assume my BCH should be available if it had worked.
Any help on this would be much appreciated.
EDIT: From the Edge app's own website, the chances of being able to recover my BCH seem low... https://support.edge.app/support/solutions/articles/8000068596-how-to-recover-my-bch-if-i-accidentally-sent-into-a-bitcoin-segwit-address-on-edge-
However I assume those steps of collecting information is still the same that a miner would require in case they were to help me?
submitted by win10helpme3 to btc [link] [comments]

Transcript of Open Developer Meeting In Discord - 5/10/2019

[Dev-Happy] Blondfrogs05/10/2019
Channel should be open now
Chill05/10/2019
you all rock!
just getting that out of the way :wink:
Tron05/10/2019
Cheers everyone.
theking05/10/2019
Hi fabulous dev team!
Hans_Schmidt05/10/2019
Howdy!
Tron05/10/2019
No specific agenda today.
Questions?
Has everyone seen Zelcore wallet, and Spend app?
theDopeMedic05/10/2019
Any major development status updates that haven't been listed in #news?
Synicide05/10/2019
How was the meetup yesterday? I heard it would be recorded, it is uploaded anywhere yet?
Tron05/10/2019
And Trezor support on Mango Farm assets?
@Synicide Yes it was recorded. The Bitcoin meetup organizer has the video.
I talked about Ravencoin, but mostly about the stuff that was being built on/with/for Ravencoin.
There was about 70% overlap with folks who were at the Ravencoin meetup in March.
Synicide05/10/2019
awesome, looking forward to watching it when it's available
Tron05/10/2019
I'll hit up James and see if he's posting the video.
S1LVA | GetRavencoin.org05/10/2019
@theDopeMedic I'd follow github if youre interested in development status
Synicide05/10/2019
zelcore looks super slick. Been meaning to research its security more with the username/pw being stored on device
Chill05/10/2019
How is the progress on the restricted assets and testnet coming along? A secondary question would be about the approximate fork timeframe.
S1LVA | GetRavencoin.org05/10/2019
Has anyone heard from the community dev (BW) working on Dividends?
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Any word on BW and his progress w dividends?
@S1LVA | GetRavencoin.org LOL
Tron05/10/2019
@S1LVA | GetRavencoin.org Great question. I haven't heard.
Synicide05/10/2019
last meeting BlondFrogs said he would try to connect with BW as he was sick with the flu at the time. Maybe he has an update
S1LVA | GetRavencoin.org05/10/2019
I've tried to get in contact, but with no success.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Got a funny feeling...
Jeroz05/10/2019
Last time we left off with someone mentioning a foundation and Tron saying let’s discuss that next time iirc
kryptoshi05/10/2019
Has anyone taken a look at the merits for this proposal? Thoughts? https://medium.com/systems-nexus/modified-x16r-algorithm-proposal-for-constant-hash-rate-in-short-time-164711dd9044
Medium
Modified X16R algorithm proposal for constant hash rate in short time
Interpretation Lens V. a0.01
Tron05/10/2019
I did see it. Does anyone think this is a problem?
Synicide05/10/2019
It looks interesting... but I'm not sure what it is trying to solve. Looking at netstats, our 1 hour average block time is perfectly 1 minute
S1LVA | GetRavencoin.org05/10/2019
Last I heard from him he expressed how important finishing the code was. I wouldnt jump to conclusions on his absence within the community.
Synicide05/10/2019
x16r by nature will fluctuate, but DGW seems to be doing a good job keeping consistent block times
Tron05/10/2019
Because of relatively broad distribution across the algorithms, the block times are fairly consistent. It is possible, but very, very unlikely to get a sequence that takes up to 4x longer, but that's super rare, and only 4 minutes.
We did some timing analysis of the algorithms early on. A few are 1/2 as long as SHA-256 and some are up to 4x longer. But when you randomly select 16 it usually comes out about even.
Synicide05/10/2019
1hr avg: 1.02min - 24hr avg: 1min
I think we should focus on building, and not trying to fix what isnt necessarily broken
Tron05/10/2019
Agreed.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Agreed
Tron05/10/2019
Is everyone ok with the frequency (every other week) of this discussion?
Jeroz05/10/2019
(Added thumbs down to measure)
Tron05/10/2019
@Jeroz Did you do thumbs-up and thumbs down?
S1LVA | GetRavencoin.org05/10/2019
Seems appropriate. Its not like the devs dont poke around here and chat anyways.
Tron05/10/2019
Anything critical that we should be aware of?
Jeroz05/10/2019
When I need a dev, I poke a dev. When that dev is unavailable. I poke another one :smiley:
Hans_Schmidt05/10/2019
BlondFrogs was testing some github code last month to create a dividends snapshot database of asset holders at a given blockheight. Is that planned for inclusion? That's the only thing needed for dividends.
Jeroz05/10/2019
I hope I didn’t offend any devs
With poking around
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Was thinking voting would be an excellent use case for restricted assets. Local communities, nations, etc... could kyc their residents
radiodub05/10/2019
Is x16r will remain fpga mineable
Tron05/10/2019
@Jeroz We're hard to offend.
Chill05/10/2019
Is the general dev feeling that the next fork should and will include everything needed for the next 6-9 months (barring something completely unforeseen)?
Jeroz05/10/2019
I know :smile:
Tron05/10/2019
@radiodub Nearly impossible to stop FPGAs and still keep GPUs
Jeroz05/10/2019
About that: voting is another hard fork right? Not too soon?
Tron05/10/2019
FPGAs can be reprogrammed as fast. It is silicon (true ASIC) that we can obsolete with a tiny change.
@Jeroz Messaging, voting, Tags, Restricted Assets would require a hard fork (upgrade).
We could do them each individually, but folks get weary of upgrades, so current plan is to roll them together into one.
MrFanelli™05/10/2019
Good idea
Jeroz05/10/2019
Oh voting too?
MrFanelli™05/10/2019
People will like that
Jeroz05/10/2019
I thought that was coming later
Tron05/10/2019
Voting is the one that isn't being worked on now. Tags and Restricted assets have taken precedence.
Jeroz05/10/2019
I know. But you plan on waiting to fork until voting is also done?
That would have my preference tbh
But I can see an issue with too many things at the same time
Tron05/10/2019
If someone wants to step in, we've had one of our devs sidelined and he was working on BlockBook support so more light wallets can connect to Ravencoin. Mostly test cases needed at this point.
S1LVA | GetRavencoin.org05/10/2019
Thats a pretty large upgrade.. Bigger surface for unknowns
Rikki RATTOE Sr. SEC Impresantor05/10/2019
At what point would RVN community consider moving to ASICs because having a Bitcoin level of security would eventually be needed?
MrFanelli™05/10/2019
Never rikki
Tron05/10/2019
@S1LVA | GetRavencoin.org 100% Lots of testing on testnet and bounties.
[Dev-Happy] Blondfrogs05/10/2019
I am here :smiley:
Tron05/10/2019
@Rikki RATTOE Sr. SEC Impresantor There's nothing inherently wrong with ASICs but it tends to centralize to data centers and less opportunity for anyone to just run their gaming rig overnight and collect RVN.
Welcome Blondfrogs
MrFanelli™05/10/2019
Asics are too expensive. If we want normal people to mine, then we cant be an asic network
Rikki RATTOE Sr. SEC Impresantor05/10/2019
@Tron True but what happens when the chain needs a Bitcoin level of protection?
Tron05/10/2019
More GPUs, more FPGAs
MrFanelli™05/10/2019
Nvidia loves ravencoin :stuck_out_tongue:
Chill05/10/2019
ok, so we are pro FPGAs
𝕿𝖍𝖊 𝕯𝖔𝖓 𝕳𝖆𝖗𝖎𝖘𝖙𝖔 CEO ∞05/10/2019
Build it and they will come
Tron05/10/2019
It's all relative. It is cost to attack. If an ASIC isn't available for rent, then only option is rental of non-allocated GPUs
Rikki RATTOE Sr. SEC Impresantor05/10/2019
@Chill Eventually everyone will need FPGAs to be profitable on RVN, at that point I don't see why we just don't make the switch to ASICs
Tron05/10/2019
Also, as much as we don't focus on price, the price does matter because it determines the amount of electricity and hardware will be deployed to get the block reward. Price increase means more security, more mining means more security means higher price.
It's a circle.
Chill05/10/2019
someone tell that to the twitter handler
HailKira05/10/2019
you guys adding seedphrase to desktop wallet?
[Dev-Happy] Blondfrogs05/10/2019
@HailKira We will, just is not a high priority right now.
MrFanelli™05/10/2019
Twitter handle wants rvn ded
Rikki RATTOE Sr. SEC Impresantor05/10/2019
I just don't see much difference between ASIC and FPGA and I'd rather have the added nethash an ASIC will provide once GPUs are virtually kicked off the network
kryptoshi05/10/2019
I'm at 11 GB future proof
Tron05/10/2019
That also limits miners to big money, not gaming rigs.
Synicide05/10/2019
@Rikki RATTOE Sr. SEC Impresantor you have to keep in mind the 'added nethash' is all relative
Rikki RATTOE Sr. SEC Impresantor05/10/2019
FPGAs will limit miners to big $$$ too IMO
Tron05/10/2019
@kryptoshi New algo x16r-12G requires 12GB :frowning:
Seal <:cricat:> Clubber05/10/2019
But sperating smaller gb cards would lead to less adoption if we ever become a mainstream coin.
Adpotion of mining that is
Chill05/10/2019
but we are a mainstream coin
Seal <:cricat:> Clubber05/10/2019
Mains stream as in what eth did
Tron05/10/2019
@Rikki RATTOE Sr. SEC Impresantor I agree. Not a perfect solution.
Steelers05/10/2019
Is this a Dev meeting or Algo meeting :smiley:
Seal <:cricat:> Clubber05/10/2019
But if we ever go mem lane. We should aim for 6 or 8gb.
Tron05/10/2019
Open to other questions.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
@Tron Probably not the time and the place to have this discussion as we stand currently but IMO we're gonna have this conversation for real eventually
Seal <:cricat:> Clubber05/10/2019
Most cards have 6gb now.
kryptoshi05/10/2019
Why 12 gb ? Such a massive jump
Seal <:cricat:> Clubber05/10/2019
^
Would also like to know
Tron05/10/2019
@kryptoshi I was joking. You said you had 11GB card.
Seal <:cricat:> Clubber05/10/2019
Haha
You got em good
I cant imaghine the face he had when he was 1gb short
Lel
Rikki RATTOE Sr. SEC Impresantor05/10/2019
That's what she said
kryptoshi05/10/2019
Hahaha
MrFanelli™05/10/2019
need a 2080ti
Seal <:cricat:> Clubber05/10/2019
How much does the VII have?
16?
[Dev-Happy] Blondfrogs05/10/2019
Any other questions you have for us?
Hans_Schmidt05/10/2019
@[Dev-Happy] Blondfrogs You were testing some github code last month to create a dividends snapshot database of asset holders at a given blockheight. Is that planned for inclusion? That's the only thing needed for dividends.
Chill05/10/2019
a dev might want to contact Crypto Chico for some 'splaining
[Dev-Happy] Blondfrogs05/10/2019
I still haven't contacted the developer that was working on dividends. Was pretty busy with some other stuff. I will contact him this next week, and see where we are at for that.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Chico doesn't do interviews, shame. Tron would be a much needed interview for his community
[Dev-Happy] Blondfrogs05/10/2019
As far as releasing dividends, I can be released at anytime the code is finished and doesn't require any voting or hardfork to occur
kryptoshi05/10/2019
Android asset aware wallet?
Seal <:cricat:> Clubber05/10/2019
Is in beta right
Tron05/10/2019
Testing went well today on Android. Nearing release.
[Dev-Happy] Blondfrogs05/10/2019
as it is a mechanism that is wallet specific
liqdmetal05/10/2019
no protocol level dividends you guys are saying?
[Dev-Happy] Blondfrogs05/10/2019
correct
Tron05/10/2019
DM me if you want to test Android with Asset support. I'll send you the .APK.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
RVN gonna be on tZero wallet? :yum:
liqdmetal05/10/2019
why not? what is the logic on non-protocol dividends
assets + protocol dividends is nirvana
[Dev-Happy] Blondfrogs05/10/2019
dividends is pretty much sending payments to addresses. Right now, you would have to do this manually. The dividends code, will allow this to be done quicker and easier.
No consensus changes are required.
Tron05/10/2019
New Android wallet is BIP44 and original Android wallet is BIP32/BIP39 so the words will not find the funds. You'll need to send them to another wallet, and then send them to new BIP44 derived address.
liqdmetal05/10/2019
we already have payments to addresses
so dividends is not a feature so much as simple wallet script
Hans_Schmidt05/10/2019
@[Dev-Happy] Blondfrogs The dividend code changes look risky'er to me than messaging. Would you consider "tags" branch test-ready?
[Dev-Happy] Blondfrogs05/10/2019
Not yet @Hans_Schmidt
Dividends is easier then you would think if coded correctly. I still haven't seen the code from the community developer. Excited to view it though.
Hans_Schmidt05/10/2019
@[Dev-Happy] Blondfrogs Sorry- I meant restricted, not dividend
kryptoshi05/10/2019
@Tron on the Android wallet, anyone successfully added their own node and got it to sync faster? Always have issues. I have a supped up node and cannot get it to work with the Android wallet...
[Dev-Happy] Blondfrogs05/10/2019
@Hans_Schmidt Oh, that makes more sense. Yes, they are very risky! That is why we are going to create a new bug bounty program for restricted assets testing.
Rikki RATTOE Sr. SEC Impresantor05/10/2019
Once the network does get flooded w FPGAs, should we even consider changing the algo a couple times a year? That would only give bitstream developers added time to hoard their creations for themselves
Kind of like they're already doing with their x16r bitstreams :yum:
kryptoshi05/10/2019
Flooded... lol... like that hardware has mass production scale like gpus...come on dude
MrFanelli™05/10/2019
Bip44 wallet? :smiley:
Rikki RATTOE Sr. SEC Impresantor05/10/2019
@kryptoshi Eventually yes, where there's $$$ to be made, people make things happen
MrFanelli™05/10/2019
So can we trade from that in the new Binance Dex when RVN get listed?
kryptoshi05/10/2019
@Rikki RATTOE Sr. SEC Impresantor Yes Soon TM lol. :soontm:
Tron05/10/2019
@kryptoshi There are some things we can do to speed it up. For a new wallet, it shouldn't need to sync. For recovered wallet, it needs to sync from beginning of BIP44 wallet support on iOS so words can be moved between the two.
Other options include grabbing the first derived address and looking it up on an explorer to see when it was first used and sync from there.
Another option is to add an optional number with the 12 words so it knows when to start syncing.
There isn't a good reason on an SPV wallet to sync before the seed was created.
kryptoshi05/10/2019
Cool. Glad you are looking at speedup options.. :right_facing_fist: :left_facing_fist:
[Dev-Happy] Blondfrogs05/10/2019
@MrFanelli™ If the binance dex support RVN deposits. I am sure you would be able to send from it
MrFanelli™05/10/2019
Has binance reached out for any info or anything?
I seen that we ranked in some voting competition they had on twitter
for an ama
Rikki RATTOE Sr. SEC Impresantor05/10/2019
I believe we'll need to create a fund of approximately $300,000 in order to get a BNB-RVN asset created and listed on the Binance FDEX
[Dev-Happy] Blondfrogs05/10/2019
In order to work with binance we need Ravencoin integrated into Blockbook.
Tron05/10/2019
@MrFanelli™ I've reached back out to Binance on the AMA.
MrFanelli™05/10/2019
Awesome :smile:
kryptoshi05/10/2019
@Tron you are a natural on the interviews... cool as a cucumber. :sunglasses:
Tron05/10/2019
Thanks @kryptoshi
[Dev-Happy] Blondfrogs05/10/2019
Cool. We are done for today.
Please don't ask us any more questions :smiley:
Tron05/10/2019
Thanks everyone!!!!
[Dev-Happy] Blondfrogs05/10/2019
Cya everyone!!
S1LVA | GetRavencoin.org05/10/2019
Cya happy feet, Thanks
Thanks Tron
Seal <:cricat:> Clubber05/10/2019
:bepbep:
submitted by mrderrik to Ravencoin [link] [comments]

Groestlcoin Release September 2018

Introduction

As always, the past 3 months since 22nd June have been crazy busy. The bears might still be around, but the show must go on and of course has not slowed the Groestlcoin development team in the slightest. Here’s a quick overview of what has already happened since the last release: - Integrated into the bitbns exchange, with the ability to buy Groestlcoin directly with the Indian Rupee. - Groestlcoin Rebrand Vote – Whilst there was much talk and push for a rebrand vote, the overall result was almost unanimously in favour of keeping our unique and conversation-starting name. With just 83 votes to Rebrand, and 2577 votes to No Rebrand. Thank you for all who voted, the funds raised are being used to fund ongoing hosting and development costs. - Integrated into the Cryptobridge exchange. Cryptobridge is a popular decentralised exchange where you always hold the private keys to your funds, only YOU have access to them. - Groestlcoin has been added to SimpleSwap – Groestlcoin can now be swapped with over 100 other cryptocurrencies, without signing up! - Groestlcoin has been added to UnoDax, one of the leading cryptocurrency exchanges in India, with TUSD, BTC and INR trading pairs. - Groestlcoin has been added to SwapLab.cc, where you can buy Groestlcoin using Bitcoin and over 50 other altcoins. Purchasing with VISA/Mastercard is coming VERY SOON. Discussed later: - Groestlcoin has been listed on #3 largest exchange in the world on volume, Huobi Global! More on this to come further on in the announcements. - Groestlcoin has been added to the Guarda Multi-Currency Wallet. - Groestlcoin has been added to Melis Multi-Device, Multi-Account, Multi-Platform, Multi-Signature advanced wallet! Already this list is far more than most other cryptocurrencies have achieved in the past 3 months. But this is just the tip of the iceberg of what has been developed.

What's been Happening?

GRSPay Released

We are so excited for this, that it has it's own separate reddit thread. Head over there now at https://www.reddit.com/groestlcoin/comments/9ikr5m/groestlcoin_releases_grspay/? to see more on this!
https://www.melis.io/assets/logo-navbar-4b6f0d372f15b2446d3fa4c68f346e4fb08ee113941186cee58fd6135f3f8b7d.svg

Melis Wallet

The the most advanced wallet for Bitcoin, Bitcoin Cash, Litecoin and now Groestlcoin.
With Melis you have the complete control of your bitcoins and private keys, you can define spending limits policies and make use of two or more factors authentication. Melis is open source, published on GitHub.

How Melis Works?

You can create as many accounts as you want. An account is a part of your wallet that can be customised to your requirements. You can choose how many co-signers are required to spend funds. The accounts are completely independent and act like separate wallets from each other but can be accessed via the same details. A core feature of Melis is the ability to set a ‘primary’ device. With this you can set an account as ‘Secure’ so it is only viewable (and accessible at all) from the Primary device. You can have a savings account hidden from the outside world whilst also having your ‘spending’ funds available on the go. With Melis you can create a multi-signature account between N people, where up to N signatures are required to sign a transaction, choosing if any of those should be mandatory.
Core Features:
https://guarda.co/assets/images/1PGo4ID.svg?1537791124643

Guarda Wallet

Safer than ever! Desktop Light Wallet - Anonymous and fast!
With Guarda Multi-currency Desktop Light Wallet you don’t need to register. Guarda has no access to your private keys or funds. You can receive, send, store, buy and exchange cryptocurrencies in complete anonymity and safety. All these features are available on Linux, Windows or MacOS. Choose the one that suits you!
More info about Guarda wallet on www.guarda.co
https://holytransaction.com/images/logo.png

Integrated into HolyTransaction

What is HolyTransaction?

HolyTransaction gives users access to the crypto world with a universal cryptocurrency wallet and instant exchange.

Features

For more information, visit Holy Transaction here.
https://www.groestlcoin.org/wp-content/uploads/2018/09/next-grs-groestlcoin.jpg

Integrated into NEXT Wallet

What is NEXT?

NEXT is a modern, next-generation stylish open-source Desktop wallet.

Features

For more information, visit NextWallet here.
https://blockchainfinancial.com/mediaserve2018/09/admin-06143647-bcf_logo_vec_256x256.png

Integrated into Blockchain Financial

What is Blockchain Financial?

Blockchain Financial is a set of web based services for individuals and companies that want to make things happen with the Cryptocurrencies Ecosystem. - For those that don't know anything about cryptocurrencies, we offer tools that will let them receive, send and operate with an assortment of coins. - For those that are already riding the wave, we offer tools that will let them do all those things that they weren't able to do.

Blockchain Financials mission

We're not here to reinvent the wheel. We're here to make it run smoother for you, and we provide some of the most useful services you'll find on the internet, made in a way that is easy to understand and use on a daily basis. In short, we're a bunch of people that claim to be Crypto Evangelists. We strongly believe in cryptocurrencies, and our main promise is to push them up so more people get involved and take all the advantages they offer.

More information from Blockchain Financial

Back in 2014, the world was taken by storm when Facebook approved the first cryptocurrencies tipping apps. The first was for Dogecoin, and the second was for multiple coins.
The project was hosted on whitepuma.net, and persisted for almost two years, built up a massive user community and gave a home to Bitcoin, Litecoin, Dogecoin and dozens of other bitcoin-based altcoins.
After very active months, the tipping hype started to fade away. Then, the developers decided to jump into the next stage: bringing not only tipping, but also mining and a widget that could be embedded on websites to allow everyone to accept payments. Sadly, the work was never completed because the project started to require an unsustainable amount of resources. Then, in a painful decision, a shutdown was announced by December 2015.
A couple of months after whitepuma.net was closed, the source code was released by its creator as Open Source on GitHub. But it wasn't maintained.
Now, some of the original members of the dev and admin teams gathered up with a handful of the WhitePuma's elite users, and decided to make something good with the best pieces of the old source code. That, with fresh new ideas and the power of the BardCanvas engine, synthesized the core of Blockchain Financial.
More info about Blockchain Financial wallet on .
For more information, visit [Blockchain Financial](www.blockchainfinancial.com)
https://www.huobi.com/image/logo.aeb4723.svg

Groestlcoin Listed on Huobi

Who are Huobi?

Huobi was founded in China and is now based in Singapore, with offices in Hong Kong, South Korea, Japan and the North America, currently sitting #3 in volume on Coinmarketcap. Huobi is a great leap forward for our growing presence in Asia and we are very excited to be listed here!
You can find the official Huobi announcement here.

Groestlcoin Core v2.16.3 - Please Update ASAP

A new major Groestlcoin Core version 2.16.3 is now available for download which includes both a Denial of Service component and a critical inflation vulnerability, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.
v2.16.3 is now the official release version of Groestlcoin Core. This is a new major version release with a very important security updates. It is recommended to upgrade to this version as soon as possible. Please stop running versions of Groestlcoin Core affected by CVE-2018-17144 ASAP: These are 2.13.3 and 2.16.0.
As a result in this, all exchanges and services have been asked to upgrade to this version, so please be patient if wallets go in to maintenance mode on these services.

What's new in version v2.16.3?

This is a major release of Groestlcoin Core fixing a Denial of Service component and a critical inflation vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2018-17144) exploitable by miners that has been discovered in Groestlcoin Core version 2.13.3 and 2.16.0. It is recommended to upgrade to 2.16.3 as soon as possible. If you only occasionally run Groestlcoin Core, then it's not necessary to run out and upgrade it right this second. However, you should upgrade it before you next run it. If you know anyone who is running an older version, tell them to upgrade it ASAP. Stored funds are not at risk, and never were at risk. At this time we believe over half of the Groestlcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability. However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

The Technicals

In Groestlcoin Core 2.13.3, an optimization was added (Bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (Bitcoin Core PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 2.13.3 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to 2.1.0.6). Thus, in Groestlcoin Core 2.13.3, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported. In Groestlcoin Core 2.16.0, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists. Thus, in Groestlcoin Core 2.16.0, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur. However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of Groestlcoin as they would be then able to claim the value being spent twice.
Groestlcoin would like to publicly thank Reddit user u/Awemany for finding CVE-2018-17144 and reporting it (https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2018-Septembe000064.html). You deserve gratitude and appreciation from cryptoworld, and you have ours. If you want to support him for his work, please consider donating to him on his bitcoin cash address: bitcoincash:qr5yuq3q40u7mxwqz6xvamkfj8tg45wyus7fhqzug5
http://i.imgur.com/3YhyNZK.png

Groestlcoin Electrum-GRS 3.2.2 - Ledger & Trezor Edition

What is Electrum-GRS?
Electrum-GRS is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes:

http://i.imgur.com/3YhyNZK.png

Electrum-GRS Mobile Android

What is Electrum-GRS Mobile?

Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.

Changes

Groestlcoin EasyVanity Released

Groestlcoin EasyVanity is a Windows app is built from the ground-up in C# and makes it easier than ever before to create your very own bespoke Groestlcoin address(es), even whilst not connected to the internet! You can even generate multiple keys with the same prefix and leave it on overnight whilst your CPU or GPU collects and stores these addresses locally.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then Groestlcoin EasyVanity is the right choice for you to create a more personalized address.

Features

• Ability to continue finding keys after first one is found • Includes warning on startup if connected to the internet • Ability to output keys to a text file (And shows button to open that directory) • Ability to make your match case sensitive (Where possible) • Show and hide the private key with a simple toggle switch, and copy the private key straight to your clipboard • Show full output of commands • Includes statistics whilst the application is running • Ability to choose between Processor (CPU) and Graphics Card (GPU) • Automatically detects 32 or 64 bit systems • Features both a Light and Dark Material Design inspired Themes • EasyVanity's search is probabilistic, and the amount of time required to find a given pattern depends on how complex the pattern is, the speed of your computer, and whether you get lucky. • EasyVanity includes components to perform address searching on your CPU (vanitygen) and your OpenCL-compatible GPU (oclvanitygen). Both can be built from source, and both are included in the Windows binary package. • Prefixes are exact strings that must appear at the beginning of the address. When searching for prefixes, Easyvanity will ensure that the prefix is possible, and will provide a difficulty estimate. • The percentage displayed just shows how probable it is that a match would be found in the session so far. If it finds your address with 5% on the display, you are extremely lucky. If it finds your address with 92% on the display, you are unlucky. If you stop EasyVanity with 90% on the display, restart it, and it finds your address with 2% on the display, your first session was unlucky, but your second session was lucky. • EasyVanity uses the OpenSSL random number generator. This is the same RNG used by groestlcoin and a good number of HTTPS servers. It is regarded as well-scrutinized. Guessing the private key of an address found by EasyVanity will be no easier than guessing a private key created by groestlcoin itself. • To speed up address generation, EasyVanity uses the RNG to choose a private key, and literally increments the private key in a loop searching for a match. As long as the starting point is not disclosed, if a match is found, the private key will not be any easier to guess than if every private key tested were taken from the RNG. EasyVanity will also reload the private key from the RNG after 10,000,000 unsuccessful searches (100M for oclvanitygen), or when a match is found and multiple patterns are being searched for. • Free software - MIT. Anyone can audit the code. • Written in C# - The code is short, and easy to review.

Groestlcoin Sentinel (Android & Blackberry) – Mainnet + Testnet

What is Sentinel?

Groestlcoin Sentinel is the easiest and fastest way to track/receive/watch payments in your offline Groestlcoin Wallets. Groestlcoin Sentinel is compatible with any standard Groestlcoin address, BIP44 XPUB (Extended Public Key) BIP49 YPUB and BIP84 ZPUB
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that particular wallet.

What's New?

The P2SH paperwallet supports creating P2SH paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes
Features
The BECH32 paperwallet supports creating BECH32 paperwallets in bulk, keypair generation with QR codes and sweeping tool. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Features
![WebWallet](https://i.imgur.com/Z2oj7bj.png)

Groestlcoin Web Wallet Update 1.4

What is Groestlcoin Web Wallet?
Groestlcoin Webwallet is an open source, multisignature, HD Wallet and more! Webwallet is a a open source browser based Groestlcoin webwallet.
Webwallet is a playground for Groestlcoin in javascript to experiment with. It supports multisig, OP_HODL, RBF and many more. Groestlcoin believes strongly in privacy, the live version does not collect and store IP or transaction data.
Changes:
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

Forkdrop.io Week 6 - A Novice's Guide to Claiming Forks

forkdrop.io and follow us on Twitter https://twitter.com/forkdrop
We are at 65 Bitcoin Forks/Airdrops 13 Altcoin, 12 Historic and 59 exchanges tracked.
This week, we launched our Guides section which features includes a multi-part in-depth guide for using the bitcoin_fork_claimer tool securely and privately on an Ubuntu live-boot system. They include many screenshots to help step through the process at a comfortable pace.
https://forkdrop.io/novices-guide-to-claiming-forked-bitcoin-value.html
Among other things, we take you through setting up a live-boot Linux environment:
https://forkdrop.io/secure-live-boot-ubuntu-for-bitcoin-keys.html
Installing and running the Tor Browser in said environment:
https://forkdrop.io/running-tor-browser-from-ubuntu-live-boot.html
Downloading Ian Coleman's BIP39 tool for running offline and using it:
https://forkdrop.io/running-bip-39-tool-on-secure-offline-ubuntu-system.html https://forkdrop.io/using-ian-colemans-bip-39-tool.html
Covering the basics of u/ymgve's tool for preparing to run it:
https://forkdrop.io/preparing-to-use-bitcoin-fork-claimer-tool.html https://forkdrop.io/finding-parameters-for-bitcoin-fork-claimer-tool.html
Tips on finding exchanges to deposit while keeping your identity as private as you want to be:
https://forkdrop.io/scouting-exchanges-to-sell-forked-bitcoin-value.html
And then actually running the scripts:
https://forkdrop.io/running-bitcoin-fork-claimer-on-ubuntu.html
20 articles in total which will grow in size as we go forward.
There were also some minor feature improvements this week, such as adding the marker icon to the per-coin and per-exchange pages.
Summary of dataset updates:
Stuff we are working on:
  1. More guides/articles & improved presentation of existing articles
  2. Night mode (much requested!)
  3. Better price info
  4. Tell us what you want to see!
Ways to support the site:
  1. Participate in BitcoinAirdrops - we read it all
  2. Submit us your info, corrections, etc.
  3. Follow us on Twitter: https://twitter.com/forkdrop
  4. Participate in the Disqus discussion forms for each coin/exchange
  5. Use the referral links when signing up for exchanges <3 <3 <3
  6. Send donations to donation addresses on the footer of the site
All the Best,
The Forkdrop.io Team
submitted by forkdrop to BitcoinAirdrops [link] [comments]

How secure is a HD wallet using BIP39 wordlists?

I've been reading up on HD wallets used by the likes of Trezor, Ledger and a bunch of others (see http://support.ledgerwallet.com/knowledge_base/topics/how-to-restore-my-backup-without-a-ledger-wallet as an example).
I'm no cryptographer and the content in github seems pretty convincing, except that there is a common BIP39 dictionary of words used by BIP32 HD wallets, which effectively provides 2048 words x the length of the mnemonic (12 words, 24 words etc).
This to me then suggests there is a finite amount of HD wallets available - specifically (24 words x 2)2048.
I'm aware that in bitcoin miners are incented to do the right thing rather than try to crack a private key, but why wouldn't someone instead try to brute force all the possible HD wallets in existance? That would surely provide more loot to someone motivated....
submitted by anonEmous99993333 to Bitcoin [link] [comments]

Burning BTC for Smart Contracts, Or How To Add $13,784,504,653 to Bitcoin's Market Cap

Ethereum is a novel VM language built on an altledger whose native token is ETH. ETH's market cap has recently soared to $13,784,504,653 USD, demonstrating beyond a shadow of a doubt that the approach has real utility for Bitcoin users.
Through a process called Proof of Burn, BTC can be sent from standard BIP39 wallets to a provably unspendable Bitcoin address, e.g. 1BitcoinEaterAddressDontSendf59kuE, and deterministically redeemed for a token that is substantially similar to ETH, which we'll call HTE.
Merge mining of the HTE ledger's smart contract state trees will give the resulting HTE ledger full SPV support. Additional techniques can be used to create secure HTE light clients, such as VerSum. Bitcoin users needn't worry about acquiring any of the HTE token, since BTC can be burned for HTE at any time.
Unlike Blockstream's famed merge mined 2WP sidechains, the HTE ledger is built on top of Bitcoin mainnet, hence HTE doesn't share the same flawed security model of 2WP sidechains where miners can potentially steal funds outright in a 51% attack. So long as Bitcoin mainnet isn't 51% attacked, the HTE ledger lives on inside of Bitcoin.
The beauty of the HTE approach is it results in the same public permissionless utility dynamic which exists today in the Ethereum altledger. That is, domain names, equities, real estate, prediction market contracts and so forth are all permanently etched into the HTE ledger and therefore into Bitcoin's bulletproof public mainnet chain for all eternity.
The proposed system can even sustain itself by distributing a percentage of HTE burned to fuel smart contracts to Bitcoin miners who opt to participate in merge mining HTE state trees.
Also, there is nothing restricting HTE to Ethereum's VM. Any other smart contracting VM, such as that proposed for Tezos (TEZ), could be used as well (e.g. ZET). In all cases, these Proof of Burn embedded ledgers would be useable on-demand inside of normal Bitcoin wallets, and all smart contract functionality would reside on one universal ledger, that of Bitcoin's.
submitted by insette to btc [link] [comments]

In Defense of Non-Monetary Transactions on Bitcoin

In his address to the BC mailing list c. HK Scaling, Greg Maxwell stated quote:
Since Bitcoin is an electronic cash, it isn't a generic database; the demand for cheap highly-replicated perpetual storage is unbounded, and Bitcoin cannot and will not satisfy that demand for non-ecash (non-Bitcoin) usage, and there is no shame in that. Fortunately, Bitcoin can interoperate with other systems that address other applications, and--with luck and hard work--the Bitcoin system can and will satisfy the world's demand for electronic cash.
But what if fielding non-ecash gave Bitcoin a new direct consumer to Bitcoin mainnet avenue?
Let's consider one such avenue: CryptoVenmo. Imagine Venmo but with USD-backed USDX issued on the blockchain, its reserves proven by respected auditors, its funds managed in Bitcoin BIP39 mnemonic wallets.
Further, let's assume CryptoVenmo aggregates buyers of USDX from available sites and APIs (think: E-trade), presenting its own view of that data as a value added service.
Imagine if in order to "send money to friends" a la Venmo, users would need to pay Bitcoin miners to use the superior payment system, which would force those users to acquire a tiny amount of BTC. Those users wouldn't have to care about their own country's economic policies in order to be in a position of needing BTC.
The above is just one example of how non-ecash "spam" could help grow Bitcoin by potentially millions of more users on mainnet a la Venmo, without ever having to hard sell anyone on BTC.
submitted by insette to btc [link] [comments]

Bitcoin-development Digest, Vol 45, Issue 37 | Joshua | Feb 11 2015

Joshua on Feb 11 2015:
UNSUBSCRIBE
On Wed, Feb 11, 2015 at 2:25 AM, <
bitcoin-development-request at lists.sourceforge.net> wrote:
Send Bitcoin-development mailing list submissions to
bitcoin-development at lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
or, via email, send a message with subject or body 'help' to
bitcoin-development-request at lists.sourceforge.net
You can reach the person managing the list at
bitcoin-development-owner at lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bitcoin-development digest..."
Today's Topics:
  1. Re: Proposal for P2P Wireless (Bluetooth LE) transfer of
    Payment URI (Eric Voskuil)
  2. Proposal: Requiring a miner's signature in the block header
    (Hector Chu)
  3. Re: Proposal: Requiring a miner's signature in the block
    header (Natanael)
Message: 1
Date: Tue, 10 Feb 2015 09:56:39 -0800
From: Eric Voskuil <eric at voskuil.org>
Subject: Re: [Bitcoin-development] Proposal for P2P Wireless
 (Bluetooth LE) transfer of Payment URI 
To: M?rtin H?bo??tiak <martin.habovstiak at gmail.com>
Cc: Bitcoin Dev <bitcoin-development at lists.sourceforge.net>, Paul Puey
 <[paul at airbitz.co](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev)> 
Message-ID: <54DA4657.5080604 at voskuil.org>
Content-Type: text/plain; charset="utf-8"
On 02/10/2015 09:16 AM, M?rtin H?bo??tiak wrote:
I'm not sure if I was clear enough. Handshake should be used to
establish authenticated AND encrypted communication using ECDH (or
just DH, but I think it's easier to use ECDH, since required functions
are already used in Bitcoin protocol), like RedPhone does. BTW
knowledge of verification string is useless to the attacker.
Yes, I think this was clear from your description.
Yes, the customer must verify it verbally and the merchant shouldn't
send the transaction before verification. Other possibility is that in
case of differing verification strings new address is generated, so
attacker doesn't know the address. But in this case, amount is leaked
and there is quite high probability it can be found in the Blockchain.
Yes, for each handshake the payment request would need to contain a
different address, mitigating some of the privacy loss.
Anyway, I don't believe the transaction can be made securely without
such interaction except with white-listing public keys, so I see no
reason why interaction should be problematic.
It can be done securely and privately by transfer of a shared secret
through a private channel.
We don't have such strict regulations but I agree that security is
important. Currently I think that verbal verification and manual
confirmation is the best way to achieve high security and reasonable
user-friendliness.
I think for a broadcast model (e.g. Bluetooth only) that is the only
want to ensure integrity and privacy. A narrow cast can use proximity to
establish trust.
2015-02-10 17:55 GMT+01:00 Eric Voskuil <eric at voskuil.org>:
Martin,
I like your idea for the commit protocol in that it resolves the
vandalous address substitution attack. However, I don't see a way to
prevent privacy loss without adverse impact to the scenario.
Anyone could perform the handshake and thereby obtain the payment
request. Therefore to prevent inadvertent disclosure the customer must
visually confirm the "phrase" and then verbally tell the merchant to
proceed by sending the payment request.
One might argue that it's sufficient to preserve the integrity of the
transaction while suffering the privacy loss, especially given that a
hijacked handshake should never result in a completed transaction -
unless of course the hijacker pays.
But imagine someone purchasing their meds. HIPAA requires the checkout
queue to form behind a yellow line. That speaks directly to this
question.
e
On 02/06/2015 01:07 AM, M?rtin H?bo??tiak wrote:
2015-02-06 2:29 GMT+01:00 Eric Voskuil <eric at voskuil.org>:
On 02/05/2015 04:36 PM, Martin Habov?tiak wrote:
I believe, we are still talking about transactions of physical
people in physical world. So yes, it's proximity based - people
tell the words by mouth. :)
Notice from my original comment:
A MITM can substitute the key. If you don't have verifiable
identity associated with the public key (PKI/WoT), you need
a shared secret (such as a secret phrase).
I said this could only be accomplished using a shared secret or a
trusted public key. Exchanging a value that is derived from a pair of
public keys is a distinction without a difference. The problem remains
that the parties must have a secure/out-of-band channel for
communicating this value.
The fact that they are face-to-face establishes this channel, but that
brings us back to the original problem, as it requires manual
verification - as in visual/audible scanning of the two values for
comparison. At that point the visual comparison of the address, or
some
value derived from it, is simpler.
I have never been against manual verification. What I'm trying to say
is let's just make manual verification easier and more secure.
Comparison of address is simpler for the coder but also simpler to
attack. It has these problems:
  • Addresses broadcasted in plaintext (privacy issue)
  • Amounts broadcasted in plaintext (privacy issue)
  • Address is long - takes lot of time to verify (user experience issue)
  • Address prefix can be brute-forced, if too short or used to make
"black hole" address if longer (vandalism issue)
Commit protocol can be used for both the encryption and the
authentication while user experience is not bad and everything is
still secure.
In case of RedPhone, you read those words verbally over not-yet-
verified channel relying on difficulty of spoofing your voice. Also
the app remembers the public keys, so you don't need to verify
second time.
This is reasonable, but wouldn't help in the case of an ad-hoc
connection between parties who don't know each other well.
I suggest you to try RedPhone (called Signal on iPhone) yourself.
It's free/open source, Internet-based and end-to-end encrypted. You
may find it useful some day. Also I'm willing to help you with
trying it after I wake up. (~8 hours: Send me private e-mail if
you want to.)
I appreciate the offer. I really don't trust any smartphone as a
platform for secure communication/data. But encrypting on the wire
does
of course shrink the attack surface and increase the attacker's cost.
e
D?a 6. febru?ra 2015 1:22:23 CET pou??vate? Eric Voskuil
<eric at voskuil.org> nap?sal:
On 02/05/2015 04:04 PM, M?rtin H?bo??tiak wrote:
That's exactly what I though when seeing the RedPhone code, but
after
I studied the commit protocol I realized it's actually secure and
convenient way to do it. You should do that too. :)
I was analyzing the model as you described it to me. A formal
analysis
of the security model of a particular implementation, based on
inference
from source code, is a bit beyond what I signed up for. But I'm
perfectly willing to comment on your description of the model if you
are
willing to indulge me.
Shortly, how it works:
The initiator of the connection sends commit message containing the
hash of his temporary public ECDH part, second party sends back
their
public ECDH part and then initiator sends his public ECDH part in
open. All three messages are hashed together and the first two
bytes
are used to select two words from a shared dictionary which are
displayed on the screen of both the initiator and the second party.
The parties communicate those two words and verify they match.
How do they compare words if they haven't yet established a secure
channel?
If an attacker wants to do MITM, he has a chance of choosing right
public parts 1:65536. There is no way to brute-force it, since that
would be noticed immediately. If instead of two words based on the
first two bytes, four words from BIP39 wordlist were chosen, it
would
provide entropy of 44 bits which I believe should be enough even
for
paranoid people.
How this would work in Bitcoin payment scenario: user's phone
broadcasts his name, merchant inputs amount and selects the name
from
the list, commit message is sent (and then the remaining two
messages), merchant spells four words he sees on the screen and
buyer
confirms transaction after verifying that words match.
So the assumption is that there exists a secure (as in
proximity-based)
communication channel?
e
2015-02-06 0:46 GMT+01:00 Eric Voskuil <eric at voskuil.org>:
On 02/05/2015 03:36 PM, M?rtin H?bo??tiak wrote:
A BIP-70 signed payment request in the initial broadcast can
resolve the
integrity issues, but because of the public nature of the
broadcast
coupled with strong public identity, the privacy compromise is
much
worse. Now transactions are cryptographically tainted.
This is also the problem with BIP-70 over the web. TLS and other
security precautions aside, an interloper on the communication,
desktop,
datacenter, etc., can capture payment requests and strongly
correlate
transactions to identities in an automated manner. The payment
request
must be kept private between the parties, and that's hard to do.
What about using encryption with forward secrecy? Merchant would
generate signed request containing public ECDH part, buyer would
send
back transaction encrypted with ECDH and his public ECDH part. If
receiving address/amount is meant to be private, use commit
protocol
(see ZRTP/RedPhone) and short authentication phrase (which is
hard
to
spoof thanks to commit protocol - see RedPhone)?
Hi Martin,
The problem is that you need to verify the ownership of the public
key.
A MITM can substitute the key. If you don't have verifiable
identity
associated with the public key (PKI/WoT), you need a shared secret
(such
as a secret phrase). But the problem is then establishing that
secret
over a public channel.
You can bootstrap a private session over the untrusted network
using
a
trusted public key (PKI/WoT). But the presumption is that you are
already doing this over the web (using TLS). That process is
subject
to
attack at the CA. WoT is not subject to a CA attack, because it's
decentralized. But it's also not sufficiently deployed for some
scenarios.
e
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
Message: 2
Date: Wed, 11 Feb 2015 08:54:15 +0000
From: Hector Chu <hectorchu at gmail.com>
Subject: [Bitcoin-development] Proposal: Requiring a miner's signature
 in the block header 
To: bitcoin-development at lists.sourceforge.net
Message-ID:
 < 
CAAO2FKEFxC_byt4xVJb0S-7yy0M7M-Av7MHUH-RBDuri_GAFtw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
A proposal for stemming the tide of mining centralisation -- Requiring a
miner's signature in the block header (the whole of which is hashed), and
paying out coinbase to the miner's public key.
Please comment on whether this idea is feasible, has been thought of
before,
etc., etc. Thank you.
Motivation
Mining is centralising to a handful of pool operators. This is bad for a
number of political reasons, which we won't go into right now. But I have
always believed that some years down the line, they could hold the users
hostage and change the rules to suit themselves. For instance by
eliminating
the halving of the block reward.
Solution
Currently the block header is formed by the pool operator and distributed
for
hashing by the pooled miners. It is possible to divide the work among the
miners as the only thing that is used to search the hash space is by
changing
a nonce or two.
I propose that we require each miner to sign the block header prior to
hashing. The signature will be included in the data that is hashed.
Further,
the coinbase for the block must only pay out to the public key counterpart
of
the private key used to sign the block header.
A valid block will therefore have a signature in the block header that is
verified by the public key being paid by the coinbase transaction.
Ramifications
Work can no longer be divided among the pooled miners as before, without
sharing the pool's private key amongst all of them. If the pool does try to
take this route, then any of the miners may redeem the coinbase when it
matures. Therefore, all miners will use their own key pair.
This will make it difficult to form a cooperating pool of miners who may
not
trust each other, as the block rewards will be controlled by disparate
parties
and not by the pool operator. Only a tight clique of trusted miners would
be
able to form their own private pool in such an environment.
Attacks
Pooled hashpower, instead of earning bitcoins legitimately may try to break
the system instead. They may try a double-spending attack, but in order to
leverage the pool to its full potential the pool operator would again have
to
share their private key with the whole pool. Due to the increased
cooperation
and coordination required for an attack, the probability of a 51% attack is
much reduced.
-------------- next part --------------
An HTML attachment was scrubbed...
Message: 3
Date: Wed, 11 Feb 2015 10:25:27 +0100
From: Natanael <natanael.l at gmail.com>
Subject: Re: [Bitcoin-development] Proposal: Requiring a miner's
 signature in the block header 
To: Hector Chu <hectorchu at gmail.com>
Cc: bitcoin-development at lists.sourceforge.net
Message-ID:
  Ref9mN7bJLg-odep3m5teZ7JWDLC+zknQdQQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Den 11 feb 2015 09:55 skrev "Hector Chu" <hectorchu at gmail.com>:
A proposal for stemming the tide of mining centralisation -- Requiring a
miner's signature in the block header (the whole of which is hashed), and
paying out coinbase to the miner's public key.
Please comment on whether this idea is feasible, has been thought of
before,
etc., etc. Thank you.
Motivation
Mining is centralising to a handful of pool operators. This is bad for a
number of political reasons, which we won't go into right now. But I have
always believed that some years down the line, they could hold the users
hostage and change the rules to suit themselves. For instance by
eliminating
the halving of the block reward.
[...]
I propose that we require each miner to sign the block header prior to
hashing. The signature will be included in the data that is hashed.
Further,
the coinbase for the block must only pay out to the public key
counterpart of
the private key used to sign the block header.
[...]
This will make it difficult to form a cooperating pool of miners who may
not
trust each other, as the block rewards will be controlled by disparate
parties
and not by the pool operator. Only a tight clique of trusted miners would
be
able to form their own private pool in such an environment.
People already trust things like cloud mining, so your solution with
increasing technical trust requirements won't help. But you will however
break P2Pool instead.
Also, note that threshold signatures (group signatures) could probably be
used by an actual distrusting pool's miners. There are already a proof of
concept for this implemented with secp256k1 that works with Bitcoin clients
silently. This wouldn't prevent such a pool from working.
-------------- next part --------------
An HTML attachment was scrubbed...
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is
your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
Bitcoin-development mailing list
Bitcoin-development at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
End of Bitcoin-development Digest, Vol 45, Issue 37
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150211/57ec266d/attachment.html>
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007403.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

How to crack Bitcoin accounts, MUCH MONEY CAN BE MADE ✔️ Bitcoin Generator Free Mining Site 100% working 2020 I BTC CGen Kryptos Im Blickpunkt - YouTube Tutorial Hack block chain test private key Can we hack a random Bitcoin wallet????

Bip39, Bitcoin Secret test . Transaktionen werden nach dem spätesten Zeitpunkt sortiert und ein Limit von 200 tx wird zurückgegeben. Die Währung, in der die Gelder abgehoben werden sollen (möglicherweise mit Umtauschgebühren verbunden). Wie in BIP 44 definiert, scannt die Wallet-Software nicht mehr als 20 nicht verwendete Adressen. Mithilfe dieser Funktionalität können Sie Parameter in ... Litecoin Miner - Betrachten Sie dem Liebling unserer Tester. Jeder unserer Redakteure begrüßt Sie als Leser zum großen Produktvergleich. Die Betreiber dieses Portals haben uns der Kernaufgabe angenommen, Verbraucherprodukte unterschiedlichster Variante ausführlichst auf Herz und Nieren zu überprüfen, dass Sie als Interessierter Leser unmittelbar den Litecoin Miner finden können, den Sie ... Bitcoin USB-Stick Miner bitshopper GekkoScience NewPac 22 bis 45 GH/s Hash-Geschwindigkeit: 22 bis 45 GH/s; Taktrate der beiden Bitmain BM-1387 ASICs kann über CGMiner Softwareparameter eingestellt werden; Kernspannung mittels Potentiometer einstellbar. Meßpunkte für die Feinjustierung vorhanden. Stromverbrauch: 2 bis ca. 10 W pro USB-Port je nach eingestellter Taktrate und Kernspannung ... Bitcoin Miners Antminer S9 L3 D3 Stromversorgung APW3++ PSU im Lager Schnell Versand 1200W @ 110V 1600W @ 220V APW3++ Netzteil; Bitmain Antminer S9K - 13.5TH/s Bitcoin Miner Hash Rate: 13.5 - 13.95 TH/s ; Klassisches Upgrade, mehr Energieeinsparung: Upgrade des Classic Antminer S9; Leistung: 1148W; Leistungseffizienz: 85 J/TH; Auf Lager für sofortigen Versand, keine Importkosten oder Steuern ... Bitcoin USB-Stick Miner bitshopper GekkoScience NewPac 22 bis 45 GH/s Hash-Geschwindigkeit: 22 bis 45 GH/s; Taktrate der beiden Bitmain BM-1387 ASICs kann über CGMiner Softwareparameter eingestellt werden; Kernspannung mittels Potentiometer einstellbar. Meßpunkte für die Feinjustierung vorhanden. Stromverbrauch: 2 bis ca. 10 W pro USB-Port je nach eingestellter Taktrate und Kernspannung ...

[index] [10610] [18693] [46677] [2113] [2278] [34912] [214] [50221] [49364] [11343]

How to crack Bitcoin accounts, MUCH MONEY CAN BE MADE

How to get UNLIMITED Bitcoin for FREE in 2020! If you see this, comment 'WOW' in the comments section. If you are interested in visiting the website previewed in today's video, press the following ... This video is unavailable. Watch Queue Queue. Watch Queue Queue In this video you will learn how to permanently "engrave" your Bitcoin Wallet 24 words (BIP39) Seed backup on SEEDPLATE metal backup system. Get your SEEDPLA... Seitdem Satoshi Nakamoto sein Whitepaper zu Bitcoin veröffentlichte, ist irgendwie nichts mehr so wie es einmal war. Von daher erwarten dich auf meinem Kanal... bitcoin miner software crack, free bitcoin software download, bitcoin mining software free download, bitcoin doubler software, bitcoin adder software free download, desk software bitcoin adder ...

#