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 (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/groestlcoin-conf.md) about the groestlcoin.conf file describes how to use it to configure Groestlcoin Core.
- 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?
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.
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.
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
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
- Bech32 support
- Multiple wallet support
- Electrum - Support for both random and custom peers
- Encrypted storage
- Biometric + Pin authentication
- Custom fee selection
- Import mnemonic phrases via manual entry or scanning
- RBF functionality
- 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.
- Ability to Broadcast raw transactions
Download iOS Android
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.
- Simplified payment verification for fast mobile performance
- No server to get hacked or go down
- Single backup phrase that works forever
- Private keys never leave your device
- Import password protected paper wallets
- Payment protocol payee identity certification
Download Main Release (Main Net) Testnet Release
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.
- 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.
Live Version (Not Recommended) https://www.groestlcoin.org/recovery/
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).
- 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)
- Multi-GPU support
- CUDA optimisation via inline PTX assembly
- Seed protected by pbkdf2_hmac_sha512 (BIP38)
- Support P2PKH, P2SH and BECH32 addresses
- Support split-key vanity address
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).
- 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.
Remastered! – Groestlcoin WPF Desktop Wallet (v18.104.22.168)
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
- Bech32 support
- P2sh support
- Fixed Import/Export to wallet.dat
- Testnet Support
- 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.
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.
- Selection options for 3-24 words (simply putting the space separated words in the first word box will also work) along with a bip39 passphrase
- User input for total number of addresses desired
- Creation of P2PKH, P2SH, P2WPKH and P2WSH addresses along with xpriv and xpub as per BIP32 spec, using a word list as the starting point following the BIP39 standard.
- Pre-sets for BIP44, BIP49, BIP84 and BIP141 standards, along with custom user input for derivation path
- Option for Hardened or non-hardened addresses
- Option for Testnet private and public keys
- Output containing derivation path, private key in WIF, integer and hex format, public key address, public point on curve and scriptpubkey
- Results are output in a file titled 'wallet.txt' with the time addresses were generated, along with all information presented onscreen
Download Windows Linux
pip3 install -r requirements.txt python3 bip39\_gui.py
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.
- Use your own node
- Tor support
- 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
Download Windows Linux / OSX
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.
Download Main Net Main Net (FDroid) Test Net
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.
- Removed Cryptopia
- Added adaptive icons for Android 8 and above
- Add block book block explorer
UPDATED – P2Pool Test Net
- Add compatibility for Groestlcoin Core 2.18.2
Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/
joey at 1:57 PM
What kind of transaction types are possible with RVN assets? Is it possible to create an asset that has a set lifetime or self-destruct time?
Tron at 2:00 PM
Not for assets/sub-assets/unique. We might be able to do that with voting tokens.
RavencoinDev at 2:01 PM
SpyderDev at 2:01 PM
[Dev] Blondfrogs at 2:01 PM
Chatturga at 2:01 PM
BruceFenton at 2:01 PM
Probably lots of ways to do a self destruct on second layer as well if desired
russ at 2:01 PM
suuuuuupso what is todays topic?
RavencoinDev at 2:02 PM
Thanks for joining us today. We would like to discuss the current status of the 2.1 release.As well as doing an open Q&A at the end.First though I want to thank everybody that helped get the word out on upgrading to the 22.214.171.124 release!Without that fix being in place and exchanges and pools upgrading we would be having a different conversation today.This community is amazing.
russ at 2:04 PM
we would have ended up like pigeoncoinnot a good look📷2
watsure at 2:05 PM
Hello Mr. God
RavencoinDev at 2:05 PM
russ at 2:05 PM
i gave pigeoncoin the pullrequest but they ignored meglad we have competent devs
[Dev] Blondfrogs at 2:05 PM
Everyone, So we are planning on getting out build 2.1 as soon as possible. We are still doing bug fixes, and getting the code hardened for release. There is currently one bug is the asset layer that we are fixing right now, and once that is done we should have a couple days of testing. It would be lovely if the community helped with testing, and we appreciate all of the testing that the community has already done. Once, we have a basic build that is tested, we are going to make a public release and notify the miners and pools.
RavencoinDev at 2:06 PM
Once that bug is addressed a release branch will be created.
russ at 2:06 PM
that duplicate ownership asset bug is nasty
RavencoinDev at 2:06 PM
You should all be able to build that and jump on testnet.
[Dev] Blondfrogs at 2:07 PM @russ
Yeah, didn't see that one. BUt I have a fix right now that seems to be working on my local machine
RavencoinDev at 2:07 PM
We need as much testing help from our devs as possible.
[Dev] Blondfrogs at 2:07 PM
so, I will have that pushed up with the day.
russ at 2:07 PM
[Dev] Blondfrogs at 2:08 PM
Just a reminder, that when the new wallet is published, if you don't update your wallet by the time assets are voting in by the blocks you will fork. So, we are going to try and get the wallet out there as soon as we can so users have weeks to upgrade.
Skan at 2:09 PM
RavencoinDev at 2:10 PM
Any questions comments about the 2.1 release?
Skan at 2:10 PM
SpyderDev at 2:10 PM
Yes and no
RavencoinDev at 2:10 PM
Good question SkanRight now that's also an issue with Bitcoin.
SpyderDev at 2:12 PM
The short version for Mojave is that the released binaries will work fine.
Skan at 2:12 PM
Interesting, so is it likely going to be a future upgrade that brings stability?
SpyderDev at 2:12 PM
However, developers should hold off.
RavencoinDev at 2:12 PM
We are currently building on High Sierra
Skan at 2:12 PM
Ok good to know for those who ask
SpyderDev at 2:13 PM
There is an incompatibility with Berkeley db version 4 that causes a segfault on init.
RavencoinDev at 2:13 PM
Or using the build scripts that Under created to build on Linux. Thjanks @Under
[Master] Roshii at 2:13 PM
Looks I'm late to the event
[Dev] Blondfrogs at 2:13 PM
RavencoinDev at 2:13 PM
Sorry it's late for you @[Master] Roshii
Skan at 2:14 PM
master roshi is never late, he is simply the turtle hermit
SpyderDev at 2:14 PM
One can upgrade Berkeley-db to the latest version and compile with the --incompatible-bdb and things will run, but there are some unknowns as far as wallet compatibility is concerned.
RavencoinDev at 2:15 PM
Raven will likely follow Bitcoin on Mojave support.
SpyderDev at 2:15 PM
The release binaries are compiled on Linux which we have tested on Mojave, so as long as you aren't compiling binaries go ahead and update to Mojave
RavencoinDev at 2:15 PM
It's a problem they have to solve as well, so...
SpyderDev at 2:15 PM
There is supposed to be a patch to bdb, but so far it isn't working
[Master] Roshii at 2:15 PM @RavencoinDev
it's never late for me.
Skan at 2:15 PM
Ok, and for the devs interested just point them to the berkeley upgrade with some warnings or to Under's scripts?
RavencoinDev at 2:16 PM
Right, the wallet runs just fine on Mojave. It's just a developer issue.
[Master] Roshii at 2:16 PM
If I can say anything it will be : don't update to Mojave
SpyderDev at 2:16 PM
There is a warning note in the docs section for OSX building
RavencoinDev at 2:16 PM
Mojave slowed down @[Master] Roshii
and the iOS wallet.
Skan at 2:16 PM
YikesOk good to know, just want to be able to help / point people in the right direction
RavencoinDev at 2:17 PM
SpyderDev at 2:17 PM
There is also an issue with Mojave dark mode and the QT wallet that makes things difficult to read (white on white text). We have a workaround which is to disable dark mode for QT in the plist file.
Skan at 2:17 PM
Ok so this is going to be pretty soon then, right ? Next week, likely?
RavencoinDev at 2:18 PM
Any further Mojave questions?Which @Skan
Skan at 2:18 PM
I think that covers it for me2.1 releaseIn order to have weeks to upgrade before main net
RavencoinDev at 2:18 PM
Yes, it is looking like we can work through this last issue with asset re-org very soon.Likely early next week.
Skan at 2:20 PM
Is 2.1 going to have any UI updates ?
RavencoinDev at 2:20 PM
Yes, frogs has more details.
[Dev] Blondfrogs at 2:20 PM
The UI is done. It is currently in the develop2. So if you have built the develop2 branch, you would be looking at the new UI for now.
RavencoinDev at 2:21 PM
There have been other QT designs kicked around and we would love to see more from the community.
[Dev] Blondfrogs at 2:21 PM
Future upgrades to come though. but those won't be mandatory upgrades. Just visual upgrades.
SpyderDev at 2:21 PM
The UI tweaks are subtle, but they make a big difference.
Skan at 2:22 PM
Very cool, I will check out dev2 branch
russ at 2:22 PM
new asset creation UI is awesome
Skan at 2:22 PM
I saw that, I like it. And the longer asset holdings list
RavencoinDev at 2:22 PM @russ
Don't make @[Dev] Blondfrogs
head any larger...
russ at 2:23 PM
RavencoinDev at 2:23 PM
Other 2.1 release questions/comments?
Skan at 2:23 PM
Cant think of anything else at the momentThanks!
Hans_Schmidt at 2:23 PM
Is dividend support officially part of 2.1 release? It wasn't intuitive to me how that works.
RavencoinDev at 2:24 PM
No it will be in the next release. However, you could write a script that would provide the same functionality with what will be released in 2.1.
Skan at 2:25 PM
I heard something about Phase 4 being complete already, is that true, and is that in 2.1?
RavencoinDev at 2:25 PM
List all addresses with an asset, loop through sending X raven to each.
Skan at 2:25 PM
RavencoinDev at 2:25 PM
Yes, Unique assets are complete.(edited)
Tron at 2:25 PM
Dividend support can be done without modifying the protocol. We can add it to a version of the software that can be used by the payer, without requiring others to upgrade.So we did phase 1, 2, 4
Skan at 2:26 PM
Oh wowGreat job everyone!
RavencoinDev at 2:26 PM
Yeah, we're super excited about the use cases that assets and unique assets provide to our develoepers(edited)
Skan at 2:27 PM
Can you tell us anything else about this separate software client? Will it be geared more towards enterprise use in general or will it just be that feature?
RavencoinDev at 2:27 PM
Speaking of, do any of you have a dev project in the works with assets?
russ at 2:27 PM
well its not a separate software client, its a backwards compatible release @Skan
(edited)kind of like a softfork if you know what that is
Skan at 2:28 PM
Yeah unique assets will be awesome, actually there's a korean community member planning on issuing them along with silver ravencoinsIf im not mistaken
RavencoinDev at 2:28 PM
russ at 2:28 PM @RavencoinDev @Scotty
is working on an asset explorerhttp://ravencoin.asset-explorer.net/
RavencoinDev at 2:29 PM
Yes, we've been watching that.
Skan at 2:29 PM
I am working with him on a Korean translation of the whitepaper, x16r whitepaper, and an introduction article so that we can take advantage of our availability in that market📷1
RavencoinDev at 2:29 PM
Super excited to see that mature.
Skan at 2:29 PM @russ
ah ok that makes senseWill there be anything else to that release?
RavencoinDev at 2:30 PM
. We want Raven to span the globe.Okay, Open Q&A time.What other questions do you guys have?
Skan at 2:31 PM
This release with rewards capability, will there be anything else added/changed for that version?
Tron at 2:31 PM
It might be released as phase 3, 5, 6.Although it could be released separately, without impacting anything.
Skan at 2:32 PM
Ah ok, so all of these features can be opted-into by someone who wants to take advantage, without cluttering the experience for a basic user
Tron at 2:32 PM
Phase 5 and 6 will be together as it requires a hard-fork.
RavencoinDev at 2:33 PM
Yes, we want to focus on user experience so it's super simple to do what you want to do.
Skan at 2:33 PM
russ at 2:33 PM
so is anyone working on RSK yet
[Dev] Blondfrogs at 2:34 PM
We aren't yet.
russ at 2:34 PM
yea im gonna have a look at the code soon
[Master] Roshii at 2:34 PM
Who said ravencoin needs RSK
RavencoinDev at 2:34 PM
It'd be great to have that done by the community.
russ at 2:34 PM
i think some people would like smart contracts @[Master] Roshii
Skan at 2:35 PM
RSK would be great for token distributions
russ at 2:35 PM
the real trick would be getting RSK to recognize assets
Tron at 2:35 PM
RSK, Segwit, Lightning are all on the table, but lower priority than phases 3, 5, 6.
[Master] Roshii at 2:35 PM
This is just like saying let's do what ravencoin does in the old fassion!
russ at 2:35 PM
well not really, smart contracts can do other things
[Master] Roshii at 2:36 PM
What's the RBF status @Tron
Skan at 2:36 PM
Keep us posted russ I think that would be amazingWhen you write smart contracts in RSK what language is it in?
russ at 2:36 PM
solidity i thinlthink
RavencoinDev at 2:36 PM
russ at 2:36 PM
eth contracts also work on RSKso thats a plus
Skan at 2:37 PM
Ok great so we dont even have to work on templates or anything
RavencoinDev at 2:37 PM
Having solidity contracts that interact with Raven assets would open up a lot of possibilities.
Skan at 2:37 PM
I think so too, especially for stuff like tokens in gaming use case📷1
russ at 2:37 PM
i guess it would also help with cross chain atomic swaps too
Skan at 2:37 PM
RavencoinDev at 2:37 PM
russ at 2:38 PM
BTC directly for an asset
Skan at 2:38 PM
sounds like a good product
russ at 2:38 PM
making ICOs easier
Tron at 2:38 PM
Yes, cross-chain atomic swaps would be amazing with user issued assets.
RavencoinDev at 2:39 PM
Skan at 2:40 PM
Smart contract atomic swap erc20token 1:1 for their new RVN counterpart
Hans_Schmidt at 2:40 PM
I believe that every cross-chain atomic swap implementation I have seen requires a trusted federation. That's even true for RSK.
Tron at 2:40 PM @Skan
I like it!
Skan at 2:42 PM
No more questions from me
RavencoinDev at 2:42 PM
Okay, seems that we're winding down on the Q&A.Thank you all for joining us today. I've really liked how this discussion has worked out on Discord.Did anybody miss IRC today?
russ at 2:43 PM
Hans_Schmidt at 2:43 PM
Like a toothache
russ at 2:43 PM
this was waaay better
RavencoinDev at 2:44 PM
Hans_Schmidtat 2:44 PM
Missed the mems tho
RavencoinDevToday at 2:44 PM
I agree. I was even able to fix my typos.That's right, we had some epic memes last time.Where are you @Pathfinder
Chatturga at 2:45 PM @Pathfinder
Do you have an epic meme for us today?
Skan at 2:45 PM
[Master] Roshii at 2:46 PM
Can somebody give @Pathfinder
a Master Memer role and color
Chatturga at 2:46 PM https://i.imgflip.com/2jgpgw.jpg
Pathfinder at 2:46 PM
heyayeah, that was my meme for today 📷 ty Chatturga
BruceFenton at 2:46 PM
RavencoinDev at 2:47 PM
[Dev] Blondfrogs at 2:47 PM
Skan at 2:47 PM
RavencoinDev at 2:47 PM
Have a great weekend. NH Raven Meetup next week!!!!
Jeroz at 2:47 PM
SpyderDev at 2:47 PM
RavencoinDev at 2:47 PM
See you there!
Pathfinder at 2:47 PM
I'll be there! looking forward to seeing folks 📷
Hans_Schmidt at 2:47 PM
See ya in NH
Tron at 2:48 PM
See ya there!
Jeroz at 2:48 PM
Cant make it, but have fun! 📷
RavencoinDev at 2:48 PM
^ did you have a question about tron's Comment?
Jeroz at 2:49 PM
No I was super excited about it
RavencoinDev at 2:49 PM
Ah, me too!
russ at 2:49 PM
mtarget is streaming the meetup, right?
RavencoinDev at 2:50 PM
Not sure, we have really appreciated his work in the past but haven't heard.
Chatturga at 2:52 PM
Yes, he is planning on doing a stream📷1
RavencoinDev at 2:53 PM
Thanks again everybody.
A week later I tried reloading the entire blockchain, and the transaction came through to my wallet at that time. However, the bitcoins are listed as watch-only. I have tried dumping the private key for that address on console for my wallet, but the results continue to say that the private key for that address is unknown. What do I do about this? Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. From 0.17.0 onwards, macOS <10.10 is no longer supported. 0.17.0 is built using Qt 5.9.x, which doesn’t support versions of macOS older than 10.10. Additionally, Bitcoin Core does not yet change appearance when macOS “dark mode” is ... Related PR #11403, needs to be merged first. I'll rebase this PR to be up to date with #11403, and rebase it to master once it has been merged. Exposes the addresstype parameter through the GUI. Currently directly changes the g_address_type global variable instead of requiring an application restart, I'm not sure if this is good practice, but could easily be changed if needed. #9108 d8e8b06 Use importmulti timestamp when importing watch only keys (on top of #9682) ... #8645 8ea4440 Remove unused Qt 4.6 patch (droark) #8608 7e9ab95 Install manpages via make install, ... #9865 289204f Change bitcoin address in RPC help message (marijnfs) Miscellaneous #8274 7a2d402 util: Update tinyformat ... Bitcoin Core should also work on most other Unix-like systems but is not as frequently tested on them. It is not recommended to use Bitcoin Core on unsupported systems. From Bitcoin Core 0.20.0 onwards, macOS versions earlier than 10.12 are no longer supported.
Extract Private Keys from Trust Wallet - works for Bitcoin, Ethereum, Litecoin and other cryptos - Duration: 5:48. Crypto Coin Investor 3,690 views Basic explanation of how to sign and verify a Bitcoin Adress from your Softwarewallet, example client was Bitcoin-qt. Feel free to donate to keep more Tutorials coming: BTC ... In this tutorial we are going to get our private keys from the bitcoin core wallet. This only works when you created the bitcoin address in the same wallet. ... Dash: QT Wallet Private Key Export/Import What is : https://dashpay.atlassian.net/wiki/pa... How to: https://dashpay.atlassian.net/wiki/pa... Tipping Address: Watch Queue Queue. Watch ... bitcoin wallet reviews, free bitcoin wallet, bitcoin wallet address, bitcoin wallet android, bitcoin wallet download, create bitcoin wallet, google wallet bitcoin ...