5 Steps to Install Bitcoin-Qt Faster - Bitcoin-en.com
5 Steps to Install Bitcoin-Qt Faster - Bitcoin-en.com
Blockchain Explorer - Search the Blockchain | BTC | ETH | BCH
QT-Data Inc.
Blockchain Explorer - Search the Blockchain | BTC | ETH | BCH
Bitcoin-Qt wallet. All about cryptocurrency - BitcoinWiki
GAIAcoin
GAIA coin is an alternative cryptocurrency based on Bitcoin. GAIA coin offers the security and reliability of the blockchain with an Extensible, Skinnable, Modular platform design. Wallet users can buy and sell items inside the built-in store instantly with Gaia currency. [url=http://www.gaiaplatform.com]read more[/url]
Reddcoin (RDD) Core Wallet Release - v3.10.0rc4 Core Staking (PoSV v2) Wallet including MacOS Catalina and more!
https://github.com/reddcoin-project/reddcoin/releases/tag/v3.10.0rc4 Reddcoin (RDD) Core Dev team releases v3.10.0rc4 Core Wallet. Includes full MacOS Catalina support, Bitcoin 0.10 codebase features, security and other enhancements. Full changelog available on github, complete release notes to be published with full 3.10.0 release anticipated shortly. NOTE: This v3.10.0rc4 code is pre-release, but may be used on mainnet for normal operations. This final "release candidate" version addresses an issue identified where the individual posv v2 stake transaction could be modified such that no funds went to the developer. - See Issue #155 for description. Also includes additional components of enhanced build system; Travis continuous integration (CI) and Transifex translations. Prerelease v3.10.0rc4 binary code is not certificate signed. To assist in translations, correct text, or add languages, please join the following team: https://www.transifex.com/reddcoin/reddcoin/qt-translation-v310/ To assist in other aspects of the Reddcoin project, please contact TechAdept or any member of the team. Bootstrap (zipped folder of blockchain, date of upload 5-1-20) may be downloaded here if required: https://drive.google.com/file/d/1ItVFGiDyIH5SfCNhfrj29Qavg8LWmfZy/view?usp=sharing Commits included since rc3: 2a8c7e6 Preparations for 3.10.0 rc4 4a6f398 Update translations 7aa5151 build: update reference time to something more recent 1a65b8c Update translations d4a1ca6 transifex: update translation instructions a03895b transifex: update config for this release 51ad1e0 move check before supermajority reached 794680f Make check for developer address when receiving block 457503e travis: Remove group: legacy 97d3a2a travis: Remove depreciated sudo flag 21dcfa6 docs: update release notes 7631aac update error messages 5b41e31 check that the outputs of the stake are correct. 9bd1820 travis: test with wallet enabled 55f2dd5 fix reference to Reddcoin 220f404 travis: disable libs for windows builds (temp) b044e0f depends: qt update download source path 2fe2d85 depends: set new download source 4cf531e remove duplicated entry 0d8d0da travis: diable tests e13ad81 travis: manually disable sse2 support for ARM processors 1f62045 travis: fix crash due to missing (and not required) package 0fb3b75 travis: update path 9d6a642 docs: update travis build status badge with correct path https://github.com/reddcoin-project/reddcoin/releases/tag/v3.10.0rc4
Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020 Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1 This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads. It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely. Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2. Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md This is a new major version release of Reddcoin. Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base. With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support. Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks. Please report bugs using the issue tracker at github: https://github.com/reddcoin-project/reddcoin/issues How to Upgrade If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux). Start wallet. All done!
Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements
To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log Blockchain Download: Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files 3.0.1 changelog *83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version Credits Thanks to everyone who contributed to coding, testing and feedback for this release, notably:
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.
Features
Groestlcoin Mainnet & Testnet supported
Bech32 support
Multiple wallet support
Electrum - Support for both random and custom peers
Encrypted storage
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
RBF functionality
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
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.
Features
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.
Features
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).
Features
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).
Features
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.
Features
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
Remastered Improvements
Bech32 support
P2sh support
Fixed Import/Export to wallet.dat
Testnet Support
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.
Features
Selection options for 3-24 words (simply putting the space separated words in the first word box will also work) along with a bip39 passphrase
User input for total number of addresses desired
Creation of P2PKH, P2SH, P2WPKH and P2WSH addresses along with xpriv and xpub as per BIP32 spec, using a word list as the starting point following the BIP39 standard.
Pre-sets for BIP44, BIP49, BIP84 and BIP141 standards, along with custom user input for derivation path
Option for Hardened or non-hardened addresses
Option for Testnet private and public keys
Output containing derivation path, private key in WIF, integer and hex format, public key address, public point on curve and scriptpubkey
Results are output in a file titled 'wallet.txt' with the time addresses were generated, along with all information presented onscreen
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.
Features
Use your own node
Tor support
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
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.
Changes
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.
The reason for the update My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:
Use an OS that was lighter
Update the Reddcoin Core software (2.0.0.0 => 2.0.1.2)
Make improvements to the configuration.
The updates
OS: using Lubuntu instead of Ubuntu MATE. Lubuntu uses less resources (130 MB RAM vs. 190 MB RAM on initial boot).
Reddcoin Core: v2.0.1.2-a8767ba-beta instead of v2.0.0.0-92768f9-beta.
Swap: using a swap partiton instead of a swap file. Also adjusting the swap size: from 1 GB to 2 GB, after reading the comments to my previous tutorial.
All data to USB: Blockchain data and the swap are now stored on the USB drive, instead of the SD card.
Private keys: added instructions on how to backup the private keys of your Reddcoin addresses!
If you would like to tip me Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
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: v2.0.1.2-a8767ba-beta (most recent version at this moment). ↳ Screenshot
Steps
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/.
Run Etcher.
Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.
Select drive: select your microSD card.
Flash.
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
In GParted, switch from your SD card (default) to your USB drive. ↳ Screenshot ↳ Screenshot
You will now see the all the partition on USB drive. Delete every partition (right mouse click). If you can't select Delete, do an Unmount first. ↳ Screenshot ↳ Screenshot
After deleting all partition, you will only see 'unallocated' space on your USB drive. ↳ Screenshot
Create the first partition: the swap partition. Right click on the blank space, select New and enter the following:
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.)
You've enabled the swap partition. Switch back to Htop and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot
To make sure the swap file is persistent (so it survives a reboot), you have to add a line to the /etc/fstab file.
In LXTerminal, enter the following command to open the file in Leafpad (text editor): sudo leafpad /etc/fstab ↳ Screenshot
In Leafpad, add this text in a new line: /dev/sda1 swap swap defaults 0 0 ↳ Screenshot (I've added spaces to vertically align the text.)
Save and close the file.
Reboot your Pi.
To see if the swap partition is in use after a reboot, open Htop ([Menu] > System Tools > htop) and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot
So, the swap partition is enabled and in use, and the data partition is prepared. We now can install the necessary software for the Reddcoin wallet; enter the following commands into LXTerminal:
After the reboot, open LXTerminal again. Download, unpack, configure, build and install Berkeley DB.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.) ↳ Screenshot
Download the source of the Reddcoin wallet and build it.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)
Speed up synchronizing with the Reddcoin blockchain by bootstrapping.
Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)
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.
Your wallet will be encrypted, and the Reddcoin Core client will be closed. Launch the Reddcore Client again. sudo /media/usb/reddcoin/src/qt/reddcoin-qt
To start stake, you need to unlock your wallet (by entering your password).
[01:11] Reddcoin Core started (sudo password entered).
[01:13] Message shown on screen: Loading block index...
[10:14] Message shown on screen: Verifying blocks...
[10:18] Message shown on screen: Loading wallet...
[12:49] Message shown on screen: Done loading
[13:13] Reddcoin Core ready to use.
Extra
Backup Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
Method 1: Backup your wallet.dat. Open Reddcoin Core. Use the menu to backup: File > Backup Wallet... ↳ Screenshot
Method 2: Backup your private keys. In case you lose your wallet.dat backup, you still can import your private keys later when needed.
To extract your private keys:
If you have a passphrase on your wallet, unlock your wallet first. Settings -> Unlock Wallet... (make sure 'For staking only' is not checked) ↳ Screenshot ↳ Screenshot
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.
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
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
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
In LXTerminal, enter: sudo apt install chromium-browser ↳ Screenshot
You can run Chromium via [Menu] > Internet -> Chromium Web Browser ↳ Screenshot
Updates / Upgrades If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.
Open LXTerminal and enter this command to update: sudo apt update && sudo apt upgrade ↳ Screenshot
Credits:
cryptoBUZE on reddit.com; for getting the official arm_support_v2.zip to work.
worstkaas on reddit.com; for his suggestion of using 2 GB instead of 1 GB for the swap space.
Credits in previous tutorial:
My main source: damsal01 on reddcointalk.org. His RDD address for donation: Rqd8xDv6oV9BYFaVrLdkWcR5JU6sPPZTKs.
hieplenet on reddit.com. His RDD address for donation: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY.
joroob on Github.com. He made some adjustments to the reddcoin wallet source code so it will compile on ARM cpus. His RDD address for donation: Rb8754QZvpbw6DjrMV1qX9SnHzYnSyXRMC.
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.
Overview
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:
cd
git clone https://github.com/joroob/reddcoin
cd reddcoin
sudo ./autogen.sh
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/v2.0.0.0/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
Extra
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.
To auto run on startup, add RealVNC to Startup Applications: [Menu] System > Control Centre > Personal > Startup Applications. ↳ Screenshot
In Startup Applications Preferences, click on Add to a new entry.
Give it a 'name' and 'comment' (optional) as you like, and put this in 'command': vncserver-x11 ↳ Screenshot
Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.
Credits:
My main source: damsal01 on reddcointalk.org. His RDD address for donation: Rqd8xDv6oV9BYFaVrLdkWcR5JU6sPPZTKs.
hieplenet on reddit.com. His RDD address for donation: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY.
joroob on Github.com. He made some adjustments to the reddcoin wallet source code so it will compile on ARM cpus. His RDD address for donation: Rb8754QZvpbw6DjrMV1qX9SnHzYnSyXRMC.
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.
The Clients:
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.
Probably not, if truth be told. Go read these two ELI5’s if you haven’t already. They contain critical information to help you decide. I’ll wait till you get back. ;)
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)!
I posted this under /cryptocurrency and /cryptomarkets as well! Might be less useful under this subreddit... but I'm using it for purposes of helping people become aware of this coin. Summation of RaiBlocks lead developer AMA. I'm very excited about this coin, and if you're asking why I did this...I'm trying out my AMA consolidating script that I wrote for fun :) I'm interested in seeing what people think about this coin! You can read the responses directly from this link: https://www.reddit.com/RaiBlocks/comments/7ko5l7/colin_lemahieu_founder_and_lead_developer_of/ What are your top priorities atm? Both in developing areas itself and in terms of integration?
The top priorities right now are:
Wallets desktop/mobile and ease-of-use improvements to the node
Integration with exchanges
Vendor adoption wider user adoption
These basically need to happen in a sequence because each item isn't useful unless the previous one is complete.
Do you have any plans to have your source code peer reviewed? By peer review I mean sending your source code down to MIT for testing and review. Where do you see Raiblocks 5-10 years from now? (For instance do you envision people using a Raiblocks mobile phone app to transfer value between each other, or buy stuff at the store?
We definitely need peer and code reviews and we're open to anyone doing this. We have ideas for people in universities that want to analyze the whitepaper or code so we'll see what comes of that. In my opinion code security guarantees can only be given with (eyes * time) and we need both. I'd like to see RaiBlocks adopted as an internet RFC and basically become an ubiquitous background technology like http. I think you're probably right and a mobile app would be the most user-friendly way to do this so people don't need to carry around extra cards in their wallet etc.
Is there a list of the team readily available? Are there firm plans to expand, and if so, in which directions? The roadmap indicated a website redesign scheduled for November 2017. Is there an update?
We have about 12 people in the core team; about half are code and half are business developers. On the redesigned website we're going to include bios for sure, no one in our team is anonymous. I think we have pretty good coverage of what we need right now, we could always use more people capable of contributing to the core code. The website design is well underway, we wanted to streamline and add some more things to it so it took longer than originally estimated. It'll looking like after the new year we'll have it ready.
Would you ever consider renaming the coin to simply "Rai" or any other simplified form other than RaiBlocks? 2. What marketing strategy do you think will push XRB forward from now on as a fully working product. Instant and free, the green coin, "it just works" coin, etc? 3. Regarding security, is "quantum-proofing" a big concern at the moment and how do you guys plan to approach this when the time comes. And how possible would it be for bad actors to successfully implement a 51% attack.
Yea there are a few difficulties people have pointed out with our name. People don't know if it's "ray" or "rye". "Blocks" doesn't have a meaning to a lot of people and the name reference might be too esoteric to be meaningful. I'm not prideful so I'm not stuck on a particular name, we'll take a look at what our marketing and business developers say peoples' impressions are and if they have any naming recommendations.
Our marketing strategy is to focus on complete simplicity. Instant and free resonates with enthusiasts and mass adoption will only come when using xrb is absolutely the same experience as using a banking or other payment app. People aren't going to tolerate jargon or confusing workflows when sending or receiving payments.
Quantum computing is going to be an amazing leap for humanity but it's also going to cause a lot of flux in cryptography. The plan I see is the similar to what I did in selecting the cryptographic algorithms we're using right now: look for leaders in academia and industry that have proven implementations and use those as they recommend migration based on computing capability. Quantum vulnerabilities can be an issue in the future but a vulnerable implementation would be an issue right now.
Hi Colin, lately XRB has been getting frequently compared to and contrasted with Iota. I was hoping that you could give us your thoughts on the differences between the two and what your general vision for the future of Raiblocks is.
It's flattering to be compared to IOTA, they have a very talented team building ambitious technology. When looking at design goals I think one thing we're not attempting to approach is transferring a data payload, we're only looking to be a transfer of value. There are lots of ideas and technology to be developed in the cryptocurrency space and I want RaiBlocks to solve one section of that industry: the transfer of value. I think the best success would be if RaiBlocks was adopted as the global standard for this and crypto efforts could move to non-value-transfer use-cases.
Do you see XRB becoming the new payment method for commerce. As in, buying coffee, groceries, etc? Do you have plans for combating the HODL mentality so this currency can actually be used in the future of buying and selling?
Being a direct transactional payment method is our goal and we're trying to build software that's accessible to everyone to make that happen. I see holding as a speculative tactic anticipating future increases and you're right, it's not in line with day-to-day transactions. I think as market cap levels off to a more consistent value the reason for holding and speculating goes away and people can instead focus on using it as a value exchange.
Are you planning to expand the RaiBlocks team over the next 12 months? If so, what types of positions are you hoping to fill?
Right now we have about 12 people, half core and half business developers. I think this count is good for working on what we're doing right now which is getting wallets and exchanges worked on. Ideally people outside our team will start developing technology around xrb taking advantage of the network effect to build more technology faster than we could internally. That being said we're going to look in a few months to see if there's anything out there people aren't developing that should be and we'll see what people we need to make it happen.
At what point did you make the decision to make RaiBlocks your full time job? What was the decision making process like?
It was after the week where the core team met here in Austin to brainstorm our next steps. I saw how much enthusiasm there was from crypto-veterans with having a working system capable of being scaled up to what's needed for massive adoption and it seemed the risk needed to be taken. It was hard decision to make, working in the crypto and finance is rough and I like using my leisure time to work on inventions. Of all the projects ideas I have this one seemed to have a high chance of success and the benefits of having a working, decentralized currency would be huge.
Hi Colin, what prevents great cryptos like XRB from being listed on bigger exchanges?
It's good to understand where the biggest headaches for exchanges lie: support tickets, operations, and development. If a technology is different from what they already have, that takes development time. If the software is new and not widely run, that's potential operations time to fix it which results in support tickets and community backlash. Adding BitCoin clones or Ethereum ICO coins is easy because they don't have these associated risks or costs.
What can the average RaiBlocks-Fan do to help XRB getting adopted / growing / expanding?
I think the best thing an average fan could do is word of mouth and telling people about RaiBlocks. More people being aware of it means there's the possibility someone who's never heard of it before would be interested in contributing as a vendor, developer, exchange etc. Good advertising or marketing will never be able to reach everyone as well as someone reaching out within their own network.
Are you looking at incorperating a datamarket like iota in the future? Given the speed of the network a data exchange for highly accurate sensors could be a game changer. Further more, are there any plans to increase the Dev team in the future? I read on the FAQ you'd like RaiBlocks to be somewhat of a protocol which is a huge ambition. A Dev from say the Mozilla foundation or other could further cement this ambitious project.
Transmitting data payloads is something we probably won't pursue. The concern is adding more features like this could cause us to make decisions that compromise the primary focus points of low-cost and speed for transferring value. We can add people to the dev team though I think we'll get the most traction by teaching teams in these other organization how to use RaiBlocks so they can be the experts on the subject in their companies.
If a node wants to independently know the balances of all accounts in the system, it must at a minimum have storage to hold accounts and all their balances. In order to know all balances it must either listen to transactions as they're happening or bootstrap from someone else to catch up as what happens on startup.
There is no incentive to run nodes. Some people will do it because it is cheap as fuck (as I read an raspberry pie can run it). But I think not many people will do it. 1. How important are the nodes in terms of further scaling? 2. On which network conditions where the 7000 transactions met? 3. What happens if the transactions per day tenfolds but the nodes don't? 4. How much better will Rai scale if someone sets up, lets say, 100 nodes with awesome hardware and network? 5. How many nodes could be enough for visa level scaling? 6. Which further improvements can be made for Rai IF there needs to be other improvements than setting up new nodes? Are there other concepts like 2nd layer solutions planned? 7. How will Rai defend network attacks? I know there is an PoW part. But since there a also large attacks on high cap coins on which people invest millions of $ to congest a network..Is it possible that the Rai network will be unusable for several days because of this?
I think the out-of-protocol incentives to running a node are under-referenced yet I see them as the primary driving factor for participating as a whole. Node rewards come at the expense of other network participants and in this closed loop the incentives aren't enough to keep a cryptocurrency alive. Long-term there needs to be a system-level comparative advantage to what people are already using for a transfer of value. If someone is using xrb and it saves them hundreds or thousands of dollars per month in fees and customer irritation in delayed payments, they have a direct monetary incentive to using xrb and a monetary incentive in the health of the system. 1) More nodes provides transaction and bootstrapping redundancy. More representatives provides decentralization. 2) The 7k TPS was a profile how fast commodity hardware could eat transactions. All of the real-world limits are going to be something hardware related, either bandwidth, IO, or CPU. 3) The scaling is more related to the hardware the nodes are using rather than the node count. If there was 10x increase in transactions it would use 10x the bandwidth and IO as nodes observe transactions happening. 4) If someone made 100 representative nodes the network would be far more decentralized though the tx throughput would be unchanged since that's a per-node requirement. 5) Scaling to Visa will have high bandwidth and IO requirements on representatives associated with doing 10k IOPS. Datacenter and business class hardware will have to be enough to handle the load. 6) Second layer solutions are always an option and I think a lot of people will use them for fraud protection and insurance. Our primary focus is to make the 1st layer as efficient and high speed as possible so a 2nd layer isn't needed for daily transactions. 7) Defending against network attacks will be an ongoing thing, people like breaking the network for lulz or monetary gain i.e. competing cryptos. If there are attacks we haven't defended against or considered it'll be a matter of getting capable people to fix issues.
Are you open to changes to the name? (Rai) What are your plans with regards to marketing?
I'm open to it, people get confused on ray/rye pronunciation, not the greatest first impression. As far as timing I think marketing works best after a more user friendly wallet and integration in to more exchanges otherwise we're sending traffic to something people can't use. We're going to start by focusing on the initial adopters which will likely be enthusiasts and going forward work on the next set of users that aren't enthusiasts but want to drive savings for their business through lower payment processing costs.
I think he's definitely right, a lot of the TPS numbers are synthetic benchmarks usually on one system. The biggest thing hindering TPS are protocol-specific limits like hard caps or high contention design. The next biggest thing will be bandwidth and then disk IO. Some of these limits can be improved by profiling and fixing code instead of actual limits in the hardware. We want to get better, real world numbers but our general opinion is that the RaiBlocks protocol is going to be limited by hardware, rather than design.
Are you planning to add a fiat gateway to the main website and mobile wallet?
If we can make it happen for sure, that seems like a very user-focused feature people would want. The difficulty at least in the US is the money-transmitter licenses which are hard to obtain. More than likely if this functionality was added it'd be a partnership with an established financial company that has procedures in place to operate within countries' regulations.
I saw a post on /iota that claims that their quantum resistance is a main benefit over raiblocks. Can you go into detail about this? explain any plans you have to let XRB persevere through upcoming quatum revolution?
I think everyone with cryptography in their programs is keeping an eye on quantum cryptography because we're all in the same boat. I don't have cryptanalysis credentials so I didn't feel comfortable building an implementation and instead chose to use one off-the-shelf from someone with assuring credentials. There are some big companies that have made small mistakes that blow up the usefulness of the entire algorithm, it's incredibly easy to do. https://arstechnica.com/gaming/2010/12/ps3-hacked-through-poor-implementation-of-cryptography/
Hello Colin, is any security audit to the source code planned?
We don't have one contracted though both internally and externally this is an important thing people want completed.
Do you have plans to radically change the interface of the desktop wallet, and to develop a universal, cross-platform, clean and simple UX design for the wallet? This will be huge for mass adoption in my humble opinion
I completely agree, we do plan on completely redoing the desktop wallet, both from a UX standpoint and maintainability so UI code doesn't need to be in C++. This could also remove out dependency on QT which is the least permissive license in the code right now. I write code better than I design GUIs ;)
It seems like Raiblocks is aiming to be a true currency with it's lacking of transaction fees and fast confirmation times, which is great! If Raiblocks can add some kind of support for privacy then I think it got the whole picture figured out in terms of being "digital cash". Do you currently have any plans to implement privacy features into RaiBlocks? If Raiblocks is unable to do this, it will still be a straight improvement over things like LTC which are currently being used as currency, but I don't think it will be able to become THE cryptocurrency without privacy features.
I love the concept of privacy in the network and it's a hard thing to do right. Any solution used would need to be compatible with our balance-weighted-voting method which means at least we'd have to know how much weight a representative has even if we're hiding actual account balances. To be fully anonymous it would have to be hide accounts, amounts, endpoints, and also timing information; with advanced network analysis the timing is the hardest thing to hide. Hopefully some day we can figure out an efficient privacy solution though the immediate problem we can solve is making a transactional cryptocurrency so we're focusing on that.
Could you provide an analysis on the flaws of RaiBlocks? Is it in any way, shape, or form at a disadvantage compared to a blockchain based ledger like bitcoin? There has to be drawbacks, but I haven’t found any. Do you plan on expanding the dev team and establishing a foundation? Also, how much money is in the development pool?
One drawback is to handle is our chain-per-account model and asynchronous updates it takes more code and design. This means instead of one top-block hash for everything there's one for each account. This gives us the power of wait-free asynchronous transactions at the cost of simplicity. After we finish up things like the wallet, website, and exchange integration we'll be looking at seeing what dev resources we need to build tech if no one else is already working on a particular thing. We have about 6 million XRB right now so we've made the existing dev funds go a long way. If something expensive to build came along and dev funds wouldn't cut it we could look at some sort of external funding.
How big of a problem is PoW for exchanges and what are potential solutions?
Considering how much exchanges stand to make through commission I don't see the cost as a barrier, it's just an abnormal technology request compared to other cryptocurrencies. We're working on providing a service exchanges can use in the interim until they set up their own infrastructure to generate the work. Other options are containers people can use on cloud services to get the infrastructure they need until they want to invest in their own.
It's my understanding that since everything works asynchronously, in the case of double spending there is a chance a merchant would receive the block that would be later invalidated and have it shown in it's wallet, even if a little later (1 minute?) the amount would correct when the delegates vote that block invalid. Is there any mechanism to avoid this? Maybe tag the transactions in the wallet as "confirming" and then "confirmed" after that minute? Is there actually any certain way for a wallet to know, in a deterministic/programable way, at what moment a transaction is 100% legit? (for example if the delegates are DoS'ed I guess that minute could be much longer). I know this is an improbable case, but still...
Yea you're hitting a good point, the consensus algorithm in the node is designed to wait for the incoming transaction to settle before accepting it in to the local chain for the exact reason you listed, if their transaction were to be rolled back the local account would be rolled back as well. We can trend the current weight of all representatives that are online and voting and make sure we have >50% of the vote weight accounted for before considering it settled.
Hey Colin, will you eventually have support for a Trezor or other hard wallet?
Yea we'll definitely work with companies like Trezor that are interested in being a hardware wallet for xrb. It's just a matter of making sure they support the signing algorithms and integrating with their API.
EDIT: I'm getting a lot of messages asking me how to buy XRB. I used this guide which was very helpful: https://www.reddit.com/RaiBlocks/comments/7i0co0/the_definitive_guide_to_buying_and_storing/ In short -- buy BTC on coinbase, open up an account on bitgrail, transfer that BTC from coinbase to bitgrail, then trade your BTC for XRB. It's a pain right now because it's such a new coin, but soon it will be listed on more exchanges, and hopefully on things like shapeshift/changelly. After that it will be much easier... but until then, the inconvenience is what we have to pay in order to get into XRB while its still early. EDIT: BAD SCRIPT, BAD!
[For Hire] Senior developer for crypocurrencies, blockchain, mobile/ desktop/web application, using C++, Python, Java, JavaScript, PHP, MySQL, and Perl
I can do
Cryptocurrency and blockchain related technologies. I understand Bitcoin, P2P, blockchain and transaction very well.
Develop applications, utility tools, and games for desktop (Windows, Linux) and mobile.
Web front and back end using HTML5, PHP, Laravel, MySQL, JavaScript, jQuery, Bootstrap.
My portfolio
I created eventpp library. It's a C++ library for event dispatcher and callback list.
I created cpgf library. It's a very complicated open source cross platform C++ library that adds reflection, serialization and script binding to standard C++.
I created Gincu library. It's an open source 2D cross platform game engine written in C++ and cpgf.
I created Jincu library. It's an open source 2D game engine and framework written in JavaScript ES6.
Very experienced. I've been developing software and game for about 18 years, and I began learning C++ since 1995.
Pursuit very high quality product and code, from the coding style to architecture. You may check my open source projects to see the quality.
I'm honest and responsible.
Communication methods I prefer to I prefer communicating via Skype, IRC, Discord(texting), or other IM tools, or email. I can speak English but it should be much less effective because my speaking English is far less good than my writing. Payment method Paypal is preferred. For long term cooperation let's discuss on the payment method. I also accept payment in Bitcoin(BTC). Check with me if you are going to pay in other cryptocurrencies. For fixed price project, I prefer 3-4-3 payments. 30% upfront, 40% after first delivery, 30% final. Negotiable. Hours I can work Depending on the project, I can work about 10~20 hours each week. Where am I I work remotely. I live in Beijing, China, GMT+8. My fee and rate I can charge by fixed fee per project/component, or by hourly. My general fee is far lower than a senior developer with my experience level in the US Bay Area, but also don't expect my fee is as low as a middle level developer from other low end freelancer sites. The fee varies depending on the project type and the technology, and negotiable. You get more than what you pay for If you are looking for high quality development and don't want to waste your time and money, contact me, you will get very good result for your money.
We have a constant stream of people coming back after abandoning Dogecoin and the sub in 2014 when the price fell. These people all have old versions of QT and are now basically trying to recover their coins, presumably to cash out and abandon us again. This is causing strain for the network, as far more people are trying to leech blocks than seed them. The thing is, none of this is necessary. Especially if you're just going to dump coins. With resources such as https://coinb.in/#settings all you need are your private keys, and you can create, sign and broadcast transactions yourself. No client required, let alone one as resource-hungry as QT.
"So, how do I get my keys?"
First of all, lets talk about data management. The overwhelming majority of coins are not lost through theft, especially direct theft of wallets (as distinct from wholesale thefts/scams/implosions like Moolah, GAW, MtGox, Cryptsy, and even our own beloved Dogetipbot). Most coins are lost because people forget about their wallets and do silly things like reformat hard drives, lose passwords and so on. So, everyone should have a wallet list. Here is a sample bit of HTML that gives you a page with two columns of wallets, one for local wallets you would withdraw coins to, the other the third-party wallets you would deposit coins to third parties through (do note that many services use temporary addresses generated for deposits which expire after 24h or so). A page like this is how I manage my 100+ wallets, and I have copies on my network and hidden online. Such a page makes it easy to at least keep track of all your wallets, for a trivial amount of work to set up.
"OK, great, so now I have a list of my wallets. Now what?"
Now you're going to need the private keys for each of those wallets. Obviously you're not going to store these in a public place though. So you will need a separate file, which can just be plain text. Copy each of those addresses into it. Now go ahead and fire up QT. If you haven't synced it in 3 years, its going to take forever, but that doesn't matter. You don't actually need the blockchain for this, so you don't have to wait for it to catch up. Open up the console which is in the Help menu. Then give the command dumpprivkey with the wallet address you want the key to. Then use the up-arrow key to bring that command back, replace the address with the next one, and keep going until you have them all. It will look something like this:
13:05:18 Welcome to the Dogecoin RPC console. Use up and down arrows to navigate history, and Ctrl-L to clear screen. Type help for an overview of available commands. 13:11:06 dumpprivkey D9xDcRthB6XP4vRGqiyKdDfVJ7CWhYuBBi 13:11:06 6KEcssuq1wWUrFVmMF8yDxHuAdQMiRezz53zDxADLmyoXnix7iM 13:12:00 dumpprivkey DUDARNrGHVTFcCgriwRWgDQJPKDuDQr9jg 13:12:00 6JNk6NNFZcr49fbsD2jcTfTxFLjJKq9DHQ5JU8CYeZ2Cz6JdKMY 13:12:25 dumpprivkey DG6xnwCT6BXePaySqU85XocobZmhbJczQH 13:12:25 6JNXFv95Mp9SzehHw9jojjdxHRNPeh77qCsRbaNwJZMp9MKCAu3
Yes, those are real wallets. But don't bother trying to steal my coins, I just generated them on https://walletgenerator.net/ and they're empty. That's basically it. All you need to do is add some descriptions of what the wallets are, pretty up the format to your liking, and save copies in multiple, secure places, including printed out.
Remember, if you lose your keys, OR someone else sees them, you lose your coins!
If those were my real wallets above, you could use the keys and spend my coins. So obviously, don't let anyone else, especially annoying little brothers, get their grubby hands on them. But also make sure they can be discovered if anything happens to you. That's why the printed copies... nobody is going to go trolling through your porn or warez collection on the offchance there's something valuable in there. But they will look in your safe or wherever you store other important documents. Just be sure to leave a note as to what they are and how to use them. Remember the woman who came here a couple years ago who had found a USB stick with 110 BTC in a locked wallet.dat on it from her dead husband? I sometimes wonder if she ever got the money. Don't be her. Or him.
"OK, great. Now I have my keys. What now?"
Well, you can spend coins using https://coinb.in/#settings from any wallet you have the keys to. First step is to choose the network. Dogecoin (mainnet) obviously. Then go to Transaction in the +New menu. Enter your address and hit the Load button. It will pull in the first 100 transactions. Now enter the address to pay, and the amount. Note the Transaction Fee box! You want this amount to be zero. Depending on whether you're moving coins to another of your wallets to consolidate them (a very good idea.. go read the UTXO ELI5, which you will find a couple pages into https://www.reddit.com/dogecoin/comments/4yts6h/start_here_for_much_wallet_wow/ - Yes, I'm going to make you work for it, cos there's tons of useful stuff there you need to know), or paying someone else, you may want to select which inputs to use. Once you're happy with the transaction, go ahead and submit it. You will now get a block of text, which is the raw, unsigned transaction. Copy this. Go to the Sign tab. Paste it. Add your private key and Submit to sign it. After a little bit, you will get a signed transaction. Copy it. Go to the Broadcast tab, paste it and hit Submit. That's it. It should go into the next block in a minute or two. Yes, even without paying a mining fee. Our network is so lightly loaded that there are no contention issues like the Bitcoin people have to put up with.
"That's it? So why do I need QT?"
You don't. The process above is all that's involved in spending coins. Everything else is window dressing. So there is no need to run QT, or any other client. Oh, and since you can download the site and run it locally (mostly offline), there is no security issue beyond the usual keyloggers/spyware that can compromise anything. And by knowing how to do this, you are much better protected from accidental loss than someone who blindly trusts black boxes they don't understand. Oh, one final thing... if you really want to help the network by seeding rather than leeching, go ahead and run a full node. Instructions are in that link above. AND you may want to help seed the bootstrap file torrent from a couple of days ago. Just because YOU don't need it, doesn't mean others don't, right?
Summation of RaiBlocks lead developer AMA. I'm very excited about this coin, and if you're asking why I did this...I'm trying out my AMA consolidating script that I wrote for fun :) I'm interested in seeing what people think about this coin! You can read the responses directly from this link: https://www.reddit.com/RaiBlocks/comments/7ko5l7/colin_lemahieu_founder_and_lead_developer_of/ What are your top priorities atm? Both in developing areas itself and in terms of integration?
The top priorities right now are:
Wallets desktop/mobile and ease-of-use improvements to the node
Integration with exchanges
Vendor adoption wider user adoption
These basically need to happen in a sequence because each item isn't useful unless the previous one is complete.
Do you have any plans to have your source code peer reviewed? By peer review I mean sending your source code down to MIT for testing and review. Where do you see Raiblocks 5-10 years from now? (For instance do you envision people using a Raiblocks mobile phone app to transfer value between each other, or buy stuff at the store?
We definitely need peer and code reviews and we're open to anyone doing this. We have ideas for people in universities that want to analyze the whitepaper or code so we'll see what comes of that. In my opinion code security guarantees can only be given with (eyes * time) and we need both. I'd like to see RaiBlocks adopted as an internet RFC and basically become an ubiquitous background technology like http. I think you're probably right and a mobile app would be the most user-friendly way to do this so people don't need to carry around extra cards in their wallet etc.
Is there a list of the team readily available? Are there firm plans to expand, and if so, in which directions? The roadmap indicated a website redesign scheduled for November 2017. Is there an update?
We have about 12 people in the core team; about half are code and half are business developers. On the redesigned website we're going to include bios for sure, no one in our team is anonymous. I think we have pretty good coverage of what we need right now, we could always use more people capable of contributing to the core code. The website design is well underway, we wanted to streamline and add some more things to it so it took longer than originally estimated. It'll looking like after the new year we'll have it ready.
Would you ever consider renaming the coin to simply "Rai" or any other simplified form other than RaiBlocks? 2. What marketing strategy do you think will push XRB forward from now on as a fully working product. Instant and free, the green coin, "it just works" coin, etc? 3. Regarding security, is "quantum-proofing" a big concern at the moment and how do you guys plan to approach this when the time comes. And how possible would it be for bad actors to successfully implement a 51% attack.
Yea there are a few difficulties people have pointed out with our name. People don't know if it's "ray" or "rye". "Blocks" doesn't have a meaning to a lot of people and the name reference might be too esoteric to be meaningful. I'm not prideful so I'm not stuck on a particular name, we'll take a look at what our marketing and business developers say peoples' impressions are and if they have any naming recommendations.
Our marketing strategy is to focus on complete simplicity. Instant and free resonates with enthusiasts and mass adoption will only come when using xrb is absolutely the same experience as using a banking or other payment app. People aren't going to tolerate jargon or confusing workflows when sending or receiving payments.
Quantum computing is going to be an amazing leap for humanity but it's also going to cause a lot of flux in cryptography. The plan I see is the similar to what I did in selecting the cryptographic algorithms we're using right now: look for leaders in academia and industry that have proven implementations and use those as they recommend migration based on computing capability. Quantum vulnerabilities can be an issue in the future but a vulnerable implementation would be an issue right now.
Hi Colin, lately XRB has been getting frequently compared to and contrasted with Iota. I was hoping that you could give us your thoughts on the differences between the two and what your general vision for the future of Raiblocks is.
It's flattering to be compared to IOTA, they have a very talented team building ambitious technology. When looking at design goals I think one thing we're not attempting to approach is transferring a data payload, we're only looking to be a transfer of value. There are lots of ideas and technology to be developed in the cryptocurrency space and I want RaiBlocks to solve one section of that industry: the transfer of value. I think the best success would be if RaiBlocks was adopted as the global standard for this and crypto efforts could move to non-value-transfer use-cases.
Do you see XRB becoming the new payment method for commerce. As in, buying coffee, groceries, etc? Do you have plans for combating the HODL mentality so this currency can actually be used in the future of buying and selling?
Being a direct transactional payment method is our goal and we're trying to build software that's accessible to everyone to make that happen. I see holding as a speculative tactic anticipating future increases and you're right, it's not in line with day-to-day transactions. I think as market cap levels off to a more consistent value the reason for holding and speculating goes away and people can instead focus on using it as a value exchange.
Are you planning to expand the RaiBlocks team over the next 12 months? If so, what types of positions are you hoping to fill?
Right now we have about 12 people, half core and half business developers. I think this count is good for working on what we're doing right now which is getting wallets and exchanges worked on. Ideally people outside our team will start developing technology around xrb taking advantage of the network effect to build more technology faster than we could internally. That being said we're going to look in a few months to see if there's anything out there people aren't developing that should be and we'll see what people we need to make it happen.
At what point did you make the decision to make RaiBlocks your full time job? What was the decision making process like?
It was after the week where the core team met here in Austin to brainstorm our next steps. I saw how much enthusiasm there was from crypto-veterans with having a working system capable of being scaled up to what's needed for massive adoption and it seemed the risk needed to be taken. It was hard decision to make, working in the crypto and finance is rough and I like using my leisure time to work on inventions. Of all the projects ideas I have this one seemed to have a high chance of success and the benefits of having a working, decentralized currency would be huge.
Hi Colin, what prevents great cryptos like XRB from being listed on bigger exchanges?
It's good to understand where the biggest headaches for exchanges lie: support tickets, operations, and development. If a technology is different from what they already have, that takes development time. If the software is new and not widely run, that's potential operations time to fix it which results in support tickets and community backlash. Adding BitCoin clones or Ethereum ICO coins is easy because they don't have these associated risks or costs.
What can the average RaiBlocks-Fan do to help XRB getting adopted / growing / expanding?
I think the best thing an average fan could do is word of mouth and telling people about RaiBlocks. More people being aware of it means there's the possibility someone who's never heard of it before would be interested in contributing as a vendor, developer, exchange etc. Good advertising or marketing will never be able to reach everyone as well as someone reaching out within their own network.
Are you looking at incorperating a datamarket like iota in the future? Given the speed of the network a data exchange for highly accurate sensors could be a game changer. Further more, are there any plans to increase the Dev team in the future? I read on the FAQ you'd like RaiBlocks to be somewhat of a protocol which is a huge ambition. A Dev from say the Mozilla foundation or other could further cement this ambitious project.
Transmitting data payloads is something we probably won't pursue. The concern is adding more features like this could cause us to make decisions that compromise the primary focus points of low-cost and speed for transferring value. We can add people to the dev team though I think we'll get the most traction by teaching teams in these other organization how to use RaiBlocks so they can be the experts on the subject in their companies.
If a node wants to independently know the balances of all accounts in the system, it must at a minimum have storage to hold accounts and all their balances. In order to know all balances it must either listen to transactions as they're happening or bootstrap from someone else to catch up as what happens on startup.
There is no incentive to run nodes. Some people will do it because it is cheap as fuck (as I read an raspberry pie can run it). But I think not many people will do it. 1. How important are the nodes in terms of further scaling? 2. On which network conditions where the 7000 transactions met? 3. What happens if the transactions per day tenfolds but the nodes don't? 4. How much better will Rai scale if someone sets up, lets say, 100 nodes with awesome hardware and network? 5. How many nodes could be enough for visa level scaling? 6. Which further improvements can be made for Rai IF there needs to be other improvements than setting up new nodes? Are there other concepts like 2nd layer solutions planned? 7. How will Rai defend network attacks? I know there is an PoW part. But since there a also large attacks on high cap coins on which people invest millions of $ to congest a network..Is it possible that the Rai network will be unusable for several days because of this?
I think the out-of-protocol incentives to running a node are under-referenced yet I see them as the primary driving factor for participating as a whole. Node rewards come at the expense of other network participants and in this closed loop the incentives aren't enough to keep a cryptocurrency alive. Long-term there needs to be a system-level comparative advantage to what people are already using for a transfer of value. If someone is using xrb and it saves them hundreds or thousands of dollars per month in fees and customer irritation in delayed payments, they have a direct monetary incentive to using xrb and a monetary incentive in the health of the system. 1) More nodes provides transaction and bootstrapping redundancy. More representatives provides decentralization. 2) The 7k TPS was a profile how fast commodity hardware could eat transactions. All of the real-world limits are going to be something hardware related, either bandwidth, IO, or CPU. 3) The scaling is more related to the hardware the nodes are using rather than the node count. If there was 10x increase in transactions it would use 10x the bandwidth and IO as nodes observe transactions happening. 4) If someone made 100 representative nodes the network would be far more decentralized though the tx throughput would be unchanged since that's a per-node requirement. 5) Scaling to Visa will have high bandwidth and IO requirements on representatives associated with doing 10k IOPS. Datacenter and business class hardware will have to be enough to handle the load. 6) Second layer solutions are always an option and I think a lot of people will use them for fraud protection and insurance. Our primary focus is to make the 1st layer as efficient and high speed as possible so a 2nd layer isn't needed for daily transactions. 7) Defending against network attacks will be an ongoing thing, people like breaking the network for lulz or monetary gain i.e. competing cryptos. If there are attacks we haven't defended against or considered it'll be a matter of getting capable people to fix issues.
Are you open to changes to the name? (Rai) What are your plans with regards to marketing?
I'm open to it, people get confused on ray/rye pronunciation, not the greatest first impression. As far as timing I think marketing works best after a more user friendly wallet and integration in to more exchanges otherwise we're sending traffic to something people can't use. We're going to start by focusing on the initial adopters which will likely be enthusiasts and going forward work on the next set of users that aren't enthusiasts but want to drive savings for their business through lower payment processing costs.
I think he's definitely right, a lot of the TPS numbers are synthetic benchmarks usually on one system. The biggest thing hindering TPS are protocol-specific limits like hard caps or high contention design. The next biggest thing will be bandwidth and then disk IO. Some of these limits can be improved by profiling and fixing code instead of actual limits in the hardware. We want to get better, real world numbers but our general opinion is that the RaiBlocks protocol is going to be limited by hardware, rather than design.
Are you planning to add a fiat gateway to the main website and mobile wallet?
If we can make it happen for sure, that seems like a very user-focused feature people would want. The difficulty at least in the US is the money-transmitter licenses which are hard to obtain. More than likely if this functionality was added it'd be a partnership with an established financial company that has procedures in place to operate within countries' regulations.
I saw a post on /iota that claims that their quantum resistance is a main benefit over raiblocks. Can you go into detail about this? explain any plans you have to let XRB persevere through upcoming quatum revolution?
I think everyone with cryptography in their programs is keeping an eye on quantum cryptography because we're all in the same boat. I don't have cryptanalysis credentials so I didn't feel comfortable building an implementation and instead chose to use one off-the-shelf from someone with assuring credentials. There are some big companies that have made small mistakes that blow up the usefulness of the entire algorithm, it's incredibly easy to do. https://arstechnica.com/gaming/2010/12/ps3-hacked-through-poor-implementation-of-cryptography/
Hello Colin, is any security audit to the source code planned?
We don't have one contracted though both internally and externally this is an important thing people want completed.
Do you have plans to radically change the interface of the desktop wallet, and to develop a universal, cross-platform, clean and simple UX design for the wallet? This will be huge for mass adoption in my humble opinion
I completely agree, we do plan on completely redoing the desktop wallet, both from a UX standpoint and maintainability so UI code doesn't need to be in C++. This could also remove out dependency on QT which is the least permissive license in the code right now. I write code better than I design GUIs ;)
It seems like Raiblocks is aiming to be a true currency with it's lacking of transaction fees and fast confirmation times, which is great! If Raiblocks can add some kind of support for privacy then I think it got the whole picture figured out in terms of being "digital cash". Do you currently have any plans to implement privacy features into RaiBlocks? If Raiblocks is unable to do this, it will still be a straight improvement over things like LTC which are currently being used as currency, but I don't think it will be able to become THE cryptocurrency without privacy features.
I love the concept of privacy in the network and it's a hard thing to do right. Any solution used would need to be compatible with our balance-weighted-voting method which means at least we'd have to know how much weight a representative has even if we're hiding actual account balances. To be fully anonymous it would have to be hide accounts, amounts, endpoints, and also timing information; with advanced network analysis the timing is the hardest thing to hide. Hopefully some day we can figure out an efficient privacy solution though the immediate problem we can solve is making a transactional cryptocurrency so we're focusing on that.
Could you provide an analysis on the flaws of RaiBlocks? Is it in any way, shape, or form at a disadvantage compared to a blockchain based ledger like bitcoin? There has to be drawbacks, but I haven’t found any. Do you plan on expanding the dev team and establishing a foundation? Also, how much money is in the development pool?
One drawback is to handle is our chain-per-account model and asynchronous updates it takes more code and design. This means instead of one top-block hash for everything there's one for each account. This gives us the power of wait-free asynchronous transactions at the cost of simplicity. After we finish up things like the wallet, website, and exchange integration we'll be looking at seeing what dev resources we need to build tech if no one else is already working on a particular thing. We have about 6 million XRB right now so we've made the existing dev funds go a long way. If something expensive to build came along and dev funds wouldn't cut it we could look at some sort of external funding.
How big of a problem is PoW for exchanges and what are potential solutions?
Considering how much exchanges stand to make through commission I don't see the cost as a barrier, it's just an abnormal technology request compared to other cryptocurrencies. We're working on providing a service exchanges can use in the interim until they set up their own infrastructure to generate the work. Other options are containers people can use on cloud services to get the infrastructure they need until they want to invest in their own.
It's my understanding that since everything works asynchronously, in the case of double spending there is a chance a merchant would receive the block that would be later invalidated and have it shown in it's wallet, even if a little later (1 minute?) the amount would correct when the delegates vote that block invalid. Is there any mechanism to avoid this? Maybe tag the transactions in the wallet as "confirming" and then "confirmed" after that minute? Is there actually any certain way for a wallet to know, in a deterministic/programable way, at what moment a transaction is 100% legit? (for example if the delegates are DoS'ed I guess that minute could be much longer). I know this is an improbable case, but still...
Yea you're hitting a good point, the consensus algorithm in the node is designed to wait for the incoming transaction to settle before accepting it in to the local chain for the exact reason you listed, if their transaction were to be rolled back the local account would be rolled back as well. We can trend the current weight of all representatives that are online and voting and make sure we have >50% of the vote weight accounted for before considering it settled.
Hey Colin, will you eventually have support for a Trezor or other hard wallet?
Yea we'll definitely work with companies like Trezor that are interested in being a hardware wallet for xrb. It's just a matter of making sure they support the signing algorithms and integrating with their API.
EDIT: I'm getting a lot of messages asking me how to buy XRB. I used this guide which was very helpful: https://www.reddit.com/RaiBlocks/comments/7i0co0/the_definitive_guide_to_buying_and_storing/ In short -- buy BTC on coinbase, open up an account on bitgrail, transfer that BTC from coinbase to bitgrail, then trade your BTC for XRB. It's a pain right now because it's such a new coin, but soon it will be listed on more exchanges, and hopefully on things like shapeshift/changelly. After that it will be much easier... but until then, the inconvenience is what we have to pay in order to get into XRB while its still early. EDIT: BAD SCRIPT, BAD!
Bitcoin-Qt is the so – called" official " client of the network, which is developed and promoted by Bitcoin Foundation, a non-profit organization uniting core developers and responsible for the community's contacts with corporations and governments.Bitcoin Foundation branches are opened in several dozens of countries around the world. Integrated with the Blockchain Wallet, our Exchange is a one-stop shop where you can deposit funds and place trades seamlessly in minutes. Get Started. Dive Deeper. You’ve thought about it, now it’s time. Create a Wallet. Sign up for the Exchange. Buy Bitcoin in minutes. Get Started. Twitter Instagram Medium. Products. Wallet. Exchange. Learn. This demo shows how MQTT enables communication throughout the supply chain. The Qt UI enables a live preview in real-time and in any browser. A sensor sends environmental data using Qt Bluetooth, and transmits it to the cloud via MQTT and Using Ethereum BlockChain to secure data of decentralized edge devices. Pinkcoin is a blockchain-based digital asset designed to support Charities and Non-Profit organizations, and encourage community participation. Blockchain Platform. Pinkcoin’s blockchain is secured by it’s dual PoS + FPoS system. Learn more. OUR PARTNERS. 25,505,266 PINKCOIN DONATED. Moving the wallet blockchain files to another directory. Note: To move the blockchain data directory we are going to use the command line parameter. Also this works with almost any crypto currency QT wallets (Bitcoin, Litecoin, Zcash4Win, Monero, Dash, Doge, Verge, etc) Finding the wallet files and taking a backup
NEW BTC HACK RELEASED ! BLOCKCHAIN HACK # NEW 100 $ HACK BITCOIN
We do an install, look at the blockchain data,... Skip navigation Sign in. Search. ... look at the blockchain data, encrypt the wallet and look at the Bitcoin-QT interface. Tip ... I Bought a $3 2TB USB Drive and Got More Than Just Malware - Duration: 11:18. Jays Tech Vault Recommended for you Communicate with Bitcoin-qt using C# - .NET. ... Building a Blockchain in Under 15 Minutes ... Bootstrap a Blockchain career ... blockchain e bitcoin, como investir e bitcoin, ... bitcoin que es, bitcoin queen, bitcoin qt, bitcoin quantum, bitcoin q&a, bitcoin qr code generator, bitcoin qt wallet, bitcoin qartulad, 💾 DOWNLOAD LINK: https://bit.ly/32sxvlS =====Don't forget===== LIKE COMMENT SHARE SUBSCRIBE 👍 Smash the “Like”...
