For discussion about Litecoin, the leading cryptocurrency derived from Bitcoin. Litecoin is developed with a focus on speed, efficiency, and wider initial coin distribution through the use of scrypt-based mining.
Soo, i found some old wallet files stored away. I probably hasn't anything on them, but you never know.... I downloaded Bitcoin Core and trying to check it, but it seems like i need to download the whole chainstate first, 230gb that is. i'we only progressed 25% in 24hrs, and my poor old HHD is getting hammered 100%, it probably doens't like that. I tried getting it from this site but it seems to be dead: https://getbitcoinblockchain.com/ Any solutions? I'm currently downloading a 21gb bootstrap.dat that supposedly will get my client and wallet up to date, but dunno of that helps.
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
Storage space: I am using an 8 GB microSD card for the OS, and a 128 GB USB drive for data. Minimums I would recommend: 8GB SD card and 32 GB USB drive.
Reddcoin Core client version: v18.104.22.168-a8767ba-beta (most recent version at this moment). ↳ Screenshot
You need the OS; Lubuntu. Download Lubuntu (707 MB) for the Raspberry Pi: https://ubuntu-pi-flavour-maker.org/download/. It's a .torrent download, so you will need a BitTorrent client. Message me or post in this thread if you need help with this.
You need software to write the OS to the SD card. I use Etcher. Download Etcher: https://etcher.io/.
Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.
Select drive: select your microSD card.
Plug the SD card into your Raspberry Pi and power it up.
Lubuntu should boot up.
Set up Lubuntu, connect to the internet (wired or wireless). ↳ As username, I chose "rpi3b". You will see this username throughout this whole tutorial.
Make sure date and time are correct ([Menu] > System Tools > Time and Date). ↳ Click on Unlock to make changes. I personally change Configuration to "Keep synchronized with Internet servers". ↳ Screenshot
Reboot ([Menu] > Logout > Reboot). I am connected to wifi, but have issues getting wifi to work on initial boot. A reboot solves this issue.
Make sure system is up-to-date, install never versions.
Open LXTerminal ([Menu] > System Tools > LXTerminal). ↳ Screenshot
Enter the following in LXTerminal: sudo apt update && sudo apt upgrade ↳ Screenshot
You will be asked if you really want to continue. Enter Y (yes).
Updates are being installed! Wait until it's finished.
Install programs that will be used in this tutorial.
GParted: to partition the USB drive.
Htop: to see the amount of memory (RAM) and swap that is in use.
Enter the following in LXTerminal to install these 2 programs. sudo apt install gparted && sudo apt install htop ↳ Screenshot
Create 2 partitions on the USB drive: 1) Swap partition 2) data partition (for the Reddcoin blockchain) The swap partition is necessary: The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 2 GB of 'virtual' memory by creating a swap partition.
Important: Backup your USB drive if needed. The USB drive will be formatted, so the data on the USB drive will be wiped.
Please use the USB drive solely for this purpose, do not combine it with other stuff.
Keep your USB drive plugged in, do not (randomly) plug it out.
Plug your USB drive in.
GParted will be used to create the partititons. Start GParted via LXTerminal: sudo gparted ↳ Screenshot
Apply the changes. Click on the check mark or select Edit > Apply All Operations. ↳ Screenshot ↳ Screenshot
Important: The name of the swap partition is needed later, so please write it down. Mine is /dev/sda1 (first partition on first drive (drive 'a')). ↳ Screenshot
Reboot. After the reboot, the data partition you just created should be visible on your desktop. ↳ Screenshot
The swap partition is created, so now we can enable and use it.
The swap in use can be monitored with the program Htop. Open Htop ([Menu] > System Tools > Htop) to see the 'Swp' (swap) in use. ↳ Screenshot By default, swap is not used, so 0K. ↳ Screenshot You can leave Htop open.
To enable the swap partition, open LXTerminal and enter the following commands: (Assuming /dev/sda1 is your swap partition.)
Unpack the file (large file, takes around 15 minutes to unpack): sudo xz -d bootstrap.dat.xz ↳ Screenshot
After a successful unpack, your will find the file bootstrap.dat in your USB root folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
The welcome screen will appear and ask you about the data directory. I suggest a new folder on your USB drive, I picked blockchain. The directory will be created with all the necessary files. ↳ Screenshot
Click on the three dots (...) on the right. ↳ Screenshot
Click on Create Folder at the upper right corner. Type and enter in the folder name. (In my case: blockchain.) Click on Open. ↳ Screenshot ↳ Screenshot ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Move the bootstrap.dat file to your data directory you selected in the previous step. By doing this, Reddcoin Core will use the bootstrap.dat file to import the blockchain, which speeds up syncing. sudo mv bootstrap.dat /media/rpi3b/usb/blockchain/ (Assuming blockchain as data directory.) ↳ Screenshot
The Reddcoin Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Keep the client running until it's fully synchronized. It will use the bootstrap file first, and download the rest of the blockchain to complete the sync. This can take some time (it took 2 days for me). Syncing the blockchain uses a lot of resources, so the software may react slow.
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen! ↳ Screenshot
When synchronization is complete, you can start staking your Reddcoins.
You can write down your private key or copy and save it in a document. Make sure you save it somewhere only you can access it.
To import later: Debug window -> Console -> importprivkey [label] [label] is optional. ↳ Screenshot (without a label) ↳ Screenshot (with a label)
Boot with only 1 USB drive plugged in: Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly. If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
Start Reddcoin Core easier Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.
Right Click on your Desktop and select Create New -> Empty File. ↳ Screenshot
Enter a file name, make sure it ends with .sh, and click on OK. I've chosen for Reddcoin.sh. ↳ Screenshot The file will be created on your Desktop. ↳ Screenshot
Add the command to start Reddcoin to the file.
Right click on the file, select Leafpad (to open the file in a text editor). ↳ Screenshot
Add the following to the file and save the file: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot
To be able to execute the shell script (.sh), it has to have 'execute permissions'.
Right click on the file, and select Properties. ↳ Screenshot
Click on the Permissions tab.
For Execute, select Anyone, and click on OK. ↳ Screenshot
To start Reddcoin Core, double click on the file. A new window will pop-up, asking you what you want. Execute in Terminal is what we want, so you can click on enter. ↳ Screenshot Reddcoin Core will now start. Do not close the Terminal window, you can minimize it if needed.
Minimization options Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
Activate 'Minimize on close'. Settings -> Options... -> Window (tab) -> Minimize on close. ↳ Screenshot Reddcoin will still run when you click on the X button. To close/exit Reddcoin, right click on the Reddcoin icon in the system tray (bottom right corner). ↳ Screenshot
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
After your download is finished, open the file and click Install Package. ↳ Screenshot
To run the VNC Connect once:
Open [Menu] > Run, and enter: vncserver-x11 ↳ Screenshot
To auto run on startup:
Open Default applications for LXSession ([Menu] > Preferences > Default applications for LXSession). ↳ Screenshot
In LXSessions configuration, select Autostart in the menu left.
Under Manual autostarted applications, enter vncserver-x11 and click on + Add. ↳ Screenshot ↳ Screenshot
Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.
When VNC Connect is running, you'll see a VNC icon on the right bottom corner. Double click the icon to open VNC Connect and to see the IP address you need to enter to connect to your Raspberry Pi. ↳ Screenshot
I'm not at all on top of my incoming messages, so in an attempt to stem the flood and address most of them, here's the current contents of my head. I feel some are using our rise to illustrate the absurdity of cryptocurrency pricing (http://uk.businessinsider.com/dogecoin-cryptocurrency-has-market-cap-above-2-billion-2018-1 for example). To me, in an environment where a cryptoasset with $30 USD equivalent transaction fees has a market cap of over a quarter of trillion dollars, I don't think we're the absurd one. Yes we take ourselves less seriously, but that doesn't mean we're not serious behind the scenes. We're a 4 year old currency with transaction fees barely over a cent and significantly higher throughput than most other cryptocurrencies. That said, now is not the time to pat ourselves on the back, 1.14 needs shipping and we need wider adoption. If you run a service/store, please look into taking Dogecoin. If you don't, please talk to others about how you can help them accept Dogecoin (DO NOT just flood them with emails saying they should, but ask why they don't and what you can do about it). On that note, lets talk structure of Dogecoin for a second. A lot of people presume Dogecoin is managed by a single coherent entity - this is very much not the case. The founders, current developers, reddit moderators, IRC, social and other teams behave as loosely coupled teams, with our own projects. We talk frequently, but there's no single leadership structure. In common with Bitcoin we have a post-launch dev team; we are not those who decided to launch a coin (that's Jackson & Billy), we saw Dogecoin as it was and decided it was something we wanted to be involved in. We're also not those who missed out on Bitcoin, I was in Bitcoin in 2011, but I didn't believe in how it was designed. As a consequence of this, "Why is no-one doing ?" generally boils down to either "We like it this way" or "Why aren't you doing ?". Most crucially; we're not taking the inflationary coins away because they're why we're in Dogecoin. I said I was in Bitcoin in 2011, and the reason I didn't stick with it is I don't believe in deflationary currencies. Even if we did, we'd have to somehow convince the miners to mine a coin where they weren't paid (which is what the inflation pays for), so the realistic scenario is an inflation-less Dogecoin would either have no miner adoption, or fees matching Bitcoin. This is typically where someone says something about their investment in Dogecoin. I really can't advise on investments, I bought Bitcoin in 2011 and sold early enough on that I'm typing this from my bedroom rather than a beach, so you probably shouldn't listen to me. I will however say that the developers have a lot less Dogecoin than virtually anyone thinks, and certainly the next dev fund payout is likely to be a significant multiple of my personal holdings, simply because we're post-launch so we've had to buy our Doge the way everyone else had to buy or mine. What else... Nodes - I've added a new permanent node in LA, and I'm bringing additional nodes up in Ireland and Seoul now. A bootstrap.dat torrent is being worked on right now, which should help too. If you're running a node please note:
It really needs to be kept online, to ensure it's actually relaying more data than it's consuming
If you can open port 22556 to the world, please do so, it will vastly improve the number of nodes that can connect to you
It's full nodes (those running Dogecoin Core) we need, leaving Multidoge/Android wallet/etc. open doesn't help us very much
1.14 will also significantly improve performance, and is making nice progress. Fees are my next task after this post, and then there's a lot of small items to address, but I'm hoping to get an alpha out shortly. Also I haven't broken testnet yet, which is a nice change compared to 1.10! We aren't about to introduce paying nodes because it's essentially technically impractical. This could either come from mining rewards (and you can fight either the miners or those who we create too many coins already, for that), or from other receiving nodes themselves. If it's from mining then somehow we'd have to identify contributing nodes, if it's from receiving nodes I'm not sure people are going to be happy with their balance dropping due to network usage. Although it might be a break-even I suppose. Generally, though, paying nodes is called proof of stake, and that's a whole different discussion. Someone asked about the website - it's being discussed, let me get back to you. Please treat your Dogecoins and wallet files like you would cash. We can't get them back for you if you send them to the wrong person (if we could, we'd have raided the Dogeparty address and be retired on a beach by now). Keep backups, and never delete old wallets (you never know when you might need a random key from an old wallet). Full list of changes in 1.14 is coming (although generally if it's in Bitcoin Core 0.14, expect to see it in), but the highlight for me beyond the improved performance is hierarchical deterministic wallets, which mean restoring old wallet backups will recover more recent funds. That should save a lot of lost funds, I hope! Last one, quick list of Twitter accounts to follow:
Among the advantages of TOR vs I2P listed on your site, you mentioned that the former has some mechanism to deal with blocking: the bridges. That's not a priority for I2P yet, but that's only because of a still limited adoption. If adoption increases, blocking will be more likely. Anyway i'm writing this post to propose a better solution than Tor's Bridges, which require the user to manually search them on the web and add them to the list. The bridge mechanism is very similar to the old eMule's "nodes.dat" : do you remember when the eMule bootstrapping nodes were blocked/offline , and you had to manually search the web for a new nodes.dat file? And you had to manually load it from the software? 15 years have passed, but the P2P bootstrapping mechanisms haven't evolved so much. Even cryptocurrency full nodes have the same issue: if the Bitcoin Core's bootstrapping nodes are taken down, you have to manually search and add other ones to the list. What i propose is: automating that for you. The I2P or other P2P software, when it has trouble with bootstrapping, it googles for something like "I2P ADD NODES" , and the SERP will show you strings like "I2P ADD NODES , ..., " that have been previously posted by someone around the web, on purpose. The I2P client then will fetch those results from the SERP, verifying that the content has been posted by the I2P devs and not someone else, by checking the SIGNATURE . When the I2P devs know that some country blocked critical nodes, they will put ADD NODE instructions like that on public forums or other sites indexed by the engines, so that the I2P software can find them. After all that's what the old eMule users did manually: they searched Google for "nodes.dat". Why not automate that boring task ? Let me know your thoughts on this solution!
Cannot find bitcoin.qt data folder, dont know where to put blockchain.dat
Read alot of explanations on the net trying to figure this out and i really have had no luck and need it sorted asap. Searched for %APPDATA%\Bitcoin and C:\Users\YourUserName\Appdata\Roaming\Bitcoin but theres no bitcoin folder to be found, there is a bitcoin core folder though. Not sure how to create one if thats what i need to do and really just hoping to get some straight forward help finding where to place this blockchain data and get it up to date asap. Thanks for any and all help.
I have both Armory and Bitcoin Core (qt) running, but my balance isn't showing up in Armory. I just installed everything last night and I'm new to Bitcoin. If I go to Blockchain.info I can see my balance fine. I do notice that Bitcoin Core says my wallet is "out of sync" and I'm sure this software is the problem. I did nothing on install to configure it. Any suggestions? thx edit: forgot to mention I'm running OS X 10.9.4
I want to stake Reddcoins on my Raspberry Pi, but there is no easy to install package for the Reddcoin Core client. I found some tutorials (mentioned at the bottom, under 'credits'), but I still struggled to get the result I wanted. It took some small adjustments, but I got the GUI Wallet of Reddcoin Core working on my Raspberry Pi Model 3B. See the steps below. :).
If you have any questions or comments, please post a comment in this thread, so others can also benefit from it.
If you would like to tip me: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
Even though Raspbian is the primary OS for the Raspberry Pi, it seems that it's not possible to build and compile the Reddcoin wallet software for Raspbian Stretch. However, I got the wallet compiled using Ubuntu MATE.
RPi: Raspberry Pi 3 Model B
OS: Ubuntu MATE 16.04.2 (Xenial)
Space needed: I would recommend at least 32 GB. I am using an 8 GB SD card for the OS, and a 128 GB USB drive for data.
The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 1 GB of 'virtual' memory by creating a swap file. After your Raspberry Pi has rebooted, open MATE Terminal again and enter the following commands:
sudo fallocate -l 1G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
To make sure the swap file persistent (so it survives a reboot), you have to add a line to the /etc/fstab file.
In MATE Terminal, enter the following command to open the file in Pluma (text editor): sudo pluma /etc/fstab
In Pluma, create a new line, add this text: /swapfile none swap sw 0 0 ↳ Screenshot (You should add spaces to vertically align the lines.)
Save and close the file.
Back to MATE Terminal; reboot your Pi: sudo reboot
To see if the swap file is used after a reboot, run: sudo cat /proc/swaps ↳ Screenshot
After the reboot, open MATE Terminal again. Download, unpack, configure, build and install Berkeley DB:
Add this line in Pluma: /uslocal/BerkeleyDB.4.8/lib/ ↳ Screenshot
Save and close the file.
Back in MATE Terminal: sudo ldconfig
Download the source of the Reddcoin wallet and build it:
git clone https://github.com/joroob/reddcoin
sudo ./configure --disable-tests
sudo make ↳ Screenshot (this will take some time; with me it took just over 1 hour)
sudo make install
Speed up synchronizing with the Reddcoin blockchain by bootstrapping.
cd (to make sure your working directory is your home directory)
Download the bootstrap file (1.45 GB): sudo wget https://github.com/reddcoin-project/reddcoin/releases/download/v22.214.171.124/bootstrap.dat.xz
Unpack the file: xz -d bootstrap.dat.xz
After a successful unpack, your will find the file ''bootstrap.dat'' in your home folder. ↳ Screenshot
On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
Start the Reddcoin Core client: sudo $HOME/reddcoin/src/qt/reddcoin-qt
The welcome screen will appear and ask you about the data directory. I suggest a new directory in your home directory, I picked 'blockchain'. The directory will be created with all the necessary files. ↳ Screenshot
After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.
Use the file manager (Caja) to browse to your home directory and move the ''bootstrap.dat'' file to your data directory you selected in the previous step. Your home directory is the first item in the File Manager in the left menu.
The Reddit Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
Launch the Reddcoin Core client again: sudo $HOME/reddcoin/src/qt/reddcoin-qt
Keep the client running until it's fully synchronized. This can take some time (it took 2 days for me).
You can see the progress in the debug window (Help > Debug window). ↳ Screenshot
When the synchronization is completed, the red (out of sync) will disappear on the Overview screen!
Your wallet will be encrypted, and the Reddcoin Core client will be closed. Launch the Reddcore Client again. ↳ Screenshot 4
To stake, you need to unlock your wallet (by entering your password): Settings > Unlock Wallet...
Make sure "For staking only" is checked before clicking OK. ↳ Screenshot
You can only stake with Reddcoins that have matured: coins have to be at least 8 hours in your wallet to mature.
The grey arrow at the bottom should be green when staking. Hover over that icon to see the progress of staking. ↳ Screenshot
Backup your wallet! File > Backup wallet... ↳ Screenshot
Start Reddit on system login. Settings > Options ↳ Screenshot > This works when using only an SD card. > I can't get this to work when using SD card (for OS) and a USB (for data/blockchain).
Adjust minimization options, so you can safely press on the red X (close/exit button). ↳ Screenshot
The default browser, Firefox, stops working and crashes after updating Ubuntu MATE. My solution is installing another browser: Chromium. To install Chromium, enter the following in MATE Terminal: sudo apt-get install chromium-browser ↳ Screenshot You can then access Chromium via [Menu] Applications > Internet. ↳ Screenshot
To remote connect to the Raspberry Pi, I use VNC Connect from RealVNC.
There is a discussion about nodes that came up today, where it seems I'm discouraging people from running the full QT/Core client. Yes and No. What I'm trying to make sure people understand is how things work, and that it is NOT mandatory to run a client in order to use Dogecoins (and yes, I realise that browser-based tools like coinb.in and wallet sweepers are 'clients' by strict definition). That said, more nodes is absolutely a good thing for the network. Preferrably full nodes. How do you run a full node? Just run Core/QT and open up Port 22556 on your router so it can connect to more than 8 peers. What will it cost you? You need your machine to be on 24/7/365, you need enough storage for the full blockchain (currently about 20Gb. Bitcoin is over 120Gb) and enough bandwidth to keep it in sync and share blocks with peers. A couple of Gb a month, most likely. This is best done with a desktop on a wired broadband link. Or maybe a hosted VM in the cloud. :)
EDIT 2017-01-09: Wallets WITHOUT Clients
Since I started helping people on /BitcoinBeginners, I'm getting a lot of questions about how to use wallets without running clients or trusting third parties. So here are a couple of resources that will make that possible, and not just for Dogecoin: Multi-Coin Wallet GeneratorNow supporting 129 currencies!Coinb.in Start by setting the currency, found in the gear wheel in the Broadcast tab. Dogecoin Wallet Sweeper Redeem 'paper' wallets containing up to about 100 UTXOs. Bitinfo Charts My favourite block explorer, handles a bunch of cryptos. Using these resources, it is possible to hold, receive and spend coins in various currencies, without having to run QT or a 'lite' client. You can also download and run the pages on your own device.
EDIT 2016-11-23: SEMANTICS about MINING! :P
Even though there is already a section on mining below, it has been suggested given the huge number of posts on the subject that this needs to be made clearer. Since people get their panties in a twist over the word 'dead', lets change that...
MINING IS DEAD!
MINING DOGECOIN IS UNPROFITABLE!
Put simply, there is no way to mine Dogecoin and make a profit because of the massive hashpower provided by industrial-scale Litecoin miners. Mining Doge directly stopped being viable when our hashrate exploded with the introduction of AuxPoW. Mining with CPU's and GPU's died when ASICs were introduced. And mining with a laptop WILL kill your laptop and cost you a fortune to repair or replace. Mining Litecoin with an exchange that also mines Doge and others will earn less than the electricity consumed, and you won't recover your costs. Probably ever, but certainly not in any reasonable time. Mining other currencies may be a thing, but that's beyond our scope here. This is /Dogecoin, not /GetRichMiningCryptos after all. If you want to mine the newest scamcoin for fun and profit, look elsewhere for advice. :/ Oh, and most important:
READ BEFORE YOU POST!
At any given time, there are half a dozen posts on the frontpage just like the one you're about to write, where the answers have already been given. Read them. Don't make people waste their time repeating themselves because you were too lazy to bother reading stuff. :P So there I was, having a quiet Sundy arvo bludge, as you do, when 42points turned up on Facebook and asked me to write a new sticky post for /dogecoin. Why would he do this, when he should be having a bludge himself, I hear you ask? Well, seems he was doing exactly that, and wanted to fob off the work he’s too slack to do himself. ;) Ah well, being a sucker for punishment, I’ll grudgingly oblige I guess. OK, first things first.
A client is a piece of software you keep on your computer which holds one or more wallets. Here are the current client versions. If you're using an older client please upgrade to the newest version prior to sending/receiving coins. Backup! Backup! Backup your wallet.dat file or private key so you can import them into the latest version of the client.
Be warned that unless you’re running Core (aka QT), you could have issues with wallets containing lots of UTXOs (Unspent Transaction Outputs - Where your coins REALLY live). Go read the ELI5 below, and keep a close eye on your transaction counts. If you DO run Core, realise that all full clients, regardless of the coin, require a copy of the blockchain and must keep it up to date. This will cost you time, storage space and bandwidth. You can save a little by downloading the bootstrap file though. I haven’t checked how recent this one is, so let me know if you find a more current version.
OK, so next, grab this wallet generator. Even if you plan on running a client(s). Because a) it does many, many cryptocurrencies, and b) you WILL need wallets at some stage over and above what you keep in your clients. Just be sure to run it locally (and offline if you’re truly paranoid).
Oh, and here’s a simple way to keep track of all your wallets using HTML. You can grab the source and modify it, then upload it wherever you need to suit your needs. You will also want a separate file with your private keys, but don’t upload that one anywhere, because if you lose your keys or someone else gets access to them, you will lose your coins.
Next, be aware that there are online wallets available. While any wallet you don’t own the keys to isn’t actually yours, and therefore isn’t safe, the following are safer than most. Dogetipbot of course is used daily by shibes on Reddit. Block.io uses multisig and gives you Doge, BTC and LTC wallets as well as testnets, and Dogechain gives you your private keys (and also offers a wallet sweeping service).
Exchanges also offer wallets, of course. Not that you should use them to store your hard-earned coins, because they can and do get hacked with monotonous regularity. But at some stage you’re going to want to trade, or hold a few uncommon coins. You could do worse than these three:
And then there’s the obligatory question of mining. Put simply, mining is for all intents and purposes dead, and has been for a long time now. The costs are greater than any possible returns. But, if you insist on doing it anyway, maybe because you inherited a miner, you can earn about 0.01 LTC/day per MH/s merge-mining at Litecoinpool. That’s about 4 cents. :(
Shibes sometimes complain that the devs are not as active in /dogecoin as they used to be. You can find them on IRC, slack or their very own sub if you need them though. Or poke sporklin, who can often help.
You can of course ask any questions here, or post them in the sub. However, do try searching first, because I guarantee every possible question has been asked many times before. And you should also subscribe and hang out in /dogeducation occasionally. There’s much awesomeness there.
From peoplma I was wondering if you could add just a couple things. A link to the coinomi android wallet, it's probably the best one out there. And a sentence somewhere along the lines of "if you need help with any dogecoin software you are welcome to make a post, but PLEASE include your OS, version number of the client, and any relevant transaction IDs that you are willing to share" if you can fit that in somewhere. Also, if you want to link to Prohashing, I'm pretty sure it's the only Scrypt mining pool that will actually pay out in doge. The others I know of pay out in litecoin or bitcoin. And it's a profit switching multipool, so gives a better return than just mining ltc/doge. And there's these two wiki articles I thought would be helpful to link /dogecoin/wiki/technical for those technically minded newbies or intermediate users who want to dig a little deeper. And maybe a link to /dogecoin/wiki/dogecoincoreguide next to the link for dogecoin core. From pts2002 Finally a proper sticky post! Here's some other stuff you could add: zpool.ca mining pool - You can get paid in pretty much any coin, and you can mine in multiple algos (currently mining lyra2v2 with my GPU). Doing about 500Ð/day shapeshift.io exchange - My favourite exchange, quick and easy. No registration required! Also, you should add some blockchain explorers! chain.so - Support for bitcoin, litecoin and doge. dogechain.info - Official blockchain explorer. Includes a wallet (already mentioned). Live update currently not working (?) EDIT: Here's another thing I found! preev.com currency value calculator - Easy way to check the value of your dogecoins (or bitcoins, or litecoins, or peercoins)!
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 (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
The block index database will now hold headers for which no block is stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility.
On Saturday we had 20 questions with a score of ten or more. Today we have 10 questions with a score of ten or more. https://area51.stackexchange.com/proposals/110056 None of the dogecoin stack followers have downvoted any questions. Maybe an external moderator downvoted questions in the proposal? Or a group of people decided to wihdraw their votes? Why? Such scare! Very conspir.. plz up.! Status 69 Followers 10 questions with a score of 10 or more *Required to start comittment phase 20 more questions with a score of 10 or more A lot of followers haven't voted, if you haven't voted, plz vote. If you haven't signed up, plz sign. Current Question List
How can I setup a Dogecoin wallet?
What are the best ways to back up my wallet?
What is "cold storage"? Why is it better for long-term holding?
How can I buy Dogecoin?
I am trying to install dogecoin core on ubuntu how do i install the dependancies?
How can Dogecoin be used outside of Internet transactions?
How can I "bootstrap" to speed up the process of syncing up with the Dogecoin blockchain?
How can I sell my stuff for dogecoins?
Can an old, unencrypted core wallet backup be used to move dogecoins out of that same wallets currently encrypted core wallet?
How does merged mining work with litecoin?
How do I backup my wallet, and how do I restore form the backup?
How to setup a dogecoin public node?
How do I get dogecoins?
What is a public node?
How do i import a existing wallet.dat file from a previous dogecoin installation
Why are online wallets considered bad?
What would happen to the dogecoin hash rate if litecoin became unpopular?
How long does it take for the dogecoin wallet to sync with the dogecoin blockchain?
Where can I buy things with doge?
How do Dogecoin transaction fees work?
What is Dogecoin mining, and how do I begin?
Is there a way to tip videos on youtube with dogecoin?
Is there a limit on how many Dogecoins can ever be mined/exist?
What price would dogecoin need to be in order for the mining rewards to cover the cost of electricity?
What is "sweeping" from one wallet to another and why is it important?
How can Dogecoin avoid the long transaction wait times and high fees that Bitcoin is currently experiencing?
What is the best (most efficient) way to mine Doge?
How do I set up Dogecoinfold?
What are three reasons to use Dogecoin that the average, non-technical user would find compelling?
Is it possible to have two Dogecoin core wallets running on the same computer at the same time?
Is there a roadmap for Dogecoin's future?
Who are the devs?
What exactly is a shibe?
How can we help to boost DogeCoin as an accepted Currency?
Can I recover my dogecoins if I accidentally have deleted my wallet?
What is it about the Dogecoin community that makes it so wow?
What happened to the dogecoin foundation?
Who owns and runs the dogecoin.com website?
Does segregated witness implementation reduce traceability on the blockchain?
What is the purpose of cryptocurrency?
Can I mine dogecoin on my laptop?
What programming language is used for the dogecoin core?
Let's go ... to the moooon! edit This back from Stack Exchange User does not have to follow the proposal in order to vote on the sample questions. As the faq says, any user with 150 rep on Area 51 can downvote any example question. So we're being sabotaged and we don't even know who is doing it... At least three people and none are followers. Such sad, very disappoint. FWIW: https://meta.stackexchange.com/questions/297329/proposal-questions-downvoted-by-anonymous
Viacoin Core 0.15.2 released: https://github.com/viacoin/viacoin/releases/tag/v0.15.2 For anyone who did not upgrade yet, please run Viacoin Core 0.15.2 which fixes the Denial-of-Service vulnerability CVE-2018-17144 This bug was also found in Bitcoin Core versions 0.14.0 up to 0.16.2 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 (on Windows) or just copy over /Applications/Viacoin-Qt (on Mac) or viacoind/viacoin-qt (on Linux). The first time you run version 0.15.0 or higher, your chainstate database will be converted to a new format, which will take anywhere from a few minutes to half an hour, depending on the speed of your machine. The file format of fee_estimates.dat changed in version 0.15.0. Hence, a downgrade from version 0.15 or upgrade to version 0.15 will cause all fee estimates to be discarded. Bootstrap for Viacoin 0.15+ is available: https://bootstrap.viacoin.org/
[Quick guide] Run a full node with btcd (an alternative to bitcoin-core) on debian
It's good to run a full node, and even better to run one with an alternative implementation to bitcoin-core. I was surprised how easy it is to install btcd (conformal's alternative implementation of a full node). I was also surprised how little bandwidth a full node uses. This quick guide will get you up and running. To use this method you will need debian testing (Jessie) because the version of golang on debian stable is too old. However, the binary produced will run on debian stable. You will need about 25GB free to store the blockchain, with an extra 20GB or so if you use the bootstrap.dat torrent. Probably the same instructions will work on ubuntu (but using sudo instead of root). INSTRUCTIONS TO RUN A FULL NODE WITH BTCD On debian testing the steps are: 1 - as root, do
2 - pull in and compile btcd and associated utilities as normal user,
$ mkdir btcd; cd btcd; export GOPATH=$(pwd); $ go get github.com/conformal/btcd/...
3 - run your node
$ cd bin $ ./btcd --externalip=YOUREXTERNALIP
(where YOUREXTERNALIP is your external IP address). 4 - on your router, forward port 8333 to the computer your node is running on. Once your node is running, check the port is open with a tool such as canyouseeme.org 5 - enjoy being part of the network! OPTIONAL STEP A (to download the blockchain faster, to be run before step 3): A1 - download Jeff Garzik's torrent to bootstrap the blockchain or the magnet link, magnet:?xt=urn:btih:36719ba2cecf9f3bd7c5abfb7a88e939611b536c&dn=bootstrap.dat&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.publicbt.com%3A80&tr=udp%3A%2F%2Fcoppersurfer.tk%3A6969%2Fannounce&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=http%3A%2F%2Fbttracker.crunchbanglinux.org%3A6969%2Fannounce (discussion here) A2 - run as normal user,
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
These instructions assume you are starting from scratch with a completely blank OS.
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
sudo nano /etc/dphys-swapfile
and Change the CONF_SWAPSIZE from 100 to:
Exit nano with control + x to write out the file.
Then, run the following to restart the swapfile manager:
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
In the Terminal window, change directory to where you put the binaries, e.g.:
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x *
That marks the binaries as executable.
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
Place the bootstrap.dat file into the ~/.lore directory.
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None;
Power usage and payback time
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
Securing your Pi
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
You'll be prompted to enter the old and the new passwords.
Security by default
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
You can query the status of the firewall like this:
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
Back up & Recovery
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale There are almost certainly free packages with similar functionality, I have just used that one for years.
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
And if that doesn't do the job, do a full reindex of the blockchain:
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
In the meantime, feel free to comment with your best practices.
After the extremely short update on Sunday, now 1.10 RC 1 is out the door I wanted to write a bit more on what we're doing, what happens next, and the importance of 1.10. So, as you're probably aware, 1.10 is our first major release in over a year. There was a 1.9, however development of it was abandoned in the middle of this year, as the process used was simply infeasible to follow (too much manual checking of changes from Bitcoin Core, unfortunately). It brings in a huge number of changes, but there's a few worth emphasising:
Security update to miniupnpc to fix a major security issue
Security fixes for transaction malleability (through DER signature modification and low-S/high-S signatures)
Security fixes for OpenSSL's handling of DER signatures
Massively improved synchronization process (much faster, essentially eliminates need for bootstrap.dat)
Improved reliability (although this is part of why a reindex is needed)
Improved user interface look & feel that fits in with the host OS
Most of the security fixes are also being made available in 1.8.3, although the fixes for CVE-2015-3641 are not readily compatible with that release, so it's only to be used where upgrading to 1.10 is not an option. Final releases of both should be out at the end of this month, but both clients have been heavily tested, and generally I'd encourage upgrading to 1.10 now if you can, and it's then fairly straight-forward to install the final release over it once it's out. Post-1.10, Bitcoin Core 0.12 should be branched early next year, and will likely form the basis for Dogecoin Core 1.11. Meanwhile langer_hans has been working on the Android client and updating it to use bitcoinj and libdohj, and we're hammering out bugs in libdohj. So far, that's going fairly well, and while we don't have an ETA, once out it should vastly reduce the time to update to new versions of bitcoinj (because we're extending it, rather than rewriting it). Multidoge HD will also follow the same development model, and hopefully we'll see it update to bitcoinj 0.14 at some point, enabling us to move forward with adding libdohj support.
Transfer Vertcoins from Bittrex to a Wallet. Synchronizing of Vertcoin Core Wallet is extremely long.
Hi. I would like to transfer my Vertcoins from Bittrex to a Wallet. It did'nt worked with Bitcoin Wallet. So I downloaded Vertcoin Core Wallet. When I launch it, it synchronizes. But it takes a very very long time. I downloaded bootstrap.dat, and I closed my Vertcoin wallet, I put it in the right folder (Vertcoin folder in Application Support folder). Then I relaunched my Vertcoin Wallet, and it always takes that long. The progress is 0.13% and I launched it yesterday night... So my questions : - Do I have to wait the end of the sync to transfer my Vertcoins from Bittrex to my Vertcoin Core Wallet ? - If not, there is no problem to transfer it later to Bittrex ? - If yes, how can I do to accelerate the progress ? I don't know what to do, help me please guys ! :)
Reddcoin 2.0.0 is a complete rebuild based off Bitcoin 0.9. This means in terms of the code-base we have introduced all the Bitcoin changes up to and including v0.9.5 into this version of Reddcoin Core. Taking this path will allow faster adoption of critical fixes and features. Within this release we have also included some features from the 0.10 bitcoin build, including a connected peers tab and visual bandwidth monitoring We suggest to read the release notes of Bitcoin up to and including 0.9.5 to get a full understanding of the changes. On top of the new features, Reddcoin Core v2.0.0 update contains very important security fixes and all users MUST upgrade to this version as soon as possible. Details on several vulnerabilities were made public by the Bitcoin team (Official Bitcoin warning) regarding the issues. It is particularly important that users who are staking do upgrade. This release introduces BIP66, and version 4 blocks. Once BIP 66 is enforced, version 3 blocks will be rejected from the network entirely as they contain less secure transactions. This means, if you are staking, you need to upgrade so that you don't risk miss out on your staking rewards Details of other notable changes are posted on Github Releases
First, Backup your existing wallet.dat and data folder Where to find your Reddcoin data folder?
Would be great if someone who has the skills & tools could generate us a nice stable MacOS build? Anyone?
Backup your wallet before using this. You've probably already done that, as I am sure you backup your wallet on a regular basis, right? Something bad happens, your wallet is destroyed AND you didn't take a backup? Don't blame me.
A lot of stuff has been renamed to 'Myriad' - however there are a couple of exceptions for reasons of compatibility with older existing versions:
default data directory is still myriadcoin
config file is still myriadcoin.conf
daemon is myriadcoind, rpc client is myriadcoin-cli
If you are compiling yourself, please configure with something like this:
That will enable the SSE2 version of the Scrypt algorithm. This may reduce the CPU load when syncing the blockchain. Oh, and there's still some tests that fail if you build and run the testsuite. I've been unable to find the issue, so please, when you fix it, submit a pull request.
A big thanks to cryptapus and 8bitcoder for their help in getting this release completed. Obviously we must also thank all of the contributors to the Bitcoin Core project, as that is the base that this is all built upon. And again thanks to 8bitcoder for starting Myriad in the first place.
Because this release is based on Bitcoin Core 0.10.0 and upwards, it makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with older versions of Myriad Core or other software:
Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
The block index database will now hold headers for which no block is stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.11.2 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility.
Notable changes (Borrowed from Bitcoin Core's Release Notes)
Myriad Core now uses 'headers-first synchronization'. This means that we first ask peers for block headers and validate those. In a second stage, when the headers have been discovered, we download the blocks. However, as we already know about the whole chain in advance, the blocks can be downloaded in parallel from all available peers. In practice, this means a much faster and more robust synchronization. On recent hardware with a decent network link, it can be as little as 3 hours for an initial full synchronization. You may notice a slower progress in the very first few minutes, when headers are still being fetched and verified, but it should gain speed afterwards. A few RPCs were added/updated as a result of this: - getblockchaininfo now returns the number of validated headers in addition to the number of validated blocks. - getpeerinfo lists both the number of blocks and headers we know we have in common with each peer. While synchronizing, the heights of the blocks that we have requested from peers (but haven't received yet) are also listed as 'inflight'. - A new RPC getchaintips lists all known branches of the block chain, including those we only have headers for.
RPC access control changes
Subnet matching for the purpose of access control is now done by matching the binary network address, instead of with string wildcard matching. For the user this means that -rpcallowip takes a subnet specification, which can be
a single IP address (e.g. 126.96.36.199 or fe80::0012:3456:789a:bcde)
a network/CIDR (e.g. 188.8.131.52/24 or fe80::0000/64)
a network/netmask (e.g. 184.108.40.206/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address matches one of them. For example:
0.9.x and before
-rpcallowip=::/0 (still dangerous!)
Using wildcards will result in the rule being rejected with the following error in debug.log:
Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 220.127.116.11), a network/netmask (e.g. 18.104.22.168/255.255.255.0) or a network/CIDR (e.g. 22.214.171.124/24).
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know all addresses (or scripts), even without the private keys. This can be used to track payments without needing the private keys online on a possibly vulnerable system. In addition, it can help for (manual) construction of multisig transactions where you are only one of the signers. One new RPC, importaddress, is added which functions similarly to importprivkey, but instead takes an address or script (in hexadecimal) as argument. After using it, outputs credited to this address or script are considered to be received, and transactions consuming these outputs will be considered to be sent. The following RPCs have optional support for watch-only: getbalance, listreceivedbyaddress, listreceivedbyaccount, listtransactions, listaccounts, listsinceblock, gettransaction. See the RPC documentation for those methods for more information. Compared to using getrawtransaction, this mechanism does not require -txindex, scales better, integrates better with the wallet, and is compatible with future block chain pruning functionality. It does mean that all relevant addresses need to added to the wallet before the payment, though.
It has been observed that many of the RPC functions offered by myriadcoind are "pure functions", and operate independently of the myriadcoind wallet. This included many of the RPC "raw transaction" API functions, such as createrawtransaction. myriadcoin-tx is a newly introduced command line utility designed to enable easy manipulation of myriad transactions. A summary of its operation may be obtained via "myriadcoin-tx --help" Transactions may be created or signed in a manner similar to the RPC raw tx API. Transactions may be updated, deleting inputs or outputs, or appending new inputs and outputs. Custom scripts may be easily composed using a simple text notation, borrowed from the bitcoin test suite. This tool may be used for experimenting with new transaction types, signing multi-party transactions, and many other uses. Long term, the goal is to deprecate and remove "pure function" RPC API calls, as those do not require a server round-trip to execute.
Hi, I haven't run my wallet (bitcoin-qt) in quite some time and today I decided to open it up. My local copy of the blockchain is 40 weeks behind (yeah, life get's in the way sometimes), and it looks like it will take several days to get up to date. So I've been looking for the bootstrap.dat file and had a hard time finding it. According to a quora article the reason it's no longer available is that since version 0.10.0 synchronization is faster than downloading and processing the bootstrap file. I'm running the latest version (0.13.1) and in about 3 hours it got from 40 to 39 weeks behind. I do have quite a hefty pipe at 250 Mbps, so bandwidth shouldn't be an issue. I thought that maybe the new "fast synch" doesn't play well with an existing blockchain and only kicks in when it starts from zero, so I renamed the bitcoin dir and started from a new empty one. After seeing it crawl through a couple thousand blocks at roughly the same speed it did with the 40 week-old blockchain, it was clear it wouldn't end in a reasonable time. So I'm now downloading a bootstrap.dat file I found in this bitcointalk post, but it could very well be a bogus or invalid file. Of course if that's the case it won't sync with the network, but it's a lot of bandwidth and time just to find out, isn't it? So, my question is: Why isn't the fast synch working? How are unsuspecting newbies supposed to use the core client? If the community is generating boostrap files, why not publish them where they can easily be found? Meh, I'll have it working in a few hours, but this experience put me in a foul mood. Sorry for the rant.
Welcome again Reddheads to another weekly update of Reddcoin Development. This month of August will usher in a new era for Reddcoin and its future development. After 9 months of work, and with the help of volunteers for testing and translations, and with some work provided by the original developers, I am pleased to announce that the new Reddcoin wallet v2.0 is ready to go live onto the main blockchain. If you are not aware, with this release we have taken a fork from Bitcoin (rather than Litecoin as originally). Using this as a base, it will pave the way for easier feature implementation from the upstream Bitcoin core software that launched most other coins. Thank you everyone for your patience while this work has been undertaken. And thank you for everyone who took the time to get involved. Over the coming months, the goal will be to introduce more upstream updates into the Reddcoin Core to further improve the Reddcoin network.. Here is the current status of what else is happening:
All work for v2.0 wallet is finalised.
Continue testing of block chain synchronisation on different platforms.
Creating an updated official bootstrap.dat and testing.
Release notes and other documentation updates.
Continue investigating the performance and behaviour of PoSV.
Investigate PoSV2 and improving network node support
Continue development of ReddID
New v2.0 Wallet is now ready
I have been saying it for a while now, but I am pleased to announce to you that the new wallet is now ready. I have completed putting the finishing touches and tidying the repository to a point where I feel it is ready for mainstream adoption. Release Date: 13th August 2016 AEST (Australian Eastern Standard Time)
Code-base switched to Bitcoin
New utility applications
Faster blockchain synchronization
Strict signature encoding (BIP66)
Staking v4 blocks
OP_Return 80byte data transactions
RPC access changes
Stakeminer will wait for both the blockchain and network on non encrypted wallets
QT includes network bandwidth and connected peer details
New DNS Seeds added
Reddcoin v2.0 will be provided as both downloadable binaries and also compile from source
32bit Linux binaries
64bit Linux binaries
64bit Windows binaries
64bit OSx binary
In the meantime, in preparation of this public release of the new wallet, I am continuing to contact and engage with the various major exchanges and 3rd party services to advise them that we will have an updated wallet in the near future.
If your interested in c++, js or python drop me a line, I have some interesting projects that need attention.
We are a global community, and cross many borders but boundaries do not need to hinder us. The crypto currency world has not reached its tipping point yet, but when it does, it is sure to escalate at an amazing rate. There are going to be many ups and downs, and an interesting ride for sure. If you would like to get involved and dont know where to start, reach out and we will see where you can jump in @Deadpool has a great Trello site going with activities that need looking at.
Thank you for your patience. I know in this arena things projects move fast, but I am confident that we now have a platform to move forward. There are lots of exciting projects out there, but none quite touch on the ideas I have in mind. As always, there is still plenty to do, and there is no time for resting. So where ever you are, enjoy your week ahead Keep on staking! Gnasher (John Nash) x-posted (https://www.reddcointalk.org/topic/866/state-of-the-redd-nation-august-08-2016)
All these Bitcoin Core wallet.dat files with lost passwords. Try to brute force and get a bounty in Bitcoins (sometimes in Bitcoin Cash, Bitcoin SV, or Bitcoin Gold too). We guarantee balance on wallets. Otherwise, we will give you your money back! Overview. There are basically four pieces of data that are maintained: blocks/blk*.dat: the actual Bitcoin blocks, in network format, dumped in raw on disk. They are only needed for rescanning missing transactions in a wallet, reorganizing to a different part of the chain, and serving the block data to other nodes that are synchronizing. Bitcoin (BTC) prices - Nasdaq offers cryptocurrency prices & market activity data for US and global markets. The following wallets, selling wallet.dat Bitcoin Core and btc Ethereum wallet are now available: More than 10 wallets are open thanks to you, thanks for your cooperation. Soon all purchase links will be on the new satoshi-box.com service. Satoshidisk.com may not work or be malfunctioning, we ask you if the purchase link does not work or if the file did not reach you, write to us for direct I downloaded the latest version of bitcoin core, added the wallet.dat file to the data directory, started it with -rescan, and waited almost a month (!) for the blockchain data to get up to date. The balance showed as 0 the whole time. I thought it would update once the blockchain was totally downloaded, but it still just says 0.