[uncensored-r/Bitcoin] Can I run p2pool nodes for BTC and LTC on the same server?
The following post by sufuninja is being replicated because the post has been silently greylisted. The original post can be found(in censored form) at this link: np.reddit.com/ Bitcoin/comments/7p01ed The original post's content was as follows:
freenode.net [13:47:03] The guide is divided into sections, each with a specific section of activity and a cause for why I should work on that area. [13:47:03] Those are still facts [13:47:08] So there is still a little more work to do. [13:47:15] I need to add all the pages to the wiki. [13:47:18] After that, I'll start putting more resources up, including some images and if I'm doing it right, some story sections. [13:47
freenode/ip.220.127.116.11) has joined #/cicada3302 [21:18] or uh, scribe great, wtf? [21:18] He's come into this room, perhaps from the dark house? So we should return the greeting? [21:18] (We can't go there. I don't think. He's been there before, but on a cloudy day.) [21:18] <@shecalledmepaul> no it's been such a while since youve heard anything that I don't think you'll remember [21:18] <@shecalledmepaul
freenode/ip.18.104.22.168) Quit (Ping timeout: 245 seconds) [10:47] how about talk about the XP drop rate in general? [10:47] also [10:47] <@dine909> wait wtf [10:47] <@dine909> X is 75% [10:47] <@dine909> of XP [10:47] i think you have to have very high level to get 95% in dungeons [10:47] <@dine909> yeah i guess [10:48] but yeah [10:48] maybe it has something
freenode/ip.22.214.171.124] has joined #/cicada3302 [01:45] and yes, we have /vaspool/cicada3302/daemon/rules also. anything is possible, we know that [01:45] not everything though [01:45] well, some of the entries do not exist [01:45] So this new detective in the thread goes by "ricardo75"? [01:46] Hi everyone, I am new here, but I'm quite convinced that whoever made this 2.
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.
Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers
Hello Vertcoin Community, Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc. I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting. The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc. Why run a headless node on a Single Board Computer?
You want to support vertcoin. Running a node makes the network more robust and able to serve more wallets, more users, and more transactions.
You are building or using applications such as mining that must validate transactions according to vertcoin’s consensus rules.
You are developing vertcoin software and need to rely on a vertcoin node for programmable (API) access to the network and blockchain.
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc. Required: USB Flash Drive 6GB - 32GB Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD. Supports
Raspberry Pi 3 B+ | ARM Cortex-A53 1.4GHz | 1GB SRAM |
Raspberry Pi Zero (W) | Single Core ARMv6 1 Ghz | 433MB RAM |
All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible. Functionality
Installs Vertcoin full node to Single Board Computer
Installs p2pool-vtc (Optional)
Installs LIT and LIT-AF (Optional)
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined. BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.
Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.
If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive. https://etcher.io/ PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.
You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on). You will need to know the IP address of your node, this can be found on your router page. ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi. A brief list of commands that can be used to check on the Vertcoin node status: vertcoin-cli getblockchaininfo | Grab information about your blockchain vertcoin-cli getblockcount | Grab the current count of blocks on your node vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page. vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop) Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0 This work is dedicated to the users of Vertcoin, thank you for making this possible. 7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3 You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
UPDATE: VTC mining on Easymine back to normal, payouts have resumed. Zero fees for the rest of the month. Here's a more detailed response to https://old.reddit.com/vertcoin/comments/96z77t/psa_easy_mine_problem/ - bear with me and put on your nerd hat for a few mins. The stratum server for all EasyMine pools is node-merged-pool - a merge mining fork of node-stratum-pool. See my repo here @ https://github.com/nzsquirrell/node-merged-pool This is what miners connect to for work and to submit valid shares on the search for blocks. The information that is exchanged in hex digits, and the data coming back from the miner includes the time, the job, ExtraNonce2 and nonce (see https://en.bitcoin.it/wiki/Stratum_mining_protocol#mining.submit). All of these fields are used to notify the server of valid work exceeding a specific difficulty. Hex digits are not case-sensitive. So 'FF00AA11' is the same as 'ff00aa11'. Both equate to decimal 4278233617. So for the purposes of construction a block header, it doesn't matter if the hex digits are uppercase, lowercase, or a mixture of both - it all works out the same, and produces the same hash. Hold this thought. The stratum server knows what shares each miner has submitted, it keeps a track of all of the data in an array. It checks every time that work is submitted that the same work hasn't been submitted before whilst searching for the next block. If it was submitted, then the new submission is rejected as duplicate work. Now, where this has all gone wrong is that the way the data is stored in this array was a string containing the four fields mentioned above. Strings are case-sensitive and when making comparisons 'FF00AA11' != 'ff00aa11', as well as 'ff00aA11' and 'ff00AA11' and so on.... This allowed our attacker to submit the same work many many times, altering only the case of the hex digits (he was doing it to the nonce, but the other fields are also susceptible to the attack), so the logic to check for duplicate work wasn't firing, the shares were valid (as they produced a valid hash above difficulty), and our attacker was faking most of his hash-rate. A lot. A shit-ton of it. I have fixed this in my fork of node-stratum-pool - the fix is very easy, we just make all the characters lower case before testing for duplicate shares. See https://github.com/nzsquirrell/node-merged-pool/commit/9d068535d042516835f565a859852c7cf715da98 for my fix. My big concern is that the other forks I've seen for node-stratum-pool are susceptible to the attack, and quite possibly other pool software is toopossibly even p2pool? I've not looked. If someone can check and let me know and I'll update this. p2pool has been confirmed as resilient to this type of attack. So, Who-The-F&*k did this. This is what I have so far: He's used the following VTC and NIX addresses:
I've seen connections coming in from the following IP addresses:
He is still attacking EasyMine, but it's not having any effect now. Actually the server keeps banning him now as it's detecting that he's submitting too many invalid shares. Take that. The path forward I have a big mess to clean up, he's made off with about 652 VTC and about 3576 NIX, essentially stolen from you miners. I will see what I can do to recover some of this (not all of it has been paid to him yet), but there is going to be a substantial shortfall. Mr Attacker, feel free to PM me and we can arrange a settlement :) Payouts on both the VTC & NIX pools are suspended until i can clean this up, I hope this won't take more than a couple of days. Thanks.
This post is a temporary resting place for FAQs while we wait for the release of VertDocs.
What is Vertcoin?
Vertcoin is a digital peer to peer currency focused on decentralization and ASIC resistance. Vertcoin is aiming to be easily accessible to the everyday user without extensive technical knowledge. Vertcoin has started to lower the barrier of entry with lots of video guides and the development of the One Click Miner (OCM).
Why does ASIC Resistance Matter?
ASICs (Application Specific Integrated Circuits) are dedicated mining devices that can only mine one algorithm. Coins like Bitcoin and Litecoin both made GPU mining obsolete when SHA-256 and Scrypt ASICs were created.
ASIC Resistance and How it Makes Vertcoin Decentralized
Vertcoin believes that ASIC resistance goes hand in hand with decentralization. ASICs are made by companies like Bitmain and almost all the original sellers of ASICs sell on a preorder basis. When pre ordering an ASIC you are buying from a limited batch that the ASIC company has produced. Often times the batch will not be fully filled and the ASIC company will often have left over ASICs. When the ASIC company has left over ASICs they will put them to work mining. Soon enough the ASIC company will have a very large amount of unsold ASICs that are mining and slowly the ASIC company starts to own a large part of the network’s hashrate. When an ASIC company(s) starts to own a large majority of the hashrate the network can become very centralized after a while. Having your network consist of a few large companies can be very dangerous as they could eventually get 51% hashing power and 51% attack your network, destabilizing the network. When your network is made out of a lot of smaller miners, like Vertcoin, it is much harder for your network to be 51% attacked, therefore increasing network security. By having centralized hashing power your coin effectively centralizing the network as the centralized hashing power can deny transactions and stop any activity they don’t want.
What Ways is Vertcoin Superior to Litecoin and Bitcoin?
Network Difficulty Adjustments with Kimoto Gravity Well
Vertcoin uses a difficulty adjustment called Kimoto Gravity Well which adjusts the difficulty every block, whereas Bitcoin and Litecoin’s difficulty changes every 2016 blocks. By adjusting the difficulty every block Vertcoin’s block time can stay consistent by adjusting for the fluctuation in network hash rate from hash rate renting and part time miners. If a large miner switches off Bitcoin or Litecoin mining the network could be slowed to a crawl until 2016 blocks are mined and the difficulty can change to adjust for the new network hash rate. We observed this happen to Bitcoin when Bitcoin Cash became more profitable than Bitcoin and Bitcoin’s network hash rate saw a steep fall off, slowing the network to a crawl. If this was to happen with Vertcoin the difficulty would adjust after 1 block was mined, allowing Vertcoin to always be profitable to mine.
Anyone can Meaningfully help Verify Transactions
In Proof-of-Work crypto currencies miners help secure the blockchain and get rewarded with the block reward. In ASIC mineable coins like Bitcoin and Litecoin you can’t meaningfully verify transactions unless you pay 1000-2000$ for a ASIC miner. When you mine with a CPU or GPU in a ASIC mineable coin you make no meaningful impact on the network. It is like trying to break concrete with a shovel while everyone else has a jackhammer.
Simple Upgrades Aren’t Held back by 1-2 Large Miners
In ASIC market people buy ASICs in batches in a preorder. With Bitcoin ASICs there is not enough demand for ASICs so the batch often doesn’t get sold out so now the manufacturer has spare ASICs. Now that the manufacturer has spare ASICs they will often start mining with them and eventually the ASIC company has one of the highest hash rates. If the ASIC company doesn’t want a certain upgrade to go through, for example SegWit, they can vote with their hash rate to hold back the upgrade forever or at least until people who want SegWit get more hash rate.
You Have a Say in Protocol Rules and Consensus
In Bitcoin you are a passive observer because you can only issue transactions and you have no part in the process after that. In Vertcoin you can be apart of the process for deciding the ordering of transactions and deciding what transactions get into blocks.
Block Rewards and Transaction Fees are Distributed Evenly
In Bitcoin and Litecoin the block rewards and transaction fees are often given to the large miners in China due to mining centralization created by ASICs. Vertcoin distributes its mining rewards to people all around the world thanks to the mining decentralization.
When will Atomic Swaps Be Ready?
Atomic Swaps can be done in two flavors: On-chain and Off-chain (via Lightning Network). On-chain swaps were actually done already using Blocknet, you can see it in use on Youtube. We're looking into doing it again using Interledger. However our main focus is to do off-chain Atomic Swaps using Lightning Network technology. Because it has the same benefits as Lightning transactions: No network fees and instant transactions. For off-chain swaps we need Lightning Network to be fully operational. It's difficult to give an ETA on that since we aren't the ones developing it. U/gertjaap posted a video on the current state of the Lightning Network for Vertcoin a while ago, which you can see here. This was actually the "bleeding edge" of Lightning Network at the time. was able to use it on VTC's main net, meaning that our blockchain is ready for the good stuff. As you can see however, it can't yet be considered production ready (most users would want a little better UX than a command line app). Now off-chain Atomic Swaps is a technique based on the same principles as Lightning Network, but adds an extra complexity for it being across chains. So it's basically the same as a "multi hop" Lightning payment, which is not yet built by any of the implementations. They're still working hard on making the single-hop payments robust. So in order for AS to be possible, LN has to be fully operational. A timeline cannot be given at this time, because frankly we don't know. The implementation of Lightning Network we feel has the most potential is LIT, because it supports multiple currencies in its protocol (where LND is bitcoin-only at the time and requires significant work to support other currencies, which is an essential part of being able to work across multiple blockchains). LIT is open source and there's nothing secretive about its progress, you can see the development on Github. We even have our lead dev James Lovejoy (u/jamesl22) close to the action and contributing to it where possible (and our team as well through testing it on the Vertcoin chain). So we're not developing LN or AS ourselves, we're just ready with our blockchain technology whenever it becomes available. If we have any real progress that has some substance, you can expect us to let the world know. We're not interested in fluffy marketing - we post something when we achieve real progress. And we are not keeping that secret.
How do I Choose the Right Vertcoin Wallet?
Deciding what Vertcoin wallet you should choose can be a difficult process. You can choose between three different wallets: Core, Electrum and Paper. Once you decide you can use the "How to Setup Your Vertcoin Wallets" video guide to assist you.
The Core wallet is the wallet that most people should use. It will store the entire blockchain (~2GB) on your computer. The Core wallet is the only wallet that fully supports P2Pool mining. You will also have to use the Core wallet if you plan to run a P2Pool node or any Vertcoin related server.
The Electrum wallet is a light wallet for Vertcoin. You do not have to download the blockchain on your computer, but you will still have your own private keys on your computer. This is recommended for people who don't need to store Vertcoins for very long and just need a quick but secure place to store them.
The Paper wallet is as the name implies, a physical paper wallet. When generating a paper wallet you will get a pdf that will need to print out. A paper wallet is normally used for long term storage since it is the safest way to store Vertcoins. A paper wallet can also be called "cold storage." Cold storage references the storage of your coins offline, preventing you from getting hacked over the internet.
Ledger Nano S
The Ledger Nano S is a hardware wallet designed by Ledger. A hardware wallet is similar to a paper wallet since it is normally used for cold storage. The hardware wallet is on par with the security of a paper wallet while being easy to use and setup. Note: You should never mine directly to a Ledger hardware wallet.
You can get the latest version of the One Click Miner in the Vertcoin Discord. The download is pinned to the top of the #oneclick channel.
What do all the Numbers Mean on P2Pool’s Web Interface
I've seen a lot of confusion from new miners on public p2pool nodes, so here's a primer for the most common static node page style, for first time miners: https://imgur.com/K48GmMw
Active Miners on this Node
Address - This is the list of addresses currently mining on this node. If your address does not show up here, you are not mining on this node.
This is a snapshot of your hashrate as seen by the node. It will fluctuate up to 15% from the hashrate you are seeing on your mining software, but will average out to match the output in your mining software.
This is the amount of your hashing contribution that is rejected, both in hashrate and as a percentage of your total contribution. Running your own p2pool node minimizes this number. Mining on a node that is geographically close to reduce lag also minimizes this number. Ideally you would like it to be less than 1%, but most people seem happy keeping it under 3%.
This speaks for itself, it is the difficulty of the share being currently worked on. Bigger numbers are more difficult.
Time to Share
This is how long you need to mine before you will receive any payouts, or any "predicted payout." The lower your hashrate, the higher your time to share.
This is the reward you would receive if a block was found by p2pool right now. If it reads "no shares yet" then you have not yet been mining the requisite amount of time as seen in the previous "time to share" column.
This is the total hashrate of all the miners mining vertcoin everywhere, regardless of where or how.
Global Pool Hashrate
This is the total hashrate of all the miners mining vertcoin on this p2pool network, be it the first network or the second network.
Local Pool Hashrate
This is the total hashrate of all the miners mining Vertcoin on this node.
Current Block Value
This is the reward that will be given for mining the current block. The base mining reward is currently 50 VTC per block, so any small decimal over that amount is transaction fees being paid by people using the network.
Network Block Difficulty
This is the difficulty of the block being mined. The higher the number, the higher the difficulty. This number rises as the "Network Hashrate" rises, so that blocks will always be found every 2.5 minutes. Inversely, this number falls when the "Network Hashrate" lowers as well.
Expected Time to Block
This is a guess at how much time will elapse between blocks being found by this p2pool network. This guess is accurate on average, but very inaccurate in the short term. Since you only receive a payout when the network finds a block, you can think of this as "Estimated Time to Payout."
Why is P2Pool Recommended Over Traditional Pools?
P2Pool is peer to peer allowing a decentralized pool mining system. There are many nodes setup around the world that connect to each other too mine together. Many other coins have 1 very large pool that many miners connect to and sometimes the largest pool can have 51% or more of the network hash rate which makes the network vulnerable to a 51% attack. If P2Pool is the largest network then that prevents the Vertcoin network to be susceptible to a 51% attack as P2Pool is decentralized.
PPLNS Payout System
P2Pool uses a PPLNS (Pay Per Last N Shares) payout system which awards miners more the longer they mine, sort of like a loyalty system. A drawback to this system is that part time miners that aren't 24/7 won't be able to earn that much.
While Network 1 is catered towards 24/7 miners and people who have dedicated mining rigs, Vertcoin has a second P2Pool network where part time miners and miners under 100 MH/s can go to mine.
Mines Directly to Your Wallet
P2Pool mines directly to your wallet and cuts out the middleman. This reduces the likely hood that the pool will run away with your coins.
Since P2Pool is decentralized and has different nodes for you to choose from there will be no downtime because the P2Pool network does not die if one node goes down. You can setup a backup server in your miner so that you will have no downtime when mining.
Anonymity and Security
When using P2Pool you use a wallet address making your real identity anonymous, you are simply known by a random 34 letter string. Along with using a wallet address instead of a username there is no password involved P2Pool preventing the possibility of cracking your pool account (If you were on a traditional pool,) and stealing all your coins.
How do I Find a Nearby P2Pool Node
You can find the public p2pool nodes the the P2Pool Node Scanners. If you want to find a network 1 node go here. If you want to find a network 2 node go here.
The quickest way for you to get help is for you to join the Vertcoin Discord Group. We almost always have knowledgable Vertans, whether that be developers or experienced Vertans, online to help you with whatever problems you may have.
How can I donate to the Developers?
You can donate to the dev fund at https://vertcoin.org/donate/. You can select what you want your funds to go to by donating to the corresponding address. You can also see how much funding is required and how much we have donated.
The Vertcoin developers currently have a trello board where you can see the goals and what the status of said goal is. You can also vote on what you want the Vertcoin developers to focus on next.
What is the Status of the AMD Optimized Miner?
The AMD Optimized Miner internal beta is aiming to be ready by the end of September. The AMD Optimized Miner is currently being developed by @turekaj on the Vertcoin Discord. He currently does not have a Reddit account and Discord is the only way you can contact him.
What Does Halving Mean?
Halving means that the block reward for miners will be split in half. Halving happens around every 4 years for Vertcoin or 840,000 blocks. This means around December miners will only receive 25 VTC per block instead of the current 50 VTC per block. If you would like to add another question to this list please comment it and I will get around to adding it ASAP.
[Serious, long] My thoughts on what next for Dogecoin
There’s been a lot of discussion in recent days about the decreasing price of Dogecoin, as well as the risk of a 51% attack from Wafflepool or similar. I wanted to do a wrap-up of the discussions happening amongst the developers of the last few weeks, partly to illustrate that we are looking at options, but mostly to talk about what is happening. Please note that this is all rapidly changing. Dogecoin is actually moving at breakneck speed for a project of its size, especially as we still have a relatively limited core team. This is part of why we don’t write posts very often, as they become out of date so quickly as new arguments and facts are presented. Lets talk about 51% attacks first. The theory is that if anyone has over 51% of the total hashing power of the network, they can form a blockchain of their own which is considered “more valid” than the blockchain most users are on. This is because cryptocurrency blockchains are secured through proof of work, and therefore more work on a chain makes it, in essence, more valid. This risks an attacker spending coins on one chain, then releasing their own private, longer, blockchain. That latter blockchain replaces the original blockchain, and the coins they spent on the original blockchain are effectively returned to them as if the transactions never happened. It’s important to understand this because I hear suggestions that Wafflepool shouldn’t accept over 51% of the network hashrate, and unfortunately all this would do is hide the risk. Having one pool own over 51% of the network hashrate is not a problem if it’s actually being used to mine, but instead if it’s used to create a personal blockchain. The other issue raised is one of price; we’ve been steadily dropping since around early February. The core of my answers here is that you need to consider demand vs supply. What happened back in February was that we saw a surge in demand beyond sustainable levels, likely in a form of tulip mania. As supply continued (mining), and demand dropped-off, our price has dropped. This has been worsened by a succession of bad news affecting Bitcoin (MtGox and other exchanges struggling, uncertainty of China and Russia, etc.), which both directly brings down our price, as well as undermining confidence in the entire cryptocurrency ecosystem. It has been suggested (and I can believe this, but have not done my own analysis) that as multipools continue to dominate Dogecoin mining, and they tend to sell coins directly, that they are further reducing the price. Specifically, given that while there is demand for further coins from miners, as they have already expended resources on mining hardware they cannot then purchase the cheap coins the mining pools are producing. Lastly, there’s the question of ASICs; these are specialised mining devices which are significantly faster than CPU/GPU mining hardware, and typically cheaper to run due to reduced power and space requirements. Their introduction into mining at the moment leaves vastly disproportionate mining power in the hands of a few (there’s one individual with a hashrate of around 20GH/s, for example), and in time is likely to make mining on commodity hardware infeasible. We’ve had a lot of suggestions for what to do; change proof of work algorithm, add multiple proof of work algorithms, move to proof of stake, merge-mine with Litecoin, have DigiShield merge-mine with us. We’ve considered everything, and then some; I’m not sure how much discussion has happened in total, but I’ve spent over a dozen hours looking at these issues on IRC. In virtually all cases, the majority of people with the skills to implement these changes have rejected them as too high risk and/or having other significant drawbacks. In summary:
Changing proof of work introduces a number of risks; potential for a bug in the change to cause serious consequences (see recent the issue withCleanWaterCoin for examples),that we don’t manage to get a majority updated before fork and end up effectively 51% attacking our own blockchain (not to mention that at least one exchange frequently misses these updates and causes problems as a result), that the algorithm itself has problems (see the long term issues of multipools managing to exploit “random” block rewards), or we simply lose users/merchants who are fed up constantly updating software.
As a less technical concern; personally I’m uncomfortable knowingly make changes which intentionally introduce unneeded inefficiencies, which mean consumption of vastly more resources (electricity, and by proxy fossil/nuclear fuels). I imagine I’ll be swamped by shibes running geothermal mining facilities at the end of this post…
Changing to proof of stake (and this is particularly relevant in context of my previous comment) is interesting, however right now I don’t feel I personally know enough to make a judgement on how to make the jump safely and efficiently. Statistician/economist shibes, I’d love to hear more from you.
While I don’t like the idea of changing proof of work, I’m also pragmatic about these things; I am trying to find time to read up on Myriadcoin‘s multiple-PoW support, and in particular considering whether it could be hooked into the code without necessarily enabling it right now, as a harness for potential future changes.
Merged mining with Litecoin (and thanks to Charlie Lee for the invitation, of course) would likely help us mitigate 51% attack risks, by merging our mining power together, however it would introduce what have so far been considered undue issues for our mining community. Specifically, merged mining would require significant changes to mining infrastructure, adopting either p2pool or a mining proxy. Many have raised concerns that LTC miners would simply dump DOGE; personally I believe we could have an LTC/DOGE swap doing in the p2pool layer to give each miner whichever coin they prefer, to mitigate this, so this is not a risk I consider a major issue. There are also concerns that we would always be the secondary coin to LTC; personally I’d have considered a pre-defined block at which we de-merge a requirement, but again this isn’t a route we’re taking, I am just going through the evaluation I have done for reference.
Having smaller coins merge with us is interesting, however given our size in proportion to those coins, and that they are likely to be reluctant to merge with us (as we are reluctant to merge with Litecoin), I’m not expecting to see much progress in this area. We have made the invitation to DigiByte however.
The best suggestion we have so far is to out-do the multipools directly, by working on open source multipool software which is more DOGE-friendly. As I understand it two key approaches are being considered for improving DOGE-friendliness; either by directly exchanging other coins to DOGE, or through improved trading algorithms which result in less sharp shocks to the price. For very large mining farms such as SFire’s, it’s hoped this will cause them to separate from the mining pools (which they pay fees to) and go solo. This reduces fees for the miner, as well as reducing the ability for DDoS attacks to be targeted at them, and for us it reduces risk of a 51% attack, improves confidence in the coin security, and enables us to better mitigate impact of people mining huge quantities to sell. Meanwhile, the main focus is on making Dogecoin (and cryptocurrencies in general) a viable way of moving value around. The 1.7 client (beta release is imminent, and in fact if you’re comfortable compiling it yourself, the code is available from https://github.com/dogecoin/dogecoin/tree/v1.7.0-Beta-1 ) is a major re-write of Dogecoin Core to base it on the Bitcoin Core 0.9 client (with Scrypt added in, of course). This gives us significant performance improvements, as well as a better underlying architecture. To repeat; this will not be a required update, although it will be strongly encouraged as it’s a huge leap forward technologically. One of the features which is currently not working in 1.7, but will be for release, is the Bitcoin payment protocol, which massively improves the payment request/receiving process for merchants. Fundamentally 1.7 is intended to prove we have the technical skills to maintain a stable, useful coin, and help drive/support adoption. Once 1.7 is done, my immediate priority is technical documentation; we have a security specialist currently working on a guide to cryptocurrency security (setup, risks, best practices, etc.), to help give merchants and exchanges an in-depth understanding of how to securely use cryptocurrency. I’ll be addressing the need for formal standards in Dogecoin, and preparing RFCs for the “dogecoin:” URI and relay network protocol for submission to the IETF (and IANA for the URI). Lastly; there was a post recently about the need for multi-signature addresses; I’d like to add my own “hell yes!” to that, although obviously I have to prioritise. If anyone else can look at these, that would be fantastic. For anyone wanting a more permanent link, there's a copy of this on my blog ( http://jrn.me.uk/wp/what-next-for-dogecoin-mid-april-2014/ ), however posting as full text here as probably easier for most people, and I'm not sure my server would survive a reddit hug! Edit: It's been pointed out that there's no verification of the problems with Blackcoin, and the source alleging problems has a serious credibility issue. Have removed the reference now.
After many months of consideration, I have finally made the choice to announce the planned closure of BTC Guild. Below, I've outlined the closure process/timeline and reasons that this decision was made. Closure Timeframe and Process As identified in the support section and in the 2nd post on this thread, BTC Guild has had an official policy for the amount of time that will be given in the event of closure. The official date that BTC Guild will cease all business is January 31, 2015. This post is the start of the identified 3 months of warning. 1) Effective immediately, registrations are closed to new users. 2) BTC Guild mining servers will remain online until November 30, 2014. 3) Users will have until 11:59 PM (PST) on January 31, 2015 to withdraw any remaining balances on their account. The above timeline may change if BTC Guild is sold prior to the planned date of closure. Main Reasons for Closure 1) Risk/cost of a successful attack against the pool. As pooled mining in general is shrinking due to large manufacturers creating private farms, the potential revenue for the pool has gone down as expected. While the pool is still very profitable, the amount of time it would take to recover from an attack has increased due to the overall share of the network shrinking. BTC Guild has, to date, never been successfully hacked. However, I have seen a rise in attack attempts, and things like Heartbleed/Shellshock which show that efforts are being put into compromising common Linux services if possible. Neither of those attacks had any affect on BTC Guild, but they were both reminders that under BTC Guild's own code, there are many services which could be a doorway into the pool's servers if a vulnerability was discovered. One successful attack could cost close to a year of pool revenue, maybe more depending on what happens in the mining landscape over that period of time. If something else happened in that time (subsequent attack or regulation forcing closure), it would mean continuing to operate the pool beyond this point has cost me more money than it might potentially make in the rest of its lifetime. 2) US government/regulators are already taking stances against specific business types in Bitcoin, applying requirements which would be impossible for BTC Guild to operate under if they attempt to extend regulation into pooled mining, either directly or indirectly due to unclear definitions. Nobody will mine on a pool which requires them to provide personally identifiable information when they can change a single line in their configuration to point elsewhere. Additionally, state regulators are starting to make noise about Bitcoin. New York is the first to publicly put anything forward, but there are 49 other states which can put their own spin on things. Due to the ability for states to establish a nexus for businesses dealing with their state's residents, it is a scary landscape to continue operating in. I have no intention of leaving the US myself, and given the recent history of the US when it comes to online businesses, I don't feel safe simply moving the business legal entity to another country while continuing to live in the US myself. Aquisition and Users's Privacy/Funds In the event that BTC Guild is acquired prior to closure, users will not have their mining history and withdrawal history transferred to the new owner. All balances up to the date of aquisition will be retained by myself, and a separate service will be made available to claim any funds owed. I am unwilling to compromise on this, because I refuse to do anything where it puts the users of the pool at risk of not receiving what they've earned under my watch. Pool Recommendations and Advice For users looking for a new home for their miners, I highly recommend BitMinter, Eligius, and p2pool. I do not recommend Slush over any of those 3 options, and I actively encourage users to not use Discus Fish or GHash.io. Other smaller pools exist which are run by honest people, but due to their size, it is difficult to recommend them to the average miner. Closing Words When I got into Bitcoin back in March of 2011, I never expected anything that we've seen over the last 3 and a half years. I had never built a computer before, never run a server beyond a Gentoo PC in a spare bedroom, and never setup a website that experienced even 0.1% of the traffic BTC Guild gets on an average day. Bitcoin and BTC Guild have both radically changed my life. While I am closing BTC Guild, I still plan to remain a part of the Bitcoin community. I do believe, even in the face of over-regulation, that Bitcoin will continue to grow and become more useful and usable. I just feel that it is time to move on from BTC Guild, and take pride in the fact that BTC Guild's closure can show that not all Bitcoin businesses end with somebody stealing funds from their users, either by "getting hacked" or outright theft.
Hello Vertans! Here is my instructive tale about my first 'green' steps.
So hello fellows! *Long story short: * I started to use Crypto currency in the mid '13. Bitcoin was around 200€. Tried mining (CPU, GPU), setting up a full node on a company server :) Lived trough the hype with the BTC rising around 900€ in November 2013. Then after it becomes falling. I lost interest in the crypto world. Fast forward to now: *I have purchased my first Vertcoins! Yeeeeah! * Im working for a laarge IT companywith full of geeks. Started to talk about BTC and it was all over the news. So i was back in the business :) Looked at BTC... Holly SSs... After a while started researching and found out that lots of Altcoins are wort nothing. I mean value, not m00ney! I ended up here. My reasons are:
BTC is now overloaded
Too expensive transactions
Extreme slow transactions even after putting a high fee (10€)
It already lost it’s purpose.
Mining is only for the big fishes, who processing only the large fee transactions
How i brought my coins: Opened a Coinbase account some time ago and purchased BTC via SEPA transfer. I saw how “bad” is the BTC situation I decided to use some altcoin, and my research took me here! 1st try: the big loss: Open shapeshift web > Select BTC – VTC in precise mode. There is a ticker with time, starting from 5 minutes and counts down. So I send my BTC to the given address, specify my VTC and returning address. Then wait…. The time was Fucking over, no VTC, transfer pending somewhere in the network. Later that day: I received my money back to coinbase account. I payed 2X the fee, so was short in around 18€ 2th try: Did research on the BTC network load. At the 1st try it was overloaded then newer before. So I looked it today early morning. The chart was low, transactions fee was kinda ok. So I did coinbase > shapeshift (quick) > VTC! My todo for the Vertcoin community:
Doge Street is giving away 150,000 Doges to raise awareness of P2Pools and raise the global P2Pool speed
For those new to us, P2Pools allow mining to be decentralised. Pool operators can set up nodes that connect to each other and share hash speed. There are many benefits for miners
No funds are kept on the pool server, payouts are automatic whenever the P2Pool network finds a block (no chance of coins being stolen)
No need for registration, you only need your payout address
P2Pool nodes keep shares synchronised, so if a node does go down you will not lose any shares.
if you want a more in depth explanation, you can find one here. However - I'll be brutally honest here. Because of the way P2Pool works, miners that have speeds that are lower than 100kh/s will have trouble getting payouts (in semi-rare cases up to 24 hours with no payout). I'm running the node at Doge Street and I will give out 25k in Dogecoins every 3 hours to all P2Pool patrons (you can mine on any node, don't have to use mine) until 150k have been given out. The 25k giveaways will be distributed to those on the P2Pool payout list according to the share standings). I know a lot of Shibes here run P2Pool nodes as well. So if you all want to plug your nodes in the comments or if you'd like do a give away, you are more than welcome. Raising the global P2Pool speed benefits all P2Pool miners, since we'll be able to get more blocks faster and earn a bit more from the transaction fees. The global pool speed is currently ~200mh/s, help us take it into the gh/s range! edit: Give away is still continuing, 1st payout in 20 minutes. Since not much people have seen the post, we'll send out 25k every 3 hours so more people can get in. edit: 1st 25k sent, the rest will come every 3 hours. I set a script do to it automatically. edit: 2nd 25k sent edit 3rd 25k sent edit 4th 25k sent edit 5th 25k sent edit 6th 25k sent Upvote us and help p2pools grow! If you are coming in just now, it's not too late to get into the give away. I still have some funds left to encourage miners to switch to p2pool. If you didn't anything from the 25k chunks, message me and I'll send some more over.
This is the error I'm getting while trying to run a P2P and I am not technical enough to know what to do now
This is the error I'm getting now and my batch is: server=1, rpcuser=node, rpcpassword=***************, rpcport=5888, rpcallowip="my public ip", rpcallowip=127.0.0.1 Error while checking Bitcoin connection: Traceback (most recent call last): File "twisted\internet\defer.pyc", line 653, in _runCallbacks File "twisted\internet\defer.pyc", line 1357, in gotResult File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator --- --- File "p2pool\util\deferral.pyc", line 41, in f File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\bitcoin\helper.pyc", line 17, in check File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\util\jsonrpc.pyc", line 126, in _http_do twisted.web.error.Error: 401 Unauthorized
I’m so frustrated!!! I’ve been trying to set up a node for days and every time I think I have it, I run into another problem.
I’ve gotten 501 forbidden error, connection actively rejected by host and I thought my port forwarding was screwed up but it wasn’t. I really need some directions. I’ve tried every guide an tutorial I could find but none have any explanation of the errors I’m seeing EDIT: This is the error I'm getting now and my batch is: server=1, rpcuser=node, rpcpassword=***************, rpcport=5888, rpcallowip="my public ip", rpcallowip=127.0.0.1 Error while checking Bitcoin connection: Traceback (most recent call last): File "twisted\internet\defer.pyc", line 653, in _runCallbacks File "twisted\internet\defer.pyc", line 1357, in gotResult File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator --- --- File "p2pool\util\deferral.pyc", line 41, in f File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\bitcoin\helper.pyc", line 17, in check File "twisted\internet\defer.pyc", line 1299, in _inlineCallbacks File "twisted\python\failure.pyc", line 393, in throwExceptionIntoGenerator File "p2pool\util\jsonrpc.pyc", line 126, in _http_do twisted.web.error.Error: 401 Unauthorized
5 Fun things and useful services you can contribute to the network if you run your own full node!
Our active node count just above 500 nodes, which while the 4th most nodes for a crypto (behind bit, dash and lite) still seems pretty low given the size of our community. So I thought I'd make this little post to show some cool things to do with a node rather than just leave it sitting there running.
Add your node's IP as a "trusted peer" in the Android wallet so you don't have to trust random nodes in the network. You'll know your node is running the longest chain and that confirmations shown in your android wallet are valid, because your node verified them and not someone else's. Instructions: Go into settings in the Android wallet and set the public IP address of your node as the trusted peer.
Host your own blockchain explorer. Maybe you don't trust 3rd party explorers. Or maybe sometimes what your Core client is telling you and what 3rd party explorers don't match up (they really should though). Maybe you'd like a user friendly interface to explore YOUR blockchain on the internet from wherever you are that you own instead of someone else's. Here is a very early open source blockchain explorer which works with multiple blockchains Instructions (Python)
Run your own P2Pool mining node in conjuction with a litecoin node. You can mine with work generated from your very own node, no more trusting pools not to use your hashpower maliciously or paying pool fees. Other miners can connect to you also to receive work and find blocks mining litecoin and merge mining dogecoin. Instructions (Python)
Run an electrum server. Electrum for doge has had a rough history, it had been up and running like 3 times and currently isn't working again. I'm not completely sure why it failed, I think it was simply because no one was willing to run a server. Some more development might be needed before this is an option again, I'm not real sure where we stand there. Anyone else know? Instructions (Python)
You can make Bash scripts to do things automatically. Maybe you want to consolidate all your small faucet inputs into a single output every day or week and check the balance, send a portion to deposit to dogetipbot and backup your wallet.dat. You can script that instead of doing it manually. Here's a great reference for bitcoind commands, but all of it applies the same to dogecoind.
A note about security - you are broadcasting your IP to the entire cryptocurrency world when you run a node. It is essential that you run on an uncompromised computer kept free of malware, keyloggers and viruses. It is essential that you encrypt your wallet.dat with a very strong password (>16 chars, numbers and symbols). I would recommend not keeping too much in your wallet, keep most of it stored securely in an offline address.
While DDOSing my pool, check out what this asshole sent me
So I run blisterpool.com (simple p2pool node + layer of bonuses), and this asshole decides to try to extort 2btc from me. My node has been under a ddos attack for about 2-3 hours now. I get an email to all my addresses, and then finally a message on bitcointalk a few minutes ago. Copy/pasta of message:
DD4BC Newbie * Online Online Activity: 1 View Profile Personal Message (Online) Trust: -11: -2 / +0(0) Warning: Trade with extreme caution! HELLO? « Sent to: Hunterbunter on: Today at 04:02:32 PM » Reply with quoteQuote ReplyReply Remove this messageDelete Hello Your mining server is extremely vulnerable to ddos attacks I want to offer you info how to properly setup your protection, so that you can't be ddosed, at >least not with so little power. My price is 2 Bitcoin only. Right now I'm running small (very small) attack which will not crash your server, but you should >notice it in logs. Just check it. If I increase the attack size, I could completely crash, it would drop all connections and damage >would be big... Don't worry, I will not do it. Smiley I want to offer you info on how I did it and what you have to do to prevent it. If interested pay me 2 BTC to 17aLGgw8AwJdqiBtMMG1QtQJgNQQkiyEsp Thank you.
It's a shame for him that I can just shut the server down for a while and join one of the hundred other public p2pool nodes out there.
From my local P2Pool: p2pool.util.jsonrpc.NarrowError: -32601 Method not found
I've run my own local P2Pool server for well over a year now. I had to upgrade everything because of recent changes to the BTC protocol and etc. But that's the last error it keeps throwing. And then it spits out the following over and over and over again...
Error while checking Bitcoin connection: Traceback (most recent call last): File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 651, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 1355, in gotResult _inlineCallbacks(r, g, deferred) File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 1297, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File "/uslib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) --- --- File "/home/lunacy/p2pool/p2pool/util/deferral.py", line 41, in f result = yield func(*args, **kwargs) File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 1297, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File "/uslib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File "/home/lunacy/p2pool/p2pool/bitcoin/helper.py", line 13, in check if not (yield net.PARENT.RPC_CHECK(bitcoind)): File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 1297, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File "/uslib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File "/home/lunacy/p2pool/p2pool/bitcoin/networks/bitcoin.py", line 16, in not (yield bitcoind.rpc_getinfo())['testnet'] File "/uslib/python2.7/dist-packages/twisted/internet/defer.py", line 1297, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File "/uslib/python2.7/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File "/home/lunacy/p2pool/p2pool/util/jsonrpc.py", line 133, in _http_do raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None)) p2pool.util.jsonrpc.NarrowError: -32601 Method not found
And yeah wow what a mess. That was the cleanest I could get it too... :|
I think there's an interesting legal liability question here - if someone buys a product and then uses your service to Finney attack the merchant, are you part of a conspiracy to defraud the seller?
-Mike Hearn What Mike is saying is that even though the Bitcoin protocol allows miners total freedom to put any valid transaction they want to in their blocks, the legal system may be used to try to restrict that freedom and punish miners to don't the de facto practice of only mining the first valid transactions broadcast to the network. It's easy to see the legal case playing out: suppose insecure hacks like Mycelium's transaction radar catch on. We'll have a lot of people doing transactions that depend on miners all following the same mining rules, and eventually someone is going to get hurt. They're going to want to find someone to sue, and what better than the mining pool who mined the double-spend transaction? What's wrong with that? Of course, first and foremost by encouraging people to use Bitcoin insecurely we invite heavy handed regulation when things go wrong. We're already seeing regulators cite the hundreds of millions of dollars lost by MtGox as evidence of the need for legal regulation, rather than technological measures like multisig. Why make the exact same mistake all over again with unconfirmed transactions? There's a deeper reason too: relying on unconfirmed transactions is only possible by making Bitcoin more centralized at the mining level, at the network level, and at the development team level. Every Bitcoin release accepts a slightly different set of transactions as valid - do you want to be worried about legal liability if your mining operation allows an attacker to rip off someone because you upgraded sooner or later than the rest of the network? Or just were using a different client all together? Like it or not, if one miner accepts a different set of transaction types than another, that's an opportunity to double-spend. At the network level transactions simply do not and never will propagate through the network instantly. At the same time until a transaction is confirmed there isn't any proof that the transaction propagated to any hashing power at all - the proof that a transaction was succesfully published is in the form of PoW only. Again, the only way to make unconfirmed transactions even close to safe is to make the network of miners smaller - do you want to be exposed to legal liability just because your small mining pool had a worse network connection than the biggest pool? You could even be in a situation where you've been sybil attacked, preventing you from seeing some transactions at all. You won't have any proof of that fact - instead it'll look like you participated in an attempt to rip someone off. Finally it's been proposed multiple times that merchants pay for security directly with insurance contracts with major minering pools. The miners agree not to double-spend, and the merchants pay extra for that. Of course, if you're a small miner you're not going to get these contracts - you're much too small to bother talking to. The major mining pools wind up earning more BTC/hash than you, and on top of that, if you ever do end up including a double-spend in one of your blocks it's quite likely those contracts will have those pools just kill off your blocks in a re-organization. The fact is Bitcoin by itself just isn't suited to instant confirmations: if you want decentralization, you have to give everyone time to come to consensus securely. Fortunately we have lots of technologies that can be used in conjunction with Bitcoin for the times when 10 minutes isn't good enough, but if we don't use them we'll end up with a less secure and less decentralized Bitcoin. What you should do if you're a pool operator, solo miner, or mine on p2pool Replace-by-fee simply means that rather than only accepting the first transaction you see to your mempool, you accept whatever one pays the most fees. It's a simple rule that results in the most profit per block, lets users re-issue transactions with higher fees if needed, and most importantly, makes it clear to everyone that relying on unconfirmed transactions by themselves is insecure. I've written a simple replace-by-fee patch based directly on the v0.9.1 codebase. Installation is just a matter of getting my replace-by-fee-v0.9.1 branch from https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.1 and compiling it; you run the code just like you would normally. Unlike BitUndo it's an entirely decentralized system where the 100% of the profits for replacing one unconfirmed transaction with another goes directly to miners. The patch implements preferential peering, which means it seeks out other nodes supporting replace-by-fee to ensure you'll always be connected to like-minded peers; you don't need to -addnode a central server. While I wouldn't recommend a pool like ghash.io to install it right off the bat, if you're a miner on, say, p2pool, installing the patch carries no risk to you, and will help keep Bitcoin decentralized in the future.
F2Pool is a geographically distributed mining pool, helping miners all over the globe secure Bitcoin and 40+ Proof–of–Work networks since 2013. Bitcoin-Qt ist ein Open-Source-Projekt und derzeit einer der sichersten Vertreter unter den Mining-Clients. Hier müssen Sie sich nicht um eventuelle Angriffe auf Ihr virtuelles Geld sorgen. Ebenfalls Open-Source und vertrauenswürdig ist Electrum.Das Tool punktet mit einer 2-Faktor-Authentifizierung, dem Support von Add-ons und der Möglichkeit, Ihre Keys jederzeit in andere Bitcoin-Clients ... As the Bitcoin P2Pool article describes it, "P2Pool is a decentralized mining pool that works by creating a peer-to-peer network of miner nodes". The most important aspect of P2Pool is that it is highly decentralised, operating through peer-to-peer communication between many, many nodes, as opposed to placing pooled mining power into the hands of traditional mining pool operators, thus greatly ... E-Pool is a Bitcoin and altcoin mining pool running on the P2Pool model where miners connect to a decentralized node. This pool uses the PPLNS payment method with a 0.25% fee. Users can mine BTC, LTC, VCN, ZTC, XJO, BXT, CSC, CAT, NOTE, FRK, GAME, NLG, SEX, WDC, FST, EMC2 QRK, SRC, CNO, DGC, DASH, […] P2Pool approach. P2Pool mining nodes work on a chain of shares similar to Bitcoin’s blockchain. When a block is found, the reward is divided among the most recent shares in this share-blockchain. Like the puddinpop and Luke-Jr approaches, p2pool pays via generation. Comparison
What is the best or most profitable mining pool? Specifically Litecoin mining pool or a scrypt based multi-coin mining pool that the bitmain antminer L3+ can mine on. I showcase my results with ... Gource visualization of p2pool (https://github.com/p2pool/p2pool). Peer-to-peer Bitcoin mining pool Chamath Palihapitiya Live: Bitcoin Halving, BTC Updates, Price and Mining Chamath US Live 57,685 watching Live now DIY Bitcoin Mining: Hardware (part1) - Duration: 7:45. In diesem Tutorial geht es um den speziellen P2P-Pool. Früherer Zugang zu Tutorials, Abstimmungen, Live-Events und Downloads https://www.patreon.... Full node configuration: server=1 rpcuser=user rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED_385593 Download P2Pool: https:...