New England New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/ NewEnglandcoin Symbol: NENG NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones. Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt. 1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377 NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number Bitcoin Fork - Suitable for Home Hobbyists NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs. The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity. MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018) https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software. Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%. NENG v1.4.0 release enabled CPU mining inside android phones. Youtube Video Tutorial How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG. We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange. Twitter Airdrop Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners Graphic Redesign Bounty Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form. Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues. Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1 Milestones
Sep 3, 2018 - Genesis block was mined, NewEnglandcoin created
Sep 8, 2018 - github source uploaded, Window wallet development work started
Sep 11,2018 - Window Qt Graphic wallet completed
Sep 12,2018 - NewEnglandcoin Launched in both Bitcointalk forum and Marinecoin forum
Sep 14,2018 - NewEnglandcoin is listed at ShorelineCrypto Exchange
Sep 17,2018 - Block Explorer is up
Nov 23,2018 - New Source/Wallet Release v1.1.1 - Enabled Dynamic Addjustment on Mining Hashing Difficulty
Nov 28,2018 - NewEnglandcoin became CPU minable coin
Nov 30,2018 - First Retail Real Life usage for NewEnglandcoin Announced
Dec 28,2018 - Cheetah_Cpuminer under Linux is released
Dec 31,2018 - NENG Technical Whitepaper is released
Jan 2,2019 - Cheetah_Cpuminer under Windows is released
Jan 12,2019 - NENG v1.1.2 is released to support MacOS GUI CLI Wallet
Jan 13,2019 - Cheetah_CpuMiner under Mac is released
Feb 11,2019 - NewEnglandcoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork
Mar 16,2019 - NewEnglandcoin v22.214.171.124 Released - Ubuntu 18.04 Wallet Binary Files
Apr 7, 2019 - NENG Report on Security, Decentralization, Valuation
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto
Sep 1, 2019 - Shoreline Tradingbot project is Launched by ShorelineCrypto
Dec 19, 2019 - Shoreline Tradingbot v1.0 is Released by ShorelineCrypto
Jan 30, 2020 - Scrypt RandomSpike - NENG v1.3.0 Hardfork Proposed
Feb 24, 2020 - Scrypt RandomSpike - NENG core v1.3.0 Released
Jun 19, 2020 - Linux scripts for Futurebit Moonlander2 USB ASIC on solo mining Released
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining and Ubuntu 20.04 support
Jul 21, 2020 - NENG v126.96.36.199 Released for MacOS Wallet Upgrade with Catalina
Jul 30, 2020 - NENG v188.8.131.52 Released for Linux Wallet Upgrade with 8 Distros
Aug 11, 2020 - NENG v184.108.40.206 Released for Android arm64 Upgrade, Chromebook Support
Aug 30, 2020 - NENG v220.127.116.11 Released for Android/Chromebook with armhf, better hardware support
2018 Q3 - Birth of NewEnglandcoin, window/linux wallet - Done
2018 Q4 - Decentralization Phase I
Blockchain Upgrade - Dynamic hashing algorithm I - Done
Cheetah Version I- CPU Mining Automation Tool on Linux - Done
2019 Q1 - Decentralization Phase II
Cheetah Version II- CPU Mining Automation Tool on Window/Linux - Done
Blockchain Upgrade Dynamic hashing algorithm II - Done
2019 Q2 - Fiat Phase I
Assessment of Risk of 51% Attack on NENG - done
Launch of Fiat USD/NENG offering for U.S. residents - done
Initiation of Mobile Miner Project - Done
2019 Q3 - Shoreline Tradingbot, Mobile Project
Evaluation and planning of Mobile Miner Project - on Hold
Initiation of Trading Bot Project - Done
2019 Q4 - Shoreline Tradingbot
Shoreline tradingbot Release v1.0 - Done
2020 Q1 - Evaluate NENG core, Mobile Wallet Phase I
NENG core Decentralization Security Evaluation for v1.3.x - Done
Light Mobile Wallet Project Initiation, Evaluation
2020 Q2 - NENG Core, Mobile Wallet Phase II
NENG core Decentralization Security Hardfork on v1.3.x - Scrypt RandomSpike
Light Mobile Wallet Project Design, Coding
2020 Q3 - NENG core, NENG Mobile Wallet Phase II
Review on results of v1.3.x, NENG core Dev Decision on v1.4.x, Hardfork If needed
Light Mobile Wallet Project testing, alpha Release
2020 Q4 - Mobile Wallet Phase III
Light Mobile Wallet Project Beta Release
Light Mobile Wallet Server Deployment Evaluation and Decision
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.
This is just used for messing around with Cisco stuff, to get a feel for the configuration
HP Procurve 2650 J4899B 48 (50) Port Managed Switch, 48x100Mb ports + 2x1Gb ports (1Gb ports can be switched out for 1Gb SFP Fibre adapters)
Need to get some brackets for this one, not used currently but will eventually be used to mess around with VLANs
Cisco 3600 Router (WIC2T, 2x2FE2W), running the latest compatible IOS
Also just for messing around with, not got as much info on this one as I don't use it as often
Dell PowerEdge R300 (16GB DDR2 RAM, Intel Xeon X3363 CPU @ 2.83GHz, 2xSamsung 40GB SATA HDDs [temporarily, will have 2x500GB in there soon] RAID1, Windows Server 2012 R2 Standard)
This is a new machine, I just got it. Having recently started a job as an ASP.NET Framework and ASP.NET Core dev, I wanted a Windows Server machine to mess around with at home in order to get good practice with Azure DevOps, ASP.NET Web Apps and IIS. I know my C# but ASP.NET is new to me
To mine Bitcoin Rhodium you need to set up an XRC wallet and configure your miner of choice. You can choose between Web wallet, Electrum-XRC or Magnum wallet. To set up a web wallet please visit wallet.bitcoinrh.org. Or download and install Electrum-XRC wallet (recommended) for Windows, Linux and MacOS.
Any miner that supports X13 will be able to mine XRC. We have a few examples below of miners that are well tested with Bitcoin Rhodium network.
For any miner, configure the miner to point to:
(0–0.8 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3061 (0.8–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062 (3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063 (5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064 with your XRC address as username and x as password. You don’t need to open an account on pool. You will be mining to XRC address and mined coins will be transferred to your wallet • after blocks reach 10 block maturity • after you mined up minimal amount of coins (currently 0.1 XRC) • sometimes mined blocks could get rejected by network (orphaned) after they were counted as valid blocks. This is normal network behavior to follow longest chain
CCMiner is a GPU-based miner (NVIDIA) Command to run your CCMINER: ccminer-x64.exe -a x13 -o stratum+tcp://poolcore.bitcoinrh.org:3062 -O :without -D — show-diff
Settings: Url: (0–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062 (3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063 (5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064 Algo: x13User: your XRC receiving address (make sure you set 2 distinct addresses for each hashing board) Pass: x Extranonce: leave off Priority set to 0 and 1 Once pool stratum address and your wallet as user are set up you should see your miner mining against XRC pool. When miner is working the status column is green. The pool and miner are incorrectly configured now as status says “Dead” highlighted in red.
Instructions for mining XRC on BSOD pool
Pool link:bsod.pw/en/pool/dashboard/XRC/ Use this code for your miner: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig BSOD pool allows both solo and party mining.
For solo mining use code: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=solo And for party mining use: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=party.yourpassword
NOTICE: You can use us for North America and asia for Asia instead of euin your .bat file or config. You can also use BSOD pool’s monitor app forAndroidandiOS.
Instructions for mining XRC on ZERGPOOL
Zergpool offers low fees (just 0.5%) and also SOLO and PARTY mining with no extra fees. To mine XRC on Zergpool use this command lines for your miner:
Regular: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC Solo: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=solo Party: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=party
Use your coin wallet address as username in mining software. Specify c=SYMBOL as password to identify payout wallet coin, and the same coin in mc=SYMBOL to specify mining coin. For more information and support please visit http://zergpool.com Notice that when there are more pools mining XRC in different geographic/availability locations choose the nearest to you as lowest priority and then add desirable fall back pool options in different geographic locations or pools. This is useful when one pool experiences issues, to fall back to different pool in Bitcoin Rhodium network.
Calculate your Bitcoin Rhodium mining profitability
Mega FAQ (Or: Please come here for your questions first)
Qbundle Guide (Step by step setup & Bootstrap) https://burstwiki.org/wiki/QBundle 1( I want to mine or activate My account. Where do find the multiple coins? You only need 1, an outgoing transaction or reward reassignment will set the public key. Get them from: https://www.reddit.com/burstcoinmining/comments/7q8zve/initial_burstcoin_requests/ Or (Faucet list) https://faucet.burstpay.net/ (if this is empty, come back later) http://faucet.burst-coin.es Or https://forums.getburst.net/c/new-members-introductions/getting-started-initial-burstcoin-requests 2( I bought coins on Bittrex and want to move to my new wallet, but can't. Why? Bittrex will only send to accounts with a public key (not a Burst requirement) so see number 1 and either set the name on the account (IF you will not mine) or set the reward recipient to the pool. Either action will enable the account and allow for transfers from Bittrex. 3( I sent coins from Poloniex/anywhere to Bittrex and they don’t show up after a considerable time. Why? You need to set an unencrypted message on the transaction, informing Bittrex which account to send the funds to (this is in the directions on Bittrex). Did you do this? Contact Bittrex support with all the details and eventually you will get your funds. 4( How much can I make on Burst? https://explore.burst.cryptoguru.org/tool/calculate Gives you an average over time assuming a few things like: Average luck/100% uptime/no overlapping/fees on pool/good plot scan time (<20 seconds) if you do not have all of these, you may not see that number. 5( If I use SSD’s would I make more money? No, it’s 95% capacity and 5% scan time that determine success. More plot area = better deadlines = better chance of forging a block, or better rates from a pool. 6( What is ‘solo’ and ‘pool’ (wasn’t his name Chewbacca?) Solo is where you attempt to ‘forge’ (mine) a block by yourself; you get 100% of the block reward and fees. But you only receive funds if you forge, no burst for coming in second place. Pools allow a group of miners to ‘pool’ together their resources and when a miner wins, they give the pool the winnings (this is done by the reward assignment you completed earlier), it is then divided according to different percentages and methods and burst is sent out according to pool rules (minimum pay-out, time, etc.) 7( I have been mining for 2 days and my wallet doesn’t show any Burst WHY? Mining solo: it is win-or-lose, nothing in between, and wining is luck and plot size. Pool mining: because it costs 1 burst to send burst, the pools have either a time requirement (every X days) or a minimum amount (100 burst +) so you need to research your pool. Some pools allow for you to set the limit (cryptoGuru and similar) to be met before sending 8( How do I see what I have pending? On CryptoGuru, based pools, it’s the ‘Pending (burst)’ column, other pools, look for the numbers next to your burst ID. One is Paid and the other pending. 9( I’m part of a pool and I forged a block, but I didn’t recieve the total value of the block, why? A pool has 2 basic numbers that denote the pay-out method, in the format ‘XX-XX’ (i.e. 50-50) The first number is the % paid to the block forger (miner) and the second is the retained value, which is paid to historic ‘shares’ (or, past blocks that the pool didn’t win, but had a miner that was ‘close’ to winning with a good submitted deadline) Examples of pools: 0-100 (good for <40TB) 20-80 (30-80TB) 50-50 (60-200TB) 80-20 (150-250) 100-0 (solo mine, 150+ TB) Please note that there is an overlap as this is personal preference and just guidance; a higher historical share value means a smoother pay-out regime, which some people prefer. If fees are not factored in, or are the same on different pools, the pay-out value will be the same over a long enough period. 10( Is XXX model of hard drive good? Which one do you recommend? CHEAP is best. If you have 2 new hard drives, both covered by warranty, get the one with the lowest cost per TB (expressed as $/TB , calculated by dividing the cost by the number of terabytes) because plot size is KING, 11( How many drives can I have on my machine? For best performance, you can have up to 2 drives per thread (3 on a new fast AVX2 CPU). So that quad-core core-2-quad can have up to 8 drives, but a more modern i7 with 4 cores + hyper threading can squeeze 8 * 3 or 24 drives. (Performance while scanning will suffer) 12( Can I game while I mine? Some people have done so, but you cannot have the ‘maximum’ number of drives and play games generally. 13( Can I mine Burst and GPU mine other coins? Yes, if you CPU Mine Burst. 14( I’m GPU plotting Burst and GPU mining another coin, my plots are being corrupted, why? My advice is dedicating a GPU to either mining or plotting, don’t try to do both. 15( What is a ‘plot’? A plot is a file that contains Hashes, these hashes are used to mine burst. A plot is tied to an account, but they can be created (with the same account ID) on other machines and connected back to your miner(s). 16( Where can I trade/buy/sell Burst? A list of exchanges is maintained on https://www.reddit.com/burstcoin/ (on the right, ‘Exchanges’ tab) the biggest at the moment are Bittrex and Poloniex, some offer direct Fiat-to-Burst purchase (https://indacoin.com for example) 17( Do I have to store my Burst off the exchange? No, but it’s safer from hackers who target exchanges, if you cannot guarantee the safety or security of your home computer from Trojans etc, then it might be best to leave on an exchange (but enable 2FA security on your account PLEASE!) 18( What security measures can I take to keep my coin safe? When you create an account, sign out and back in to your wallet (to make sure you have copied the pass phrase correctly) and keep multiple copies of the key (at least one physically printed or written down and in a safe place, better in 2 places) do not disclose the passphrase to anyone. Finally use either a local wallet or a trusted web wallet (please research before using any web wallet) 19( How can I help Burst? Run a wallet, which will act as a node (or if you’re a programmer, contact the Dev team Bring attention to burst (without ‘shilling’ or trying to get people to buy) And help translate into your local language Be a productive member of the community and contribute experience and knowledge if you can, or help others get into Burst. 20( Will I get coins on the fork(s) and where will they be? There will be no new coin, and no new coins to be given/air dropped etc, the forks are upgrades to burst and there will not be a ‘classic’ or ‘new’ burst. 21( Will I need to move my Burst off of the exchange for the fork? No, your transactions are on the block chain, which will be used on the fork, they will be visible after the move; nothing will need to be done on your side. 22( Where can I read about the progress of Burst and news in general on the community? There is no finer place than https://www.burstcoin.ist/ 23( What are the communities for Burst and the central website? Main website: https://www.burst-coin.org/ Reddit: https://www.reddit.com/burstcoin and https://www.reddit.com/burstcoinmining/ Burstforum.net: https://www.burstforum.net/ Getburst forum: https://forums.getburst.net/ Official Facebook channel: https://m.facebook.com/groups/398967360565392 (these are the forums that are known to be supporting the current Dev Team) Other ways to talk to the community: Discord: https://discordapp.com/invite/RPhpjVv Telegram (General): https://t.me/burstcoin Telegram (Mining): https://t.me/BurstCoinMining 24( When will Burst partner up with a company? Burst is a currency, the USD does not ‘partner up’ with a company, the DEV team will not partner up and give over to special interests. 25( Why is the DEV team anonymous? They prefer anonymity, as it allows them to work without constant scrutiny and questions unless they wish to engage, plus the aim is for Burst to become a major contender, and this brings issues with security. They will work and produce results, they owe you nothing and if you cannot see the vision they provide then please do not ‘invest’ for short term gain. 26( When moon/Lambo/$100/make me rich? My crystal ball is still broken, come back to the FAQ later for answer (seriously, this is a coin to hold, if you want to day-trade, good luck to you) 27( How can I better educate myself and learn about Dymaxion? Read about the Dymaxion here: https://www.reddit.com/burstcoin/wiki/dymaxion 28( My reads are slow, why? There are many reasons for this, if your computer has a decent spec it’s likely due to USB3 hub issues, or plugging into a USB2 hub, but other reasons can be multiple plots in the same folder, but it’s best to visit the mining subreddit. They can help more than an simple FAQ https://www.reddit.com/burstcoinmining/ 29( I have a great idea for Burst (not proof of stake related)? Awesome! Please discuss with the DEV team on discord https://discordapp.com/invite/RPhpjVv (Please be aware that this is a public forum, you need to find who to ask/tell) 30( I have a great idea for Burst (Proof of stake related)? No. if you want a POS, find a POS coin. On the tangle which is being implemented a POS/POW/POC coin can be created, but BURST will always be POC mined. You are welcome to implement a proof of stake coin on this! 31( Will the Dev team burn any coins? Burst is not an ICO, so any coins will need to be bought to be burnt. You are welcome to donate, but the DEV team have no intention of burning any coins, or increasing the coin cap. 32( When will there be an IOS wallet? IOS wallet is completed; we are waiting for it to go on the app store. Apple is the delaying factor. 33( Why do overlapping plots matter? Plots are like collections of lottery tickets (and if only one ticket could win). Having 2 copies is not useful, and it means that you have less coverage of ‘all’ the possible numbers. It’s not good, avoid. 34( My local wallet used to run, I synchronised it before and now it says ‘stopped’. when I start it, it stops after a few seconds, what should I do? I suggest that you change the database type to portable MariaDB (on Qbundle, at the top, ‘Database’ select, ‘change database’) and then re-import the database from scratch (see 35) 35( Synchronising the block chain is slow and I have the patience of a goldfish. What can I do? On Qbundle , ‘Database’ select ‘Bootstrap chain’ and make sure the CryptoGuru repository is selected, then ‘start Import’ this will download and quickly stuff the local database (I suggest Portable MariaDB, see 34) (lol, loop) 36( What will the block reward be next month/will the block rewards run out in 6 months? https://www.ecomine.earth/burstblockreward/ Rewards will carry on into 2026, but transaction fees will be a bigger % by then, and so profitable mining will continue. 37( How can I get started with Burst (wallet/mining/everything) and I need it in a video https://www.youtube.com/watch?v=LJLhw37Lh_8 Watch and be enlightened. 38( Can I mine on multiple machines with the same account? Yes, if you want to pool mine this can be done (but be prepared for small issues like reported size being incorrect. Just be sure to keep question 33 in mind.) 39( Why do some of my drives take forever to plot? Most likely they are SMR drives, it’s best to plot onto another SSD and then move the finished plot/part of a plot across to the SMR drive as this is much quicker. SMR drives are fine on the read, just random writes that are terrible. So plot an SMR drive quickly, plot to a non SMR or better still SSD drive, in as big a chunk as possible (fewer files better) and move. a version of Xplotter, called Splotter, can do this easily. https://github.com/NoParamedic/SPlotter 40( I have a great idea; why not get listed on more exchanges!! Exchanges list coins because of 2 reasons:
The coin pays (often A LOT, seriously we’ve been asked for 50 BTC)
I suggest you speak with your exchange and ask ‘when will they offer Burst?’ 41( Do you have a roadmap? https://www.burst-coin.org/roadmap 42( Why is the price of Burst going up/down/sideways/looping through time? The price of burst is still quite dependent upon Bitcoin, meaning that if Bitcoin gains, the value of Burst gains, if Bitcoin drops then Burst also drops. If there is news for Burst then we will see something independent of Bitcoin moving. Variations can be because of people buying in bulk or selling in bulk. There are also ‘pump and dump’ schemes that we detest, that can cause spikes in price that have nothing to do with news or Bitcoin, just sad people taking advantage of others. 43( Where is the best place to go with my mining questions? https://www.reddit.com/burstcoinmining/ or https://t.me/BurstCoinMining 44( What hardware do you advise me to buy, is this computer good? See question 43 for specific questions on hardware, it depends on so many variables. The ‘best’ in my opinion is a 36 bay Supermicro storage server, usually they have dual 6-core CPU’s and space for 36 drives. No USB cables, plotting and mining monster, anything else, DYOR. 45( Where do you buy your hard drives? I have bought most from EBay in job lots, and some refurbished drives with short warranties. Everything else I have bought, from Amazon. 46( Can I mine on my Google drive/cloud based storage? In short: no. If you want to try, and get to maybe 1 TB and then find that your local connection isn’t fast enough, or that shortly after, your account is blocked for various reasons. Please be my guest. 47( Can I mine on my NAS? Some you can mine with the NAS (if it can run the miner, it can scan locally) but generally they’re not very fast. good for maybe 16 TB? Having a plot on a NAS and mining from another computer depends on the network speed between the NAS and scanning computer. I believe you can scan about 8 TB (maybe a bit more) and keep the scan times to within acceptable, but YMMV. 48( How can I set up a node? No need to set up a node, just set up a wallet (version 2.0.4) or Qbundle (2.2) and it will do the rest 49( Are the passphrases secured? I’ll leave the effort to a few people to show how secure a 12-word passphrase is: https://burstforum.net/topic/4766/the-canary-burst-early-warning-system Key point: brute forcing it will be around 13,537,856,339,904,134,474,012,675,034 years. 50( I logged into my account (maybe with a different burst ID) and see no balance!! I have dealt with this very issue multiple times, and there are only 3 options:
You have typed in the password incorrectly
You have copy-pasted the password incorrectly
You are trying to log into a ‘local wallet’ which the block chain has not finished updating
IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018
[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC [16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A. [16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started. [16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet? [16:03] <@Tron> Sure. [16:03] can someone volunteer to take notes and post also? [16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778 [16:04] <@Tron> It looks back 180 blocks to calculate the diff. [16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does. [16:04] I'll save a log of the whole meeting and can post it on the subreddit thread. [16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries. [16:04] great [16:05] <@Wolfsokta> We plan to release the binaries later today. [16:05] @Tron have you looked into the timestamp attack concerns of DGW? [16:05] https://github.com/zawy12/difficulty-algorithms/issues/30 [16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks. [16:06] <@Tron> Moved from 2h to 12 minutes. [16:06] nice [16:06] Oh wow okay [16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks. [16:07] why would 2h ever be acceptable? lol [16:07] 2h was originally used for daylight savings shenanigans I believe [16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time. [16:07] makes sense [16:08] what about the segmentation fault when reindexing? [16:08] any fix yet? [16:08] @Tron 12 minutes seems to be pretty small window for clock skew [16:08] I assume it was chosen due to 1/10th scaling from BTC? [16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit. [16:09] <@Tron> We did divide existing by 10. [16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet? [16:10] What block is it activating on mainnet? [16:10] <@Wolfsokta> 338778 [16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)? [16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo. [16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet. [16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo [16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain. [16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though. [16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right. [16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works. [16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked. [16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly. [16:14] Are there any issues or comments on the DGW code that should be addressed? [16:14] @devs in general [16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge. [16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right? [16:16] because of the 12 minute timestamp thing? [16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited. [16:17] nice [16:17] @russki Yeah, pretty much. [16:17] verge is a different type of situation - but overall asics and mining are a risk always [16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change? [16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added. [16:19] ooh yeah i saw those github commits [16:19] looking good [16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT [16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/ [16:20] nice [16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z [16:20] <@Tron> We'll post a FAQ on assets later today. [16:21] <@Wolfsokta> And it only is 100 Raven for a subasset [16:21] on testnetv4 it still says asset activation status: waiting [16:21] why? [16:21] <@Tron> Yep, it needs to be voted in. [16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better. [16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through. [16:21] ok nice [16:22] <@Wolfsokta> Any questions about subassets? [16:23] are they unique? [16:23] <@Tron> No [16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset. [16:23] <@Tron> Maybe I misunderstood the question. Unique with parent. [16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50? [16:23] yes [16:23] oooh ok that makes more sense [16:23] <@Wolfsokta> Exactly thanks traysi [16:24] <@Tron> And, not the same thing as "Unique Assets" [16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase. [16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT [16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them? [16:25] <@Tron> Yes [16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere? [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:25] satoshi corbie @russkidooski [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:26] <@Tron> Sub-assets are identical to assets after creation. [16:26] <@Tron> Just cheaper to create, and in your "owned" namespace. [16:26] Okay cool [16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1 [16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly. [16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue [16:26] How much is it going to be for a sub-asset? [16:27] 100 [16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under. [16:28] do you know what the issue was? [16:28] <@Wolfsokta> It seems to be a build problem with the boost library. [16:28] Still looking into though. :) [16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3 [16:29] yea i get the same issue on windows 10 [16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB [16:30] static compiled on ubuntu 18.04 [16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test. [16:30] @Trap we will look into that also [16:30] no problem, im just curious lol [16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue. [16:32] <@Tron> We're dropping Windows support ;) [16:32] lol [16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it. [16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue. [16:34] what did you guys do to fix the linux version? [16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement [16:34] The issue has been fixed on Linux and Mac though? [16:34] (oops sorry already answered) [16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found. [16:34] Built the binairies on a Ubuntu 16.04 box. [16:34] that was it? [16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue. [16:35] is there a boost 1.58 repo on 18.04? [16:35] 18.04 used 1.65*** [16:36] I've built with boost 1.68 on arch Linux [16:36] It worked [16:37] wallet 2.0.x? [16:37] @Trap, the issue is when -reindex is used. [16:37] Oh sorry my bad [16:37] Wallet 2.0.3 [16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208 [16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04 [16:39] Any other questions pertaining to the segfault? [16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting. [16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join [16:42] Yea. It is very hard to read this back. [16:42] Also no message history [16:42] If you disconnect and reconnect [16:42] <@Tron> I'll throw in a vote for Discord. [16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad. [16:43] Some of us used a VPN before we connected to IRC [16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A [16:43] https://www.strawpoll.me/16247952 [16:43] poll [16:43] Make a discord when only mods can submit links [16:43] Where* [16:45] Discord won the poll 5 to 2 [16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings. [16:45] we know [16:46] <@Wolfsokta> We also want any developer to be able to speak. [16:48] <@Wolfsokta> We're open to try Discord next week. [16:48] <[kai]> perhaps you could even get a feed from this irc to discord? [16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here. [16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working? [16:50] <[kai]> https://github.com/reactiflux/discord-irc [16:50] <[kai]> im sure you could make this a one way deal. [16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord. [16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week. [16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins. [16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield? [16:54] <[kai]> DGW solution seems solid. [16:55] <[kai]> was just curious if it was one of the four solutions you looked at. [16:55] <@Wolfsokta> Tron is answering... Any others Q? [16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA. [16:55] <[kai]> right on. [16:56] <[kai]> cheers guys, see you next time. [16:56] OPen the gates for the last 4 minutes for any other questions? [16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request. [16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community. [16:59] ^ 6:59] You devs are pretty cool [16:59] did the burn get discussed? [16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice. [17:00] <@Tron> Thanks everyone!
X399 Multipurpose Server, virtualized FreeNAS with passthrough sata controllers and some other guests?
I just picked up 8x8TB WD Red 256MB from the 8TB EasyStore deals on Black Friday. I currently have a ZFS mirror running on a QNAP 251 running Nas4Free, 2x6TB at about 5TB used. I primarily use it just as backup/archival, so usually few writes and only slightly more reads. With the new 8x8TB, I was thinking of doing 4 vdevs of mirrors for a total of 32TB pool. I was thinking of making a multipurpose server. Something with the rough following hardware: 1950X Threadripper X399 Mobo with x8 SATA (Gigabyte Aorus gaming 7 or MSI Carbon Pro AC, Asrock X399 Taichi) ECC would be great, but is seems to be pretty hard to get lately 64 or 128GB, my current rig doesn’t have ECC and it’s been rolling fine for 4 years. 500GB-1TB SSD maybe some cards to mine with 4x1070s A lot of this seems contingent on IOMMU groups so you can achieve this set up. Ideally I’d have an Ubuntu host that would run some VM framework and the bare essentials, keep it updated and pretty much nothing else, this is meant to the be crash proof layer. Next, I’d run a guest with the sata controllers passed through so it could run ZFS natively on the disks. Give it 2 cores and 16-32GB of ram. Just running some SMB shares so I can access the data from other guests. This would essentially run all the time. The following guests I’m more flexible about running simultaneously it would be great if I could run them at the same time, but if I can’t not a huge deal. a. Windows General Productivity (When in use allocate high QoS) (possibly one pass through GPU for CAD/compute acceleration) b. Windows/Linux bitcoin/AltCoin Mining (passthrough GPUs) (allocate resources here when idle) c. macOS general productivity (When in use allocate high QoS) (possibly one pass through GPU for CAD/compute acceleration) d. Linux general production (When in use allocate high QoS) (possibly one pass through GPU for CAD/compute acceleration) My dream system works like this: a. Press Power Button (Host boots and auto loads FreeNAS guest, then loads macOS guest and Bitcoin guest). b. If I start using macOS it gets preferred resource allocation, if I don't the bitcoin guest ramps up. This gets back to the IOMMU stuff where I get fuzzy. Would any of X399 boards support a setup like this? Is this even a good idea? If it is a stupid idea, what is a better way? TLDR: Is 4vdevs of 2 drive ZFS mirrors for the 8x8TB WD Reds safe enough? Should I consider a different configuration? Can any X399 boards support IOMMU passthrough of the sata controllers to virtualize a FreeNAS guest and similarly passthrough several gpus to a mining guest?
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.
Bitcoin mining rigs and systems have come a long way since the beginning. The first Bitcoin miners made do with the tools they had at their disposal and set up various software to control the mining hardware in their rigs. While these make-shift solutions were better than nothing, they didn’t exactly work efficiently. Not only did that slow down the mining process, but it also made it ... CGMiner is a Bitcoin mining tool written with the C programming language. It is designed to run on ASIC mining devices, works on both Windows and Linux, and is ideal for advanced cryptocurrency users. The CGMiner application is command-line based, and users interact with it via a command-line interface. It can mine for Bitcoin using multiple methods (GPU and CPUs) and does it quite efficiently ... In this article, I will talk about what Bitcoin is, what a Bitcoin wallet is, how to install Bitcoin core on Ubuntu and how to use it. Let’s get started. About Bitcoin. Bitcoin is a crypto-currency. You can also call it a virtual currency as well. It was created by Satoshi Nakamoto. The advantage of bitcoin is that you don’t need to rely on ... Step-by-Step Setup AMD Radeon Vega 56 / Vega 64 (Configure) Phoenix Miner – miner for Ethash algorithm (v5.0b) Polaris BIOS Editor 1.6.7 (Elpida, micron, samsung, hynix) Download and configure; XMR-Stak v2.5.1 cryptonight V8 download and configure; OhGodAnETHlargementPill – Tablet for mining on GTX 1080 GTX 1080 Ti [DOWNLOAD] Tags Mac OS X comes with its firewall disabled by default, but if you have enabled it, see the section Allowing Specific Applications from the official Apple guide. Ubuntu also comes with its firewall disabled by default, but if you have enabled it, see the Ubuntu wiki page for information about adding port forwarding rules.
How To Mine Bitcoin On PC, Mac, Or Linux - Duration: 21:41. ... How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS - Duration: 11:33. Cát Dự Trần 48,737 views. 11:33 ... Sign up here: https://honeyminer.com/referred/5adm5 In this video we show you how to mine bitcoin on a Mac. This process is using a just released app called ... In this episode of Crypto Miner Tips, we go over how to get started Bitcoin Mining with a PC. However, the mining software mentioned in this tutorial can be ... Today I'll show you how to how to get started mining Bitcoin and other cryptos super fast using MinerGate. It couldn't be easier! I'll be using MinerGate, an all-in-one tool for PC, Mac, and Linux ... In this video, I'm going to show you how to start mining Bitcoin on Linux/Debian based operating systems. https://bitcoinminingsoftware2019.com/bitcoin-minin...