Electrum Wallet Anleitung - Schnelle und einfache Bitcoin ...
Electrum Personal Server - LightningHood
Esplora and Other Alternatives to ElectrumX
How to run a bitcoin node as a traveling digital nomad?
I would like to upgrade my bitcoin citizenry status and operate a full node, but the problem is, I have not found an easy solution that works with my lifestyle. I am a "digital nomad". I do not have any permanent home base. The longest I normally stay in any single location is about a month. I travel light, since my entire life needs to fit into luggage. Hardware that is already in my travel kit includes an iPhone, a Macbook, and a Trezor one. Is there an easy solution to running a full node with this kind of lifestyle? Can I utilize any of my current kit sufficiently? Or do I need separate/additional hardware? Does it make sense to run a full node from my MacBook? Would this interfere with how I need to use and rely on my MacBook for my other tasks/work? Do regular and intermittent internet stoppages matter? (Since I travel often, the node would be disconnected often and reconnected to a new WiFi network,etc). Any insight and recommendation is greatly appreciated. Cheers
Hi team, can you please explain two things: 1) I have read there is also an implementation called ElectrumX. But I only found a guide how to installl EPS by Chris Belcher on github. Can you linke me to a nice guide for ElectrumX? What are the main differences between ElectrumX vs EPS ? 2) What security related tradeoffs are you making when using EPS for your full node? EPS is a server, so are not servers able to "spy" on server activities and see everything in an un-encrypted manner? 3) When you run your own EPS how can you make sure that it works also in years? From what is its functionality depending? Is it some sort decentralized mash network? I like to know which scenario must take place in order for the EPS server infrastructure not to work anymore? the Worst case Thanks all
I've heard of Zcash for a while, but it wasn't until recently that I tried my hand playing around with the daemon and wallets. Obviously, there's no point in using ZEC if you're only using t-addresses, but my desire for a z-address capable wallet certainly narrows the choice of wallets available to me. Running a full node is no problem for me; I'd like to take advantage of a GUI if possible though. For that reason, I am drawn to ZecWallet's full node version. But I'm still uneasy when it comes to key security. (Can anyone share their experience with the ZecWallet paper wallet generator?) From what I gather there is no wallet with HD support for t-addresses, is that right? Not much of a concern for me because I am interested in the shielded pool. I just figured t-addresses would support Electrum-style seeds but apparently not? Sapling addresses seem to be exactly what I want; in particular I am drawn to their reusability and ability to export the view key. I was hoping this would ease the process of securing and backing up my private keys. Here's my key handling protocol I use for Monero: 1) Generate the wallet on an air-gapped machine 2) This gives you a mnemonic seed. I write that down and keep it as an analog backup. By using a passphrase in conjunction with the seed, I can effectively encrypt this paper wallet easily. 3) Export the private view key and address to an online machine and make a watch-only wallet. This lets my watching wallet see incoming transactions 4) When outputs are received, I have to export the list of outputs to the air-gapped machine. The air-gapped machine uses this data to make signed key images. 5) I export the key images back to the watching wallet. At this point, the watching wallet can see outgoing transactions. 6) Now I can create unsigned transactions with the watching wallet, sign them in the air-gapped machine, and transmit them via the watching wallet using my full node. The major benefit of using Monero in this way is that I only have to make a human-readable backup of my wallet once and I'm set for life. Obviously, Zcash is going to be a little bit different. Since the core client doesn't give us mnemonic seed phrases, that complicates backup a little bit. What's the best way to back up ZEC? If I keep an up-to-date backup of my wallet.dat is that all I need? Is there an option in the wallet to encrypt this backup as well, or do I need to accomplish that externally with the likes of Veracrypt? I must admit the idea of unencrypted wallet data being written to my disk makes me uneasy. I see that there is an option in zcash-cli to import/export the view key of Sapling addresses. However, I can't see the option to do so in ZecWallet, and when I do so manually via the CLI nothing seems to be reflected in ZecWallet. Is ZecWallet by its very nature an obligatory hot wallet, or am I missing some functionality in the wallet? My end goal is to run a ZEC full node on Qubes and hold my coins in z-addresses. Qubes allows me to make virtually air-gapped VMs to greatly simplify key management. So for example when I use Bitcoin, I have a networked VM that runs a Bitcoind + Electrum Personal Server + Electrum Wallet stack, where I import my master public key. When I need to sign a transaction, I spin up a networkless VM equipped with Electrum and my private keys. Qrexec let's me easily ferry unsigned/signed transactions back and forth between the two VMs. Overall this provides a decent UX with above-average security and privacy. I'd like to port this general setup to Zcash. To do so, I need a GUI wallet that supports both z-addresses and public/private key splitting. Does such a tool exist? (Can Electrum Personal Server be ported to ZEC?) If not, how can I streamline this process with the CLI? I'm more familiar with Monero than Bitcoin, so the Zcash/Bitcoin CLIs are still a little foreign to me, though I am not "afraid" of CLI wallets in general. My Cryptonote muscle memory makes me prone to annoying little syntax errors I'd much rather do without. My plan is to buy ZEC from Coinbase Pro, withdraw to a t-address, and then sweep my coins to a z-address. I want to monitor the balance of both t-addresses and z-addresses (and later send transactions) without ever exposing my private keys to the Internet. However, it seems like the Zcash CLI is my only viable option for z-address watching wallets. Should I just play around on testnet until I get more familiar, or is there a GUI wallet solution out there that fits my needs? Does anyone have a cheat sheet for doing this via the CLI that could help me along the learning curve? TL;DR New to Zcash, need advice as it relates to wallet backup, watching wallets, and z-addresses. Assistance is much appreciated! Edit: I don't suppose there's a way to use a Trezor Model T with a full node and or z-addresses?
Recently restored a wallet from seed onto a new laptop. Went through gpg4win to verify certificate/signature/public key from electrum. During and immediately after restore process, antivirus flagged up various 'intrusion attempts' which look to have been blocked. New laptop, almost zero software downloaded, any ideas on what happened? I disconnected wifi, not yet connected again, any suggestions as to best route forward? Uninstall electrum and start all over again? Any advice much appreciated.
I'm new to Litecoin, but have some familiarity with Bitcoin. I have successfully spun up and synced a Litecoin node. With Bitcoin, I use my Trezor in conjunction with a full node by way of Electrum wallet and Electrum Personal Server. I know there is an Electrum LTC wallet. Has anyone ported the EPS code to LTC? Or is there another recommended wallet interface? Thanks
Hello, I have been a fan of electrum because of its offline capability. I like that I can use Bitcoin while storing my private keys on a computer that has the wifi card removed and hot glue stuffed in the Ethernet port. However it looks like maybe the electrum developers have over-promised and under-delivered in this regard. Or, maybe they simply do not have the time, energy, resources to make this work in real life. Let me explain. I have an old-ass computer that is running Ubuntu 12 (precise), this computer has electrum 2.5.4 installed with a cold-storage wallet that has my private key. I want to send some bitcoin from that address to a new wallet on my desktop so I can spend the bitcoin. So I installed electrum (newest version 3.3.8) on my desktop, imported the bitcoin address, and created a transaction. Then I sent the transaction to the offline computer out of band, and verified that the out-of-band transmission worked by comparing the hash of the txn file on both the offline and online machines. Then I tried to open the txn file on the offline machine with Electrum 2.5.4. Well, guess what, it didn't work. Electrum 2.5.4 printed to the console: Traceback (most recent call last): File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 2261, in do_process_from_file self.show_transaction(tx) File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 577, in show_transaction show_transaction(tx, self, tx_desc) File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 37, in show_transaction d = TxDialog(tx, parent, desc, prompt_if_unsaved) File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 48, in __init__ self.tx.deserialize() File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 523, in deserialize d = deserialize(self.raw) File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 454, in deserialize d[inputs] = list(parse_input(vds) for i in xrange(n_vin)) OverflowError: Python int too large to convert to C long That's pretty frustrating, the first thing I tried was to install Electrum 2.5.4 on my Desktop and try to create a new unsigned transaction with Electrum 2.5.4. However, this is a no-go because old versions of Electrum cannot connect to Electrum servers any more. So I have to try to update the Electrum on the Offline computer. But I'm not even sure if this is possible considering how ubuntu 12 it's definitely out of support at this point and the offline computer does not even have python3 installed, let alone the GTK stuff or whatever is probably required to run Electrum. I'm starting to regret choosing a GUI-based wallet for my offline storage considering how hard it is to actually use this and how it simply melts over time... even just 5 years is is enough time to completely melt and destroy this software and make it un-usable. Time Catches All. So now I have to go out and buy a new computer that can run the updated OS, so I can install the new version of Electrum, so I can access my bitcoin. Do you have any other ideas? Has anyone else experienced anything like this?
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.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
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
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.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
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.
Simplified payment verification for fast mobile performance
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.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
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).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
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).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
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.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
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.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
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.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
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.
I've had an ElectrumX Server set up, running and accessible over the Internet for almost two months and, judging from the logs, I'm the only person who's accessed it. Is this normal, or have I configured something incorrectly? My node is listening for SSL on port 50002, with a letsencrypt certificate. I've got a cloudflare DNS record for bitcoin.mydomain pointing at my public IP and I have tested this on electrum clients on Internet connected machines (specifically ones not connected to my LAN) and it works fine. I have to type the domain name into the server selection box, though, it hasn't yet appeared on the list of peers the client picks up automatically in one of my test scenarios. This makes me suspect I'm not advertising my server correctly. Here are the relevant parts of my elextrumx.conf:
I just spun up a Bitcoin Cash electrum server - here's why!
Two days ago someone in a local group was creating a guide for noobs to get their BCC from their private keys and his awkward solution was: Download BitcoinABC and the 138Gb blockchain from his server to speed up sync. Kudos to him for trying to help people but it was so sad to see an experienced Bitcoin-user being so misguided about how Bitcoin is supposed to work for noobs. N-Corea always spins the pro-1mb-argument that larger blocks is an entrance barrier for new users but the fact is that 99% of all users can use SPV-clients to access their Bitcoin in just two minutes - without any practical decrease in security or decentralization. Full nodes are for the 1% that need them, like companies, developers and the extremely paranoid. The rest can happily use light clients. If new users think they have to download 138Gb and waste crazy amounts of CPU-time to sync then that's a real entrance barrier and it might as well be 1Tb - which it soon will be no matter if the blocksize limit is 1Mb or 8Mb. I don't really need to run a full node or an electrum server - but I choose to, to do my part in helping the network and to show that 99% of users don't need to run full nodes - they can just connect to mine or someone else's on the decentralized network. My BitcoinCash electrumx server is running on: bitcoincash.i4s.dk Donate if you like. P.S. I see a lot of FUD about ElectronCash but I have yet to see any evidence the developers are hiding malicious code in the binaries and even if they are you can sign tx's offline. P.P.S. I support SW2X but I don't believe BCC and SW2x are mutually exclusive.
Bitcoind finished synchronizing a few days ago, and the systemd service for Electrumx is running after the proper setup.
Why am I still unable to connect? I have the port forwarding set up, iptables rules, and everything, but no matter where I try to connect from, the connection fails. It does not work from LAN, let alone the Internet. The problem is that I have no idea where verbose ElectrumX log and debug files are located, there are no docs on such a thing anywhere. Journalctl -u electrumx -f doesn't update much over time. But for the sake of posterity, I'll include a tail of it:
-- Logs begin at Fri 2019-08-09 18:36:29 EDT. -- Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:coin: BitcoinSegwit Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:network: mainnet Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:height: 499,601 Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:tip: 00000000000000000051b03a584817c09caaae919eb661dd93af1012efcccec0 Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:tx count: 282,736,468 Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:flushing DB cache at 1,200 MB Sep 18 20:10:21 [scrubbed] electrumx_server: INFO:DB:sync time so far: 32d 22h 55m Sep 18 20:10:25 [scrubbed] electrumx_server: INFO:History:history DB version: 0 Sep 18 20:10:25 [scrubbed] electrumx_server: INFO:History:flush count: 479 Sep 18 20:10:25 [scrubbed] electrumx_server: INFO:History:DB shut down uncleanly. Scanning for excess history flushes...
Any ideas as to why I can't connect no matter which client I use? And where I can locate the actual log file instead of accessing it in some roundabout way? EDIT: For the record, what I am trying to do is connect to an ElectrumX serveBitcoin full node that I own, from another device connected to LAN and/or the Internet.
How do I use my bitcoin core node to validate transactions against BRD, HODL, Samourai or other mobile wallets???
I have my bitcoin core node setup. I use electrum personal server and can connect electrum to my own core node just fine. However, all of these mobile wallets that allow you to "switch to manual mode" and use your own bitcoin core node dont seem to work. Some allow you to put in your RPC Username/Password and others just allow you to put in an IP and a Port. I am obviously connecting via my own local LAN between my phone and the core node. I have server=1 set in my config and I have an RPC usepassword/port setup as well. What else needs to be done here or does anyone have any tips/tricks to get this to work? Thanks.
Hi, If you come across the above problem in your electrum wallet I have a solution to solve this. The problem is caused due to ssl verification errors, if you check Electrum logs. How to fix it:- Open Electrum
Go to Tools->Network
Choose a server from electrum app or copy one from here https://1209k.com/bitcoin-eye/ele.php (Just copy the server name): e.g electrum3.hodlister.co NB:MAKE SURE YOU ARE USING TRUSTED SERVER, I RECCOMEND YOU USE THE ONES ALREADY IN THE APP
Open cmd prompt/terminal and type ```ping electrum3.hodlister.co ``` replace electrum3.hodlister.co with the name you want, remove the quotes.
Copy the IP address and paste into electrum in the server use the port specified on the site or leave to the one you found.
Make sure "Select server automatically" is unticked so you can input the server name.
Close and Enjoy............
TIP ME HERE BTC: 1DSWXvJQxUhdpg72c9nGESzaza6aWYGtMn BCH: qpn0t39t570k5lrw2sk3p6hvxmetyuc5vy3p4cfs5h Always download electrum desktop from electrum official server ( https://electrum.org/#home ) EDIT:I personally use 126.96.36.199 port:110
Another Quarter, Another Release! The Groestlcoin production factory has been working overtime as always in order to deliver even more tech to push Groestlcoin mainstream when the time comes. There have been many new fantastic wallets and exchanges added to Groestlcoins repertoire over the past 3 months so we will re-cap these before moving on to what is new today.
Groestlcoin added to SatWallet – A 3-in-1 service. Multicurrency wallet, exchange and soon a debit card!
ChangeHero announced a week of 0% commission for Groestlcoin trades.
Added to BC Bitcoin cryptocurrency exchange, offering 8 fiat pairs!
Added to Chameleon Pay mobile wallet for Android and iOS!
Added to the Okex' strategic partners cryptocurrency exchange; CoinAll! Offering BTC and ETH pairs! With a 21,5000 GRS Giveaway!
Added to Spark Card! Our second MasterCard for Groestlcoin! Provided by Pungoio, powered by TarjetaSpark and issued by Mastercard!
Added to Swirlpay! A decentralised peer-to-peer payment gateway.
Added to Archos Safe-T Mini hardware wallet! Built around encrypted Chipset memory.
Added to Agama Wallet – A multi-asset encrypted wallet for iOS, Android, Windows, Mac OS and Linux from Komodo.
Added to Mr Coin exchange, with 2 fiat pairs (EUR and HUF)
Added to CryptoFacil Exchange – An exchange powered by Bittrex and is a fiat gateway. Leaving you with the ability to buy GRS with Visa and Mastercard.
Added to Bits Game – A gambling service with 2 'PvP' games
Added to Boost X Change Cryptocurrency exchange!
Added to Sucon's Suworld Korean cryptocurrency exchange!
Added to DCXinsta cryptocurrency exchange and swap service with Fiat pairings.
Added to DCXtrade, an Indian cryptocurrency exchange with BTC and ETH pairings.
Added a fiat KRW pairing on Huobi Korea Cryptocurrency Exchange!
Added to AirGap wallet, allowing you to securely store your GRS on an offline device.
Added as a payment method on hodlhodl, allowing you to make global trades without KYC/AML.
Added to TrustWallet cryptocurrency wallet for iOS and Android
The existing Magnum wallet adds SegWit support for the wallet! Allowing SegWit addresses to be used and created from within the wallet.
Added to CycleBit – Who provide POS Terminals that accept GRS payments anywhere, in-store and online. 130 coffee houses in Spain already accept GRS using Cyclebit POS terminals!
Added to Bitinka Cryptocurrency exchange! The #1 exchange in Latin America with 5 fiat and cryptocurrency pairs!
Added to Atomic wallet, a non-custodial cryptocurrency wallet with encrypted private keys and 40,000 monthly users.
Added to NoMiddleMan cryptocurrency payment gateway, offering no usernames, no registration, no KYC, no fees. Completely free to use!
Added to Blockchair! An advanced data analysis tool, mempool monitor and block explorer!
Added to SecuX V20, SecuX W20 and SecuX W10 hardware wallets!
Re-forged: Groestlcoin Samourai
Groestlcoin Samourai is a wallet for the streets. A modern Groestlcoin wallet hand-forged to keep your transactions private, your identity masked, and your funds secure. Its main advantages are its extreme portability and is the most secure Groestlcoin mobile HD wallet. We've built a wallet that Groestlcoin deserves. If you are looking for a wallet that Silicon Valley will never build, the regulators will never allow, and the VC's will never invest in, this is the perfect wallet for you. ![Groestlcoin Samourai Release Video](http://img.youtube.com/vi/i3WU8Tde8XQ/0.jpg)
Head over to the Groestlcoin Samourai Release Page here for the full release announcement.
Groestlimage turns any file into a mnemonic phrase allowing users to generate Groestlcoin private keys and addresses based on the data URI of the provided file. A picture is worth a thousand Groestls.
Turn any image, document or audio file into a BIP39 mnemonic phrase
Groestlcoin Core Config Generator is a simple GUI to configure the groestlcoin.conf file – A developers dream tool! Each configuration option is available via the user interface, grouped by what attributes they affect. For ease of getting started with a new configuration, a variety of preset "node classes" are available on the right-hand-side of the screen. Selecting a preset will load our recommended base configuration for a node fitting that description, at which point you can then tune the configuration at the single option level.
Choose between Mining, Non-Standard Ports, Low Bandwidth, Pruned, Raspberry Pi, Tor, Testnet, Regtest, Non-Syncing and Lightning Éclair presets.
Groestlcoin Simple Push TX is a server to push Groestlcoin transactions via SMS. Now everybody can send new transactions via SMS if the Internet is not usable (i.e. blocked by government entities or becomes otherwise unavailable).
Ability to push either Base64 or Hex-Encoded Raw Transactions via SMS.
Send SMS transactions to PushTX through the number +32460224477 (+32460224GRS)
Electrum-GRS is Groestlcoins #1 thin-client for Windows, MacOS, Linux and Android, based on a client-server protocol. Supporting multi-sig wallets without the bloat of downloading the entire blockchain.
New Features (Universal)
Electrum Protocol: The client's "User Agent" has been changed from "3.3.6" to "electrum/3.3.6". Other libraries connecting to servers can consider not "spoofing" to be Electrum
Added CoinGecko.com fiat rate provider. Changed default provider to CoinGecko.com
Minor bugfixes and usability improvements.
New Features (Windows, MacOS, Linux)
Fix Crash during 2FA wallet creation
Fix Synchroniser so that it does not keep resubscribing to addresses of already closed wallets.
Fix removing addresses/keys from imported wallets
The logging system has been overhauled. Logs can now also optionally be written to disk, disabled by default.
Fix a bug in the synchroniser where client could get stuck. Also show the progress of history sync in the GUI.
Fix Revealer in Windows and MacOS binaries
Ledger Nano X is now recognised, supporting mainnet and testnet
KeepKey is now recognised and supports mainnet and testnet
Device was not getting detected using Windows binary
Support Firmware 6.0.0+
Implement "Seedless" mode
Coin Control in QT – Implemented freezing individual UTXOs in addition to freezing addresses
Fix CPFP – The fees already paid by the parent were not included in the calculation, so it was always overestimated.
Testnet – There is now a warning when the client is started in testnet mode as there were several reports of users getting scammed through social engineering.
CoinChooser – Performance of creating transactions has been improved significantly for larger wallets.
Importing/Sweeping WIF keys: Stricter checks
Several other minor bugfixes and usability improvements.
New Features (Android)
Fix rare crash when changing exchange rate settings
Fix bug with local transactions
Allow selecting Fiat Rate providers without historical data
How do I point Electron Cash to my own server (ABC/SV full node) ?
Hi, I have both Bitcoin SV and ABC full node on a personal Linux server. (headless, as TCP/8533 and TCP/8333 respectively) how do I point my Electon Cash client towards it ? Simply choosing the IP address and custom port (TCP/8533) doesn't seem to work, as it says it cannot find server. Do I need only Bitcoin SV node (server side) or another layer on top, like Electron Cash SV server ? What is ElectrumX? Are there any public ElectrumX SV nodes?
Edge wallet, why are you not using SSL connections?
I noticed that 'Edge wallet' clients (https://edge.app) are all using TCP instead of SSL, when connecting to my ElectrumX server. I checked out the app and tried to connect to a custom node, as described as being possible here, but was unable to connect when using the SSL port. Any chance for an update that enables SSL connections?
Spun up a new Electron Cash BCH server on tor onion
Announcing a full node running with a new Electron Cash BCH server on tor onion. I originally got into bitcoin six years ago as a coder. Started very enthusiastic but then left bitcoin development two years ago (with much less enthusiasm). But now, thanks to Bitcoin Cash, it feels like the good old days again. So I'm back here and ready+eager to help grow the infrastructure which makes bitcoin more useful for the community. For BTC, I've used Electrum for years, an excellent SPV wallet, and am now using Electron Cash for BCH. But there are still too few servers for Electron Cash and even fewer which give user-privacy high priority. My first contribution is cashskns6ycfx762.onion, which is a privacy-focused Electron server for the Bitcoin Cash mainnet. It runs the latest Bitcoin ABC 0.16.1 daemon and the ElectrumX 1.2 server configured for BCH. This server operates as a hidden service instance, exclusively over Tor, and obviously does not log. Feel free to use it to get an extra layer of privacy for your Electron Cash wallet client. Unlike regular full nodes it is not able to link IPs to transactions or addresses. Just point Electron to cashskns6ycfx762.onion port 50001 or read more on the service's homepage, http://cashskns6ycfx762.onion/ Other features: Consistent uptime (link to uptime monitor from homepage) / multiple backups / ample bandwidth. Hope that this is useful to someone!
For security, we recommend everyone moves their ZCL and/or BTC to a new address before using the private key for the address it was in for the fork. For now, SegWit BTC balances cannot be claimed. They should be available soon, please keep an eye out for it. If you are using a multi-signature wallet, these will not apply to you. Go to the bottom.
1) Unzip and run BitcoinPrivateDesktopWallet.jar (after installing latest java). 2) Start it and allow the blockchain to sync. 3) Go to Wallet > Import One Private key -> this will take quite some time 4) Press yes when asked to sweep. Please be patient as the blockchain headers download. Your BTCP will be available after this.
Electrum (No z addresses yet)
1) Unzip and run electrum executable 2) Create a NEW wallet 3) Go to wallet > private keys > sweep 4) Enter all private keys and sweep BTCP into new address
1) Unzip and run electrum executable 2) Press next, select multi signature, press next 3) Set to proper number of key holders and cosigners, press next 4) Press "I already have a seed" and enter it. 5) Enter public keys of other cosigners. 6) After wallet start up, make a new multi-sig wallet and send funds there for safety and security reasons.
Interesting technical facts about Groestlcoin that might explain price rise
Disclaimer: After doing some research, I own a small amount of Groestlcoin and no Vertcoin (I rkn VTC is overvalued currently). Might buy some VTC after it corrects. Here's why...
Groestlcoin with a market cap of only $14,458,912 seems undervalued for now given the current Crypto market climate
Groestlcoin appears to be technologically superior, however has an unfortunate name and a lacking community (644 Reddit subscribers)
Vertcoin appears to have a larger community (13398 Reddit subscribers), has been pumped for last 11 days (up 400%) and now a Market Cap of $183,045,997
This week people seem to be more interested in ASIC resistant coins and looking towards alternatives like VTC and GRS (essentially better versions of Bitcoin Gold with experienced teams and developers)
See below for some more technical facts about GRS from jackilove4u that was posted 4 days ago.
This is what I've been working on for the past few months: A Bitcoin POS Terminal from scratch
Hey /Bircoin! Over the past few months, I've been working on a Bitcoin POS Terminal and I think it has come to a stage where it is worth sharing. Skip to the end of the post for a gallery of photos and a demo video. What? The terminal will allow any merchant to easily accept bitcoins in a store. Just hook it up to your cash register and you are ready to go. There is no need to install any additional software, not even a bitcoin client is required locally. Why? Other solutions out there are not as convenient to use. You have to turn your screen to the customer to let him scan a QR code or mess with printed tickets. Also integration into your existing hard and software can be tricky. How? Let's get technical! The terminal communicates with your cash register using a protocol called 'Open Payment Initiative' (O.P.I.). It is TCP based, so you only need an Ethernet cable to connect the terminal to the computer running your POS software. When a new transaction is requested, the terminal creates a QR code to tell the customers wallet where to send the bitcoins. To watch the bitcoin network for incoming transactions, Obelisk backend servers are used. The protocol is famous for being developed and used by the Electrum bitcoin client. The terminal also has built in NFC capabilities to allow even faster precessing. In the future it may even be possible to transmit the transaction data from the phone to the terminal via NFC. That way even offline devices can pay with bitcoins. Hardware The terminal is completely developed from scratch. The main processor is a LPC2387 (ARM7 core, 512kB Flash, 98kB RAM). Also included are drivers for NFC and Ethernet. The Ethernet driver is capable of 100MBit transmission, although that speed is far from being needed by the terminal. The display has a resolution of 240 by 160 pixels, enabling any device to easily read the QR codes. The prototype case is 3d printed and designed using FreeCAD, an open source CAD software. Software The software running on the terminal is written in C and compiled with arm-elf-gcc. Everything is open source, and so will be the terminal software. The sources will be released as soon as they move from 'a hack' to a proper alpha version. The software uses some libraries:
The famous uIP, which handles TCP/UDP connections. uIP is probably the TCP/IP stack for embedded devices and even used in many commercial applications.
A ported version of qrduino is used for QR code generation.
trezor-crypto is used for all bitcoin related crypto stuff. It is developed by the inventors of trezor, a hardware bitcoin wallet.
Demo There is a gallery here and a video showing the terminal interact with posPER, a free, open source POS software. TL;DR The Bitcoin POS Terminal enables any merchant to easily acccept bitcoins using existing hard and software. Watch the video above for a quick demo. If you like what you just saw, all bitcoins received at 16AXtZAQ6GmTEqf9TEfYRLyxo3qtPDajnq will be exclusively used to further develop the terminal.
I was already running a full node on my server, but after using Electrum for my personal bitcoins for a while I decided to set up an Electrum server on top of it as well. Feel free to point your clients to orannis.ddns.net, default ports.
PSA: Clearing up some misconceptions about full nodes
Electrum is a lightweight Bitcoin client, based on a client-server protocol. It was released on November 5, 2011. Main features. Encrypted wallet: the file that contains bitcoin private keys is protected with a password, and never leaves the user's computer.; Deterministic key generation: If you lose your wallet file, you can recover it from its seed.You are protected from your own mistakes. Electrum uses Electrum servers to interact with the bitcoin network. It uses them to find out which transactions are relevant to your wallet and also to broadcast spending transactions. The server you are connected to will see your addresses, transaction history and balances. It will not get access to your seed or your private keys. Server connection status orb. Servers are run by volunteers ... Wenn Sie Bitcoin bereits an einer Börse oder an einem anderen Ort aufbewahren, können Sie diese Gelder jetzt in Ihre Electrum-Wallet überweisen. In diesem Fall wird ein sehr kleiner Transfer empfohlen. Erwarten Sie Fehler beim Erlernen von Electrum, besonders wenn Sie neu bei Bitcoin sind. Es ist weitaus besser, Ihre Klumpen zu nehmen, wenn Sie sich mit dem Wechselgeld befassen, als wenn ... Electrum Personal Server (EPS) offers less performance than ElectrumX or Electrs, but is easier to set up and connect to a Bitcoin node, making it a good choice for individuals interested in installing a private Electrum server for personal use. It’s also light on resources compared to a fully-indexed ElectrumX or Electrs instance, so it can be run on low-end hardware. Electrum Personal Server aims to make using Electrum bitcoin wallet more secure and more private. It makes it easy to connect your Electrum wallet to your own full node. It is an implementation of the Electrum server protocol which fulfills the specific need of using the Electrum wallet backed by…
Im showing you step by step how to set up and start mining BITCOIN PRIVATE COIN with your GPU STRATUM HOST (SERVER) CHANGED TO: pool2.btcprivate.org BITCOIN ... No need to port forward TCP8333 from now on! - Linux terminal new stuff: adduser, who, id * All other commands have been covered in previous videos - Add user to Tor group: sudo adduser USER_NAME ... The end result is a bitcoin electrum wallet connected to my own bitcoin node running over TOR. Pretty cool privacy preserving and sovereign design. It will help me with future videos as I won't ... Thanks for watching! For donations: Bitcoin - 1CpGMM8Ag8gNYL3FffusVqEBUvHyYenTP8 BTCPay Server 3,518 views 7:48 Live Tradenet Day Trading Room - 03/26/2020 - Stay Calm And Keep Learning Sale! 🏡📝 Meir Barak - Tradenet Day Trading Academy 1,270 watching