5 Steps to Install Bitcoin-Qt Faster - Bitcoin-en.com
Instaling BTC Core - Prune settings help
I am installing BTC Core for the first time on my mac. I am trying to instal the pruned verison. What I've done is begun the complete installation by default because without there is no directory create on my system. When the installation begun and I had my directory then I accessed it the right way to create the bitcoin.conf file: - Library/Application Support/Bitcoin Then to the conf file included prune=550 and then restarted the the installation. Now the estimated time to sync is around the same as when I started without the prune. Is this the right way to proceed? Is there any way to confirm that now a pruned version is being created? Thanks for your help and also your understanding that I am a beginner with beginner questions.
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.
(Upvote to the top) > SOLUTION FOR ZCLASSIC Eleos Wallet: "Wallet daemon can not be run. Check if daemon does not already run"
So I noticed a lot of people recently (including myself) are experiencing the error "Wallet daemon can not be run. Check if daemon does not already run" when trying to open up their ZCL Eleos wallet, and people are unable to access their funds or cannot export their private keys as well. A solution to this is now official (thanks to JBrutWhat from the BTCP team for helping me out on this.) Note: Post is being edited as more info becomes available to me. This solution also works for users who are on the ZClassic Swing wallet experiencing the error "A general unexpected critical error has occurred: error: Couldn't connect to server, see the console output for more detailed error information!." Eleos Wallet Troubleshooting section
The Wallet.dat file from the Eleos wallet or Swing wallet DOES NOT work with Zclassic electrum, so we are going to import the private key of the wallet into electrum instead.
Navigate to the c:\users\username\appdata\roaming\zclassic folder and copy the wallet.dat file from there, back it up somewhere.
Paste the wallet.dat you backed up earlier into the same folder as the walletaid tool folder
Right click the config.ini file and edit the file using notepad or notepad++ or your own text editor
remove the "#" symbol from the zclassic sections under "#Pubkeyprefix list" and "#privkeyprefix list"
copy the text "1cb8" and replace the "00" under the pubkeyprefix section under "[settings]" at the top
Doubleclick the walletaid.py file and press enter. Let it create the entire file with ALL the wallet addresses from your wallet.dat file. Or you could paste in the exact address you want and it should export a foundkeys.txt file into the walletaid directory. (The extract keys.bat file doesn't always work. It didn't work for me.) NOTE: If the walletaid.py script opens and instantly closes, this is because your wallet.dat file has a different name. Please rename your wallet file back to "wallet.dat" for compatibility.
Open up the foundkeys.txt file and it should list out every detected address and it's corresponding private key from your wallet.dat file you pasted in earlier
Do a ctrl + F and paste in the wallet address that contains your funds.
Locate the wallet address you are looking for and it's corresponding private key. We'll come back to this later.
IMPORTANT: MAKE SURE YOU DELETE THE PRIVATE KEYS FILE FROM YOUR COMPUTER AFTER FINISHING WITH IT. BACK IT UP TO AN OFFLINE USB STICK. DO NOT KEEP IT ON YOUR DESKTOP/HARD DRIVES OR ONLINE. Your private keys can potentially compromise ALL of your funds. Keep this safe and NEVER share it with anybody.
For users that are experiencing problems syncing their Electrum ZCL wallets, or their transactions are showing "not verified" after importing a wallet, this is because the blockchain_headers have not been successfully downloaded. We'll have to delete them let it re-sync. For Windows users, first close the electrum wallet. Then navigate to C:\Users\UsernameXXX\Appdata\Roaming\Electrum-ZCL\ and from there delete ONLY the "blockchain_headers" file. Then re-open the wallet and allow it to sync. For Mac OS users, close the wallet and navigate to ~/.electrum-zcl/ and delete ONLY the blockchain_headers file once again. Then reopen the wallet. Please see github issue #77 thread here for more help.
Create a new standard wallet and restore the 2FA wallet using your "seed" codes. DO NOT password protect this wallet.
Disable the 2FA feature when presented with the option.
Navigate to C:/Users/YOUR-NAME/AppData/Roaming/Electrum-zcl/wallets. Open the new standard wallet file with Notepad.
You will need to gather the 2 private keys and one public key. To find this easily, press “CTRL+F” and search for “xprv”. Copy the 2 “xprv” values as well as the last “xpub” value. You will need these in a later step.
Create a new “Multi-signature wallet”. Select “From 3 co-signers” on the first slider. Select “Require 2 signatures” on the second slider.
To add the first co-signer, click “Use public or private keys”. Enter the first xprv key in this box.
Add the second co-signer via a private key also.
Add the third co-signer with the public key. Complete the set-up.
Your wallet funds now have the ability to be sent from the multi-signature wallet.
It's recommended by the BTCP team to switch over to the ZCLASSIC Electrum wallet ASAP as the Eleos wallet has become unstable now. The original ZClassic swing wallet is reported to still be working. Up to you whether or not to use the electrum wallet, but I'd personally recommend it.
Open up the wallet and create a new wallet, then when it gives you the option to import private keys, paste in your appropriate private key from the foundkeys.txt file we generated earlier.
Afterwards, your wallet should have successfully migrated your wallet into the ZCL electrum wallet. There's currently a synchronization issue upon first boot of the wallet, so close and re-open it again and you should be fine. If not, try closing the electrum wallet, navigate to "c:\users\username\appdata\roaming\Electrum-zcl folder and delete the "blockchain_headers file, as initial download of the blockchain headers sometimes initially fails. Then restart the wallet and you should be fine, according to the dev team.
Users of older ZCL electrum wallets before version 1.0.3 should download the latest version. I was on the older version (1.0.0 and noticed my wallet wouldn't sync.) So I upgraded to the latest version and wallet has successfully synced.
Also make sure to encrypt your electrum wallet by clicking the little settings icon at the bottom right.
For Users who were already using the Electrum wallet beforehand, you can go to file > new/restore wallet > next > import zclassic private keys and input the private key you obtained from the walletaid tool, and it should import the wallet into the electrum wallet. Then from there, go to file > backup wallet and export a copy of the wallet.dat file onto an offline USB.
Side notes: ZCL-Electrum wallet Does support mining directly to it. More ZCL Electrum servers will be added along with newer releases soon. Another note: Every time you want to migrate funds from one address to another, test it with a small amount first before proceeding with the full amount. BTCP Team has also partnered with Coinomi to release a wallet supporting ZCL and BTCP after the hard fork occurs.
Reminder: Backup and delete the private keys file from your desktop pc/hard drive, move it into an offline USB for safekeeping. Do not leave it on an online device. Donate to me if you found the guide useful! Your donations 100% voluntary but they are greatly appreciated and keep us going! ZCL: t1fkxCWJs3f2oXznGwZuEgftJ2SCjYZ8VjZ BTC: 14Xmfm9jf4h1h4RXZBQCFK6i4LWibqWVPu LTC: LhAERgWcjbbXQbGqjhy4owALGhwfpj1aw2 ETH: 0xe723305337926e1fcb5dd0495e6648569a252c13 BCH: 1JXqLHqjYH8bew38AXwEt9dmKvsdYwLtvr LINKS (You can join the discord rooms where there are channels for users looking for help)
Groestlcoin September 2019 Development Release/Update!
For a more interactive view of changes, click here In our current world; bordering on financial chaos, with tariff wars, Brexit and hyperinflation rife, you can count on Groestlcoin to consistently produce innovation that strikes to take the power away from the few and into the many, even after a full five and a half years of solid development. Here is what the team has already announced in the last 3 months since the last development update:
Groestl Nodes aims to map out and compare the status of the Groestlcoin mainnet and testnet networks. Even though these networks share the same protocol, there is currently no way to directly compare these coins in a single location. These statistics are essential to evaluate the relative health of both networks.
Shows Onion (Tor) nodes
Shows IPv6 nodes
Supports both main net and test net
Node Checker – Check the status of a remote node
Ability to download node data by CSV, JSON or TXT format
Ability to download unique address data by CSV, JSON or TXT format
This is a tool for creating unsigned raw Groestlcoin transactions and also to verify existing transactions by entering in the transaction hex and converting this to a human-readable format to verify that a transaction is correct before it is signed.
Create Raw Unsigned Groestlcoin transactions
Generates a QR code for the transaction
Compatible with most Groestlcoin wallets including but not restricted to Groestlcoin Core and Electrum-GRS
Estimates final signed transaction size
Taking a raw transaction format and shows its Transaction ID, Transaction Inputs and Outputs
AGCore is an Android app designed to make it easier to run a Groestlcoin Core node on always-on Android appliances such as set-top boxes, Android TVs and repurposed tablets/phones. If you are a non-technical user of Groestlcoin and want an Android app that makes it easy to run a Groestlcoin Core node by acting as a wrapper, then AG Core is the right choice for you.
Update to Groestlcoin Core 2.17.2
Switched to native builds via NDK for Groestlcoin Core resulting in a smaller footprint.
Added embedded tor
Added tor pairing support
TOR upgrade bug fixes
Improved blockchain Sync progress using getblockchaininfo verificationprogress
Improved package download progress bar
Added support for external storage access > Android M
Added support for Android Oreo, including new notification mechanism
Bump Fee (RBF) improvements – Implemented a new fee-bump strategy that can add new inputs, so now any transaction can be fee-bumped. The old strategy was to decrease the value of outputs (starting with change). We will now try the new strategy first, and only use the old as a fallback.
Coin Choser improvements
More likely to construct transactions without change (where possible)
Less likely to construct transactions with really small change
Only spend negative effective value coins when beneficial for privacy
Fix long-standing bug that broke wallets with >65k addresses
Windows binaries: Now build the PyInstaller bootloader ourselves, as this seems to reduce anti-virus false positives
Fix performance regression for large wallets
Fix high-DPI issues related to text fields
Trezor – Allow bypassing 'too old firmware' error
Trezor – Use only the Bridge to scan devices if it is available
Hardware wallets – On Win10-1903, some hardware devices with U2F functionality can only be detected with Administrator privileges. A workaround is to run as Admin, or for Trezor to install the Bridge.
The AppImage Linux x86_64 binary and the Windows setup.exe are now built reproducibly.
Fix watch-only wallets that could not bump fee in some scenarios
Faster transaction signing for segwit inputs or really large transactions.
Groestlwallet is designed to protect you from malware, browser security holes, even physical theft. With AES hardware encryption, app sandboxing, keychain and code signatures, groestlwallet represents a significant security advance over web and desktop wallets, and other mobile platforms. Simplicity is groestlwallet's core design principle. Because groestlwallet is "deterministic", your balance and entire transaction history can be restored from just your recovery phrase.
iOS 0.7.3 Changes
Fix BIP70 payments
Updated QR Scanner
Lowered spending limit
Updated DNS Seeds
Fixed URL Scheme
Fixed GRS Name in mailing
Fixed crash upon starting in some scenarios
Android v89 Changes
Use default fee
Republished on Google Play by removing send_sms permissions
Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)
Hi! Happy if this guide helps you. Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v UPDATE 04/06/17 Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF. UPDATE 03/13/17 ADDED a tl;dr; Version at the end of this Post. UPDATE 03/12/17: Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning. Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works. I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui. The SD is almost full, but it works so far I also updated the whole manual a bit to make things more clear. Thank you for all your feedback! Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far. I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi. Have fun! I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways. Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't! If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much. This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully. For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual. I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain. PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node! The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it! Now you might think "but you said less than 16GB in the title!" Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning. Maybe even a 8GB SD Card works just fine including Linux (jessie lite)! So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it. For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)
This is the manual how to get started on you PC / MAC / Linux (I did it on Win7) Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64). Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive. You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows. or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add
to the file. Line by line. By the way here you could also just add dbcache - to use more memory to speed up the process a bit:
if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values) You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine. So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD. The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe! Make sure to close the client always via "quit" - ctrl+q. After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE! First - close the Client and let it close smoothly. After it is really closed you can follow these steps:
By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.
Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD. You can prune by editing your bitcoin.conf file by adding:
I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.) Save the bitcoind.conf file and restart your windows client. It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data. Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client. Inside the Bitcoin Folder, you'll find two folders called:
those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later! Now you are good to start the raspi transfer explained in the next part.
Here is what I did: 1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line) 2) I followed partly this tutorial to get everything running and setup:
Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped. On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS. Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here. I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here! It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi. So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE. I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI. Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.
sudo apt-get install git -y (only jessy lite)
I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.
as I don't need the wallet functionality. I didn't need to use "MAKE" which saves you maybe up to 2.5 hours. instead you can just go ahead with:
sudo make install
(If I am wrong in doing so - please let me know) The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing. After the installation took place you can finally get your Raspberry Pi Node running in no time! To test if the the installation went through - you can just start bitcoind using:
than check if everything is working so far:
after a few seconds you should see version: etc... if not, something went wrong. Try to redo the steps in the raspnode tutorial. (don't give up if it failed - retry! Ask your questions here) IMPORTANT: you need to stop bitcoin on your raspberry now!
If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):
cd .bitcoin sudo nano bitcoin.conf
and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)
That's it for the raspi. update: To signal UASF enter in a new line:
Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry. I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple. Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH) You should now see the directories on your Raspberry Pi. There is a folder called
enter it and you will see the two folders
blocks & chainstate
you can delete them on the raspberry as they have some data from your previous test inside. Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file. Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder. I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed. The whole copy process might take some minutes (against some weeks in the old way). After copying is finished, you can now start bitcoind on the Raspberry.
the & symbol let you still use the command line while the process is running btw. The process - if succesfull - will take some time to finish.
Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good! If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes. Congrats! You are almost a part of the network! To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it! You can now go to: https://bitnodes.21.co/nodes/ scroll down to "JOIN THE NETWORK" and check check if your node IP is connected! It will show up as soon as the blocks are checked and the raspi is running. Well done! Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks! I really hope, my little tutorial worked for you and your are part of the Node network now. If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better. Have fun and NODL! the noob tl;dr; (if you are a real noob start with the non-tl;dr version!) tl;dr; PART ONE 1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download 2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB). 3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin 4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain. You are running a full node on your PC. tl;dr; PART TWO 1) Install jessie lite and the needed dependencies on your SDCard - Raspberry ( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )
see tutorial for more info.
2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC. 3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin 4)Start "bitcoind &" 5) let everything sync 6) Make sure you have port 8333 opened on your router. You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard) Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v updated 03/12 - will update more, soon. updated 03/12.2 - I updated the whole process a bit and also added some improvements. updated 03/14/ Added a tl;dr version at the end.
OLD STUFF I rewrote the post after my discovery of how the network traffic works. The answer in short, unfortunately, is NO. But R* can detect it. I will assure you. From several tests, there are NO distinguishable traffic from the UDP protocol, in a public lobby that allows you to identify a modder, if you are being harassed by one. However, I tested two mod menus on my decoy account (I have two Steam accounts, and two Rockstar Social Club Accounts). The one thing that is significant is that there is a suspicious communication to the Rockstar servers. Mod menus generate DTLSv1.0 packets. Sent to Rockstar's servers at "18.104.22.168 prod.ros.rockstargames.com". Playing the game legitimately, no DTLSv1.0 packets are sent. But if you load a mod menu, Rockstar knows. The problem is, it is traffic going to the dedicated Game Service Servers. You, as a random person in a public lobby, will not be able to see it. TLDR... Let Rockstar catch and ban modders. You will never find them They are doing a pretty decent job. According to MPGH chatter, since four days ago a lot of the mod developers are pulling out of implementing money hacks into the game. As they cannot find a way to get past R* Anticheat yet. http://www.mpgh.net/forum/forumdisplay.php?f=414 I tested the one with the "Safe Money Drop". My decoy account got banned for 30 days. But you could be a real creepster. And tell people with unprotected (no VPN no proxy) internet connections, what city and state they live in. That still works. How to do that? I tested it on 5 different people already, all my friends. In-game, you have to be following the player around. The closer you are with the player, the more bytes are generated and sent between your IP and theirs. That helps you distinguish their IP from anyone else's. Now
Start Wireshark capture Statistics Endpoints Bytes Tab (Sort by highest) Your highest NON-LOCAL IP on ports 6672 (UDP, most players have traffic through this) is the player's IP
Using that IP, you can choose to either click the Name Resolution Checkbox on the bottom left of the Endpoints window. Or, you can just Google it. The potential of this vulnerability? DO NOT DO THIS Lets say you wanted to be a douchelord or something, and you don't like another player. Keep GTA V running in Windowed Mode, fire up wireshark, start capture. Locate the player IN-GAME and follow him around for at least one or two minutes. After you positively identified the player's IP (using the bytes-captured method on port 6672), you can attack it with a subscription DDoS/DoS Botnet provider. Also known as a "stresser" or "booter" for obvious reasons. (Note: they only accept either BitCoin or PayPal, I hate both of them). A few examples... (1) Defiance Protocol (2) Thunder Stresser (3) PolyStress (4) Stress3d.me (5) DataBooter (6) ExoStresser What does it do if you choose to do this? Well, first of all, even though they are known as booters or stressers, they initiate a Denial of Service attack on the victim machine. That means even if you left the session (you better), you can initiate the attack. It will shutdown their entire home network for a X amount of ms, just enough to kick someone, including the host of the lobby, out of the session. All you need to know to launch the attack is... (a)The IP address of victim machine (b)The Port you want to attack (port 6672) (c)The method of attack (chose one that is relevant to the protocol), like TCPStorm, DOMINATE, SYNFLOOD, etc. Seriously, don't do it. All I figured out is how to stalk my friends on GTA V. I have yet to even learn how to decrypt the captured GVSP data. If you want to catch modders on your own, you need to crack that hash. Seems like there is a new key generated a session. Hopefully R* in GTA VI will patch this vulnerability. GOOD LUCK, DON'T DoS people, and GO sign up for a VPN or Proxy, RIGHT NOW. Stuff Online on DTLSv1.0 Traffic https://wiki.wireshark.org/DTLS DTLS is a SSL Protocol that is compatible through UDP. It can be used to create SSH Tunnels back to R* Servers. Since the last thing a mod developer wants to do is give R* all of your info willingly, I am assuming that this DTLS traffic is part of the anticheat mechanism implemented by R*. DTLS traffic, as of yet, cannot be filtered by capture alone. However, you simply just look at the packet, and then filter the UDP traffic and port to display the majority of DTLS traffic. Example Packet Summary: Modder Machine To RockstaTake Two Interactive, New York, New York Upon Use of a Mod
Frame 204: 151 bytes on wire (1208 bits), 151 bytes captured (1208 bits) on interface 0 Interface id: 0 Censored TO Avoid MAC Ban Encapsulation type: Ethernet (1) Arrival Time: Jan 19, 2017 18:23:39.836486000 Pacific Standard Time [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1484879019.836486000 seconds [Time delta from previous captured frame: 0.002543000 seconds] [Time delta from previous displayed frame: 0.002543000 seconds] [Time since reference or first frame: 1.598633000 seconds] Frame Number: 204 Frame Length: 151 bytes (1208 bits) Capture Length: 151 bytes (1208 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:ip:udp:dtls] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Censored TO Avoid MAC Ban Internet Protocol Version 4, Src: 10.0.1.113 (10.0.1.113), Dst: prod.ros.rockstargames.com (22.214.171.124) User Datagram Protocol, Src Port: 58016 (58016), Dst Port: 61457 (61457) Datagram Transport Layer Security
Modder Machine To Victim Machine Upon Giving Him All Weapons from Mod Menu. Victim is from Miami, Florida
Frame 210: 101 bytes on wire (808 bits), 101 bytes captured (808 bits) on interface 0 Interface id: 0 Censored TO Avoid MAC Ban Encapsulation type: Ethernet (1) Arrival Time: Jan 19, 2017 18:23:39.887777000 Pacific Standard Time [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1484879019.887777000 seconds [Time delta from previous captured frame: 0.000169000 seconds] [Time delta from previous displayed frame: 0.000169000 seconds] [Time since reference or first frame: 1.649924000 seconds] Frame Number: 210 Frame Length: 101 bytes (808 bits) Capture Length: 101 bytes (808 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:ip:udp:gvsp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Censored TO Avoid MAC Ban Internet Protocol Version 4, Src: 10.0.1.113 (10.0.1.113), Dst: c-75-74-37-8.hsd1.fl.comcast.net (126.96.36.199) User Datagram Protocol, Src Port: vision_server (6672), Dst Port: vision_server (6672) Source Port: vision_server (6672) Destination Port: vision_server (6672)
These are the settings you must have on Windows Firewall, on Windows 10. Make one rule for INBOUND and one for OUTBOUND. You can do this while playing the game. Set them to enabled and change session. You should be on a new lobby with MUCH LESS PLAYERS. Keep Lobby-Surfing until you end up alone or the other people leave. My Wireshark capture tells me that the only other player in the game is connected to me via UDP 35464. He eventually left. Leaving me in a session by myself. It won't guarantee you a solo lobby anymore, but it makes it much rarer for packed lobbies with modders and jet griefers. If you are feeling lonely, then disable those firewall rules and switch session again. I still have a UDP connection via 6672 despite the rules. My wireshark picks up no traffic at all though. Hmm interesting. If you block your traffic it now generates DTLSv1.0 traffic (like modder traffic) to Rockstar at 188.8.131.52. There is also a lot more TCP traffic through Port 80 (but its still obfuscated). And it is going through my blocked UDP ports in the new firewall rules. It basically SSH tunneled through UDP directly to R*. So it's just me and their gameserver. No one else. Well the admins know I am not cheating. They prolly think I have a lousy internet connection or a jerk of a admin (they think) who doesn't want me to use UDP gaming ports. I am not worried at all. If you wanna sell all of your shit without being picked on. Then do this,
enable the firewall rules both inbound and outbound, sell your shit, and then disable them and switch sessions again so you won't be lonely anymore.
Here are the packet captures that I am WILLING to share. Basically it shows two things. R* Will open a SSH tunnel secret in at least TWO conditions (1) If you are modding. There will be a SSH Tunnel created using the DTLSv1.0 protocol on your UDP ports. Telling R* what you are doing if your game traffic looks suspicious (2) If you are using the firewall glitch, the game will get around your Windows Software Firewall and start connecting to R* with the SSH tunnel.
For #2 if you check on my packet capture links, even though I told Windows Firewall to block that UDP port, packets were sent through anyways as DTLS traffic. I have yet to be banned for this. This ensures that R* can still save my data. And you get to have less populated and/or totally alone sessions so you can play the damn game! And here is a example of normal traffic. Me and three of my friends in a 4-player Survival Game
Edit: Uploaded a 38 minute video, soloing biker deliveries without interference from other players. Works as long as I end up being the only player in the session, no new players can join because I blocked my ports
Other Possible Ramifications (Very Bad If It's True!) Not to freak everyone out. But it MAY be possible, for someone with actual hacking talent (not me), to drop a Staged Meterpreter Shell into your computer, assuming that he or she knows your IP address through the discovery on Wireshark. They can then... (1) Have the payload on execution rewrite a critical system file in your computer (2) Download the remaining stages of the payload (3) Slowly compromise other system processes on your computer (4) Gain root-access (Administrator in Windows) (5) Start executing commands as Root/Admin (6) Do creepy shit like use your webcam to take a picture of your face. Or steal your saved payment information in your browser cookies for Amazon, etc. I typically would picture our typical home networks like this in a typical game lobby on GTA Online Me
Laptop running GTA V My Router and Firewalls My Public IP (UDP Port 6672) My ISP
ISP routing path Your ISP Your Public IP (UDP Port 6672 and/or other) Your Home Router and Firewalls Your Computer
The problem with the UDP protocol, is that it has very little verification and checksumming. It just keeps spamming packets, making it viable for low latency applications (gaming). If I can make a virus or reverse shell look like typical game data, then it SHOULD get through your firewall, and automatically get forwarded by your router to your computer. As long as I am connected to you, all the validation is authentic. As long as I am connected to you, either in a game mode, or through the public lobby! If those conditions are met. Then it's going to look like regular traffic to your network. I have yet to even try this. I did managed to reencode a standard reverse shell payload (msfvenom) and infected myself with it (successfully SSH tunneling through my own router from the WWW against my Linux installation). However, my Windows variant failed to execute due to Windows User Account Controls. Windows Defender was futilely, furiously searching for this "virus", and eating up all my hard drive usage (100% while playing GTA) until I finally removed it after running a scan with HitmanPro (a heuristics second-opinion scanner that hunts for files that exhibit virus/malware like activity). PSA: DO NOT USE WIRESHARK TO MONITOR GTA V TRAFFIC, R* EULA HAS RECENTLY BEEN CHANGED, DEPENDING ON SEVERITY IT MAY BE A INSTANT PERMANENT BAN At 4:30 AM PST, January 22nd, my account received a permanent ban as I was with my friends on their yacht looking through the scope of a sniper rifle in the middle of a Piracy Prevention Match. As it turns. Sniffing network traffic via Wireshark may or may not be a ground for a ban. Regardless of whether or not I am doing it right now. I even double checked the vague Rockstar Games EULA to make sure. https://www.rockstargames.com/eula
You agree not to: reverse engineer, decompile, disassemble, display, perform, prepare derivative works based on, or otherwise modify the Software, in whole or in part;
Well I attempted to! And I violated a good half of those.
cheat or utilize any unauthorized robot, spider, or other program in connection with any online features of the Software;
"Spider" (I am guessing they are referring to internet crawlers), but "other program"? Yeah Wireshark fits the bill.
TECHNICAL PROTECTIONS: The Software may include measures to control access to the Software, control access to certain features or content, prevent unauthorized copies, or otherwise attempt to prevent anyone from exceeding the limited rights and licenses granted under this Agreement. Such measures may include incorporating license management, product activation, and other security technology in the Software and monitoring usage, including, but not limited to, time, date, access, or other controls, counters, serial numbers, and/or other security devices designed to prevent the unauthorized access, use, and copying of the Software, or any portions or components thereof, including any violations of this Agreement. Licensor reserves the right to monitor use of the Software at any time. You may not interfere with such access control measures or attempt to disable or circumvent such security features, and if you do, the Software may not function properly. If the Software permits access to Special Features, only one copy of the Software may access those Special Features at one time. Additional terms and registration may be required to access online services and to download Software updates and patches. Only Software subject to a valid license can be used to access online services, including downloading updates and patches. Except as otherwise prohibited by applicable law, Licensor may limit, suspend, or terminate the license granted hereunder and access to the Software, including, but not limited to, any related services and products, at any time without notice for any reason whatsoever.
The Secret UDP SSH Tunnel (DTLSv1.0), got it. R* Anticheat. Check. Don't fuck with it? Naw mang, sorry, totally lost it. Well... if I straight up spilled the beans on how your anticheat works, including what it could possibly do and can't do, and how it might work, I'd guess you'd be pretty mad at me too. Especially since posting on Reddit is the equivalent of me following you around IRL with a megaphone, screaming in public in earshot "Don't trust him! He is reading your shit! He's looking through your gameplay traffic right now. And he knows everything!!!!"
Remember what I said about DDoSing people that are discovered on Wireshark? If you do this, and the victim knows the right people to call, I wouldn't be surprised if G-Men in suits knock on your door. At first, I thought, that was it. Then I decided to go Google "GTA V Banwave" and set the time to one week ago. What I saw was a real trip. A huge spike in fake bans and urgent warnings, "PSA's" all over YouTube It's something related to the latest iteration of Mod Menus that have been popping up. I have not seen so much panic run through the forums of UnknownCheats and MPGH in my life. New versions, updates, and customized variants of Mod Menus have been popping up on a daily basis. And with a detection period from launch, of at most, a week long. That is, the day that the new mod menu gets uploaded, to the point that users start to report they are getting banned for it, can be up from a week from now. R* anticheat went into overdrive. Developers have been scaling back on implementing the money drop feature for fear of triggering instant bans for their users (hence the lack of money drops recently). Then I noticed something... The prevailing issue of "Persistent Mods" and possible "Memory Corruption" implicating innocent players I am talking about mod menus that permanently break a lobby's features like free roam missions, like CEO or Bikers, but this time, it can carry over betweens lobby sessions. I saw my first variant earlier this week and shrugged it off. Then I saw my second one today. Some modder was caging me and my friends and trying to flatten us with Bugattis. Normally I would just join another session and any wacky attachment would fall off. But now the damage, errors, and bugs caused by mod menus can "carry-over" with me. I realized that I couldn't change my Outfits via the "Style Menu" for the second session in a row, I could not eat snacks to regenerate health, nor could I equip body armor. In some cases, I couldn't register as a CEO and start my missions, even though I already SWITCHED to a new lobby. After fully restarting the game from Steam, the "mod persistence" ceased. I had full control of my character again. Because we are talking about starting over again with fresh untainted memory. First instance of discussion of innocent bans recentlyhttps://www.youtube.com/watch?v=rKYnCDolKSc This video claims that you should be avoiding public lobbies on the PC like the plague or apocalypse. IDK if you have to be THAT extreme. Just don't interact too much with modders. Or try glitching yourself into a solo public lobby via the firewall glitch. This is really sad though. This guy is a victim of a modder, and he gets a ban for it, probably from memory corruption caused by the modders that Rockstar's Anticheat picked uphttps://www.youtube.com/watch?v=_1IEs-Bf7Is I am certain that if you react quickly enough, you will NOT get flagged by the modder's actions. You just need to do a full restart of the game. Not your PC. Just the game on Steam. So don't enjoy a modder's company for too long, no matter how pleasant they may appear. Holy fuck dude. The game still costs $60 on Steam. After all these years. I'll just wait until my decoy account gets unbanned. I'll see you guys in 30 days. Fortunately, it is NOT a MAC Ban. I logged into my decoy account. Decoy account still has a one month suspension.
We’re happy to announce the release of Dogecoin version 1.5.1! This release incorporates a range of updates from community contributors, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate. Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe). Downloads:Windows InstallerWindows ArchiveMac OS X App Release highlights: - Switched to Boost 1.55 to fix network connectivity issues on Windows - Removal of reliance on IRC for discovering nodes - Support for URL protocol, eg. dogecoin:addr?amount=xxx&(see Bitcoin’s implementation) - Ability to automatically look up transactions on Dogechain from your client - Working Windows setup script and installer - Opt-in debug logging via -debuglog (to save disk space and stop constant writing) - Fixed Mac Splashscreen’s greedy desktop behavior - Reimplemented testnet, fixing RPC crash due to no genesis block being present - Allow user to load any wallet from data directory specified using -wallet=mywallet.dat - Updated to LevelDB 1.15 to address blockchain database corruption issues - Allow user to send change only to specified address(es) using -change= (one -change parameter per address) - Fixed RPC difficulty look up Troubleshooting If anyone experiences issues, delete all 1.4 data (apart from your backed up wallet.dat file) and do a fresh 1.5.1 install. Enjoy!
Hi, so here are a few things going on; also at the end some notes about using Joinmarket in today's environment:
Just pushed a feature to joinmarket-clientservemaster : you can now send coins to (not from) bech32 segwit addresses.
I was prompted on this by user Onecoinbob, although there's a very valid discussion about whether wallets should have gone straight to bech32 addresses (instead of p2sh wrap), the reality is that some have (in particular, Electrum) and so I think it's pretty important that people can send coins there. Whether doing direct send (no coinjoin, -N 0), coinjoin, or in joinmarket-Qt you can now use bech32 addresses like "bc1qyzd2qj8tdrvyacvtknj2xav900qkr3a2xjrmg7" as valid destinations. Only master branch for now, will make a new release soon, it's a bit overdue.
Installation: a lot of work by user arubi (thanks!) on installation, you can install with ./install.sh on Linux and probably on MacOS too.
Thanks to a couple of other users (including trotski2000), we have instructions how you can install manually in docs/INSTALL.md should there be some problem with the one-step installation. Feel free to ask on github issue or IRC or here (maybe ping me) for more help on this, but note I personally don't run a MacOS machine so I will redirect you.
A reminder: there is a Qt gui for joinmarket joinmarket-qt.py in the scripts/ directory that works Taker side, including direct sending of funds.
I recently found that people don't know this exists, indeed I first created it nearly 2 years ago!.
Backend wallet refactoring by user undeath
See the PR ; this is backend stuff so little direct relevance to users; devs may be interested, it looks like a really good effort to rationalize and improve this section of the code.
Python 3 support/migration
I have started doing work on this, but it's not a small job, Joinmarket being very byte-manipulation heavy means there's quite a lot of changes to get it working on both 2 and 3. However it's really a good idea, a lot of useful libraries are migrating to/only supported on Py3. No real date or goal here.
High fees and Joinmarket
I think most users already figured this out, but as a Taker the hit on fees from using Joinmarket is far too high in almost all cases (nothing to do with coinjoin fees; just Bitcoin network fees, which the Taker pays basically all of). It is possible in the model to share these fees, by certain sets of configuration, but the system hasn't really been set up like that. Alternatively, the Taker may lowball a fee to a crazy extent and lock up the Maker coins for a long time. I'd advise against using Joinmarket in periods of very high fees like we had last week; I'd even advise against Makers running their bots to prevent newbies suffering an unexpectedly high hit on fees. But of course everyone can make their own decision. (EDIT: Forgot to add the really important thing, which is that whatever kind of transaction you're doing, including direct_send, seriously consider using the feature that setting tx_fees to any value above 144 results in using that figure as a custom fee in satoshis per kB, with a small randomization. So setting tx_fees = 300000 in the config means using a fee of 300 sat/b. Has been mentioned before but bears repeating!) For myself, I have been actively looking at a number of alternative models (see some of my blog posts at https://joinmarket.me/blog/blog for example, my CoinswapCS repo, also "Snicker"), and of course other people are looking at things too e.g. the ZeroLink project of nopara. Joinmarket as a model may also continue to be viable if the fee regime changes, and/or when new tech comes online that changes the economics (Schnorr in particular; CT itself would radically change the economics/viability of coinjoin but that is another discussion).
I installed the Lightning Network on my Mac following the tutorial on this page: http://coin5s.com/content/setting-bitcoin-lightning-network-node-macos-peanuts-eclair It was not quite as easy as the tutorial said, mainly because I installed the testnet version of Bitcoin Core on an external hard disk in order not to conflict with the mainnet version I already have. All the other software, like Eclair and Homebrew, I installed on the default directories. It appears to work, although I have a few questions. First, it seems I have to stay connected to Bitcoin Core and to Eclair all the time in order for my channels to stay open. Is that true? If that's the case, once I install it on the mainnet I will install it on an older Mac so I won't conflict with my main Mac which I use for real work and which I turn off at night. I can see myself opening channels with Coinbase, Local Bitcoins, and Coinucopia, in order to lower my fees while buying Bitcoins. Other than that, I don't want to make small purchases with Bitcoin because I primarily buy it to save for my retirement. And most importantly, the main reason I want to use the Lighting Network in the future would be to earn some money, even if it's a few satoshis, while processing transactions. How will that work? Are there any tutorials for that? Based upon what I've seen, your node only connects to other specific nodes. Will you get paid as other people's money goes through your node or what? I don't see how can this happen on my current installation. It has been a good learning experience to install the Lightning Network on my Mac, although I don't see how can it be useful unless you make regular transactions with specific vendors. I would appreciate it if somebody who knows more about the Lightning Network than me answers my questions.