Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network. GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled. HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user. Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
Simplified payment verification for fast mobile performance
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases. This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats. To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator. VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline. If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address. VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase. VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet. If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode. This wallet was previously deprecated but has been brought back to life with modern standards.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node. It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node. Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine. Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in. Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet. Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links. When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets). Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet. Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
Hi Everyone, Over the past few weeks, I've seen some unhappy comments here on Reddit. I think one of the trends in those comments is that the development team is quiet here on Reddit and perhaps that’s a just observation. So I felt the need to organize some of my thoughts and lay them out for all of my Reddit friends (that’s assuming I still have some). So, if I were to believe some of the comments made here, Vertcoin is dead and buried. Developers are “in hiding”. I’m still active in our Discord almost daily and talk to many people there. I don’t feel that way in the slightest. I talk to fellow dev team members on a daily basis, and we’re progressing on the work we need to do right now, which is working on the security of our network. Trying to maintain a secure, pure, honest, decentralized peer-to-peer Proof of Work currency is hard. Yes, there are easy solutions to the most obvious problem: introduce checkpointing, notarization or even master nodes. The attack vector of 51% attacks could be removed easily. But is the Vertcoin we would be left with really something unique? When I joined this team, I learned about its goals. Its primary goal is a decentralized currency that tries to distribute the rewards of maintaining the ledger in as fair a manner as possible. Being able to begin and end your participation in consensus without permission, and using readily-available and affordable commodity hardware like a GPU. I don’t think it’s easy to achieve, and the longer I’m part of this team and trying to figure this out, the harder it seems to become. But allowing consensus to be dominated by specialized, hard to acquire hardware - or entrusting the consensus partly or entirely to privileged consortia of nodes would be the true death of this project. I honestly think that it’s worth it to continue down this road. And I will keep doing that because I think it’s interesting and because I am happy to be working together with some very capable people that are a part of the Vertcoin team. I think we have a good vibe going (despite all the negative comments thrown our way), which shows in the fact that a lot of team members have been with us since long. I’ve been with these guys for nearly 2 years and I’m still one of the rookies. So first and foremost, our “Layer 1” has to be secure. Without that, there’s no point in building anything cool on top of it because it will break down. We temporarily removed ASICs and Nicehash dominance from our network by forking to Lyra2REv3, but we know this is no permanent solution. We have to figure out how we can best protect our network against specialized hardware and large pools of rented hash rate. This, to me, is our biggest challenge and our most prominent item to work on. To that effect, we’re actively working on a new Proof-of-Work algorithm dubbed Verthash, and have been doing so since last year. I expect this to materialize somewhere over the next 2 to 6 months. We are continuously making iterations on the design and have a proof-of-concept implementation in a Vertcoin Core build running on a forked testnet between our developers. We want to ensure its stability and that it does not interfere with any of the features currently available to Vertcoin users, like p2pool, pool mining in general, and SPV wallets like Electrum. Otherwise, we’ll have to keep iterating until it does. Once we’ve established that, and the design is final, we release a first testnet beta and all the source code to Verthash well before even planning a mainnet fork. We will make sure there is a GPU miner with that testnet release so everyone can try mining our new Proof-of-Work algorithm and see what kind of hash rate they can expect for their hardware. There’s actively being worked on this on a weekly basis. Some weeks more, some weeks less. Another part of securing the base layer is keeping up-to-date with upstream Bitcoin Core improvements. We are currently behind a tad, but one of our community members is actively trying to bring us up to date with the latest upstream improvements, and it’s great to see someone stepping up like that. This person is also actively being supported by dev team members to complete his task and is noticing and taking away roadblocks to make this process easier in the future. I think this is a great initiative and an example that if you want to contribute to the development of Vertcoin, you can. Lastly, there’s a bunch of other ideas we could work on. Since people haven’t heard about things in a while doesn’t mean they’re not still viable ideas (such as the Litbox concept, an updated, multi-platform One-click Miner, improved version of P2Pool, Vertcoin Assets, Stealth Transactions). In general, I think we have way more ideas than the capacity to implement them. If people at some point had the idea that these ideas were close to launching, I am sorry about that. I have never considered any of these to be release-imminent. There are two ways to deal with the misalignment of ideas and resources: either lower your expectations and be realistic about what can be achieved, or hire people to speed up execution. Since we don’t have the funds for the latter, we have to stick to the former. Literally, everyone involved in Vertcoin does this in their spare time, and they work on what they think is the most interesting, challenging, what they can learn from the most, etcetera. It’s both the beauty of volunteers, that work on something they’re passionate about - and not just because they get paid - and also its biggest pitfall: people that lose interest, life getting in the way, and projects stalling. We don’t have people we can dictate what to work on, that’s a reality we have to live with. So if you think: “these Vertcoin guys are a bunch of amateurs” - it’s because we are… at Vertcoin at least. Most of us have careers in fields very valuable to Vertcoin and bring in the knowledge that other projects have to spend an arm and a leg on. In conclusion, I very much disagree with the fact that this project would be dead. I agree that there is a greatly reduced community activity on Reddit, Discord and other channels. It’s obvious that the market valuation of Vertcoin is down a lot. But neither of those indicate the death of this project. As long as people are passionate about its goals and are actively trying to achieve them, this project will go on. It’s been around for over five years, and I don’t see any reason to doubt it will be around for plenty of time to come. Gert-Jaap Volunteer at Vertcoin
UPDATE: VTC mining on Easymine back to normal, payouts have resumed. Zero fees for the rest of the month. Here's a more detailed response to https://old.reddit.com/vertcoin/comments/96z77t/psa_easy_mine_problem/ - bear with me and put on your nerd hat for a few mins. The stratum server for all EasyMine pools is node-merged-pool - a merge mining fork of node-stratum-pool. See my repo here @ https://github.com/nzsquirrell/node-merged-pool This is what miners connect to for work and to submit valid shares on the search for blocks. The information that is exchanged in hex digits, and the data coming back from the miner includes the time, the job, ExtraNonce2 and nonce (see https://en.bitcoin.it/wiki/Stratum_mining_protocol#mining.submit). All of these fields are used to notify the server of valid work exceeding a specific difficulty. Hex digits are not case-sensitive. So 'FF00AA11' is the same as 'ff00aa11'. Both equate to decimal 4278233617. So for the purposes of construction a block header, it doesn't matter if the hex digits are uppercase, lowercase, or a mixture of both - it all works out the same, and produces the same hash. Hold this thought. The stratum server knows what shares each miner has submitted, it keeps a track of all of the data in an array. It checks every time that work is submitted that the same work hasn't been submitted before whilst searching for the next block. If it was submitted, then the new submission is rejected as duplicate work. Now, where this has all gone wrong is that the way the data is stored in this array was a string containing the four fields mentioned above. Strings are case-sensitive and when making comparisons 'FF00AA11' != 'ff00aa11', as well as 'ff00aA11' and 'ff00AA11' and so on.... This allowed our attacker to submit the same work many many times, altering only the case of the hex digits (he was doing it to the nonce, but the other fields are also susceptible to the attack), so the logic to check for duplicate work wasn't firing, the shares were valid (as they produced a valid hash above difficulty), and our attacker was faking most of his hash-rate. A lot. A shit-ton of it. I have fixed this in my fork of node-stratum-pool - the fix is very easy, we just make all the characters lower case before testing for duplicate shares. See https://github.com/nzsquirrell/node-merged-pool/commit/9d068535d042516835f565a859852c7cf715da98 for my fix. My big concern is that the other forks I've seen for node-stratum-pool are susceptible to the attack, and quite possibly other pool software is toopossibly even p2pool? I've not looked. If someone can check and let me know and I'll update this. p2pool has been confirmed as resilient to this type of attack. So, Who-The-F&*k did this. This is what I have so far: He's used the following VTC and NIX addresses:
I've seen connections coming in from the following IP addresses:
He is still attacking EasyMine, but it's not having any effect now. Actually the server keeps banning him now as it's detecting that he's submitting too many invalid shares. Take that. The path forward I have a big mess to clean up, he's made off with about 652 VTC and about 3576 NIX, essentially stolen from you miners. I will see what I can do to recover some of this (not all of it has been paid to him yet), but there is going to be a substantial shortfall. Mr Attacker, feel free to PM me and we can arrange a settlement :) Payouts on both the VTC & NIX pools are suspended until i can clean this up, I hope this won't take more than a couple of days. Thanks.
BCH nov15-dec15 update . BCH moves along and claims its #4 place back on CMC
https://news.bitcoin.com/hash-wars-bch-proponents-face-a-new-dawn-in-the-battles-aftermath/ 35 days later after the fork, Bitcoin Cash supporters are working towards moving past the hash war that took place a little after the scheduled BCH upgrade on Nov. 15. Now both networks are operating and the Bitcoin Satoshi’s Vision (BSV) coin has its own price ticker and market capitalization listed on data sites like Coinmarketcap and Satoshi Pulse. A portion of crypto-trading platforms have now listed BSV as a separate currency and the entire ecosystem of exchanges, payment processors and a great majority of wallets have awarded the ABC side of the chain the BCH ticker. At the time of writing, the global average price for BCH is $144 after markets jumped 47 percent on Dec. 19. BSV spiked 18 percent this Tuesday and each coin is currently trading for $92 per token. Since the fork, the BCH network hashrate has dropped considerably, even more so than the 50 percent loss BTC suffered this past month. Average hashrates for a great number of SHA-256 algorithm coins have endured deep drops in processing power according to global statistics. The Bitcoin Cash hashrate used to command a rough average of 5 exahash per second (EH/s), but now only captures 1 EH/s to 850 petahash per second (PH/s) on a daily basis throughout this month. On the bright side, the BCH network has been 5-8 percent more profitable to mine than BTC over the last two days. Further, BCH has amassed a large swathe of different mining pools that are processing BCH blocks on a regular basis. This includes Viabtc, Btc.com, Antpool, Multipool, Bitcoin.com, Btc.top, Waterhole, Copernicus, P2pool, Ckpool, and some other unknown mining entities as well. Another BCH metric that has halved since the fork on Nov. 15 is the cryptocurrency’s daily transaction rate over the last month. Before, bitcoin cash transactions per day were about 20,000-25,000, whereas today that number stands at roughly 9,750 over the course of the last 24 hours. Over the last three weeks, the BCH daily transaction rate has been averaging 10k per day, with a few instances of 15k-22k spikes here and there. There has been a steady increase in daily transactions week after week, and with 99 percent of BCH infrastructure back in order, this should continue. A good example of this behavior is the increase in BCH price and trade volume on exchanges over the last few weeks. Pre-fork BCH trade volumes captured anywhere between $400-900 million worth of global trades every day. After the fork, this statistic dropped to around $50-100 million daily on global exchanges. This was because some cryptocurrency trading platforms with a ton of bitcoin cash liquidity had paused BCH transactions and some exchanges halted trading. Week after week, however, global BCH trade volume has been steadily increasing on exchanges like Upbit, Binance, Huobi, Lbank, and Coinbase Pro. With the 40 percent increase over the last 24 hours, BCH trade volume has jumped to over $400 million in global trades on Dec. 19. At the time of publication, this makes BCH the seventh most traded digital asset out of the entire crypto economy. The Bitcoin Cash community had also suffered from daily battles on Reddit’s btc forum and social media platforms like Twitter. A good portion of the trolling and infighting seems to have quietened down, and most BCH supporters are just trying to move forward. There’s been plenty of developments since the fork, with projects like Electron Cash, Honest Cash, Cash Shuffle, and Openswap adding more utility to the BCH network. Furthermore, BCH enthusiasts look forward to the upcoming BCH upgrades that are under discussion and they can track the code’s development too. For now, BCH supporters are extremely pleased that the fork is behind them and are thrilled to reclaim fourth position among all cryptocurrency market capitalizations.
This post is a temporary resting place for FAQs while we wait for the release of VertDocs.
What is Vertcoin?
Vertcoin is a digital peer to peer currency focused on decentralization and ASIC resistance. Vertcoin is aiming to be easily accessible to the everyday user without extensive technical knowledge. Vertcoin has started to lower the barrier of entry with lots of video guides and the development of the One Click Miner (OCM).
Why does ASIC Resistance Matter?
ASICs (Application Specific Integrated Circuits) are dedicated mining devices that can only mine one algorithm. Coins like Bitcoin and Litecoin both made GPU mining obsolete when SHA-256 and Scrypt ASICs were created.
ASIC Resistance and How it Makes Vertcoin Decentralized
Vertcoin believes that ASIC resistance goes hand in hand with decentralization. ASICs are made by companies like Bitmain and almost all the original sellers of ASICs sell on a preorder basis. When pre ordering an ASIC you are buying from a limited batch that the ASIC company has produced. Often times the batch will not be fully filled and the ASIC company will often have left over ASICs. When the ASIC company has left over ASICs they will put them to work mining. Soon enough the ASIC company will have a very large amount of unsold ASICs that are mining and slowly the ASIC company starts to own a large part of the network’s hashrate. When an ASIC company(s) starts to own a large majority of the hashrate the network can become very centralized after a while. Having your network consist of a few large companies can be very dangerous as they could eventually get 51% hashing power and 51% attack your network, destabilizing the network. When your network is made out of a lot of smaller miners, like Vertcoin, it is much harder for your network to be 51% attacked, therefore increasing network security. By having centralized hashing power your coin effectively centralizing the network as the centralized hashing power can deny transactions and stop any activity they don’t want.
What Ways is Vertcoin Superior to Litecoin and Bitcoin?
Network Difficulty Adjustments with Kimoto Gravity Well
Vertcoin uses a difficulty adjustment called Kimoto Gravity Well which adjusts the difficulty every block, whereas Bitcoin and Litecoin’s difficulty changes every 2016 blocks. By adjusting the difficulty every block Vertcoin’s block time can stay consistent by adjusting for the fluctuation in network hash rate from hash rate renting and part time miners. If a large miner switches off Bitcoin or Litecoin mining the network could be slowed to a crawl until 2016 blocks are mined and the difficulty can change to adjust for the new network hash rate. We observed this happen to Bitcoin when Bitcoin Cash became more profitable than Bitcoin and Bitcoin’s network hash rate saw a steep fall off, slowing the network to a crawl. If this was to happen with Vertcoin the difficulty would adjust after 1 block was mined, allowing Vertcoin to always be profitable to mine.
Anyone can Meaningfully help Verify Transactions
In Proof-of-Work crypto currencies miners help secure the blockchain and get rewarded with the block reward. In ASIC mineable coins like Bitcoin and Litecoin you can’t meaningfully verify transactions unless you pay 1000-2000$ for a ASIC miner. When you mine with a CPU or GPU in a ASIC mineable coin you make no meaningful impact on the network. It is like trying to break concrete with a shovel while everyone else has a jackhammer.
Simple Upgrades Aren’t Held back by 1-2 Large Miners
In ASIC market people buy ASICs in batches in a preorder. With Bitcoin ASICs there is not enough demand for ASICs so the batch often doesn’t get sold out so now the manufacturer has spare ASICs. Now that the manufacturer has spare ASICs they will often start mining with them and eventually the ASIC company has one of the highest hash rates. If the ASIC company doesn’t want a certain upgrade to go through, for example SegWit, they can vote with their hash rate to hold back the upgrade forever or at least until people who want SegWit get more hash rate.
You Have a Say in Protocol Rules and Consensus
In Bitcoin you are a passive observer because you can only issue transactions and you have no part in the process after that. In Vertcoin you can be apart of the process for deciding the ordering of transactions and deciding what transactions get into blocks.
Block Rewards and Transaction Fees are Distributed Evenly
In Bitcoin and Litecoin the block rewards and transaction fees are often given to the large miners in China due to mining centralization created by ASICs. Vertcoin distributes its mining rewards to people all around the world thanks to the mining decentralization.
When will Atomic Swaps Be Ready?
Atomic Swaps can be done in two flavors: On-chain and Off-chain (via Lightning Network). On-chain swaps were actually done already using Blocknet, you can see it in use on Youtube. We're looking into doing it again using Interledger. However our main focus is to do off-chain Atomic Swaps using Lightning Network technology. Because it has the same benefits as Lightning transactions: No network fees and instant transactions. For off-chain swaps we need Lightning Network to be fully operational. It's difficult to give an ETA on that since we aren't the ones developing it. U/gertjaap posted a video on the current state of the Lightning Network for Vertcoin a while ago, which you can see here. This was actually the "bleeding edge" of Lightning Network at the time. was able to use it on VTC's main net, meaning that our blockchain is ready for the good stuff. As you can see however, it can't yet be considered production ready (most users would want a little better UX than a command line app). Now off-chain Atomic Swaps is a technique based on the same principles as Lightning Network, but adds an extra complexity for it being across chains. So it's basically the same as a "multi hop" Lightning payment, which is not yet built by any of the implementations. They're still working hard on making the single-hop payments robust. So in order for AS to be possible, LN has to be fully operational. A timeline cannot be given at this time, because frankly we don't know. The implementation of Lightning Network we feel has the most potential is LIT, because it supports multiple currencies in its protocol (where LND is bitcoin-only at the time and requires significant work to support other currencies, which is an essential part of being able to work across multiple blockchains). LIT is open source and there's nothing secretive about its progress, you can see the development on Github. We even have our lead dev James Lovejoy (u/jamesl22) close to the action and contributing to it where possible (and our team as well through testing it on the Vertcoin chain). So we're not developing LN or AS ourselves, we're just ready with our blockchain technology whenever it becomes available. If we have any real progress that has some substance, you can expect us to let the world know. We're not interested in fluffy marketing - we post something when we achieve real progress. And we are not keeping that secret.
How do I Choose the Right Vertcoin Wallet?
Deciding what Vertcoin wallet you should choose can be a difficult process. You can choose between three different wallets: Core, Electrum and Paper. Once you decide you can use the "How to Setup Your Vertcoin Wallets" video guide to assist you.
The Core wallet is the wallet that most people should use. It will store the entire blockchain (~2GB) on your computer. The Core wallet is the only wallet that fully supports P2Pool mining. You will also have to use the Core wallet if you plan to run a P2Pool node or any Vertcoin related server.
The Electrum wallet is a light wallet for Vertcoin. You do not have to download the blockchain on your computer, but you will still have your own private keys on your computer. This is recommended for people who don't need to store Vertcoins for very long and just need a quick but secure place to store them.
The Paper wallet is as the name implies, a physical paper wallet. When generating a paper wallet you will get a pdf that will need to print out. A paper wallet is normally used for long term storage since it is the safest way to store Vertcoins. A paper wallet can also be called "cold storage." Cold storage references the storage of your coins offline, preventing you from getting hacked over the internet.
Ledger Nano S
The Ledger Nano S is a hardware wallet designed by Ledger. A hardware wallet is similar to a paper wallet since it is normally used for cold storage. The hardware wallet is on par with the security of a paper wallet while being easy to use and setup. Note: You should never mine directly to a Ledger hardware wallet.
You can get the latest version of the One Click Miner in the Vertcoin Discord. The download is pinned to the top of the #oneclick channel.
What do all the Numbers Mean on P2Pool’s Web Interface
I've seen a lot of confusion from new miners on public p2pool nodes, so here's a primer for the most common static node page style, for first time miners: https://imgur.com/K48GmMw
Active Miners on this Node
Address - This is the list of addresses currently mining on this node. If your address does not show up here, you are not mining on this node.
This is a snapshot of your hashrate as seen by the node. It will fluctuate up to 15% from the hashrate you are seeing on your mining software, but will average out to match the output in your mining software.
This is the amount of your hashing contribution that is rejected, both in hashrate and as a percentage of your total contribution. Running your own p2pool node minimizes this number. Mining on a node that is geographically close to reduce lag also minimizes this number. Ideally you would like it to be less than 1%, but most people seem happy keeping it under 3%.
This speaks for itself, it is the difficulty of the share being currently worked on. Bigger numbers are more difficult.
Time to Share
This is how long you need to mine before you will receive any payouts, or any "predicted payout." The lower your hashrate, the higher your time to share.
This is the reward you would receive if a block was found by p2pool right now. If it reads "no shares yet" then you have not yet been mining the requisite amount of time as seen in the previous "time to share" column.
This is the total hashrate of all the miners mining vertcoin everywhere, regardless of where or how.
Global Pool Hashrate
This is the total hashrate of all the miners mining vertcoin on this p2pool network, be it the first network or the second network.
Local Pool Hashrate
This is the total hashrate of all the miners mining Vertcoin on this node.
Current Block Value
This is the reward that will be given for mining the current block. The base mining reward is currently 50 VTC per block, so any small decimal over that amount is transaction fees being paid by people using the network.
Network Block Difficulty
This is the difficulty of the block being mined. The higher the number, the higher the difficulty. This number rises as the "Network Hashrate" rises, so that blocks will always be found every 2.5 minutes. Inversely, this number falls when the "Network Hashrate" lowers as well.
Expected Time to Block
This is a guess at how much time will elapse between blocks being found by this p2pool network. This guess is accurate on average, but very inaccurate in the short term. Since you only receive a payout when the network finds a block, you can think of this as "Estimated Time to Payout."
Why is P2Pool Recommended Over Traditional Pools?
P2Pool is peer to peer allowing a decentralized pool mining system. There are many nodes setup around the world that connect to each other too mine together. Many other coins have 1 very large pool that many miners connect to and sometimes the largest pool can have 51% or more of the network hash rate which makes the network vulnerable to a 51% attack. If P2Pool is the largest network then that prevents the Vertcoin network to be susceptible to a 51% attack as P2Pool is decentralized.
PPLNS Payout System
P2Pool uses a PPLNS (Pay Per Last N Shares) payout system which awards miners more the longer they mine, sort of like a loyalty system. A drawback to this system is that part time miners that aren't 24/7 won't be able to earn that much.
While Network 1 is catered towards 24/7 miners and people who have dedicated mining rigs, Vertcoin has a second P2Pool network where part time miners and miners under 100 MH/s can go to mine.
Mines Directly to Your Wallet
P2Pool mines directly to your wallet and cuts out the middleman. This reduces the likely hood that the pool will run away with your coins.
Since P2Pool is decentralized and has different nodes for you to choose from there will be no downtime because the P2Pool network does not die if one node goes down. You can setup a backup server in your miner so that you will have no downtime when mining.
Anonymity and Security
When using P2Pool you use a wallet address making your real identity anonymous, you are simply known by a random 34 letter string. Along with using a wallet address instead of a username there is no password involved P2Pool preventing the possibility of cracking your pool account (If you were on a traditional pool,) and stealing all your coins.
How do I Find a Nearby P2Pool Node
You can find the public p2pool nodes the the P2Pool Node Scanners. If you want to find a network 1 node go here. If you want to find a network 2 node go here.
The quickest way for you to get help is for you to join the Vertcoin Discord Group. We almost always have knowledgable Vertans, whether that be developers or experienced Vertans, online to help you with whatever problems you may have.
How can I donate to the Developers?
You can donate to the dev fund at https://vertcoin.org/donate/. You can select what you want your funds to go to by donating to the corresponding address. You can also see how much funding is required and how much we have donated.
The Vertcoin developers currently have a trello board where you can see the goals and what the status of said goal is. You can also vote on what you want the Vertcoin developers to focus on next.
What is the Status of the AMD Optimized Miner?
The AMD Optimized Miner internal beta is aiming to be ready by the end of September. The AMD Optimized Miner is currently being developed by @turekaj on the Vertcoin Discord. He currently does not have a Reddit account and Discord is the only way you can contact him.
What Does Halving Mean?
Halving means that the block reward for miners will be split in half. Halving happens around every 4 years for Vertcoin or 840,000 blocks. This means around December miners will only receive 25 VTC per block instead of the current 50 VTC per block. If you would like to add another question to this list please comment it and I will get around to adding it ASAP.
Q: What is your relationship with Blockstream now? Are you in a Cold War? Your evaluation on BS was pretty high “If this amazing team offers you a job, you should take it,” tweeted Gavin Andresen, Chief Scientist, Bitcoin Foundation.” But now, what’s your opinion on BS? A: I think everybody at Blockstream wants Bitcoin to succeed, and I respect and appreciate great work being done for Bitcoin by people at Blockstream. We strongly disagree on priorities and timing; I think the risks of increasing the block size limit right away are very small. I see evidence of people and businesses getting frustrated by the limit and choosing to use something else (like Ethereum or a private blockchain); it is impossible to know for certain how dangerous that is for Bitcoin, but I believe it is more danger than the very small risk of simply increasing or eliminating the block size limit.
Q: 1) Why insist on hard fork at only 75%? You once explained that it is possible to be controlled by 5% if we set the threshold at 95%. I agree, but there should be some balance here. 75% means a high risk in splitting, isn’t it too aggressive? Is it better if we set it to 90%? A: 1)The experience of the last two consensus changes is that miners very quickly switch once consensus reaches 75% -- the last soft fork went from 75% support to well over 95% support in less than one week. So I’m very confident that miners will all upgrade once the 75% threshold is reached, and BIP109 gives them 28 days to do so. No miner wants to create blocks that will not be accepted by the network. Q: 2) How to solve the potentially very large blocks problem Classic roadmap may cause, and furthur causing the centralization of nodes in the future? A: 2)Andreas Antonopoulos gave a great talk recently about how people repeatedly predicted that the Internet would fail to scale. Smart engineers proved them wrong again and again, and are still busy proving them wrong today (which is why I enjoy streaming video over my internet connection just about every night). I began my career working on 3D graphics software, and saw how quickly we went from being able to draw very simple scenes to today’s technology that is able to render hundreds of millions of triangles per second. Processing financial transactions is much easier than simulating reality. Bitcoin can easily scale to handle thousands of transactions per second, even on existing computers and internet connections, and even without the software optimizations that are already planned. Q: 3) Why do you not support the proposal of RBF by Satoshi, and even plan to remove it in Classic completely? A: 3) Replace-by-fee should be supported by most of the wallets people are using before it is supported by the network. Implementing replace-by-fee is very hard for a wallet, especially multi-signature and hardware wallets that might not be connected to the network all of the time. When lots of wallet developers start saying that replace-by-fee is a great idea, then supporting it at the network level makes sense. Not before. Q: 4) . Your opinion on soft fork SegWit, sidechain, lighnting network. Are you for or against, please give brief reasons. Thanks. A: 4) The best way to be successful is to let people try lots of different things. Many of them won’t be successful, but that is not a problem as long as some of them are successful. I think segregated witness is a great idea. It would be a little bit simpler as a hard fork instead of a soft fork (it would be better to put the merkle root for the witness data into the merkle root in the block header instead of putting it inside a transaction), but overall the design is good. I think sidechains are a good idea, but the main problem is finding a good way to keep them secure. I think the best uses of sidechains will be to publish “write-only” public information involving bitcoin. For example, I would like to see a Bitcoin exchange experiment with putting all bids and asks and trades on a sidechain that they secure themselves, so their customers can verify that their orders are being carried out faithfully and nobody at the exchanges is “front-running” them. Q: 5) Can you share your latest opinion on Brainwallet? It is hard for new users to use long and complex secure passphrase, but is it a good tool if it solves this problem? A: 5) We are very, very bad at creating long and complex passphrases that are random enough to be secure. And we are very good at forgetting things. We are much better at keeping physical items secure, so I am much more excited about hardware wallets and paper wallets than I am about brain wallets. I don’t trust myself to keep any bitcoin in a brain wallet, and do not recommend them for anybody else, either.
Q: Gavin, do you have bitcoins now? What is your major job in MIT? Has FBI ever investigated on you? When do you think SHA256 might be outdated, it seems like it has been a bit unsafe? A: Yes, a majority of my own person wealth is still in bitcoins -- more than a financial advisor would say is wise. My job at MIT is to make Bitcoin better, in whatever way I think best. That is the same major job I had at the Bitcoin Foundation. Sometimes I think the best way to make Bitcoin better is to write some code, sometimes to write a blog post about what I see happening in the Bitcoin world, and sometimes to travel and speak to people. The FBI (or any other law enforcement agency) has never investigated me, as far as I know. The closest thing to an investigation was an afternoon I spent at the Securities and Exchange Commission in Washington, DC. They were interested in how I and the other Bitcoin developers created the software and how much control we have over whether or not people choose to run the software that we create. “Safe or unsafe” is not the way to think about cryptographic algorithms like SHA256. They do not suddenly go from being 100% secure for everything to completely insecure for everything. I think SHA256 will be safe enough to use in the all ways that Bitcoin is using it for at least ten years, and will be good enough to be used as the proof-of-work algorithm forever. It is much more likely that ECDSA, the signature algorithm Bitcoin is using today, will start to become less safe in the next ten or twenty years, but developer are already working on replacements (like Schnorr signatures).
Q: It’s a pleasure to meet you. I only have one question. Which company are you serving? or where do you get your salary? A: The Media Lab at MIT (Massachusetts Institute of Technology) pays my salary; I don’t receive regular payments from anybody else. I have received small amounts of stock options in exchange for being a techical advisor to several Bitcoin companies (Coinbase, BitPay, Bloq, Xapo, Digital Currency Group, CoinLab, TruCoin, Chain) which might be worth money some day if one or more of those companies do very well. I make it very clear to these companies that my priority is to make Bitcoin better, and my goal in being an advisor to them is to learn more about the problems they face as they try to bring Bitcoin to more of their customers. And I am sometimes (once or twice a year) paid to speak at events.
Q: Would you mind share your opinion on lightning network? Is it complicated to implement? Does it need hard fork? A: Lightning does not need a hard fork. It is not too hard to implement at the Bitcoin protocol level, but it is much more complicated to create a wallet capable of handling Lightning network payments properly. I think Lightning is very exciting for new kinds of payments (like machine-to-machine payments that might happen hundreds of times per minute), but I am skeptical that it will be used for the kinds of payments that are common on the Bitcoin network today, because they will be more complicated both for wallet software and for people to understand.
Q: 1) There has been a lot of conferences related to blocksize limit. The two took place in HongKong in Decemeber of 2015 and Feberary of 2016 are the most important ones. Despite much opposition, it is undeniable that these two meetings basically determines the current status of Bitcoin. However, as the one of the original founders of Bitcoin, why did you choose to not attend these meetings? If you have ever attended and opposed gmax’s Core roadmap (SegWit Priority) in one of the meetings, we may be in a better situation now, and the 2M hard fork might have already begun. Can you explain your absence in the two meetings? Do you think the results of both meetings are orchestrated by blockstream? A: 1) I attended the first scaling conference in Montreal in September of 2015, and had hoped that a compromise had been reached. A few weeks after that conference, it was clear to me that whatever compromise had been reached was not going to happen, so it seemed pointless to travel all the way to Hong Kong in December for more discussion when all of the issues had been discussed repeatedly since February of 2015. The February 2016 Hong Kong meeting I could not attend because I was invited only a short time before it happened and I had already planned a vacation with my family and grandparents. I think all of those conferences were orchestrated mainly by people who do not think raising the block size limit is a high priority, and who want to see what problems happen as we run into the limit. Q: 2) We have already known that gmax tries to limit the block size so as to get investment for his company. However, it is obvious that overthrowing Core is hard in the short term. What if Core continues to dominate the development of Bitcoin? Is it possible that blockstream core will never raise the blocksize limit because of their company interests? A: 2) I don’t think investment for his company is Greg’s motivation-- I think he honestly believes that a solution like lightning is better technically. He may be right, but I think it would be better if he considered that he might also be wrong, and allowed other solutions to be tried at the same time. Blockstream is a funny company, with very strong-willed people that have different opinions. It is possible they will never come to an agreement on how to raise the blocksize limit.
Q: I would like to ask your opinion on the current situation. It’s been two years, but a simple 2MB hard fork could not even be done. In Bitcoin land, two years are incredibly long. Isn’t this enough to believe this whole thing is a conspiracy? A: I don’t think it is a conspiracy, I think it is an honest difference of opinion on what is most important to do first, and a difference in opinion on risks and benefits of doing different things. Q: How can a multi-billion network with millions of users and investors be choked by a handful of people? How can this be called decentrilized and open-source software anymore? It is so hard to get a simple 2MB hard fork, but SegWig and Lighting Network with thousands of lines of code change can be pushed through so fast. Is this normal? It is what you do to define if you are a good man, not what you say. A: I still believe good engineers will work around whatever unnecessary barriers are put in their way-- but it might take longer, and the results will not be as elegant as I would prefer. The risk is that people will not be patient and will switch to something else; the recent rapid rise in developer interest and price of Ethereum should be a warning. Q: The problem now is that everybody knows Classic is better, however, Core team has controlled the mining pools using their powers and polical approaches. This made them controll the vast majority of the hashpower, no matter what others propose. In addition, Chinese miners have little communication with the community, and do not care about the developement of the system. Very few of them knows what is going on in the Bitcoin land. They almost handed over their own power to the mining pool, so as long as Core controls the pools, Core controls the whole Bitcoin, no matter how good your Classic is. Under this circumstance, what is your plan? A: Encourage alternatives to Core. If they work better (if they are faster or do more) then Core will either be replaced or will have to become better itself. I am happy to see innovations happening in projects like Bitcoin Unlimited, for example. And just this week I see that Matt Corallo will be working on bringing an optmized protocol for relaying blocks into Core; perhaps that was the plan all along, or perhaps the “extreme thin blocks” work in Bitcoin Unlimited is making that a higher priority. In any case, competition is healthy. Q: From this scaling debate, do you think there is a huge problem with Bitcoin development? Does there exsit development centrilization? Does this situation need improvment? For example, estabilish a fund from Bitcoin as a fundation. It can be used for hiring developers and maintainers, so that we can solve the development issue once and for all. A: I think the Core project spends too much time thinking about small probability technical risks (like “rogue miners” who create hard-to-validate blocks or try to send invalid blocks to SPV wallets) and not enough time thinking about much larger non-technical risks. And I think the Core project suffers from the common open source software problem of “developers developing for developers.” The projects that get worked on are the technically interesting projects-- exciting new features (like the lightning network), and not improving the basic old features (like improving network performance or doing more code review and testing). I think the situation is improving, with businesses investing more in development (but perhaps not in the Core project, because the culture of that project has become much less focused on short-term business needs and more on long-term exciting new features). I am skeptical that crowd-funding software development can work well; if I look at other successful open source software projects, they are usually funded by companies, not individuals.
You are one of the most-repected person in Bitcoin world, I won’t miss the chance to ask some questions. First of all, I am a Classic supporter. I strongly believe that on-chain transcations should not be restrained artificially. Even if there are transcations that are willing to go through Lighting Network in the future, it should be because of a free market, not because of artificial restrication. Here are some of my questions: Q: 1) For the past two years, you’ve been proposing to Core to scale Bitcoin. In the early days of the discussion, Core devs did agree that the blocksize should be raised. What do you think is the major reason for Core to stall scaling. Does there exist conflict of interest between Blockstream and scaling? A: 1) There might be unconscious bias, but I think there is just a difference of opinion on priorities and timing. Q: 2) One of the reason for the Chinese to refuse Classic is that Classic dev team is not technically capable enough for future Bitcoin development. I also noticed that Classic does have a less frequent code release compared to Core. In your opinion, is there any solution to these problems? Have you ever thought to invite capable Chinese programers to join Classic dev team? A: 2) The great thing about open source software is if you don’t think the development team is good enough (or if you think they are working on the wrong things) you can take the software and hire a better team to improve it. Classic is a simple 2MB patch on top of Core, so it is intentional that there are not a lot of releases of Classic. The priority for Classic right now is to do things that make working on Classic better for developers than working on Core, with the goal of attracting more developers. You can expect to see some results in the next month or two. I invite capable programmers from anywhere, including China, to help any of the teams working on open source Bitcoin software, whether that is Classic or Core or Unlimited or bitcore or btcd or ckpool or p2pool or bitcoinj. Q: 3) Another reason for some of the Chinese not supporting Classic is that bigger blocks are more vulnerable to spam attacks. (However, I do think that smaller blocks are more vlunerable to spam attack, because smaller amount of money is needed to choke the blockchain.) What’s our opinion on this? A: 3) The best response to a transaction spam attack is for the network to reject transactions that pay too little fees but to simply absorb any “spam” that is paying as much fees as regular transactions. The goal for a transaction spammer is to disrupt the network; if there is room for extra transactions in blocks, then the network can just accept the spam (“thank you for the extra fees!”) and continue as if nothing out of the ordinary happened. Nothing annoys a spammer more than a network that just absorbs the extra transactions with no harmful effects. Q: 4) According to your understanding on lighting network and sidechains,if most Bitcoin transactions goes throught lighting network or sidechains, it possible that the fees paid on the these network cannot reach the main-chain miners, which leaves miners starving. If yes, how much percent do you think will be given to miners. A: 4) I don’t know, it will depend on how often lightning network channels are opened and closed, and that depends on how people choose to use lightning. Moving transactions off the main chain and on to the lightning network should mean less fees for miners, more for lightning network hubs. Hopefully it will also mean lower fees for users, which will make Bitcoin more popular, drive up the price, and make up for the lower transaction fees paid to miners. Q: 5) The concept of lighting network and sidechains have been out of one or two years already, when do you think they will be fully deployed. A: 5) Sidechains are already “fully deployed” (unless you mean the version of sidechains that doesn’t rely on some trusted gateways to move bitcoin on and off the sidechain, which won’t be fully deployed for at least a couple of years). I haven’t seen any reports of how successful they have been. I think Lightning will take longer than people estimate. Seven months ago Adam Back said that the lightning network might be ready “as soon as six months from now” … but I would be surprised if there was a robust, ready-for-everybody-to-use lightning-capable wallet before 2018. Q: 6)Regarding the hard fork, Core team has assumed that it will cause a chain-split. (Chinese miners are very intimitated by this assumption, I think this is the major reason why most of the Chinese mining pools are not switching to Classic). Do you think Bitcoin will have a chain-split? A: 6) No, there will not be a chain split. I have not talked to a single mining pool operator, miner, exchange, or major bitcoin business who would be willing to mine a minority branch of the chain or accept bitcoins from a minority branch of the main chain. Q: 7) From your point of view, do you think there is more Classic supporters or Core supporters in the U.S.? A: 7) All of the online opinion pools that have been done show that a majority of people worldwide support raising the block size limit.
Q: Which is more in line with the Satoshi’s original roadmap, Bitcoin Classic or Bitcoin Core? How to make mining pools support and adopt Bitcoin Classic? A: Bitcoin Classic is more in line with Satoshi’s original roadmap. We can’t make the mining pools do anything they don’t want to do, but they are run by smart people who will do what they think is best for their businesses and Bitcoin.
Q: Do you have any solution for mining centralization? What do you think about the hard fork of changing mining algorithms? A: I have a lot of thoughts on mining centralization; it would probably take ten or twenty pages to write them all down. I am much less worried about mining centralization than most of the other developers, because Satoshi designed Bitcoin so miners make the most profit when they do what is best for Bitcoin. I have also seen how quickly mining pools come and go; people were worried that the DeepBit mining pool would become too big, then it was GHash.io… And if a centralized mining pool does become too big and does something bad, the simplest solution is for businesses or people to get together and create or fund a competitor. Some of the big Bitcoin exchanges have been seriously considering doing exactly that to support raising the block size limit, and that is exactly the way the system is supposed to work-- if you don’t like what the miners are doing, then compete with them! I think changing the mining algorithm is a complicated solution to a simple problem, and is not necessary.
Q: Last time you came to China, you said you want to "make a different". I know that in USA the opposition political party often hold this concept, in order to prevent the other party being totally dominant. Bitcoin is born with a deep "make a different" nature inside. But in Chinese culture, it is often interpreted as split “just for the sake of splitting”, can you speak your mind on what is your meaning of "make a different"? A: I started my career in Silicon Valley, where there is a lot of competition but also a lot of cooperation. The most successful companies find a way to be different than their competitors; it is not a coincidence that perhaps the most successful company in the world (Apple Computer) had the slogan “think different.” As Bitcoin gets bigger (and I think we all agree we want Bitcoin to get bigger!) it is natural for it to split and specialize; we have already seen that happening, with lots of choices for different wallets, different exchanges, different mining chips, different mining pool software.
Q: 1) The development of XT and Classic confirmed my thoughts that it is nearly impossible to use a new version of bitcoin to replace the current bitcoin Core controlled by Blockstream. I think we will have to live with the power of Blockstream for a sufficient long time. It means we will see the deployment of SegWit and Lighting network. If it really comes to that point, what will you do? Will you also leave like Mike Hearn? A: 1) With the development of Blockchain, bitcoin will grow bigger and bigger without any doubts, And also there will be more and more companies related to the bitcoin network. When it comes to money, there will be a lot of fights between these companies. Is it possible to form some kind of committee to avoid harmful fights between these companies and also the situation that a single company controlling the direction of the bitcoin development? Is there any one doing this kind of job right now? Q: 2) My final question would be, do you really think it is possible that we can have a decentralized currency? Learning from the history, it seems like every thing will become centralized as long as it involves human. Do you have any picture for a decentralized currency or even a society? Thanks. A: 2) I think you might be surprised at what most people are running a year or three from now. Perhaps it will be a future version of Bitcoin Core, but I think there is a very good chance another project will be more successful. I remember when “everybody” was running Internet Explorer or Firefox, and people thought Google was crazy to think that Chrome would ever be a popular web browser. It took four years for Chrome to become the most popular web browser. In any case, I plan on working on Bitcoin related projects for at least another few years. Eventually it will become boring or I will decide I need to take a couple of years of and think about what I want to do next. As for fights between companies: there are always fights between companies, in every technology. There are organizations like the IETF (Internet Engineering Task Force) that try to create committees so engineers at companies can spend more time cooperating and less time fighting; I’m told by people who participate in IETF meetings that they are usually helpful and create useful standards more often than not. Finally, yes, I do think we can have a “decentralized-enough” currency. A currency that might be controlled at particular times by a small set of people or companies, but that gives everybody else the ability to take control if those people or businesses misbehave.
Hi Gavin, I have some questions: Q: 1) I noticed there are some new names added to the classic team list. Most people here only know you and Jeff. Can you briefly introduce some others to the Chinese community? A: 1) Tom Zander has been acting as lead developer, and is an experienced C++ developer who worked previously on the Qt and Debian open source projects. Pedro Pinheiro is on loan from Blockchain.info, and has mostly worked on continuous integration and testing for Classic. Jon Rumion joined recently, and has been working on things that will make life for developers more pleasant (I don’t want to be more specific, I don’t want to announce things before they are finished in case they don’t work out). Jeff has been very busy starting up Bloq, so he hasn’t been very active with Classic recently. I’ve also been very busy traveling (Barbados, Idaho, London and a very quick trip to Beijing) so haven’t been writing much code recently. Q: 2) if bitcoin classic succeeded (>75% threshold), what role would you play in the team after the 2MB upgrade finished, as a leader, a code contributor, a consultant, or something else? A: 2)Contributor and consultant-- I am trying not to be leader of any software project right now, I want to leave that to other people who are better at managing and scheduling and recruiting and all of the other things that need to be done to lead a software project. Q: 3) if bitcoin classic end up failed to achieve mainstream adoption (<75% 2018), will you continue the endeavor of encouraging on-chain scaling and garden-style growth of bitcoin? A: 3) Yes. If BIP109 does not happen, I will still be pushing to get a good on-chain solution to happen as soon as possible. Q: 4) Have you encountered any threat in your life, because people would think you obviously have many bitcoins, like what happened to Hal Finney (RIP), or because some people have different ideas about what bitcoin's future should be? A: 4) No, I don’t think I have received any death threats. It upsets me that other people have. Somebody did threaten to release my and my wife’s social security numbers and other identity information if I did not pay them some bitcoins a couple of years ago. I didn’t pay, they did release our information, and that has been a little inconvenient at times. Q: 5) Roger Ver (Bitcoin Jesus) said bitcoin would worth thousands of dollars. Do you have similar thoughts? If not, what is your opinion on bitcoin price in future? A: 5) I learned long ago to give up trying to predict the price of stocks, currencies, or Bitcoin. I think the price of Bitcoin will be higher in ten years, but I might be wrong. Q: 6) You've been to China. What's your impression about the country, people, and the culture here? Thank you! A: 6) I had a very quick trip to Beijing a few weeks ago-- not nearly long enough to get a good impression of the country or the culture. I had just enough time to walk around a little bit one morning, past the Forbidden City and walk around Tianmen Square. There are a LOT of people in China, I think the line to go into the Chairman Mao Memorial Hall was the longest I have ever seen! Beijing reminded me a little bit of London, with an interesting mix of the very old with the very new. The next time I am in China I hope I can spend at least a few weeks and see much more of the country; I like to be in a place long enough so that I really can start to understand the people and cultures.
Q: Dear Gavin, How could I contact you, we have an excellent team and good plans. please confirm your linkedin. A: Best contact for me is [email protected] : but I get lots of email, please excuse me if your messages get lost in the flood. 15. satoshi Q: Gavin, you've been both core and classic code contributor. Are there any major differences between the two teams, concerning code testing (quality control) and the release process of new versions? A: Testing and release processes are the same; a release candidate is created and tested, and once sufficiently tested, a final release is created, cryptographically signed by several developers, and then made available for download. The development process for Classic will be a little bit different, with a ‘develop’ branch where code will be pulled more quickly and then either fixed or reverted based on how testing goes. The goal is to create a more developer-friendly process, with pull requests either accepted or rejected fairly quickly.
I am a bitcoin enthusiast and a coin holder. I thank you for your great contribution to bitcoin. Please allow me to state some of my views before asking:
I'm on board with classic
I support the vision to make bitcoin a powerful currency that could compete with Visa
I support segwit, so I'll endorse whichever version of bitcoin implementation that upgrades to segwit, regardless of block size.
I disagree with those who argue bitcoin main blockchain should be a settlement network with small blocks. My view is that on the main chain btc should function properly as a currency, as well as a network for settlement.
I'm against the deployment of LN on top of small block sized blockchain. Rather, it should be built on a chain with bigger blocks.
I also won’t agree with the deployment of many sidechains on top of small size block chain. Rather, those sidechains should be on chain with bigger blocks.
With that said, below are my questions: Q: 1) If bitcoin is developed following core's vision, and after the 2020 halving which cuts block reward down to 6.125BTC, do you think the block transaction fee at that time will exceed 3BTC? A: 1) If the block limit is not raised, then no, I don’t think transaction fees will be that high. Q: 2) If bitcoin is developed following classic's vision, and after the 2020 halving which cuts block reward down to 6.125BTC, do you think the block transaction fee at that time will exceed 3BTC? A: 2) Yes, the vision is lots of transactions, each paying a very small fee, adding up to a big total for the miners. Q: 3) If bitcoin is developed following core's vision, do you think POW would fail in future, because the mining industry might be accounted too low value compared with that of the bitcoin total market, so that big miners could threaten btc market and gain profit by shorting? *The questioner further explained his concern. Currently, its about ~1.1 billion CNY worth of mining facilities protecting ~42 billion CNY worth (6.5 Billion USD) of bitcoin market. The ratio is ~3%. If bitcoin market cap continues to grow and we adopt layered development plan, the mining portion may decrease, pushing the ratio go even down to <1%, meaning we are using very small money protecting an huge expensive system. For example, in 2020 if bitcoin market cap is ~100 billion CNY, someone may attempt to spend ~1 billion CNY bribe/manipulate miners to attack the network, thus making a great fortune by shorting bitcoin and destroying the ecosystem. A: 3) Very good question, I have asked that myself. I have asked people if they know if there have been other cases where people destroyed a company or a market to make money by shorting it -- as far as I know, that does not happen. Maybe because it is impossible to take a large short position and remain anonymous, so even if you were successful, you would be arrested for doing whatever you did to destroy the company or market (e.g. blow up a factory to destroy a company, or double-spend fraud to try to destroy Bitcoin). Q: 4) If bitcoin is developed following classic's vision, will the blocks become too big that kill decentralization? A: 4) No, if you look at how many transactions the typical Internet connection can support, and how many transactions even a smart phone can validate per second, we can support many more transactions today with the hardware and network connections we have now. And hardware and network connections are getting faster all the time. Q: 5) In theory, even if we scale bitcoin with just LN and sidechains, the main chain still needs blocks with size over 100M, in order to process the trading volume matching Visa's network. So does core have any on-chain scaling plan other than 2MB? Or Core does not plan to evolve bitcoin into something capable of challenging visa? A: 5) Some of the Core developer talk about a “flexcap” solution to the block size limit, but there is no specific proposal. I think it would be best to eliminate the limit all together. That sounds crazy, but the most successful Internet protocols have no hard upper limits (there is no hard limit to how large a web page may be, for example), and no protocol limit is true to Satoshi’s original design. Q: 6) If (the majority of) hash rate managed to switch to Classic in 2018, will the bitcoin community witness the deployment of LN in two years (~2018)? A: 6) The bottleneck with Lightning Network will be wallet support, not support down at the Bitcoin protocol level. So I don’t think the deployment schedule of LN will be affected much whether Classic is adopted or not. Q: 7) If (majority) hash rate upgraded to blocks with segwit features in 2017 as specified in core's roadmap, would classic propose plans to work on top of that (blocks with segwit)? Or insist developing simplified segwit blocks as described in classic's roadmap? A: 7) Classic will follow majority hash rate. It doesn’t make sense to do anything else. Q: 8) If most hash rate is still on core's side before 2018, will you be disappointed with bitcoin, and announce that bitcoin has failed like what Mike did, and sell all your stashed coins at some acceptable price? A: 8) No-- I have said that I think if the block size limit takes longer to resolve, that is bad for Bitcoin in the short term, but smart engineers will work around whatever road blocks you put in front of them. I see Bitcoin as a long-term project. Q: 9) If we have most hash rate switched to classic's side before 2018, what do you think will be the fate of Blockstream company? A: 9) I think Blockstream might lose some employees, but otherwise I don’t think it will matter much. They are still producing interesting technology that might become a successful business. Q: 10) If we have most hash rate still on core's side before 2018, what do you think will be the fate of Blockstream company? A: 10) I don’t think Blockstream’s fate depends on whether or not BIP109 is adopted. It depends much more on whether or not they find customers willing to pay for the technology that they are developing. Q: 11) If we have most hash rate still on core's side before 2018, what do you think will be the fate of companies that support classic, such as Coinbse, bitpay, and Blockchain.info? A: 11) We have already seen companies like Kraken support alternative currencies (Kraken supports Litecoin and Ether); if there is no on-chain scaling solution accepted by the network, I think we will see more companies “hedging their bets” by supporting other currencies that have a simpler road map for supporting more transactions. Q: 12) If we have most hash rate switched to classic's side before 2018, will that hinder the development of sidechain tech? What will happen to companies like Rockroot(Rootstock?) ? A: 12) No, I think the best use of sidechains is for things that might be too risky for the main network (like Rootstock) or are narrowly focused on a small number of Bitcoin users. I don’t think hash rate supporting Classic will have any effect on that. Q: 13) Between the two versions of bitcoin client, which one is more conducive to mining industry, classic or core? A: 13) I have been working to make Classic better for the mining industry, but right now they are almost identical so it would be dishonest to say one is significantly better than the other.
Q: Gavin, can you describe what was in your mind when you first learned bitcoin? A: I was skeptical that it could actually work! I had to read everything I could about it, and then read the source code before I started to think that maybe it could actually be successful and was not a scam.
hi guys. i have been mining for the last 6 months and thought will share some of my experience with you guys. initially started out using slush's pool. then moved on to eligius, btc guild. finally i was mining with ghash and by far the best experience i have had mining has been with ghash. However, while experimenting trying to set up a solo mining pool for my mining needs, i stumbled upon p2pool. i was already running a bitcoin node at home and setting up a p2pool node was fairly easy. With ghash approaching 51% i decided to give p2pool a try. Been mining on p2pool since 31st May and during that time 14 blocks have been found by P2Pool as compared to about 20 that should have been found for the average hash rate on P2Pool. Lots of donations were received during this period especially the last 7 days. on average the earnings by donations compared to mining was about 4-5% for me. The hash rate on P2Pool stays about 0.5 to 0.6 Ph/s as compared to about 40 Ph/s on Ghash. Though i read lots of posts asking people to shift to P2Pool during the last week, i have not seen the hash rate have any significant change. I have lost about 30 percent of my potential earnings mining on P2Pool which i would have easily made on Ghash and i have been tempted to go back to Ghash but mining on P2Pool feels more pure to me and i feel i am going to stick to P2Pool and hope for more people to join this pool so that variance can reduce to a more acceptable level.
Hello cryptocurrency lovers! Welcome to Coin-a-Year, the laziest series yet in the Coin-a-Day publishing empire. This year's coin is Nyancoin (NYAN). I originally covered Nyancoin in an article here in /cryptocurrency published January 4th, 2015. Without (much) further ado, I'm going to include the original report next, unmodified. This is unlike my Coin-a-Week series, where I use strikeout and update in-text. Because this is going to be a longer update, I'll just make all further comments and updates below, just realize that all information below is as of January 4th, 2015 and thus is more than a year out of date as of posting now, at the end of February 2016. Since I use horizontal rules as internal dividers in the original post, I'll use a double horizontal rule to divide the original text from this prelude and the following update. Coin-a-Day Jan 4th Welcome to the fourth installment of Coin-a-Day! To see convenient links to the introduction and the previous entries, please see /coinaday. Today's coin is Nyancoin (NYAN). Summary • ~173.6 million available currently ; 337 million limit  • All-time high: ~0.000024 BTC on February 16, 2014  • Current price: ~3 satoshi  • Current market cap: ~$1,275  • Block rate (average): 1 minute   • Transaction rate: ~25? / last 24 hours; estimated $3-4  • Transaction limit: 70 / second  • Transaction cost: 0 for most transactions  • Rich list: ???  • Exchanges: Cryptsy  • Processing method: Mining  • Distribution method: proof-of-work block rewards and 1% premine for "bounties, giveaways & dev support"   • Community: Comatose  • Code/development: https://github.com/nyancoin-release/nyancoin ; there hasn't been a released code change in 10 months. The new developer has talked about some changes, but has not made a new release. He has given advice about how to keep the network running and operate the client.  • Innovation or special feature: First officially licensed cryptocurrency (from Nyancat) ; "zombie"-coin  Description / Community: So you're probably wondering why in the world we're talking about a coin which has been declared dead and already written off. I actually first selected this coin to illustrate a "deadcoin", but the more I dug into it, the more I was amazed at the shambles I discovered. I am combining the description and community sections for this coin, because the community (or lack thereof) is the central issue for Nyancoin. Substantially all, if not literally all, of the original infrastructure is gone. From the announcement post, the original website has expired. The nyan.cat site itself survives, but has no reference to the coin. The github repo remains, but then there was never much changed from the bitcoin/litecoin original. In fact, the COPYING file doesn't even list "Nyancoin Developers". None of the original nodes seem to be running anymore. @Nyan_Coin hasn't tweeted since July 6th. And that was just to announce posting an admittedly cute picture to facebook which makes a claim for a future which seems never to have developed. Of the original 15 pools, I think all are dead except p2pool, for which at least one node still supports NYAN. The original blockchain explorer, nyancha.in, is still running. The faucet is dead or broken. The original exchanges no longer list it (two of the three having died; SwissCEX having ended its trading as of the first of this year). And so forth. And yet:
[Of course, that scene finishes with knocking out the "recovering" patient so he can be taken away...not to mention the absurdity of including Monty Python in a financial article, but moving right along.] There is still just enough left to Nyancoin to keep it twitching, even if it is on life-support. Whether it's an individual node or whether it's a pool, there are blocks being produced at a steady rate as intended. Transactions are being processed. There is still a market. There is still a block explorer. And there is a dev. It is like a case study in the absolute minimum necessary to keep a coin alive. The most likely outcome is almost certainly a final collapse when one critical piece or another of the infrastructure goes away. And yet in the meantime, a person can own a million NYAN for $8 , and then move this coin quickly and easy, albeit with no particular external demand. It's like the world's most hyped testnet. I think this case presents an interesting example of what happens to an altcoin when its initial support dries up. NYAN coin is more fortunate than some, actually, as there are some where there are no longer any nodes running it nor the original announcement thread (in fact, there was actually a second Nyancoin launched around the same time. But it died hard and its original announcement thread was deleted and at this point I would have no idea how to access it; so "Nyancoin" thus illustrates how hard a coin can die (Nyancoin 2) as well as how it can hang around despite being proclaimed dead, with far more justification behind that pronouncement than there has been for bitcoin (NYAN) ). Footnotes  http://coinmarketcap.com/currencies/nyancoin/  https://bitcointalk.org/index.php?topic=402085.0 Regarding the premine, it's unclear to me where this money is now, since the original poster hasn't been active on BCT since May and the original site is down. However, given that it's only 1%, and about $25 in value right now, there seem to be more significant concerns for NYAN.  http://nyancha.in/chain/Nyancoin - Nyan blockchain explorer; blocks are somewhat inconsistent but somewhere around the 1 minute average  There doesn't seem to be anything automatically doing these stats, so I did visual inspection on about 1500 blocks (about one day) excluding the block generation reward (~250k/day). Most blocks are otherwise empty. I counted about 24 transactions or so scrolling through, with an outlier around 300k NYAN and another around 100k NYAN. In total, about 500k NYAN, excluding the block rewards. This is very approximately $3-4.  Nyancoin is a basically unmodified, slightly out-of-date bitcoin as far as code goes, and ignoring the change in block rate and total coin supply, as well as the difficulty retarget after every block. So for purposes of estimating maximum possible transaction throughput, I start with bitcoin's estimated 7 transactions per second, and multiply by 10 for having a block on average every minute rather than every 10 minutes. In any event, this limit is not likely to be reached in the foreseeable future.  Like bitcoin, transaction fees appear to be optional in Nyancoin. Unlike bitcoin, there is almost no transaction volume, and coins tend to sit for a relatively long time before being moved. So zero-fee transactions appear to be the norm from looking at a couple transactions on the block explorer.  I couldn't find one. See the disclosure section of this article: your humble correspondent is likely represented in some way on a top 100 if one were to be made or if one exists, despite not holding it directly, depending on how the exchange holds it.  I could not find any other exchanges still listing Nyancoin. SwissCex appears to have disabled it as of a couple days ago. Cryptsy has a notice that the NYAN/BTC market will be closing, but its NYAN/LTC market appears strong.  Essentially all of the original sites, pools, faucets, etc. are dead and there has been very little to replace it. There is basically a single node, or perhaps a very few, which are running the blockchain. However, there is a developer still trying to hold things together, maxvall_dev, maxvall on BCT. He is the last hope for the NYAN.  https://bitcointalk.org/index.php?topic=597877.0 This is the thread where maxvall took over as dev, and it also discusses switching to PoS, which hasn't happened as far as I know.  "zombie"-coin: Not to be confused with ZMB (my god, does it ever end?). This is my term to describe a coin which is "undead": by rights it should be dead. And yet it's still walking around and acting like it's alive. What is it? What's going on? It's quite debatable whether this gives it any special value, but I find it an interesting state, and it's why this was chosen for early coverage. There are plenty of actually popular and successful coins, and we will go onto covering more normal selections; we're looking for variety rather than repetition. But I think this is an interesting example for what can go wrong, and yet in the midst of that, how little it takes for a coin to survive. In fact, it's almost like an alternate history bitcoin to me; this shows the concept that "it was run on one computer before; it can be run on one computer again" to some extent. And there are even some strange pragmatic benefits as well, like having no competition for getting a transaction into a block and thus zero transaction fees.  And, in fact, the author chose to do so today, spending about 0.03 BTC for about 1 million NYAN. Additional Reading • /nyancoins - Like NYAN: mostly dead, but not quite • http://nyan-coin.org/ - new official website • BCT thread listing nodes, xpool (p2pool), for mining information. • americanpegasus predicting in February that NYAN will hit $1; always an entertaining read Giveaway Instead of a challenge today, since NYAN has enough challenges, I decided I would give away 10,000 NYAN to at least the first ten people who ask for it. This still remains at my discretion, but honestly, if you really want, say, 50,000 NYAN and create four new accounts to do so, I'll probably be too amused to say no. I don't expect to get ten requests. If I get more, I'll probably still fulfill them, but as with everything else, this is left to my whim. Donations and Disclosure Okay, this is an important one today because of the tiny market here. I actually hold less USD value in NYAN than in BTC, DOGE, and PPC (although my value in PPC might be about equivalent actually), but I hold more of the total market in NYAN than any of those three. And I'll probably be buying more. So I have a conflict of interest in writing this article. I am not providing financial advice and I do not make any recommendations of any sort on any matters. Make your own decisions; do your own research. Please, I do not want to hear about anyone doing anything "on my advice." I am not offering advice. I personally hold just over 1 million NYAN on Cryptsy right now. Perhaps it would be better if I didn't write any articles about anything I were invested inspeculating on, but I started this series for my own education to further my speculation, so unfortunately, dear reader, your needs come second to my own. tanstaafl; you get what you pay for, and I'm giving you my thoughts. If by some strange quirk of fate you actually own NYAN and enjoyed this article and wished to donate some to me, K7Ho9HghBF6xWwS6JsepE6RAEPyAXbsQCV is mine (first non-empty account I've posted; transferred 1000 NYAN into here earlier from Cryptsy to test that the network and my wallet were actually working). Thank you all for reading and commenting! I've already learned a lot from this process and I look forward to more! Upcoming coins: • January 5th: Nxt • January 6th: Darkcoin • January 7th: Namecoin I'll use alphabetic labeling for footnotes in the updates to avoid any confusion with the footnotes in the original. For simplicity, unchanged items, like the 337 million limit and the 1 minute will not be mentioned, and we'll start with the summary changes. Updates: Summary
Community: We're not quite dead yet; in fact, I think we're getting better! [f]
Code/Development: I have an early draft of NYAN2, but I'm about six months past my initial goal for having it available to use. Life/work/lack of build machine/procrastination. NYAN2 will be a rebase onto a modern LTC codebase which will soft fork to fix a current vulnerability to a fork bug. For now, the network still runs on the same code that it did when I wrote the first article.
Discussion I'm going to consider the community first, since I pointed it out as the weakness and central topic in the last one, then talk about the technical situation briefly, and then review the financial results. The community has been excellent, if I do say so myself. We've got working infrastructure going thanks to the contributions of many Nekonauts (see [f]). Some original Nekonauts have returned or at least popped in from time to time, and new ones like myself have found Nyancoin (I would say given what I wrote in the original, I was still a skeptic of it at that point. Not that skeptics can't be Nekonauts, but I think I'd put my conversion to the cult of nyan shortly after writing that, even though I was already a nillionaire then for the heck of it.) While I do look forward to seeing the community continue to grow in future years and consider that important, I don't think the community is our weakest point any longer; I think it's now our strongest point. I've tried to encourage the community's revival as best I could, including giving away tens of nillions in total, and lots of long rambling articles on my views on ethics and philosophy and frankly it's worked better than I would've really expected (or at least it has coincided with an effective recovery of the community). The community also helped me through at least a couple hard times personally in there as well. The technical situation in Nyancoin is mostly unchanged but slightly improved, although with two additional known vulnerabilities. It's unchanged in that it's the same client. It's improved in that we have an active nyanchain explorer host (nyan.space), and we have a public draft of a plan for a soft forking security fix update in the near future (hopefully by the end of March (although I've slipped these deadlines before and may well miss March for release by a bit, I do think I'm inching closer now and then)). The most serious vulnerability is to forking. This is the bug which hit Peercoin if I recall correctly. NYAN2 is intended to solve this through its soft fork from the LTC fix upstream (from the BTC fix upstream). In the meantime, we've been lucky we haven't been attacked. The tiny marketcap probably helps with not being a particularly attractive attack target. We're not exactly about to pay ransom to move faucet outputs. But that's no excuse; we want this fixed and should have it finally done "soon" (tm). The less serious vulnerability is to a time warp attack in the difficulty function (Kimoto Gravity Well), which relates to general weaknesses it has and issues we've had with large gaps in the block chain because of spikes in the difficulty function causing it to be unprofitable and driving away most of the hash, and then low difficulty and price rise making it attractive to more hash, creating a spike and causing it again. While this is irritating, the chain still works, even if there are fits and starts at times. An important part of the reason I can get away with this is because there is at least one Nekonaut-supporting miner, CartmanSPC, who rescues us from time to time, and did so during the course of this article being written. We have a bunch of pools, but sometimes the hash just isn't there to get us unstuck when the difficulty goes high enough. Another part of the reason I consider it not an especially serious issue is because there's a workaround which works for me (classic bad developer logic): I use a large transaction fee (generally 337 NYAN, although I might have halved it after the most recent halving, I'll probably use 337 again) on my personal wallet by default. If necessary, I use a couple of them. It can make NYAN profitable to mine again despite the higher difficulty and "unstick" the chain. The difficulty function can go back down again in the next block if the gap has been long enough, so that can be enough to keep it going again for a while (although it can also get stuck again irritatingly fast at times). A fix for this will be putting in a better difficulty function for NYAN3, which will require a hard fork. This is tentatively scheduled for feature freeze around the middle of this year, coding to follow, activation sometime early 2017. Financial has been our most disappointing performance. A graph of the 1 year performance right now on coinmarketcap looks pretty sad, showing our fall from a little over 60 satoshi down to around 7 satoshi now. We rose too high, too fast, and I didn't stick with the safe high paying job like a sane person. Instead I hit the road, went to jail, and worked minimum wage. That doesn't sound like a sentence from a cryptocurrency financial review, does it? But the performance of NYAN since the article has been the story of my personal finances, which is the story of my life since then. So, autobiographical coinaday interlude, trying to keep it generally to the most salient points. Well, in 2014 I had been on my way home to Minnesota from California when I was pulled over leaving Eureka, Nevada for speeding (got sloppy and went 45 approaching the 45 sign and thus technically still in the 35; bored cop seeing out-of-state plates). My vehicle reeked of weed, what with having been in Mendocino County previously with no intention of traveling out of the county much less state anytime soon but family emergency brought me back, and the end result was a citation for possession of cannabis and paraphernalia along with the speeding. Fast forward to the beginning of 2015, I'm settled into a good software position and start looking more at cryptocurrency in my spare time. I write the coin-a-day series for a bit and then got annoyed and quit after a while when trying to do one a day on top of an actual job was too much for me (along with some annoyance over criticism; I can be rather thin-skinned at times). But I had gotten interested in Nyancoin, and started buying it up more and more with extra money I was making. And then comes the crash. I had to stop putting as much in as I realized that where I was living and what I was working on wasn't going to work out for me and I needed to figure something else out. So, as I seem wont to do, I went on a roadtrip. I quit my job. And I went back for the court date for my citations and refused to pay, instead spending 10 days in jail rather than pay ~$1400 (I actually had the money in cash available to me if I chose to pay as a backup if I chickened out, but the judge annoyed me enough that I really preferred to be jailed instead of paying, as stupid as that sounds since I'm quite sure the judge didn't care in the least one way or another). After that, I went back to roadtrip lifestyle for a while. It was a nice period. A lot of beautiful scenery; a lot of reading. Eventually, I busted up my car pretty badly...a couple times actually, the second time for good. Fast forwarding through the rest of the year, I worked a couple minimum wage jobs to pay bills and avoid cubicle life and kill some time until I figured out what I was going to do next. Just recently I quit as delivery boy after getting a speeding ticket (I swear, I'm not as horrible of a driver as this makes me sounds, although I have had a bad tendency to speed in the past, which I really have curbed to almost nothing; but I'm clearly not good enough) and am currently writing a Coin-a-Year article with a friend's incentive and applying to do documentation and development with the Nu project. Okay, so what did any of that have to do with NYAN? Well, it's the mess of a life that has led to the fall of the price from 60 satoshi to 7 satoshi. If instead my life history for the time since the article had been simply "I was happily employed writing software", then I don't believe we would have dropped below 20 satoshi. It's easy to see in hindsight. If anyone can lend me a time machine, I'm sure I can get some condensed instructions which should improve performance significantly. Otherwise, just going to have more chalked up for the "character building" tally. So, lessons learned if you are the major buy support for your coin: you need long-term reserves. Whatever you put in bids can be taken out in a moment by a dump for no apparent reason. This is particularly true if you may be quitting your cushy, high-paying job and wandering around without income for an extended period of time. Rather obvious, but hey, maybe someone else can learn from my mistakes. If I'd been bidding as cautiously as I am now from the beginning, I think the price would probably be somewhere from 10-20 satoshi now instead of around 7 satoshi. It's especially unfortunate given that I wanted to be able to demonstrate the more consistent growth possible building a stable store of value, as opposed to the pump and dumps common in altcoins. And instead we had a pump-and-dump looking graph ourselves after I bid up higher than I was able to sustain, and a large (10+ nillion) instadump crashed the market all the way back down to 1 satoshi momentarily. We've had a few large (2+ nillion) dumps since, but nothing that large. We haven't generally had that large of bids though either. It's hard to know when I've exhausted the supply at a price level, when it sometimes waits for a couple weeks or even more and then fills all the bids at once. But I want to maximize the minimum price paid because I think that's important for building confidence in a store of value long-term, which is one of my core goals for NYAN. At the same time, we're still up from the lowest parts of the floor and where I found it. Since I own about 30% [g], the very cheapest supply has been taken off the market. I plan to keep on buying up "cheap NYAN" as much as I can. I've bought up to 60 satoshi before, I'll probably buy up that high this time around. I've got a token 100,000 NYAN ask at 300 satoshi; I hope never to sell lower. Conclusions Now I try to wrap it all together as if I saw this all coming and am the wise expert, despite having had about 90% drop in price in the last year after bidding too high. My original concept was taking the "minimum viable coin" and reviving it to a powerhouse as a textbook example in how to do it. Part of my core concept in this is the arbitrariness of value: throughout history, humans have chosen any number of things as a store of value for the time: salt, large rocks, certain metals, disks, marked sticks, and so forth. While there has generally been a certain logic in the choice, in that there is a locally restricted supply in one way or another, and so forth, from the perspective of other centuries or cultures the choices can seem quite strange. Growing up, I was always struck by how strange the notion of salt being limited and valuable seemed in a world where people were trying to reduce intake and large amounts could be bought for trivial sums. And yet, a key nutrient necessary for life fundamentally makes more sense as being valuable than notched sticks or printed paper or a piece of plastic with some encoded information. Humans have perpetually come up with stranger and stranger ways of storing and transferring value. Each new step, as always, comes with its own disadvantages and, frankly, has generally appeared nonsensical at best and fraudulent at worst to the status quo. Which doesn't mean that each new attempt is valuable. The gold bugs always like to point out that every fiat currency ultimately returns to its true value of zero. And the skeptics of cryptocurrency argue that all cryptocurrencies will eventually return to their true value of zero. It's certainly possible. And it's possible the USD will hyperinflate someday. I tend to try the moderate view for a plausible guess of the future. By that type of logic, I would guess that over the course of decades, USD will in general lose value, and cryptocurrency will tend to slowly gain value. That might not seem the moderate view, but USD not losing value over decades would be truly shocking. And hyperinflation has been predicted since the USD went off the gold standard, or before. So some amount of inflation less than hyperinflation seems like the safe guess (but then, the Titanic arriving would also have seemed like the safe guess to me). And with cryptocurrency, I think it's clear by now the technology will continue to survive. So my first question is with what overall value as a market? It could go down, of course, but that seems unlikely in an already small, young market. Even if all the current crop die off and are replaced, whatever cryptocurrencies are around should be able to do better than a handful of billion in market cap in my view. I believe that cryptocurrency has a bright future ahead of it. The best coins should ultimately survive and thrive. But I've been wrong on most of my major calls so far, like for instance when I thought BTC was over-priced around $5-$10. I think Nyancoin can have an important role to play in the future of cryptocurrency in the years and decades to come, but it's a massively speculative long-shot. See also Nyancoin risks document. But like Linus Torvalds' autobiography, I try to keep "Just for Fun" as a core motto and principle. It's makes for a good hobby project because there will always be more to work on, with a core community motto of TO INFINITY AND BEYOND! Disclaimers / Sponsorship: As I said before:
I am not providing financial advice and I do not make any recommendations of any sort on any matters. Make your own decisions; do your own research. Please, I do not want to hear about anyone doing anything "on my advice." I am not offering advice.
And I'll reiterate that I own about 30% [g] of the current supply of NYAN, which makes me by definition maximally biased. Also, I'm not sure what's up with the address from the first post. It doesn't show up in my current wallet as a recognized address. So, anyhow, don't send there. :-) If you'd like to donate, please consider sponsoring a coin-a-day or coin-a-week article. This is the first sponsored article. This Coin-a-Year article has been brought to you by spydud22 's generous patronage. I'd been meaning to do a Coin-a-Week article on Nyancoin for a while, but between wanting to "wait until the price recovered a bit" and general procrastination, then it seemed like it would make a good Coin-a-Year article, and then I wanted to wait until the price recovered a bit more...anyhow, so thank you spydud22, for causing me to finally do this. :-) Footnotes
[a] nyan.space/chain/Nyancoin ; as of block 1091430, 263738786.71890615 NYAN outstanding. This is slightly over 50% more than the last report, which is what we would expect, since it had existed for about a year then, and has approximately annual halvings. The first year generated about 50% of total supply; the second year generated about 25% of total supply. We should expect in a year to have about 17% (one-sixth) more than we have now.
[b] https://www.cryptopia.co.nz/Exchange?market=NYAN_BTC ; this is the only market reflected in coinmarketcap and it is the primary one on which I trade. Cryptopia also has other base pairs which operate at significantly higher spreads (lower bids; higher asks) and have minimal volume. In the time since the last report, NYAN has traded as high as 60 satoshi (and briefly a little higher at times), but over the last almost twelve months since a peak about a year ago, the price has been generally declining overall, as a gross oversimplification of a lot of movements. This has been an effect of me not being able to keep buying as much and there being large dumps I wasn't expecting from time-to-time. Now I'm taking the approach of building large (one or more nillion (million NYAN)) bids on each price as I slowly work my way back up again in order to be able to handle possible dumps with less price shock.
[c] coinmarketcap.com/currencies/nyancoin/ ; as noted in [b], this only reflects the /BTC basepair on Cryptopia but that's where most of the volume is anyhow. Of course, the market is also not particularly liquid since I'm the primary buyer and have rather limited means currently.
[d] I haven't setup a script to count this yet, among many things on my to-do list for someday, so I went through by hand from what was the then-latest block of 1091430 on nyan.space back to 1089766 which was the first block generated less than 24 hours before. There was actually a three and a half hour block gap at that point, such that the next prior block was about 24 hours and 15 minutes before 1091430 while 1089766 was only about 20 hours and 45 minutes prior, and has a disproportionate number of transactions and value compared to a typical block (8 and ~313,000 NYAN respectively) from the build-up during the gap. But since that gap conveniently started right about at the start of the 24 hour period, doesn't really skew our results here.
Note that there are often times where the UTXO created during one transaction during the day is spent during a later transaction in the day. This can be considered the "same" Nyancoin being "spent" twice in the same day in our total. But in practice, I believe what's happening here is the faucet is breaking off small (10-50 NYAN) pieces from a larger (~40,000 NYAN) chunk, and so that pops up a bunch of times. So the total NYAN blockchain volume as counted for this topline number should not be interpreted as "NYAN spent in the day" but "NYAN moved on the chain", where the "same coin" can move many times. So it's a very easily gamed metric and not a strong / resistant metric like the market price tends to be (at least relatively speaking), but it's a fun number to calculate and provides a little bit of information. The transaction count can also be easily inflated and certainly, for instance, having the faucet does generate transactions which are a very common transaction. And this is also just an arbitrary 24 hour period compared to a previous arbitrary 24 hour period. Nonetheless, I do think there's clearly a bit more activity on the Nyanchain, even though the typical block is still empty and the number of transactions and volume is still tiny compared to the major cryptocurrencies. Here's an arbitrary example of the faucet transactions Note the zero transaction fee, which I love that the miners support (the defaults are all quite low as well). Here's an example of what may be the smallest transaction by NYAN volume of the day; but no, I followed its small, spent output, and it led to this gem which also links to this. I have no idea what's going on here, but it's hilarious and I love it. How's that for microtransaction support? :-)
[e] Obviously Cryptsy went down. We had had more than enough red flags with Cryptsy (including one time where I was able to withdraw 6 nillion more than I had in my balance) and got onto Cryptopia. spydud22 basically accomplished that for us, although I helped out in the tail end of the campaigning.
[f] Our community is still small (I wish there were literally dozens of us!) but we've had valuable activity from multiple people, including, just as highlights, vmp32k who hosts nyan.space, a clone of the original nyancha.in, jwflame who created the excellent nyancoin.info intro site, with the awesome status page (which currently notes that "the last 500 blocks actually took 111 minutes, which is approaching the speed of light, causing the universe to become unstable"), KojoSlayer who runs the faucet and dice, spydud22 who got us on Cryptopia, and many other Nekonauts have made worthy contributions, and the Nekonauts mentioned have done more than just that listed. So while we are small, we are active at least from time to time and technically capable.
P2Pool scanner will provide you a list of nearest mining pool nodes for Bitcoin, Litecoin and DASH cryptocurrencies. Toggle navigation P2Pool scanner . Bitcoin P2Pool ; DASH P2Pool ; Litecoin P2Pool ; How to mine. Choose the node and start your miner: Donations are appreciated: Bitcoin; Litecoin; Dash; Address Location Fee Uptime Efficiency Hash rate Users Good shares Ping GWTL Version ... Hash Rate Allocation. Go with the Best Bitcoin Cash Mining Pool. The two pools that can be recommended if you are looking for decentralized pools are Multipool.us and P2Pool. The next pools are validating the most of the blocks with Bitcoin Core 0.11 or later versions: BTCC is basically a China-based exchange, a wallet, and a mining pool. It presently has around 15% of a total hash rate. Slush ... Welcome to btc.coinpool.pw:. The only Bitcoin P2Pool mining node with a personal share difficulty target based on address hash rate instead of average pool hash rate (based on P2Pool-N pull request). This provides optimal difficulty for each miner regardless your hashrate and provides smooth mining stats and predictable payout even for small GPU miners together with minimal rejected rate. With over 15% of the network hash rate at the time of writing, F2Pool is one of the biggest mining pools around. Based in China, the simple English interface ensures you won’t get confused. The company has been around for six years and has mined the most blocks in the history of Bitcoin with a total value of more than 1,000,000 BTC. F2Pool uses the Stratum mining protocol, which is also used ... P2pool uses two ports: one for p2p communication with the p2pool network, and another for both the web UI and for stratum communication with workers. For Bitcoin, those ports are 9333 (p2p) and 9332 (stratum/web). For Litecoin, they are 9326 (p2p) and 9327 (stratum/web). For Bitcoin Cash, they are 9349 (p2p) and 9348 (stratum/web).
How to mine $1,000,000 of Bitcoin using just a laptop ...
BITCOIN BREAKTHROUGH Series Join us Wecoa.org SUBSCRIBE FOR MORE HOW MUCH - http://shorturl.at/arBHL Nviddia GTX 1080 Ti - https://amzn.to/2Hiw5xp 6X GPU Mining Rig Case - https://bitcoinmerch.com/produc... Hi! New video about: Dollar dip meets hash rate boom 5 things to watch in Bitcoin this week Source: https://cointelegraph.com/news/dollar-dip-meets-hash-rate... LINKS FREE BITCOIN HASH RATE https://www.cryptomining.farm/signup/?referrer=59576B07ED6B0 https://demixmine.com/?ref=d98QYV https://btcprominer.life/356742 h... will you be able to mine bitcoin