RSK Bitcoin Merged Mining Returns to Miners Beats The ...
Was ist Merged Mining? Kannst du zwei Kryptos gleichzeitig ...
What is merged mining – Bitcoin & Namecoin – Litecoin ...
Everything you need to get mining with bitcoins Q/A format ...
Terracoin (TRC) is a person to person digital currency. It shares many similarities to Bitcoin in that it utilizes the SHA 256 algorithm and relies on the concepts outlined in Satoshi's white paper. Terracoin originated in late 2012 after a series of difficulties arose in other digital currencies. There will only be 42 million Terracoin produced. To learn about using and/or mining Terracoin visit the bitcointalk forum or the Terracoin website, Terracoin.io.
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/188.8.131.52 Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that. Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap. We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout. Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now. Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date. The transition height is also when the team requirement will be relaxed for the network.
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use. There are so many goodies here it is hard to summarize them all. I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures. The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
Network magnitude unit pinned to a static value of 0.25
Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
500 GRC research reward limit for a CPID's first stake
6-month expiration for unclaimed rewards
10-block spacing requirement between research reward claims
Rolling 5-day payment-per-day limit
Legacy tolerances for floating-point error and time drift
The need to include a valid copy of a CPID's magnitude in a claim
10-block emission adjustment interval for the magnitude unit
One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
Verification codes of pending beacons expire after 3 days
Self-service beacon removal
Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
Rain addresses derived from beacon keys instead of a default wallet address
Beacon expiration determined as of the current block instead of the previous block
The ability for developers to remove beacons
The ability to sign research reward claims with non-current but unexpired beacons
As a reminder:
Beacons expire after 6 months pass (180 days)
Beacons can be renewed after 5 months pass (150 days)
Renewed beacons must be signed with the same key as the original beacon
Magnitudes less than 1 include two fractional places
Magnitudes greater than or equal to 1 but less than 10 include one fractional place
A valid superblock must match a scraper convergence
Superblock popularity election mechanics
Yes/no/abstain and single-choice response types (no user-facing support yet)
To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
Burn fee for creating polls scaled by the number of UTXOs claimed
50 GRC for a poll contract
0.001 GRC per claimed UTXO
Burn fee for casting votes scaled by the number of UTXOs claimed
0.01 GRC for a vote contract
0.01 GRC to claim magnitude
0.01 GRC per claimed address
0.001 GRC per claimed UTXO
Maximum length of a poll title: 80 characters
Maximum length of a poll question: 100 characters
Maximum length of a poll discussion website URL: 100 characters
Maximum number of poll choices: 20
Maximum length of a poll choice label: 100 characters
Magnitude, CPID count, and participant count poll weight types
The ability for developers to remove polls and votes
[184.108.40.206] 2020-09-03, mandatory, "Fern"
Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
Implement project level rain for rainbymagnitude #1580 (@jamescowens)
Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
Provide fees collected in the block by the miner #1601 (@iFoggz)
Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
Implement zapwallettxes #1605 (@jamescowens)
Implements a global event filter to suppress help question mark #1609 (@jamescowens)
Add next target difficulty to RPC output #1615 (@cyrossignol)
Add caching for block hashes to CBlock #1624 (@cyrossignol)
Make toolbars and tray icon red for testnet #1637 (@jamescowens)
Add an rpc call convergencereport #1643 (@jamescowens)
Implement newline filter on config file read in #1645 (@jamescowens)
Implement beacon status icon/button #1646 (@jamescowens)
Add gridcointestnet.png #1649 (@caraka)
Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
Add options checkbox to disable transaction notifications #1666 (@jamescowens)
Add support for self-service beacon deletion #1695 (@cyrossignol)
Add support for type-specific contract fee amounts #1698 (@cyrossignol)
Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
If there is a cryptocurrency that has acquired popularity close to Bitcoin, then it is Ethereum. It is among the leading crypto-currencies when it comes to market capitalization. Ethereum is not just a cryptocurrency, but it is also a blockchain system that is useful in creating decentralised applications. Since Ethereum Blockchain is used by most companies now, it is gaining popularity among Ethereum miners and developers. Ethereum mining is a great way to make more cash. Benefiting from cryptocurrencies in p is a perfect option. Since many applications for Blockchain depend on Ethereum. Ethereum mining is going to be lucrative, as its price is expected to grow. The Ethereum minimum can be simplified with the use of the best Ethereum software. There are some apps like that on the market, and we've got the seven best for you here. 7 Ethereum 's Best Apps: ETHminer- This is an Ethereum mining application which is supported on Linux , Windows, and Mac. It is also possible to use the Ethash algorithm, luke Ellaisma, Musicoin Ethereum Classic, Metaverse, It is a command-line program that allows you to construct shortcut commands using a Windows cmd / batch file or Linux Bash script. The next software on our list is CGMiner-A, which was published in 2011. It is one of the common choices and has compatibility with GPU, FPGA, and ASIC. It is open-source software and can cause advanced detection of blocks. It is written in C; Ethereum developers are able to save a hash rate without delay using this Ethereum mining programme. On Linux , Windows, and Mac, this program is open. BitMinter- The graphical interface is transparent and it links easily to the Bitminter mining pool. This software was launched in 2011 and has more than 450,000 user accounts registered. The Java Network Launch Protocol (JNLP) is the foundation of its operations. Linux, Windows and Mac are also compatible with this programme. Claymore- This is one of the most powerful mining applications for Ethereum, and without delaying the mining pace, you can scale up the hash rate. You can also mine other cryptocurrencies like Lbry, Pascal, Siacoin, and Decred using this Ethereum mining programme. This software is Linux and Windows compatible and not Mac compatible. WinETH- If you are looking for an Ethereum mining app that is fast and simple to use, then this is the one for you. It is comparable to WinETH, but it has a simpler Interface and a smarter algorithm that makes it easy to use for Ethereum miners. Minergate-It was the first mining app for Ethereum to deliver merged mining. You can use this app to concurrently mine two separate coins without impacting the main coin's hash rate. In addition, this coin will also tell you about the market's most valuable coins. This programme can be used by Ethereum miners to mine other coins, including Zcash, Liteoin, Monero. BFGMiner- This programme is written in C and operates on various Linux, Windows and Mac operating systems. You will mine crypto coins and have both SHA256D and Scrypt on its algorithm. It also offers you total support for tracking. Conclusion- These are some of the popular mining applications for Ethereum that you can use. If you would like to know more about the creation of Ethereum, or Ethereum mining, If you wish to know more about Ethereum development, or Ethereum mining, or you want to enroll for Ethereum certification, connect with Blockchain Council today.
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.
Testimonials “Not enough trolling” - nanoakron, XMR Contributor “you are so obviously a shill” - ButtBazaar, in comments on the ETH survey “Wow.” - jstolfi, in reply to the ETH survey Survey ID: 00002 Coin: Monero (XMR) Client: jwinterm Executive Summary Monero is a leading privacy-oriented cryptocurrency. It was originally forked from Bytecoin which introduced Cryptonote, and whose launch was so bad they needed another chance to get it wrong. After their launch, they were a proving ground for Bytecoin exploits. Since then, Monero has become the leader in Cryptonote comedy gold, surpassing Bytecoin. Its future promises exciting drug market comedy gold, while the development team is a zoo of likely furries. 6 Top Comedy Gold Veins
Slow development - Likely due to the amount of time spent yiffing, “nice-to-have” extras like a GUI take a while to be released. After more than two years since at least one possible design for multisig in Cryptonote (curiously enough, from a paper co-authored by Gmax), multisig is still not in Monero yet, although still in development.
Launch issues - Launched because of complaints that the Bytecoin launch was unfair (i.e., not announced on Bitcointalk), Monero launched after about a week’s notice without an overabundance of communication from its founder. It released without 32-bit support, without a GUI, and without a mac client which according to BCT trollscritics is functionally equivalent to a premine.
Fenty - Monero is poised to take a commanding lead in the drug markets because of its combination of market share and stronger privacy commitment. Fent is known to be the leader in comedy gold potential for drug markets. Someday, there will be a major incident linked to a fent shipment arranged by a cryptocurrency. If that’s Monero, the fallout could be substantial.
Bleeding Edge: Monero started out as a clonecoin, a relaunch of Bytecoin, the first CryptoNote coin. However, it is in a position which is I think unique, or at least quite rare: despite starting as the clone, it is now leading the original upstream in market cap. Further, as a result CryptoNote / Bytecoin exploits have been demonstrated first on Monero. Monero has also developed its codebase such that it could not directly import upstream easily like most clonecoins could. Like all of the bleeding edge cryptocurrencies, Monero may produce more comedy gold from bugs being exploited on the chain.
51% / miner attack: Monero has had at some points large concentration in mining. As with most if not all cryptocurrencies, this centralization can lead to miners having significant control over a coin. So far, there doesn’t seem to have been any direct impact on Monero from this, and there may not be any effect. But Bitcoin and Ethereum have both had issues relating to functional centralization in mining in one way or another. Monero could as well. If anything does develop here, the popcorn futures could be explosive.
A brief history of comedy gold in Monero
There's an old proverb that says just about whatever you want it to.
- Anonymous (from this page of anonymous quotes) In the beginning there was Bytecoin. Of course, the original bytecoin was actually just a basic BTC clonecoin. And I think there was at least one other Bytecoin not the one we’re talking about here, since deceased as well. And when exactly this Bytecoin started is a matter of no little dispute. But, whenever it was, it was. By the time it was “discovered” and posted on BCT, about 80% of the total supply had been mined. Regardless of what exactly led to this, there were many in the cryptocurrency community on BCT who wanted a relaunch to use the tech without having to buy into the existing distribution. Then came “bitMonero” (first reference BCT ANN). Launched on relatively short notice, with a de-optimized miner inherited from upstream, no mac client, without 32bit support, and without a GUI. The original developer of the bitMonero fork, thankful_for_today (TFT), supported the network through an initial bug inherited from upstream [ 1 ]. TFT disappears from the thread for a while, and some of the community pull together to make a sort of rebranding, changing to “Monero”, making a new ANN (second BCT ANN listed in references) and forming a new team to run the coin. In the meantime, TFT made another Cryptonote based coin, Fantomcoin, but TFT continued to try bitMonero development as well , before finally abandoning the attempt again. And then the coin gets pretty boring. There’s a potentially serious issue revealed  which was inherited from Cryptonote and potentially even a deliberate backdoor left in, but the fix is in pretty quick and the ecosystem is small enough there’s not really an opportunity to exploit it further. While development is slow, the coin continues to work and move on. The coin gets adopted on one of the darknet markets in 2016, and around the same period it sees a surge in market price. While there is potential for comedy gold fallout from this, there hasn’t been anything obvious so far that I’ve seen. Researcher’s Narrative: After wrapping up the ETH survey, I put up the new $5 survey special sign and settled in with a bottle of cheap vodka to contemplate deep questions like how I got here, where I’m going, and why the ground is swaying like that. By the time I woke up, the bottle was empty, but there was a $5 bill slipped under the door with a note which read “Monero?” After only a few short hours of pondering the note and where the vodka had gone, I knew what I had to do next. A dark night in a world that never sleeps and knows how to keep its secrets...But on the 12th Floor of the Acme Building, one man is still trying to find the answers to life's persistent questions: Guy Noir, drunken sotprivate comedy gold surveyor. Thanks Narrator. Although I can do without the judgemental commentary. At least I struck it out. I’ll strike you out! But this is going even more off-course than usual. I should really make at least a token effort to do my job. So off I go to the furriest corner of cryptocurrency, and I ask the Monerons what they think their greatest weaknesses are. A rather clever move, if I do say so myself, as they’ll either do much of my job for me, or they’ll say they are entirely without fault and thus provide me with more fodder about how unselfaware they are! They rather surprise me by providing solid responses, with only a rather token “we’re flawless!” attitude to be found. This actually makes my job somewhat harder, as now I have to try to figure out whether the seeming lack of major flaws is a result of such a biased “research” method, general laziness, or being co-opted by actually enjoying the community. So I take the only logical route and go on a weeklong acid binge. At the end, I realize I’m an insignificant mote in an uncaring universe where humanity itself is an unnoticed blip. The futility of civilization and life itself is obvious. After some further reflection aided by bottles and pipes, as well as overdue bill notices, I realize that while all of this is true, none of it is relevant, and my foggy mind is further from any useful answers than when I started. Disclosure of biases: I was hired to write this article with $5 in BTC from jwinterm who is a participant in Monero. In the thread where I asked Monerons what their greatest weaknesses are, I learned a bit about their development process and decided I wanted to pitch my services to them. This has unquestionably made me biased. However, I did do my best to try to figure out where the critical flaw was to maximize the comedy gold yield. In coming up short, I’m not sure whether I’ve missed flaws or simply blinded myself to them. I know there are additional paths to find more comedy gold. I should ask the Bytecoin community what they think of Monero. And DASH and etc. to try to find all of its critics. But this piece must stand as simply an initial survey and I must move on to my next step. References
[ ] https://bitcointalk.org/index.php?topic=563821.msg6147116#msg6147116 - states rationale for not using Bytecoin rather than Monero (presented as Bytecoin clonecoin at this point) as being “Also the fact that cryptonote/bytecoin was hidden deep for the last few years and was being mined by a "big" unknown community the fork would give people a fair start on this new technology.”
[ ] https://bitcointalk.org/index.php?topic=563821.msg6286990#msg6286990 - Johnny Mnemonic, “There may be no pre-mine, but not a single step was taken to make this coin any more accessible than BCN. An easy GUI miner is super critical for early adoption, as is a cross-platform wallet that can be used out of the box. So now the only miners are the same few people willing to fuss around in the command line.”
[ ] https://bitcointalk.org/index.php?topic=563821.msg6300505#msg6300505 - “The problem is in block generation code. In one of last updates in Bytecoin there was a bug introduced: it calculates extra-size penalty the wrong way. As a result we see that a mined block isn't accepted by the network. I will consume the big transaction now into correct block. As soon as network accepts this block I will release new mining code to git.”
[ ] https://coinmarketcap.com/currencies/fantomcoin/ - Fantomcoin, merged mining cryptonote coin. Gets mentioned in BCT XMR thread since the cryptonote world is relatively small, with Bytecoin being the other one I know, and the reference implementation which isn’t actually a coin. (Subsequent to writing this learned about other ones, and learned Fantomcoin was created by TFT (original creator of BMR which was rebranded to XMR))
[ ] https://news.ycombinator.com/item?id=7765455 - nullc on zerocash vs bytecoin; “(And come on, I'm not usually one to lean on authority— but you ought to believe /me/ when I say it's not copying Bitcoin and that it's doing something very useful and interesting for cryptographic privacy)”
[ ] https://bitcointalk.org/index.php?topic=583449.14980 bookmark at page 750 in case computer crashes before I’m back from smoke break; actually an interesting page; all about talking about changing the emission rate and what is fundamental and unchangeable and who needs to approve changes. Very core cryptocurrency discussion.
The Strange Birth & History of Monero, Part II: BitMonero
--YOU CAN READ THIS IN SPANISH HERE-- When i first knew about Monero i was hungry of information, and when i found the americanpegasus post about "The Strange Birth & History of Monero" i loved it. I looked for a second part for a while but as there was no trace of it i did my own investigations. Now i've decided it could be a good idea to paste the results here with the same format as americanpegasus did, to help new users looking for info about the "strange birth" of Monero. Bitmonero - a new coin based on CryptoNote technology https://bitcointalk.org/index.php?topic=563821.0 Notable comments in this thread: -1: " Important: this is not a Bytecoin relaunch or not a Bytecoin replacement but a Bytecoin fork. Bytecoin has its own long history, community and stakeholders we don't know much about. I respect them and their decisions even if I don't understand them now. An intention to relaunch coin is always harmfull for everybody involved. Fork is a right way to contribute to community in case you don't agree with decisions already made. - Why did I make fork? - Because there is a number of technical and marketing issues I wanted to do differently. And also because I like ideas and technology and I want it to succeed. I did an announcement ASAP while a lot of details aren't still defined because the earlier it is announced the more people will be able to join. Details will appear as soon as they will be defined and decided. Here are details that are already defined and I don't plan to change this:
New coin will use Bytecoin(BCN)/CryptoNote code base.
New coin is started from scratch (i.e. from genesis block).
Emission schedule has a flatter curve (close to Bitcoin's original curve).
(https://bitcointalk.org/index.php?topic=563821.msg6476068#msg6476068) [TFT breaks out (30th, Apr 2014): he does not recognize community changes] -403: “You did not really fix it. You just ignore every error in the code with your 'update' We should wait for tacotime to confirm that the issue is fixed. PS: We should all use the main thread: Please use main thread: https://bitcointalk.org/index.php?topic=583449.0” (https://bitcointalk.org/index.php?topic=563821.msg6476331#msg6476331) [It is not a secret anymore: TFT and the “rebel” community do not have a good relationship] -480: (https://bitcointalk.org/index.php?topic=563821.msg7384159#msg7384159) [Months back (June 2014) and after a few months of inactivity, TFT comes back and makes public that he will keep working in BitMonero] -487: “Actually, several attempts were made behind the scenes and TFT's continued demand was full admin rights over the Monero repo. Now, what could that be useful for when tacotime already offered push/pull rights? It's certainly not about contributing code - push/pull offers the right to do that without interference or permission. This is basically a repeating pattern of shutting out everyone else, which is ironically what caused him to lose the project in the first place. The tone of that post makes his level of maturity obvious for everyone to see. I might also point out that his contribution to date consists of 10 or so lines of code changed in a header file (to clone BCN). Then a bug 'fix' that actually allowed the chain to be attacked later (now fixed). This was followed by his disappearance. Disproportionate visibility indeed.” (https://bitcointalk.org/index.php?topic=563821.msg7387658#msg7387658) [eizh makes clear they tried to make a deal with TFT] This is basically everything worth reading in this thread. I’ve extracted the most important posts in the whole thread, from first to last page. TFT, Bitmonero and its community are key in the birth of Monero. These are the main conclussions:
BitMonero has a reason to exist. But to justify its existence it doesn’t need just reasons, but also a dedicated team and a participative community.
Thankful_for_today definitely it is not a sociable leader. His posts are scarce, every few days, and he can’t keep up to date with a nascent community really dedicated
TFT is desperate to launch BitMonero, probably to be the first Bytecoin fork and have the “first mover” advantage. He is even about to launch without Windows client.
Due to the rush, TFT has induced a few bugs. The most important one the emission curve.
Bytecoin starts to have some traction, and TFT keeps ignoring community suggestions, so the community has now doubts of BMR future. NoodleDoodle, eizh, David Latapie, Tacotime and smooth among others lead a split, firstly just to change the name and re-publishing the announcement thread, but they will eventually hard-split.
I have already ready a summary of the MRO topic that has a short life of not even 2 days but still has A LOT of interesting info about how the team is being built and what are their opinions on several topics. May i remember you that by then Monero had 1 minute blocks and an emission curve that would have created 86% of the tokens in 2 years. In the next post (will only make it public if i see there's any interest) we will see how and when the team adressed the problems with the emission curve, and when was the miner optimized to take away the probably voluntary obfuscations the code had.
The Strange Birth & History of Monero, Part III: Decentralized team
You can read here part I (by americanpegaus). This is the post that motivated me to make the part II. Now i'm doing a third part, and there'll be a final 4th part. This is probably too much but i wasn't able to make it shorter. Some will be interested in going through all them, and maybe someone is even willing to make a summary of the whole serie :D. Monero - an anonymous coin based on CryptoNote technology https://bitcointalk.org/index.php?topic=582080.0 Comentarios de interés: -4: "No change, this is just a renaming. In the future, the binaries will have to be changed, as well as some URL, but that's all. By the way, this very account (monero) is shared by several user and is meant to make it easier to change the OP in case of vacancy of the OP. This idea of a shared OP comes from Karmacoin. Some more things to come:
A website (URL will be monero.cc)
A GUI wallet
" (https://bitcointalk.org/index.php?topic=582080.msg6362672#msg6362672) -5: “Before this thread is too big, I would like to state that a bug has been identified in the emission curve and we are currently in the process of fixing it (me, TFT, and smooth). Currently coins are emitted at double the rate that was intended. We will correct this in the future, likely by bitshifting values of outputs before a certain height, and then correcting 1 min blocks to 2 min blocks. The changes proposed will be published to a Monero Improvement Protocol on github.” (https://bitcointalk.org/index.php?topic=582080.msg6363016#msg6363016) [tacotime make public the bug in the emission curve: token creation is currently 2 times what was intended to be, see this chart BTC vs the actual XMR curve, as it was and it is now, vs the curve that was initially planned in yellow see chart] -14: “Moving discussion to more relevant thread, previous found here: https://bitcointalk.org/index.php?topic=578192.msg6364026#msg6364026 I have to say that I am surprised that such an idea [halving current balances and then changing block target to 2 min with same block reward to solve the emission curve issue] is even being countenanced - there are several obvious arguments against it. Perception - what kind of uproar would happen if this was tried on a more established coin? How can users be expected to trust a coin where it is perceived that the devs are able and willing to "dip" into people's wallets to solve problems? Technically - people are trying to suggest that this will make no difference since it applies to reward and supply, which might be fair enough if the cap was halved also, but it isn't. People's holdings in the coin are being halved, however it is dressed up. Market price - How can introducing uncertainty in the contents of people's wallets possibly help market price? I may well be making a fool of myself here, but I have never heard of such a fix before, unless you had savings in a Cypriot bank - has this ever been done for another coin?” (https://bitcointalk.org/index.php?topic=582080.msg6364174#msg6364174) -15: “You make good points but unfortunately conflicting statements were made and it isn't possible to stick to them all. It was said that this coin had a mining reward schedule similar to bitcoin. In fact it is twice as fast as intended, even even a bit more than twice as fast as bitcoin. If you acquired your coins on the basis of the advertised reward schedule, you would be disappointed, and rightfully so, as more coins come to into existence more quickly than you were led to believe. To simply ignore that aspect of the bug is highly problematic. Every solution may be highly problematic, but the one being proposed was agreed as being the least bad by most of the major stakeholders. Maybe it will still not work, this coin will collapse, and there will need to be a relaunch, in which case all your coins will likely be worthless. I hope that doesn't happen.” (https://bitcointalk.org/index.php?topic=582080.msg6364242#msg6364242) [smooth tries to justify his proposal to solve the emission curve issue: halve every current balance and change block target to 2 min with same block reward] -16: “This coin wasn't working as advertised. It was supposed to be mined slowly like BTC but under the current emission schedule, 39% would be mined by the first year and 86% by the fourth year. Those targets have been moved out by a factor of 2, i.e. 86% mined by year 8, which is more like BTC's 75% by year 8. So the cap has been moved out much further into the future, constraining present and near-term supply, which is what determines the price.” (https://bitcointalk.org/index.php?topic=582080.msg6364257#msg6364257) [eizh supports smooth’s plan] -20: “So long as the process is fair and transparent it makes no difference what the number is... n or n/2 is the same relative value so long as the /2 is applied to everyone. Correcting this now will avoid people accusing the coin of a favourable premine for people who mined in the first week.” (https://bitcointalk.org/index.php?topic=582080.msg6364338#msg6364338) [random user supporting smooth’s idea] -21: “Why not a reduction in block reward of slightly more than half to bring it into line with the proposed graph? That would avoid all sorts of perceptual problems, would not upset present coin holders and be barely noticeable to future miners since less than one percent of coins have been mined so far, the alteration would be very small?” (https://bitcointalk.org/index.php?topic=582080.msg6364348#msg6364348) -22: “Because that still turns into a pre-mine or instamine where a few people got twice as many coins as everyone else in the first week. This was always a bug, and should be treated as such.” (https://bitcointalk.org/index.php?topic=582080.msg6364370#msg6364370) [smooth wants to be sure they can’t be stigmatized as “premine”] -23: “No, not true [answering to "it makes no difference what the number is... n or n/2 is the same relative value so long as the /2 is applied to everyone"]. Your share of the 18,000,000 coins is being halved - rightly or wrongly.” (https://bitcointalk.org/index.php?topic=582080.msg6364382#msg6364382) [good point made by a user that is battling “hard” with smooth and his proposal] -28: “+1 for halving all coins in circulation. Would they completely disappear? What would the process be?” -31: “I will wait for the next coin based on CryptoNote. Many people, including myself, avoided BMR because TFT released without accepting input from anyone (afaik). I pm'ed TFT 8 days before launch to help and didn't get response until after launch. Based on posting within the thread, I bet there were other people. Now the broken code gets "fixed" by taking away coins.” (https://bitcointalk.org/index.php?topic=582080.msg6364531#msg6364531) -32: “What you say is true, and I can't blame anyone from simply dropping this coin and wanting a complete fresh start instead. On the other hand, this coin is still gaining in popularity and is already getting close to bytecoin in hash rate, while avoiding its ninja premine. There is a lot done right here, and definitely a few mistakes.” (https://bitcointalk.org/index.php?topic=582080.msg6364574#msg6364574) [smooth stands for the project legitimacy despite the bugs] -37: “Since everything is scaled and retroactive, the only person to be affected is... me. Tongue Because I bought BMR with BTC, priced it with incorrect information, and my share relative to the eventual maximum has been halved. Oh well. The rest merely mined coins that never should have been mined. The "taking away coins" isn't a symptom of the fix: it's the fundamental thing that needed fixing. The result is more egalitarian and follows the original intention. Software is always a work-in-progress. Waiting for something ideal at launch is pretty hopeless. edit: Let me point out that most top cryptocurrencies today were released before KGW and other new difficulty retargeting algorithms became widespread. Consequently they had massive instamines on the first day, even favorites in good standing like LTC. Here the early miners are voluntarily reducing their eventual stake for the sake of fairness. How cool is that?” (https://bitcointalk.org/index.php?topic=582080.msg6364886#msg6364886) [this is eizh supporting the project too] -43: “I'm baffled that people are arguing about us making the emission schedule more fair. I'm an early adopter. This halves my money, and it's what I want to do. There's another change that needs to be talked about too: we don't believe that microscopic levels of inflation achieved at 9 or 10 years will secure a proof-of-work network. In fact, there's a vast amount of evidence from DogeCoin and InfiniteCoin that it will not. So, we'd like to fix reward when it goes between 0.25 - 1.00 coins. To do so, we need to further bitshift values to decrease the supply under 264-1 atomic units to accommodate this. Again, this hurts early adopters (like me), but is designed to ensure the correct operation of the chain in the long run. It's less than a week old, and if we're going to hardfork in economic changes that make sense we should do it now. We're real devs turning monero into the coin it should have been, and our active commitment should be nothing but good news. Fuck the pump and dumps, we're here to create something with value that people can use.” (https://bitcointalk.org/index.php?topic=582080.msg6366134#msg6366134) [tacotime brings to the public for first time the tail emission proposal and writes what is my favourite sentence of the whole monero history: “Fuck the pump and dumps, we're here to create something with value that people can use”] -51: “I think this is the right attitude. Like you I stand to "lose" from this decision in having my early mining halved, but I welcome it. Given how scammy the average coin launch is, I think maximizing fairness for everyone is the right move. Combining a fair distribution with the innovation of Cryptonote tech could be what differentiates Monero from other coins.” (https://bitcointalk.org/index.php?topic=582080.msg6366346#msg6366346) -59: “Hello! It is very good that you've created this thread. I'm ok about renaming. But I can't agree with any protocol changes based only on decisions made by bitcointalk.org people. This is because not all miners are continiously reading forum. Any decision about protocol changes are to be made by hashpower-based voting. From my side I will agree on such a decision only if more than 50% of miners will agree. Without even such a simple majority from miners such changes are meaningless. In case of hardfork that isn't supported by majority of miners the network will split into two nets with low-power fork and high-power not-forking branches. I don't think that this will be good for anybody. Such a voting is easy to be implemented by setting minor_version of blocks to a specific value and counting decisions made after 1000 of blocks. Do you agree with such a procedure?” (https://bitcointalk.org/index.php?topic=582080.msg6368478#msg6368478) [TFT appears after a couple days of inactivity] -63: “In few days I will publish a code with merged mining support. This code will be turned ON only by voting process from miners. What does it mean:
miners supporting merged mining are to update their nodes and miners. New miners will issue blocks with modified minor_version field indicating they are ready to accept AuxPoW blocks. But no AuxPoW blocks will be issued before 75% of last 1000 blocks will have a positive vote (a changed minor_version).
miners not supporting will not update but will still be able to mine and accept blocks. In case of successful voting they will have to switch to new code. In case of voting failed they can stay on old version.
The same procedure is suitable for all other protocol changes.” (https://bitcointalk.org/index.php?topic=582080.msg6368720#msg6368720) [And now he is back, TFT is all about merged mining] -67: “We don't agree that a reverse split amounts to "taking" coins. I also wouldn't agree that a regular forward split would be "giving" coins. It's an exchange of old coins with new coins, with very nearly the exact same value. There is a very slight difference in value due to the way the reward schedule is capped, but that won't be relevant for years or decades. Such a change is entirely reasonable to fix an error in a in coin that has only existed for a week.” (https://bitcointalk.org/index.php?topic=582080.msg6368861#msg6368861) -68: “There were no error made in this coin but now there is an initiative to make some changes. Changes are always bad and changes destroy participant confidence even in case these changes are looking as useful. We have to be very careful before making any changes in coins” (https://bitcointalk.org/index.php?topic=582080.msg6368939#msg6368939) [TFT does not accept the unexpected emission curve as a bug] -72: “You are wrong TFT. The original announcement described the coin as having a reward curve "close to Bitcoin's original curve" (those are your exact words). The code as implemented has a reward curve that is nothing like bitcoin. It will be 86% mined in 4 years. It will be 98% mined in 8 years. Bitcoin is 50% mined in 4 years, and 75% in 8 years. With respect TFT, you did the original fork, and you deserve credit for that. But this coin has now gone beyond your initial vision. It isn't just a question of whether miners are on bitcointalk or not. There is a great team of people who are working hard to make this coin a success, and this team is collaborating regularly through forum posts, IRC, PM and email. And beyond that a community of users who by and large have been very supportive of the efforts we've taken to move this forward. Also, miners aren't the only stakeholders, and while a miner voting process is great, it isn't the answer to every question. Though I do agree that miners need to be on board with any hard fork to avoid a harmful split.” (https://bitcointalk.org/index.php?topic=582080.msg6369137#msg6369137) [smooth breaks out publicily for first time against TFT] -75: “I suppose that merged mining as a possible option is a good idea as soon as nobody is forced to use it. MM is a possibility to accept PoW calculated for some other network. It helps to increase a security of both networks and makes it possible for miners not to choose between two networks if they want both:
BCN only miners will continue to mine BCN
BMMRO only miners will continue to mine BMMRO
merge miners will mine both at the same time (now some of them mine BCN only and other - BMR only)
Important things to know about MM:
MM doesn't imply that BMR is smaller or has a less hashpower. In case BMR will has more mining power than BCN it will simply accept less BCN blocks.
MM doesn't force BMR users to have BCN chain on their HDD - BCN chain isn't neede to verify blocks
MM doesn't require any specific parent chain. Miner decides himself which parent chain to use: BCN or any other chain supporting the same PoW method.
Actually the only change that goes with MM is that we are able to accept PoW from some other net with same hash-function. Each miner can decide his own other net he will merge mine BMR with. And this is still very secure. This way I don't see any disadvantage in merged mining. What disadvantages do you see in MM?” (https://bitcointalk.org/index.php?topic=582080.msg6369255#msg6369255) [TFT stands for merged mining] -77: “Merged mining essentially forces people to merge both coins because that is the only economically rational decision. I do not want to support the ninja-premined coin with our hash rate. Merged mining makes perfect sense for a coin with a very low hash rate, otherwise unable to secure itself effectively. That is the case with coins that merge mine with bitcoin. This coin already has 60% of the hash rate of bytecoin, and has no need to attach itself to another coin and encourage sharing of hash rate between the two. It stands well on its own and will likely eclipse bytecoin very soon. I want people to make a clear choice between the fair launched coin and the ninja-premine that was already 80% mined before it was made public. Given such a choice I believe most will just choose this coin. Letting them choose both allows bytecoin to free ride on what we are doing here. Let the ninja-preminers go their own way.” (https://bitcointalk.org/index.php?topic=582080.msg6369386#msg6369386) [smooth again] -85: “One of you is saying that there was no mistake in the emission formula, while the other is. I'm not asking which I should believe . . I'm asking for a way to verify this” (https://bitcointalk.org/index.php?topic=582080.msg6369874#msg6369874) [those that have not been paying attention to the soap opera since the beginning do not understand anything at all] -86: “The quote I posted "close to Bitcoin's original curve" is from the original announcement here: https://bitcointalk.org/index.php?topic=563821.0 I think there was also some discussion on the thread about it being desirable to do that. At one point in that discussion, I suggested increasing the denominator by a factor of 4, which is what ended up being done, but I also suggested retaining the block target at 2 minutes, which was not done. The effect of making one change without the other is to double the emission rate from something close to bitcoin to something much faster (see chart a few pages back on this thread).” (https://bitcointalk.org/index.php?topic=582080.msg6369935#msg6369935) [smooth answers just a few minutes later] -92: “I'm happy the Bitmonero attracts so much interest. I'm not happy that some people want to destroy it. Here is a simple a clear statement about plans: https://bitcointalk.org/index.php?topic=582670 We have two kind of stakeholders we have respect: miders and coin owners. Before any protocol changes we will ask miners for agreement. No changes without explicit agreement of miners is possible. We will never take away or discount any coins that are already emitted. This is the way we respect coin owners. All other issues can be discussed, proposed and voted for. I understand that there are other opinions. All decisions that aren't supported in this coin can be introduced in any new coin. It's ok to start a new fork. It's not ok to try to destroy an existsing network.” (https://bitcointalk.org/index.php?topic=582080.msg6370324#msg6370324) [TFT is kinda upset – he can see how the community is “somehow” taking over] -94: “Sounds like there's probably going to be another fork then. Sigh. I guess it will take a few tries to get this coin right. The problem with not adjusting existing coins is that it make this a premine/instamine. If the emission schedule is changed but not as a bug fix, then earlier miners got an unfair advantage over everyone else. Certainly there are coins with premines and instamines, but there's a huge stigma and such a coin will never achieve the level of success we see for this coin. This was carefully discussed during the team meeting, which was announced a day ahead of time, and everyone with any visible involvement with the coin, you included, was invited. It is unfortunate you couldn't make it to that meeting TFT.” (https://bitcointalk.org/index.php?topic=582080.msg6370411#msg6370411) [smooth is desperate due to TFT lack of interest in collaboration, and he publicly speaks about an scission for first time] -115: “Very rough website online, monero.cc (in case you asked, the domain name was voted on IRC, like the crypto name and its code). Webdesigner, webmaster, writers... wanted.” (https://bitcointalk.org/index.php?topic=582080.msg6374702#msg6374702) [Even though the lack of consensus and the obvious chaos, the community keeps going on: Monero already has his own site] -152: “Here's one idea on fixing the emissions without adjusting coin balances. We temporarily reduce the emission rate to half of the new target for as long as it takes for the total emission from 0 to match the new curve. Thus there will be a temporary period when mining is very slow, and during that period there was a premine. But once that period is compete, from the perspective of new adopters, there was no premine -- the total amount of coins emitted is exactly what the slow curve says it should be (and the average rate since genesis is almost the same as the rate at which they are mining, for the first year or so at least). This means the mining rewards will be very low for a while (if done now then roughly two weeks), and may not attract many new miners. However, I think there enough of us early adopters (and even some new adopters who are willing to make a temporary sacrifice) who want to see this coin succeed to carry it through this period. The sooner this is done the shorter the catch up period needs to be.” (https://bitcointalk.org/index.php?topic=582080.msg6378032#msg6378032) [smooth makes a proposal to solve the “emission curve bug” without changing users balances and without favoring the early miners] -182: “We have added a poll in the freenode IRC room "Poll #2: "Emission future of Monero, please vote!!" started by stickh3ad. Options: #1: "Keep emission like now"; #2: "Keep emission but change blocktime and final reward"; #3: "Keep emission but change blocktime"; #4: "Keep emission but change final reward"; #5: "Change emission"; #6: "Change emission and block time"; #7: "Change emission and block time and final reward" Right now everyone is voting for #4, including me.” (https://bitcointalk.org/index.php?topic=582080.msg6379518#msg6379518) [tacotime announces an ongoing votation on IRC] -184: “ change emission: need to bitshift old values on the network or double values after a certain block. controversial. not sure if necessary. can be difficult to implement. keep emission: straightforward, we don't keep change emission or block time. change final reward is simple. if (blockSubsidy < finalSubsidy) return finalSubsidy; else return blockSubsidy;” (https://bitcointalk.org/index.php?topic=582080.msg6379562#msg6379562) -188: “Yeah, well. We need to change the front page to reflect this if we can all agree on it. We should post the emissions curve and the height and value that subsidy will be locked in to. In my opinion this is the least disruptive thing we can do at the moment, and should ensure that the fork continues to be mineable and secure in about 8 years time without relying on fees to secure it (which I think you agree is a bad idea).” (https://bitcointalk.org/index.php?topic=582080.msg6379871#msg6379871) [tacotime] -190: “I don't think the proposed reward curve is bad by any means. I do think it is bad to change the overall intent of a coin's structure and being close to bitcoins reward curve was a bit part of the intent of this coin. It was launched in response to the observation that bytecoin was 80% mined in less than two years (too fast) and also that it was ninja premined, with a stated goal that the new coin have a reward curve close to bitcoin. At this point I'm pretty much willing to throw in the towel on this launch:
No web site
Botched reward curve (at least botched relative to stated intent)
No pool (and people who are enthusiastically trying to mine having trouble getting any blocks; some of them have probably given up and moved on).
No effective team behind it at launch
No Mac binaries (I don't think this is all that big a deal, but its another nail)
I thought this could be fixed but with all the confusion and lack of clear direction or any consistent vision, now I'm not so sure. I also believe that merged mining is basically a disaster for this coin, and is probably being quietly promoted by the ninjas holding 80% of bytecoin, because they know it keeps their coin from being left behind, and by virtue of first mover advantage, probably relegates any successors to effective irrelevance (like namecoin, etc.). We can do better. It's probably time to just do better.” (https://bitcointalk.org/index.php?topic=582080.msg6380065#msg6380065) [smooth is disappointed] -191: “The website does exist now, it's just not particularly informative yet. :) But, I agree that thankful_for_today has severely mislead everyone by stating the emission was "close to Bitcoin's" (if he's denying that /2 rather than /4 emission schedule was unintentional, as he seems to be). I'm also against BCN merge mining. It works against the goal of overtaking BCN and if that's not a goal, I don't know what we're even doing here. I'll dedicate my meagre mining to voting against that. That said, you yourself have previously outlined why relaunches and further clones fail. I'd rather stick with this one and fix it.” (https://bitcointalk.org/index.php?topic=582080.msg6380235#msg6380235) [eizh tries to keep smooth on board] -196: “BCN is still growing as well. It is up to 1.2 million now. If merged mining happens, (almost) everyone will just mine both. The difficulty on this coin will jump up to match BCN (in fact both will likely go higher since the hash rate will be combined) and again it is an instamine situation. (Those here the first week get the benefit of easy non-merged mining, everyone else does not.) Comments were made on this thread about this not being yet another pump-and-dump alt. I think that could have been the case, but sadly, I don't really believe that it is.” (https://bitcointalk.org/index.php?topic=582080.msg6380778#msg6380778) -198: “There's no point in fragmenting talent. If you don't think merge mining is a good idea, I'd prefer we just not add it to the code. Bitcoin had no web site or GUI either initially. Bitcoin-QT was the third Bitcoin client. If people want a pool, they can make one. There's no point in centralizing the network when it's just began, though. Surely you must feel this way.” (https://bitcointalk.org/index.php?topic=582080.msg6381866#msg6381866) [tacotime also wants smooth on board] -201: “My personal opinion is that I will abandon the fork if merge mining is added. And then we can discuss a new fork. Until then I don't think Monero will be taken over by another fork.” (https://bitcointalk.org/index.php?topic=582080.msg6381970#msg6381970) [tacotime opens the season: if merged mining is implemented, he will leave the ship] -203: “Ditto on this. If the intention wasn't to provide a clearweb launched alternative to BCN, then I don't see a reason for this fork to exist. BCN is competition and miners should make a choice.” (https://bitcointalk.org/index.php?topic=582080.msg6382097#msg6382097) [eizh supports tacotime] -204: “+1 Even at the expense of how much I already "invested" in this coin.” (https://bitcointalk.org/index.php?topic=582080.msg6382177#msg6382177) [NoodleDoodle is also against merged mining] This is basically everything worth reading in this thread. This thread was created in the wrong category, and its short life of about 2 days was pretty interesting. Merged mining was rejected and it ended up with the inactivity of TFT for +7 days and the creation of a new github repo the 30th of April. It is only 12 days since launch and a decentralized team is being built. Basically the community had forked (but not the chain) and it was evolving and moving forward to its still unclear future. These are the main takeaways of this thread:
The legitimacy of the "leaders" of the community is proven when they proposed and supported the idea of halving the balances for the greater good to solve the emission curve issue without any possible instamine accusation. Also their long-term goals and values rejecting merged-mining with a "primined scam"
It is decided that, as for now, it is “too late” to change the emission curve, and finally monero will mint 50% of its coin in ~1.3 years (bitcoin did it after 3.66 years) and 86% of its coins in 4 years (bitcoin does it in ~11 years) (was also voted here) (see also this chart)
It is decided that a “minimum subsidy” or “tail emission” to incentivize miners “forever” and avoid scaling fees will be added (it will be finally added to the code march 2015)
Merged mining is plainly rejected by the future “core team” and soon rejected by "everyone". This will trigger TFT inactivity.
The future “core team” is somehow being formed in a decentralized way: tacotime, eizh, NoodleDoodle, smooth and many others
And the most important. All this (and what is coming soon) is a proof of the decentralization of Monero. Probably comparable to Bitcoin first days. This is not a company building a for-profit project (even if on the paper it is not for-profit), this a group of disconnected individuals sharing a goal and working together to reach it. Soon will be following a final part where i'll collect the bitcointalk logs in the current official announcement threads. There you'll be able to follow the decentralized first steps of develoment (open source pool, miner optimizations and exchanges, all surrounded by fud trolls, lots of excitmen and a rapidly growing collaborative community.
10 Best Mac OS X Anti-Spyware and Anti-Virus Software for Free. Download Free Kaspersky Internet Security Antivirus for Windows 8 . 6 Months Free Genuine Serial Number For Panda Internet Security Antivirus. 5 User Friendly Ethereum GUI Mining Clients For Mac, Linux And Windows. Updated: January 9, 2020 / Home » Bitcoin [ Buy, Sell, Mine & Invest ] With Cryptocurrency price stock shooting ... Merged mining. by MinerGate Mining Pool June, 5, 2014. MinerGate has become the first CryptoNote pool that features merged mining! New main features: Fantomcoin is available on MinerGate. Merged mining support for Bytecoin, Monero, Quazarcoin, duckNote. When you merged mine a coin, it means that the hash rate for the main coin doesn’t ... In case 1 nothing happens and the merged miner inserts a new nonce value and rehashes. In case two the miner has found a solution for the Namecoin network and propagates its solution throughout that network, if mining in conjunction with Bitcoin. In case three solutions have been found for both of the chains and so a all the required ... 4) Tweaking the Mining Pool Software to Enable Merged-Mining – RSK provides a wide range of merged-mining pools that enable miners to participate in the merged mining ecosystem. Smart contract and mining experts at RSK have developed several plugins that ensure that normal Bitcoin mining operations are not adversely impacted by merged mining at all costs. These plugins support some of the ... Bitcoin Cloud Mining. Let your computer relax. Our Cloud solution will mine and hash whatever cryptocurrency you need. Get started with immediate mining results. Learn more. Cryptocurrency miners love Eobot "i like your site and service and i will invest more and more with time i try to reffer too thanks hi from france" Mathieu S., Dogecoin Miner - France "You guys make it simple, I mine for ...
Minergate mining update : mining monero with CPU. MinerGate is a mining pool created by a group of cryptocoin enthusiasts which provides service for merged mining (mine different coins ... Merged Mining. Mine Monero and FantomCoin At The Same Time Automatically With MINERGATE There are a lot of people that don't seem to be aware that you can merge mine Monero with Fantomcoin. #MinerGate is a mining pool created by a group of cryptocoin enthusiasts. It is the first pool which provides service for merged mining. This means that while mining on our pool you can mine ... More profits from mining without adding extra capacities. Blockchain platform and Emercoin cryptocurrency implements mining, combined with Bitcoin - Merged Mining in the wallet’s 0.6.0 update ... minergate review minergate download minergate unconfirmed balance minergate token expired minergate reddit minergate vs nicehash minergate calculator minergate achievements minergate wallet ...