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 (v220.127.116.11)
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/
RavencoinDev - Today at 2:03 PM
Hello Everybody, sorry we're getting started a couple of minutes late today.Today we wanted to make sure that everybody was aware of the Bug Bounty program and discuss it.Has everybody seen the information at https://github.com/RavenProject/Ravencoin/wiki?
Project staging tree. Contribute to RavenProject/Ravencoin development by creating an account on GitHub.📷
Hans_Schmidt - Today at 2:06 PM
Yes. I'm working on it...📷1
RavencoinDev - Today at 2:07 PM
I have seen that @Hans_Schmidt
Thank you for really digging into the code. You have found some really good ones.Did you get an address posted in the issues so we can reward you for your efforts?
Hans_Schmidt - Today at 2:08 PM
Yes I sent it to Tron and blondfrogs. Thanks.
[Dev] Blondfrogs - Today at 2:08 PM
I got hans address, and updated the wiki accordingly
RavencoinDev - Today at 2:09 PM
Nice! thanks guys, we'll get that sent out today.
brianmct - Today at 2:09 PM
Wow that's a lot of RVN!
Hans_Schmidt - Today at 2:09 PM
The next one is proving harder to find. That is a good thing 📷
[Dev] Blondfrogs - Today at 2:09 PM
look at the wiki, and make sure the address next to the issues you created is the correct address where you would like payment.(edited)
MSFTserver-mine more @ MinerMore - Today at 2:09 PM
just a heads up im renaming this channel to just development meetings
RavencoinDev - Today at 2:09 PM
We feel it's worth the amount for sure to find and fix those type of issues.
brianmct - Today at 2:10 PM
Probably shouldn't keep the addresses on the wiki, since it's publicly editable?
RavencoinDev - Today at 2:10 PM @MSFTserver-mine more @ MinerMore
[Dev] Blondfrogs - Today at 2:11 PM
We will look into the github wiki permissionsand verify addresses before sending payment
RavencoinDev - Today at 2:11 PM
Thats a good point, and reach out to the individuals directly to ensure it's their correct address.
brianmct - Today at 2:12 PM
Actually it's not publicly editable. My bad. Still good to confirm directly though
RavencoinDev - Today at 2:12 PM
brianmct - Today at 2:12 PM
Probably have people put their address on the issue when reporting it
[Dev] Blondfrogs - Today at 2:12 PM
brianmct - Today at 2:12 PM
Don't want any MITM attacks :P
RavencoinDev - Today at 2:13 PM
No we don't.
Chatturga - Today at 2:13 PM
Putting a public address out there is asking to get sent certain asset tokens when it goes live. 📷📷1
RavencoinDev - Today at 2:13 PM
Any questions about the issues that were found thus far?
Hans_Schmidt - Today at 2:14 PM
I verified that my address is correct.
[Dev] Blondfrogs - Today at 2:14 PM
Hans_Schmidt - Today at 2:15 PM
Will you send a dust send first to verify (for bitcoin we do that as standard procedure for large amounts)
[Dev] Blondfrogs - Today at 2:15 PM
Yes, that is the process we follow also
Hans_Schmidt - Today at 2:15 PM
RavencoinDev - Today at 2:16 PM
Just an FYI some of the developers were at the Free State Blockchain conference last week.We also spoke at the MIT Business schoolIt was great to see our community members there!
UserJonPizza™FlyToTheNorthRaven - Today at 2:17 PM
Are you guys 100% on the 31st? Ik prob been asked a million times but...
RavencoinDev - Today at 2:18 PM
Thanks to all that helped with the conference.📷1
[Dev] Blondfrogs - Today at 2:18 PM
The current code base will start voting on the 31st.
Chatturga - Today at 2:18 PM
Yes Its in the code.
RavencoinDev - Today at 2:18 PM
Any other questions about the Bug Bounty?
Hans_Schmidt - Today at 2:19 PM
What's the plan for next formal release?
[Dev] Blondfrogs - Today at 2:20 PM
Should be early next week, we are planning a 2.1.1 release, with the latest bug fixes in it.We thought we would give it a couple more days to see if any additional bugs are found.
RavencoinDev - Today at 2:21 PM
Agreed, there will be one more binary release before the end of the month.
[Master] Roshii - Today at 2:21 PM
Sorry late again
Hans_Schmidt - Today at 2:21 PM
I'm not pushing for the release, just asking. I prefer to have a few days to see if I can get my next attack attempt to work
SpyderDev - Today at 2:22 PM @[Master] Roshii
- were your ears burning?
[Dev] Blondfrogs - Today at 2:22 PM
Yep. You got it, keep attacking the chain!
RavencoinDev - Today at 2:23 PM
Yes please we would encourage everybody to help us find additional chain splitting or consensus defects.Other defects are also welcome, just not part of the bounty at this point.
Hans_Schmidt - Today at 2:24 PM
It would be helpful to know if someone is methodically verifying that the fixes work and also cover the minor variations, because I am not doing that.
[Dev] Blondfrogs - Today at 2:25 PM
Yes. I am personally verifying all bug fixes, and so are the other developers
SpyderDev - Today at 2:25 PM
We are also creatimg tests for them.
Hans_Schmidt - Today at 2:25 PM
Like I payed unique asset creation into the wrong burn address. But there are other variations. Your fix looks like it covers it all.
[Dev] Blondfrogs - Today at 2:26 PM
That is correct. We appreciate the bugs found and expand off of them to fix all other small variations of them.
Hans_Schmidt - Today at 2:26 PM
Great. I focus on new angles.
[Dev] Blondfrogs - Today at 2:26 PM
SpyderDev - Today at 2:26 PM
Chatturga - Today at 2:27 PM
RavencoinDev - Today at 2:27 PM @Tron
isn't able to be here but he wanted me to share this.
Hi All. I’m sorry I’m not able to make it to this development discussion. I’ve been invited to be on a Cryptocurrency and ICO/STO panel at the Federal Bar Council Fall Retreat. I've been informed that many of the attendees are judges from the Second Circuit Court of Appeals which is the Circuit Court for the state of NY. These presidentially appointed judges are just below the US Supreme Court and before whom the SEC and CFTC would be mere litigants. I’m on the panel with some heavyweight crypto and securities attorneys and my role will be talking primarily about the technology (blockchain, tokenized assets, smart contracts, etc.) while allowing the other distinguished panelists to address the legal aspects of this new technology. This is an amazing opportunity to introduce the audience to the best aspects of crypto-currencies and crypto-assets.
Pathfinder - Today at 2:28 PM
wow that's awesome
SpyderDev - Today at 2:28 PM
We are all hoping @Tron
will not get arrested.
mapple - Today at 2:28 PM
yesand yes to the not arrested :))
RavencoinDev - Today at 2:29 PM
I told him the mask thing was probably a bad idea for that event...
Hans_Schmidt - Today at 2:29 PM
The Raven mask or the Guy Falkes?
RavencoinDev - Today at 2:29 PM
We need a Tron with judges Meme @Pathfinder
Yes to both.
Skan - Today at 2:29 PM
ITS A TRAP
RavencoinDev - Today at 2:30 PM
Hans_Schmidt - Today at 2:30 PM
A Tron Trap?
mapple - Today at 2:30 PM
i was asked on telegram a few days ago about timeframes for all phases (currently announced) to be completed - are there estimates I've missed?I've properly looked through githubi've not lol
RavencoinDev - Today at 2:31 PM
We are hoping to complete the remaining phases by the end of Q1 but have provided no hard dates.
mapple - Today at 2:32 PM
OK - so march 2019 estimate if anyone asks again would be fair at the moment
RavencoinDev - Today at 2:33 PM
One of the topics I would like to cover for all our web developers is the ravencoin.com website.
gwrg - Today at 2:33 PM
Does it include Phase 7 which was added recently?
RavencoinDev - Today at 2:34 PM
That's not been fully thought through to this point so it's not likely.I wanted to make sure you all knew that Ravencoin.com is a community website, the source is posted and web developers are free to submit pull requests to make changes.
Vincent - Today at 2:35 PM
Chatturga had mentioned a plan to somehow modify the asset creation cost in the future...is that part of the qtr 1 plan?
RavencoinDev - Today at 2:36 PM
We'll be watching closely how the asset creation and RVN burn goes once it goes live.
Chatturga - Today at 2:37 PM
I did say that the rate is 500 RVN for now so that actual data can be gathered, which can then be applied to proposed changes. Speculative data just isnt enough.(edited)
RavencoinDev - Today at 2:37 PM
Anywho... The source for the Website is at https://github.com/RavenProject/ravenproject.github.io
Raven Project Website. Contribute to RavenProject/ravenproject.github.io development by creating an account on GitHub.📷
Pathfinder - Today at 2:37 PM https://i.imgflip.com/2kieyw.jpg
SpyderDev - Today at 2:38 PM
Pathfinder - Today at 2:38 PM
Tron's in there. Just have to look hard (like finding Waldo)
RavencoinDev - Today at 2:38 PM @Pathfinder
You are the best, I'm just saying....
Vincent - Today at 2:38 PM
i understand but pure economics will go into play. i will not harp on it here...there is plenty of time for this
Skan - Today at 2:38 PM
Ok good to know @ website, will spread that info
Vincent - Today at 2:38 PM
obvious my soapbox
RavencoinDev - Today at 2:39 PM
Any questions about Ravencoin.com?
Hans_Schmidt - Today at 2:40 PM
I come to these meetings for @Pathfinder
RavencoinDev - Today at 2:40 PM
SO DO I!If I say no will you delete your post?(edited)📷Actually, if we don't have any further questions about the website that would be a great topic.
[Dev] Blondfrogs - Today at 2:43 PM
RavencoinDev - Today at 2:43 PM @[Master] Roshii
has been hard at work adding asset support to the mobile wallets.📷3
You'll be able to see, transfer, receive assets.You'll also be able to create them right on your phone.
mapple - Today at 2:44 PM
awesome for small business use cases
Vincent - Today at 2:45 PM
will that only include RVN created assets or other currencies as well?
RavencoinDev - Today at 2:46 PM
The RVN wallets only support RVN and soon will support RVN assets.📷2
Agreed!Any other questions about Mobile support?
russ - Today at 2:48 PM
any web wallets that support assets yet?
RavencoinDev - Today at 2:48 PM
That's a good question!
Chatturga - Today at 2:49 PM @traysi -[MM Sysop]-
Might be able to answer that.
Pathfinder - Today at 2:49 PM https://i.imgflip.com/2kifzg.jpg
RavencoinDev - Today at 2:49 PM
That's amazing.I think Pathfinder could get paid to make memes for a company...@Under
Has done some great work migrating web based bitcoin tools to Raven.I would love to see a web dev kit that allowed web/mobile developers to easily incorporate Raven into their projects.
SpyderDev - Today at 2:51 PM
When is the meme bounty program?
Hans_Schmidt - Today at 2:51 PM
Just wondering- is anyone tracking use of post-2.04 client use on the mainnet? It would be good to know if the non-asset stuff is continuing to work without issues on main.
[Master] Roshii - Today at 2:52 PM @RavencoinDev
I have some ideas for mobile integration kit
[Dev] Blondfrogs - Today at 2:52 PM
Everything seems to be in order on Mainnet.
RavencoinDev - Today at 2:52 PM
Awesome @[Master] Roshii
Let's open it up for General Q&A for the last 10 minutes. Anybody have a question they have been dying to ask?
Under - Today at 2:53 PM
I’d really like to know about the build system.The solution I use is pretty reliable.
cade - Today at 2:53 PM
What would you like to know about it?
Under - Today at 2:54 PM
I’d be glad to train you up on mine
RavencoinDev - Today at 2:54 PM
We are working to incorporate the work that you have put in there. Still struggling with the Mac build part of it.
Hans_Schmidt - Today at 2:54 PM
Do you track wallet version usage on main. Any idea how many people are using newer versions?
cade - Today at 2:54 PM
The current build system we're using is based on what you've doneJust modified to fit into our CI process
[Dev] Blondfrogs - Today at 2:55 PM @Hans_Schmidt
We don't have a rolling tally but you can use the explores to view node versions.
RavencoinDev - Today at 2:55 PM
We do check what's being run on the network periodically but don't have a dashboard type view into the version data.
Vincent - Today at 2:55 PM
is the burn rate going to be tracked and charted on the asset explorer?
Under - Today at 2:55 PM
Rather than incorporating it, it vanilla in a vanilla Ubuntu 18 box works pretty well. CI like Travis could run on a fully gitian build, which I’m glad to work on too
RavencoinDev - Today at 2:56 PM @Vincent
There was talk of creating an RPC call that would show how much has been burned and for what purpose.Anybody want to take a shot at writing that?
Under - Today at 2:56 PM
I’m in the process !Lol
Vincent - Today at 2:56 PM
be a great stat to watch
russ - Today at 2:56 PM http://ravencoin.asset-explorer.net/stats @Vincent
burn and creation rate
Vincent - Today at 2:56 PM
RavencoinDev - Today at 2:57 PM
Sweet, thanks @russ
russ - Today at 2:57 PM @Scotty
cade - Today at 2:58 PM @Under
We have processes and tools that are in use within our organization and we leverage those tools for all of our projects. We have taken the awesome work you've done and tailored it to fit within our toolsets.📷2
Under - Today at 2:59 PM
I can understand that, but I’d counter that the process I describe is simply a copy of bitcoins and allows for it to be replicated in a larger community of developer outside of the Medici teamIt makes the build process trustless and decentralized if it can be replicated by anyone.But I get why you have your ways of doing it.
Hans_Schmidt - Today at 3:00 PM
If you drop the burn address into the web explorer, it tells you how much went there.
Vincent - Today at 3:00 PM
charts are nicer📷2
RavencoinDev - Today at 3:01 PM
I would like a burned endpoint that coinmarketcap can easily call to use in their circulating supply metric.
Vincent - Today at 3:01 PM
burn and rewards can only go one way.... 📷
RavencoinDev - Today at 3:02 PM
Alright, thank you all for being here today. Thank you for your support and for all your effort on Ravencoin platform!
Neo-Geo - Today at 3:02 PM
While we are aware of the dev team’s commitment to ASIC resistance, are there any assurances that RVN dev will find a solution to stay GPU exclusive for optimal decentralization? Monero’s commitment to fork every 6 months (currently on CryptoNightV8) has been wildly successful in keeping AMD’s cards pointing predominantly at their network. RVN is quickly replacing Ethereum as the defacto coin to mine for Nvidia owners (the world’s most popular video card), but the rise of FPGAs can ruin the incentive for GPU miners and lead to hash centralization.📷2
Vincent - Today at 3:02 PM
as a noob...glad to be part of this...great job by all
cade - Today at 3:03 PM @Under
We will be releasing our build process to the community
RavencoinDev - Today at 3:03 PM
we are committed to ASIC resistance and we are watching Monero closely.Thanks again everybody. Now go find some BUGS!
Under - Today at 3:04 PM
Cool thanks guys
[Dev] Blondfrogs - Today at 3:04 PM
BTW. QT wallet GUI update is coming. hahahah. have a good day everyone📷1
russ - Today at 3:05 PM
mxL86 (MinerMore.com) - Today at 3:05 PM
Hans_Schmidt - Today at 3:05 PM
Pathfinder - Today at 3:05 PM
thank you everyone!
Bitcoin Core is a community-driven free software project, released under the MIT license. Verify release signatures Download torrent Source code Show version history Bitcoin Core Release Signing Keys v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Verify release signatures Download torrent Source code Show version history. Bitcoin Core Release Signing Keys v0.11.0+ 01EA5486DE18A882D4C2684590C8019E36C2E964 bitcoin × 84 software-installation × 7 14.04 × 6 command-line × 6 apt × 6 ppa × 5 server × 4 software-recommendation × 4 compiling × 4 12.04 × 3 bash × 3 installation × 3 12.10 × 3 qt × 3 ethereum × 3 donation × 3 18.04 × 2 unity × 2 nvidia × 2 package-management × 2 upgrade × 2 lubuntu × 2 13.10 × 2 software-center × 2 Bitcoin Core (formerly Bitcoin-Qt) is the third Bitcoin client, developed by Wladimir van der Laan based on the original reference code by Satoshi Nakamoto. It has been bundled with bitcoind since version 0.5. Bitcoin-Qt has been rebranded to Bitcoin Core since version 0.9.0 .. Bitcoin Core can be used as a desktop client for regular payments or as a server utility for merchants and other 以前看过龙少这篇Windows下的教程，《VC编译调试比特币源码》，搞了半天没搞定。。最近装了个Ubuntu玩玩，于是想再试试，编译安装成功，有兴趣的可以试试。我的系统版本 Ubuntu 14.04，可以装双系统也可以装虚拟机，至于怎么装Ubuntu可以另外搜索。参考资料：（1）ubuntu下从源码编译比特币(Bitcoin
For Bitcoin Core Client updates: https://bitcoincore.org @bitcoincoreorg in Twitter Linux terminal commands: sha256sum, tar, cp, sudo, rm, exit, less * All other commands have been covered in ... BitCoin mining on Ubuntu using specialized ASIC procesors and Ubuntu software such as: CGMiner, BFGMiner, EasyMiner https://linuxhint.com/best-usb-bitcoin-mi... In this video from http://www.secureyourwallet.com we do a full review of the original Satoshi Bitcoin wallet. We do an install, look at the blockchain data,... Ubuntu -1 Setting up Bitcoin Commands, sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt sudo apt-get install bitcoind sudo blkid sudo nano /etc/fstab ... To add the PPA and install Bitcoin open a terminal window (press Ctrl+Alt+T) and copy+paste the following lines: sudo apt-add-repository ppa:bitcoin/bitcoin -y sudo apt update && sudo apt install ...