Recent Posts

Pages: [1] 2 3 ... 10
1
Tutorials / How to setup Groestlcoin Core Config Generator
« Last post by jackielove4u on June 03, 2019, 06:28:41 pm »
The following were tested in Ubuntu 14.04 and Ubuntu 16.04, some dependencies can be different in other distros.
    • curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash -
    • sudo apt-get install -y nodejs
    • git clone https://github.com/Groestlcoin/groestlcoin-core-config-generator
    • cd groestlcoin-core-config-generator
    • npm install
    • screen
    • npm start
    • Crtl+A, ctrl+D
    • cd ..
    • sudo add-apt-repository ppa:certbot/certbot
    • sudo apt-get update
    • sudo apt-get install certbot
    • certbot certonly --standalone -d config.groestlcoin.org
    • crontab -e
    • Add end of file:
      15 3 * * * /usr/bin/certbot renew --quiet
    • Crtl+o enter, ctrl X
    • apt-get install nginx
    • nano /etc/nginx/sites-available/default
    • delete all and paste:
      server {
          listen 80;
          listen 443 ssl;
          ssl_certificate /etc/letsencrypt/live/config.groestlcoin.org/fullchain.pem;
          ssl_certificate_key /etc/letsencrypt/live/config.groestlcoin.org/privkey.pem;
         
          server_name config.groestlcoin.org;

          # force https-redirects
          if ($scheme = http) {
              return 301 https://nanotip.groestlcoin.org$request_uri;
          }

          location / {
              proxy_pass http://localhost:3000;
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              proxy_set_header Host $http_host;
              proxy_set_header X-NginX-Proxy true;

              # Enables WS support
              proxy_http_version 1.1;
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection "upgrade";
              proxy_redirect off;
          }
      }
    • service nginx restart
2
Tutorials / Krypto Kindergarten
« Last post by indiamikezulu on May 27, 2019, 03:20:03 am »
Hello! Welcome to Krypto Kindergarten.

Krypto Kindie is open. We have a GRS dev, Jackie, to help us.


16/6 Operational security -- 'OPSEC' -- is unforgiving. Newcomers rush into cryptos, stash bits of information here and there, and then later can't find them. We will discuss basic OPSEC here.

3
Tutorials / How to setup Groestlcoin Lightning JukeBox
« Last post by jackielove4u on March 26, 2019, 12:31:34 pm »
The following were tested in Ubuntu 14.04 and Ubuntu 16.04, some dependencies can be different in other distros.
    • aptitude update -y && aptitude upgrade -y && apt-get update -y && apt-get upgrade -y && apt-get dist-upgrade -y
    • dd if=/dev/zero of=/swapfile bs=1M count=4096
    • mkswap /swapfile
    • swapon /swapfile
    • echo "/swapfile swap swap defaults 0 0" >> /etc/fstab
    • sudo apt-get install build-essential libssl-dev libboost-all-dev libdb5.3 libdb5.3-dev libdb5.3++-dev libtool automake libevent-dev bsdmainutils -y
    • sudo apt-get install git ntp make g++ gcc autoconf cpp ngrep iftop sysstat autotools-dev pkg-config libminiupnpc-dev libzmq3-dev -y
    • sudo apt-get install libgmp-dev libsqlite3-dev python python3 net-tools zlib1g-dev
    • git clone https://github.com/groestlcoin/groestlcoin
    • cd groestlcoin
    • ./autogen.sh
    • ./configure
    • make
    • strip src/groestlcoind src/groestlcoin-cli src/groestlcoin-tx
    • sudo mv src/groestlcoind src/groestlcoin-cli src/groestlcoin-tx /usr/bin
    • mkdir ~/.groestlcoin
    • nano ~/.groestlcoin/groestlcoin.conf
    • write:
      listen=1
      server=1
      maxconnections=865
      daemon=1
      txindex=1
      rpcuser=yourusernamehere
      rpcpassword=yourpasswordhere
      whitelist=127.0.0.1
    • Crtl+o enter, ctrl X
    • groestlcoind
    • Let it sync (can take up to 2 hours), verify with groestlcoin-cli -getinfo
    • git clone https://github.com/Groestlcoin/lightning.git
    • cd lightning
    • ./configure
    • make
    • strip lightningd/lightningd cli/lightning-cli
    • mkdir ~/.lightning
    • nano ~/.lightning/config
    • write:
      alias=Groestlcoin
      network=groestlcoin
      bitcoin-rpcuser=yourusernamehere
      bitcoin-rpcpassword=yourpasswordhere
      bitcoin-rpcconnect=127.0.0.1
      bitcoin-rpcport=1441
      bind-addr=
      announce-addr=YOURIPADDRESS:9735
    • Crtl+o enter, ctrl X
    • screen
    • ./lightningd/lightningd
    • Crtl+A, ctrl+D
    • check if all is ok: ./cli/lightning-cli getinfo
    • cd ..
    • git clone https://github.com/Groestlcoin/groestlcoin-lightning-charge
    • cd groestlcoin-lightning-charge
    • npm install
    • screen
    • npm start -- --api-token mySecretToken --host IpAddressOfServer --charge-url IpAddressOfServer:9112
    • Crtl+A, ctrl+D
    • cd ..
    • git clone https://github.com/Groestlcoin/lightning-jukebox
    • cd lightning-jukebox
    • npm install
    • screen
    • npm start -- --charge-token mySecretToken --price '0.0001 GRS' --port 80 --host 199.247.31.182 --charge-url http://199.247.31.182:9112
    • Crtl+A, ctrl+D
    • cd ..
    • sudo add-apt-repository ppa:certbot/certbot
    • sudo apt-get update
    • sudo apt-get install certbot
    • certbot certonly --standalone -d nanotip.groestlcoin.org
    • crontab -e
    • Add end of file:
      15 3 * * * /usr/bin/certbot renew --quiet
    • Crtl+o enter, ctrl X
    • apt-get install nginx
    • nano /etc/nginx/sites-available/default
    • delete all and paste:
      server {
          listen 80;
          listen 443 ssl;
          ssl_certificate /etc/letsencrypt/live/nanotip.groestlcoin.org/fullchain.pem;
          ssl_certificate_key /etc/letsencrypt/live/nanotip.groestlcoin.org/privkey.pem;

          server_name nanotip.groestlcoin.org;

          # force https-redirects
          if ($scheme = http) {
              return 301 https://nanotip.groestlcoin.org$request_uri;
          }

          location / {
              proxy_pass https://localhost:9115;
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              proxy_set_header Host $http_host;
              proxy_set_header X-NginX-Proxy true;

              # Enables WS support
              proxy_http_version 1.1;
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection "upgrade";
              proxy_redirect off;
          }
      }
    • service nginx restart
4
Tutorials / How to setup Groestlcoin Lightning Tip Box
« Last post by jackielove4u on March 26, 2019, 09:36:50 am »
The following were tested in Ubuntu 14.04 and Ubuntu 16.04, some dependencies can be different in other distros.
    • aptitude update -y && aptitude upgrade -y && apt-get update -y && apt-get upgrade -y && apt-get dist-upgrade -y
    • dd if=/dev/zero of=/swapfile bs=1M count=4096
    • mkswap /swapfile
    • swapon /swapfile
    • echo "/swapfile swap swap defaults 0 0" >> /etc/fstab
    • sudo apt-get install build-essential libssl-dev libboost-all-dev libdb5.3 libdb5.3-dev libdb5.3++-dev libtool automake libevent-dev bsdmainutils -y
    • sudo apt-get install git ntp make g++ gcc autoconf cpp ngrep iftop sysstat autotools-dev pkg-config libminiupnpc-dev libzmq3-dev -y
    • sudo apt-get install libgmp-dev libsqlite3-dev python python3 net-tools zlib1g-dev
    • git clone https://github.com/groestlcoin/groestlcoin
    • cd groestlcoin
    • ./autogen.sh
    • ./configure
    • make
    • strip src/groestlcoind src/groestlcoin-cli src/groestlcoin-tx
    • sudo mv src/groestlcoind src/groestlcoin-cli src/groestlcoin-tx /usr/bin
    • mkdir ~/.groestlcoin
    • nano ~/.groestlcoin/groestlcoin.conf
    • write:
      listen=1
      server=1
      maxconnections=865
      daemon=1
      txindex=1
      rpcuser=yourusernamehere
      rpcpassword=yourpasswordhere
      whitelist=127.0.0.1
    • Crtl+o enter, ctrl X
    • groestlcoind
    • Let it sync (can take up to 2 hours), verify with groestlcoin-cli -getinfo
    • git clone https://github.com/Groestlcoin/lightning.git
    • cd lightning
    • ./configure
    • make
    • strip lightningd/lightningd cli/lightning-cli
    • mkdir ~/.lightning
    • nano ~/.lightning/config
    • write:
      alias=Groestlcoin
      network=groestlcoin
      bitcoin-rpcuser=yourusernamehere
      bitcoin-rpcpassword=yourpasswordhere
      bitcoin-rpcconnect=127.0.0.1
      bitcoin-rpcport=1441
      bind-addr=
      announce-addr=YOURIPADDRESS:9735
    • Crtl+o enter, ctrl X
    • screen
    • ./lightningd/lightningd
    • Crtl+A, ctrl+D
    • check if all is ok: ./cli/lightning-cli getinfo
    • cd ..
    • git clone https://github.com/Groestlcoin/groestlcoin-lightning-charge
    • cd groestlcoin-lightning-charge
    • npm install
    • screen
    • npm start -- --api-token mySecretToken --host IpAddressOfServer --charge-url IpAddressOfServer:9112
    • Crtl+A, ctrl+D
    • cd ..
    • git clone https://github.com/Groestlcoin/nanotip
    • cd nanotip
    • npm install
    • screen
    • npm start -- --charge-token mySecretToken --host IpAddresssOfServer --charge-url http://IpAddressOfServer:9112 --port 80
    • Crtl+A, ctrl+D
    • cd ..
    • sudo add-apt-repository ppa:certbot/certbot
    • sudo apt-get update
    • sudo apt-get install certbot
    • certbot certonly --standalone -d nanotip.groestlcoin.org
    • crontab -e
    • Add end of file:
      15 3 * * * /usr/bin/certbot renew --quiet
    • Crtl+o enter, ctrl X
    • apt-get install nginx
    • nano /etc/nginx/sites-available/default
    • delete all and paste:
      server {
          listen 80;
          listen 443 ssl;
          ssl_certificate /etc/letsencrypt/live/nanotip.groestlcoin.org/fullchain.pem;
          ssl_certificate_key /etc/letsencrypt/live/nanotip.groestlcoin.org/privkey.pem;

          server_name nanotip.groestlcoin.org;

          # force https-redirects
          if ($scheme = http) {
              return 301 https://nanotip.groestlcoin.org$request_uri;
          }

          location / {
              proxy_pass https://localhost:9115;
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              proxy_set_header Host $http_host;
              proxy_set_header X-NginX-Proxy true;

              # Enables WS support
              proxy_http_version 1.1;
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection "upgrade";
              proxy_redirect off;
          }
      }
    • service nginx restart
5
Important Announcements / Groestlcoin Core v2.17.2 Released
« Last post by gruve_p on March 22, 2019, 10:27:08 pm »

A new major Groestlcoin Core version 2.17.2 is now available for download bringing both new features and bug fixes, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.


v2.17.2 is now the official release version of Groestlcoin Core. On top of the new features, various bugfixes, updated translations and performance improvements. It is recommended to upgrade to this version as soon as possible.


What's new in version v2.17.2?
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.17.2 but with Groestlcoin specific patches. On a general level, most of what is new is BIP174 PSBT support. BIP 174 PSBT is an interchange format for Groestlcoin transactions that are not fully signed yet, together with relevant metadata to help entities work towards signing it. It is intended to simplify workflows where multiple parties need to cooperate to produce a transaction. Examples include hardware wallets, multisig setups, and CoinJoin transactions.

Changelog:
• `-includeconf=<file>` can be used to include additional configuration files. Only works inside the `groestlcoin.conf` file, not inside included files or from command-line. Multiple files may be included. Can be disabled from command-line via `-noincludeconf`. Note that multi-argument commands like `-includeconf` will override preceding `-noincludeconf` as groestlcoin.conf will still include `relative.conf`.
•  Block storage can be limited under Preferences, in the Main tab. Undoing this setting requires downloading the full blockchain again. This mode is incompatible with -txindex and -rescan.
•  The `-wallet=<path>` option now accepts full paths instead of requiring wallets to be located in the -walletdir directory.
•  If `-wallet=<path>` is specified with a path that does not exist, it will now create a wallet directory at the specified location (containing a wallet.dat data file, a db.log file, and database/log.?????????? files) instead of just creating a data file at the path and storing log files in the parent directory. This should make backing up wallets more straightforward than before because the specified wallet path can just be directly archived without having to look in the parent directory for transaction log files. For backwards compatibility, wallet paths that are names of existing data files in the `-walletdir` directory will continue to be accepted and interpreted the same as before.
•  Previously, wallets could only be loaded or created at startup, by specifying `-wallet` parameters on the command line or in the groestlcoin.conf file. It is now possible to load, create and unload wallets dynamically at runtime:
   - Existing wallets can be loaded by calling the `loadwallet` RPC. The wallet can be specified as file/directory basename (which must be located in the    `walletdir` directory), or as an absolute path to a file/directory.
   - New wallets can be created (and loaded) by calling the `createwallet` RPC. The provided name must not match a wallet file in the `walletdir` directory or the    name of a wallet that is currently loaded.
   - Loaded wallets can be unloaded by calling the `unloadwallet` RPC.
This feature is currently only available through the RPC interface.
• When an address is paid multiple times the coins from those separate payments can be spent separately which hurts privacy due to linking otherwise separate addresses. A new `-avoidpartialspends` flag has been added (default=false). If enabled, the wallet will always spend existing UTXO to the same address together even if it results in higher fees. If someone were to send coins to an address after it was used, those coins will still be included in future coin selections.
•  It is now possible for a single configuration file to set differentoptions for different networks. This is done by using sections or by
prefixing the option with the network, such as:

    main.uacomment=groestlcoin
    test.uacomment=groestlcoin-testnet
    regtest.uacomment=regtest
    [main]
    mempoolsize=300
    [test]
    mempoolsize=100
    [regtest]
    mempoolsize=20

If the following options are not in a section, they will only apply to mainnet: `addnode=`, `connect=`, `port=`, `bind=`, `rpcport=`, `rpcbind=` and `wallet=`.
The options to choose a network (`regtest=` and `testnet=`) must be specified outside of sections.
• A new 'label' API has been introduced for the wallet. This is intended as a replacement for the deprecated 'account' API. The 'account' can continue to be used in V2.17.2 by starting groestlcoind with the '-deprecatedrpc=accounts' argument, and will be fully removed in V2.18.1. The label RPC methods mirror the account functionality, with the following functional differences:
- Labels can be set on any address, not just receiving addresses. This functionality was previously only available through the GUI.
- Labels can be deleted by reassigning all addresses using the `setlabel` RPC method.
- There isn't support for sending transactions _from_ a label, or for determining which label a transaction was sent from.
- Labels do not have a balance.

Here are the changes to RPC methods:

| Deprecated Method       | New Method            | Notes       |
| :---------------------- | :-------------------- | :-----------|
| `getaccount`            | `getaddressinfo`      | `getaddressinfo` returns a json object with address information instead of just the name of the account as a string. |
| `getaccountaddress`     | n/a                   | There is no replacement for `getaccountaddress` since labels do not have an associated receive address. |
| `getaddressesbyaccount` | `getaddressesbylabel` | `getaddressesbylabel` returns a json object with the addresses as keys, instead of a list of strings. |
| `getreceivedbyaccount`  | `getreceivedbylabel`  | _no change in behavior_ |
| `listaccounts`          | `listlabels`          | `listlabels` does not return a balance or accept `minconf` and `watchonly` arguments. |
| `listreceivedbyaccount` | `listreceivedbylabel` | Both methods return new `label` fields, along with `account` fields for backward compatibility. |
| `move`                  | n/a                   | _no replacement_ |
| `sendfrom`              | n/a                   | _no replacement_ |
| `setaccount`            | `setlabel`            | Both methods now: <ul><li>allow assigning labels to any address, instead of raising an error if the address is not receiving address.<li>delete the previous label associated with an address when the final address using that label is reassigned to a different label, instead of making an implicit `getaccountaddress` call to ensure the previous label still has a receiving address. |

| Changed Method         | Notes   |
| :--------------------- | :------ |
| `addmultisigaddress`   | Renamed `account` named parameter to `label`. Still accepts `account` for backward compatibility if running with '-deprecatedrpc=accounts'. |
| `getnewaddress`        | Renamed `account` named parameter to `label`. Still accepts `account` for backward compatibility. if running with '-deprecatedrpc=accounts' |
| `listunspent`          | Returns new `label` fields. `account` field will be returned for backward compatibility if running with '-deprecatedrpc=accounts' |
| `sendmany`             | The `account` named parameter has been renamed to `dummy`. If provided, the `dummy` parameter must be set to the empty string, unless running with the `-deprecatedrpc=accounts` argument (in which case functionality is unchanged). |
| `listtransactions`     | Renamed `account` named parameter to `label`. Still accepts `account` for backward compatibility if running with '-deprecatedrpc=accounts'. |
| `getbalance`           | `account`, `minconf` and `include_watchonly` parameters are deprecated, and can only be used if running with '-deprecatedrpc=accounts' |

• [BIP 174 PSBT](https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki) is an interchange format for Groestlcoin transactions that are not fully signed
yet, together with relevant metadata to help entities work towards signing it. It is intended to simplify workflows where multiple parties need to cooperate to
produce a transaction. Examples include hardware wallets, multisig setups, and [CoinJoin](https://bitcointalk.org/?topic=279249) transactions.
Overall, the construction of a fully signed Groestlcoin transaction goes through the following steps:
- A Creator proposes a particular transaction to be created. He constructs a PSBT that contains certain inputs and outputs, but no additional metadata.
- For each input, an Updater adds information about the UTXOs being spent by the transaction to the PSBT.
- A potential other Updater adds information about the scripts and public keys involved in each of the inputs (and possibly outputs) of the PSBT.
- Signers inspect the transaction and its metadata to decide whether they agree with the transaction. They can use amount information from the UTXOs to assess the values and fees involved. If they agree, they produce a partial signature for the inputs for which they have relevant key(s).
- A Finalizer is run for each input to convert the partial signatures and possibly script information into a final `scriptSig` and/or `scriptWitness`.
- An Extractor produces a valid Groestlcoin transaction (in network format) from a PSBT for which all inputs are finalized.
Generally, each of the above (excluding Creator and Extractor) will simply add more and more data to a particular PSBT. In a naive workflow, they all have to operate sequentially, passing the PSBT from one to the next, until the Extractor can convert it to a real transaction. In order to permit parallel operation, **Combiners** can be employed which merge metadata from different PSBTs for the same unsigned transaction. The names above in bold are the names of the roles defined in BIP174. They're useful in understanding the underlying steps, but in practice, software and hardware implementations will typically implement multiple roles simultaneously.
• `converttopsbt` (Creator) is a utility RPC that converts an unsigned raw transaction to PSBT format. It ignores existing signatures.
• `createpsbt` (Creator) is a utility RPC that takes a list of inputs and outputs and converts them to a PSBT with no additional information. It is equivalent to calling `createrawtransaction` followed by `converttopsbt`.
• `walletcreatefundedpsbt` (Creator, Updater) is a wallet RPC that creates a PSBT with the specified inputs and outputs, adds additional inputs and change to it to balance it out, and adds relevant metadata. In particular, for inputs that the wallet knows about (counting towards its normal or watch-only balance), UTXO information will be added. For outputs and inputs with UTXO information present, key and script information will be added which the wallet knows about. It is equivalent to running `createrawtransaction`, followed by `fundrawtransaction`, and `converttopsbt`.
• `walletprocesspsbt` (Updater, Signer, Finalizer) is a wallet RPC that takes as input a PSBT, adds UTXO, key, and script data to inputs and outputs that miss it, and optionally signs inputs. Where possible it also finalizes the partial signatures.
• `finalizepsbt` (Finalizer, Extractor) is a utility RPC that finalizes any partial signatures, and if all inputs are finalized, converts the result to a fully signed transaction which can be broadcast with `sendrawtransaction`.
• `combinepsbt` (Combiner) is a utility RPC that implements a Combiner. It can be used at any point in the workflow to merge information added to different versions of the same PSBT. In particular it is useful to combine the output of multiple Updaters or Signers.
• `decodepsbt` is a diagnostic utility RPC which will show all information in a PSBT in human-readable form, as well as compute its eventual fee if known.
• Since Groestlcoin Core 2.13.3, creating new BIP 32 Hierarchical Deterministic wallets has been supported by Groestlcoin Core but old non-HD wallets could not be upgraded to HD. Now non-HD wallets can be upgraded to HD using the `-upgradewallet` command line option. This upgrade will result in the all keys in the keypool being marked as used and a new keypool generated. **A new backup must be made when this upgrade is performed.**
Additionally, `-upgradewallet` can be used to upgraded from a non-split HD chain (all keys generated with `m/0'/0'/i'`) to a split HD chain (receiving keys generated with `'m/0'/0'/i'` and change keys generated with `m'/0'/1'/i'`). When this upgrade occurs, all keys already in the keypool will remain in the keypool to be used until all keys from before the upgrade are exhausted. This is to avoid issues with backups and downgrades when some keys may come from the change key keypool. Users can begin using the new split HD chain keypools by using the `newkeypool` RPC to mark all keys in the keypool as used and begin using a new keypool generated from the split HD chain.
• A new RPC, `sethdseed`, has been introduced which allows users to set a new HD seed or set their own HD seed. This allows for a new HD seed to be used. **A new backup must be made when a new HD seed is set.**
• The new RPC `scantxoutset` can be used to scan the UTXO set for entries that match certain output descriptors. Refer to the [output descriptors reference documentation](/doc/descriptors.md) for more details. This call is similar to `listunspent` but does not use a wallet, meaning that the wallet can be disabled at compile or run time. This call is experimental, as such, is subject to changes or removal in future releases.
• The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client.
• The `fundrawtransaction` RPC will reject the previously deprecated `reserveChangeKey` option.
• `sendmany` now shuffles outputs to improve privacy, so any previously expected behavior with regards to output ordering can no longer be relied upon.
• The new RPC `testmempoolaccept` can be used to test acceptance of a transaction to the mempool without adding it.
• JSON transaction decomposition now includes a `weight` field which provides the transaction's exact weight. This is included in REST /rest/tx/ and /rest/block/ endpoints when in json mode. This is also included in `getblock` (with verbosity=2), `listsinceblock`, `listtransactions`, and `getrawtransaction` RPC commands.
• New `fees` field introduced in `getrawmempool`, `getmempoolancestors`, `getmempooldescendants` and `getmempoolentry` when verbosity is set to `true` with sub-fields `ancestor`, `base`, `modified` and `descendant` denominated in GRS. This new field deprecates previous fee fields, such as `fee`, `modifiedfee`, `ancestorfee` and `descendantfee`.
• The new RPC `getzmqnotifications` returns information about active ZMQ notifications.
• When groestlcoin is not started with any `-wallet=<path>` options, the name of the default wallet returned by `getwalletinfo` and `listwallets` RPCs is now the empty string `""` instead of `"wallet.dat"`. If groestlcoin is started with any `-wallet=<path>` options, there is no change in behavior, and the name of any wallet is just its `<path>` string.
• Passing an empty string (`""`) as the `address_type` parameter to `getnewaddress`, `getrawchangeaddress`, `addmultisigaddress`, `fundrawtransaction` RPCs is now an error. Previously, this would fall back to using the default address type. It is still possible to pass null or leave the parameter unset to use the default address type.
• Bare multisig outputs to our keys are no longer automatically treated as incoming payments. As this feature was only available for multisig outputs for which you had all private keys in your wallet, there was generally no use for them compared to single-key schemes. Furthermore, no address format for such outputs is defined, and wallet software can't easily send to it. These outputs will no longer show up in `listtransactions`, `listunspent`, or contribute to your balance, unless they are explicitly watched (using `importaddress` or `importmulti` with hex script argument). `signrawtransaction` also still works for them.
•  The `getwalletinfo` RPC method now returns an `hdseedid` value, which is always the same as the incorrectly-named `hdmasterkeyid` value. `hdmasterkeyid` will be removed in V2.18.1.
•  The `getaddressinfo` RPC method now returns an `hdseedid` value, which is always the same as the incorrectly-named `hdmasterkeyid` value. `hdmasterkeyid` will be removed in V2.18.1.
•  Parts of the `validateaddress` RPC method have been deprecated and moved to `getaddressinfo`. Clients must transition to using `getaddressinfo` to access this information before upgrading to v2.18.1. The following deprecated fields have moved to `getaddressinfo` and will only be shown with `-deprecatedrpc=validateaddress`: `ismine`, `iswatchonly`, `script`, `hex`, `pubkeys`, `sigsrequired`, `pubkey`, `addresses`, `embedded`, `iscompressed`, `account`, `timestamp`, `hdkeypath`, `hdmasterkeyid`.
• `signrawtransaction` is deprecated and will be fully removed in v2.18.1. To use `signrawtransaction` in v2.17.2, restart groestlcoind with `-deprecatedrpc=signrawtransaction`. Projects should transition to using `signrawtransactionwithkey` and `signrawtransactionwithwallet` before upgrading to v2.18.1.
•  The `inactivehdmaster` property in the `dumpwallet` output has been corrected to `inactivehdseed`
• The log timestamp format is now ISO 8601 (e.g. "2018-02-28T12:34:56Z").
•  When running groestlcoind with `-debug` but without `-daemon`, logging to stdout is now the default behavior. Setting `-printtoconsole=1` no longer implicitly disables logging to debug.log. Instead, logging to file can be explicitly disabled by setting `-debuglogfile=0`.
• The transaction index is now built separately from the main node procedure, meaning the `-txindex` flag can be toggled without a full reindex. If groestlcoind is run with `-txindex` on a node that is already partially or fully synced without one, the transaction index will be built in the background and become available once caught up. When switching from running `-txindex` to running without the flag, the transaction index database will *not* be deleted automatically, meaning it could be turned back on at a later time without a full resync.
• The `-blockmaxsize` option for miners to limit their blocks' sizes was deprecated in V2.16.0, and has now been removed. Miners should use the `-blockmaxweight` option if they want to limit the weight of their blocks.
• Support for Python 2 has been discontinued for all test files and tools.

It is appreciated if feedback of the following is provided:
1. Can you receive coins on a bech32 address? (small amounts to avoid losing them)
2. Can you receive coins on a legacy address? (small amounts to avoid losing them)
3. Can you receive coins on a p2sh-segwit address? (small amounts to avoid losing them)
4. Can you send coins on a bech32 address?
5. Can you send coins on a legacy address?
6. Can you send coins on a p2sh-segwit address?
7. Can you view your transaction on a third party blockexplorer (restart the client after entering the url of the blockexplorer) ?
8. Can you use the wallet with TOR?
9. Are you able to backup your wallet (wallet.dat) file?
10. Are you able to encrypt your wallet (wallet.dat) file?
11. Are you able to use watch-only function?
12. How long does it take to fully synchronize?
13. Are you able to sign/verify messages?
14. Are you able to see you send/receive addresses?
15. Are you able to use the wallet in your local language?

The application may have unfound bugs and problems. Please report using the issue tracker at github:
https://github.com/groestlcoin/groestlcoin/issues

Important:
• There is no warranty and no party shall be made liable to you for damages. If you lose coins due to this app, no compensation will be given. Use this app solely at your own risk.
• Encrypt your wallet. This can be done by clicking the settings menu from inside the wallet. Make sure your password is secure and do not forget it.
• Make a copy your wallet.dat file as a backup and move it to a secure location:
Location Windows: Navigate to C:\Users\Username\AppData\Roaming\groestlcoin\wallet.dat (or open windows explorer and enter %appdata%\Groestlcoin\wallet.dat)
Location Mac: Finder -> Go {Hold Option] -> Library -> groestlcoin -> wallet.dat (~/Library/Application Support/groestlcoin/wallet.dat)

WARNING:
While this branch has been extensively tested to be compatible with the existing Groestlcoin v2.11.0, v2.13.3, v2.16.0 and v2.16.3 network there is the possibility that we missed something. ALWAYS BACKUP YOUR GROESTLCOIN WALLET BEFORE UPGRADING.


How to Upgrade?
If your node has a txindex, the txindex db will be migrated the first time you run 2.17.2, which may take up to a few hours. Your node will not be functional until this migration completes.
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 users: http://groestlcoin.org/forum/index.php?topic=441.0
Linux users: http://groestlcoin.org/forum/index.php?topic=97.0

Download the Windows Installer (64 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-win64.msi
Download the Windows Installer (32 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-win32.msi
Download the Windows binaries (64 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-x86_64-w64-mingw32.zip
Download the Windows binaries (32 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-i686-w64-mingw32.zip
Download the OSX Installer here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-osx.dmg
Download the OSX binaries here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-x86_64-apple-darwin11.tar.gz
Download the Linux binaries (64 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-x86_64-linux-gnu.tar.gz
Download the Linux binaries (32 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-i686-pc-linux-gnu.tar.gz
Download the ARM Linux binaries (64 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-aarch64-linux-gnu.tar.gz
Download the ARM Linux binaries (32 bit) here: https://github.com/Groestlcoin/groestlcoin/releases/download/v2.17.2/groestlcoin-2.17.2-arm-linux-gnueabihf.tar.gz

Source code:
https://github.com/Groestlcoin/groestlcoin
Build instructions for Linux can be found here: https://github.com/Groestlcoin/groestlcoin/blob/master/doc/build-unix.md
Build instructions for OSX can be found here: https://github.com/Groestlcoin/groestlcoin/blob/master/doc/build-osx.md
Build instructions for Windows can be found here: https://github.com/Groestlcoin/groestlcoin/blob/master/doc/build-windows.md
6


Groestlcoin Broadcast tool is a simple GUI to broadcast groestlcoin transactions to the network..


Groestlcoin Broadcast tool gives you the ability to broadcast transactions quicker to several services. By doing this, you will increase the chances of your transaction being included in blocks which leads to faster confirmation times..

Features
• Open source under MIT.
• Testnet support
• Groestlsight support
• Blockbook support
• Chainz.CryptoID support

It is appreciated if feedback of the following is provided:
1. Can you broadcast through Groestlsight?
2. Can you broadcast through Blockbook?
3. Can you broadcast through Chainz.cryptoid?
4. Can you broadcast testnet transactions?

This application is MIT licensed. There is no warranty and no party shall be made liable to you for damages. If you lose coins due to this app, no compensation will be given. Use this app solely at your own risk.

The application may have unfound bugs and problems. To leave feedback: 
1.  PM yokomoko on Discord
2.  Email: yokomoko@groestlcoin.org
3.  Reports of errors can also be posted in this topic.

You can download it using the links below.
Download the Windows Wallet (64 bit) here: https://github.com/Groestlcoin/Groestlcoin-Broadcaster/releases/download/1.0.0.1/Groestlcoin.Broadcaster.x64.exe
Download the Windows Wallet (32 bit) here: https://github.com/Groestlcoin/Groestlcoin-Broadcaster/releases/download/1.0.0.1/Groestlcoin.Broadcaster.x86.exe

Source code:
https://github.com/Groestlcoin/Groestlcoin-Broadcaster/- The Groestlcoin Broadcast tool source code
7


Electrum-grs is a lightweight "thin client" groestlcoin wallet Android based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


If you are an ordinary user of Groestlcoin and simply want the convenience of a web wallet with the security of a real application and support for multi-signature, then Elecrum-GRS is the right choice for you.

Changelog Electrum-GRS 3.3.4:
• The network layer has been rewritten using asyncio and aiorpcx. In addition to easier maintenance, this makes the client more robust against misbehaving servers.
• New wallet creation defaults to native segwit (bech32).
• RBF batching (opt-in): If the wallet has an unconfirmed RBF transaction, new payments will be added to that transaction, instead of creating new transactions.
• Randomise locktime of transactions
• Transactions now set nVersion to 2, to mimic Groestlcoin Core
• Android APK:
   - build using Google NDK instead of Crystax NDK
   - target API 28
   - do not use external storage (previously for block headers)
• Android: Minor GUI improvements

Changelog Electrum-GRS 3.2.3:
• BIP39 seeds: if a seed extension (aka passphrase) contained multiple consecutive whitespaces or leading/trailing whitespaces then the derived addresses were not following spec. This has been fixed, and affected should move their coins. The wizard will show a warning in this case.
• fix #4491: on Android, if user had set "uBTC" as base unit, app crashed
• Several other minor bugfixes and usability improvements.

Changelog Electrum-GRS 3.2.2:
• Android: fix some crashes
• If present, libsecp256k1 is used to speed up elliptic curve operations. The library is bundled in the Windows, MacOS, and Android binaries. On Linux, it needs to be installed separately.
• Two-factor authentication is available on Android. Note that this will only provide additional security if one time passwords are generated on a separate device.
• Semi-automated crash reporting is implemented for Android.
• Qt/Kivy: added "gro" as optional base unit.
• Kivy GUI: significant performance improvements when displaying history and address list of large wallets; and transaction dialog of large transactions.

Features
• Encrypted wallet - the file that contains your groestlcoins is protected with a password. You are protected from thieves.
• Deterministic key generation - If you lose your wallet, you can recover it from its seed. You are protected from your own mistakes.
• Instant on - the client does not download the blockchain, it requests that information from a server. No delays, always up-to-date.
• Freedom and Privacy - The server does not store user accounts. You are not tied to a particular server, and the server does not need to know you.
• No scripts - Electrum-GRS does not download any script. A compromised server cannot send you arbitrary code and steal your groestlcoins.
• No single point of failure - The server code is open source, anyone can run a server.
• Transactions are signed locally - Your private keys are not shared with the server. You do not have to trust the server with your money.
• Firewall friendly - The client does not need to open a port, it simply polls the server for updates.
• Free software - Gnu GPL v3. Anyone can audit the code.
• Written in Python - The code is short, and easy to review.
• User Friendly - Support for Groestlcoin URIs, signed URIs and Groestlcoin aliases
• No Lock-In - You can export your private keys and use them in other groestlcoin clients.
• No Downtimes - Electrum-GRS servers are decentralized and redundant. Your wallet is never down.
• Proof Checking - Electrum-GRS Wallet verifies all the transactions in your history using SPV.
• Cold Storage - Keep your private keys offline, and go online with a watching-only wallet. Sign transactions from a computer taht is always offline. Broadcast them from a machine that does not have your keys.
• Multisign - Split the permission to spend your coins between several wallets using parallel BIP32 derivations and P2SH addresses ("2 of 2", "2 of 3"). Compact serialization format for unsigned or partially signed transactions, that includes the BIP32 master public key and derivation needed to sign inputs. Serialized transactions can be sent to cosigners or to cold storage using QR codes

It is appreciated if feedback of the following is provided:
1. Can you receive coins with legacy addresses? (small amounts to avoid losing them)
2. Can you receive coins with bech32 addresses? (small amounts to avoid losing them)
3. Can you receive coins with legacy testnet addresses? (small amounts to avoid losing them)
4. Can you receive coins with bech32 testnet addresses? (small amounts to avoid losing them)
5. Can you send coins with legacy addresses? (small amounts to avoid losing them)?
6. Can you send coins with bech32 addresses? (small amounts to avoid losing them)?
7. Can you send coins with legacy testnet addresses? (small amounts to avoid losing them)?
8. Can you send coins with bech32 testnet addresses? (small amounts to avoid losing them)?
9. Does it automatically detect servers under Tools - Network?
10. Are you able to sweep private keys?
11. Are you able to sign/verify messages?
12. Are you able to encrypt/decrypt messages?

This application is licensed under the GPL version 3. There is no warranty and no party shall be made liable to you for damages. If you lose coins due to this app, no compensation will be given. Use this app solely at your own risk.

The application may have unfound bugs and problems. To leave feedback: 
1. PM me
2. Email: groestlcoin@gmail.com
3. Post reports of erros in this topic.

Important:
Store your secret phrase somewhere safe!
The multi-signature and non native segwit addresses starts with a "3" and not with a "F".

Electrum-GRS is available in the Google play store:
https://play.google.com/store/apps/details?id=org.groestlcoin.electrumgrs

Source code:
GitHub Source server: https://github.com/Groestlcoin/electrumx-grs
Github Source server installer: https://github.com/Groestlcoin/electrumx-grs-installer
Github Source client: https://github.com/Groestlcoin/electrum-grs
Github Source Icons: https://github.com/Groestlcoin/electrum-grs-icons
Github Source locale: https://github.com/Groestlcoin/electrum-grs-locale
8
Groestlcoin Development & Technical Discussion / Electrum-GRS 3.3.4 released
« Last post by gruve_p on March 22, 2019, 09:54:40 pm »


Electrum-grs is a lightweight "thin client" groestlcoin wallet Windows, MacOS and Linux based on a client-server protocol. Its main advantages over the original Groestlcoin client include support for multi-signature wallets and not requiring the download of the entire block chain.


If you are an ordinary user of Groestlcoin and simply want the convenience of a web wallet with the security of a real application and support for multi-signature, then Elecrum-GRS is the right choice for you.

Changelog Electrum-GRS 3.3.4:
• The network layer has been rewritten using asyncio and aiorpcx. In addition to easier maintenance, this makes the client more robust against misbehaving servers.
• The minimum python version was increased to 3.6
• The blockchain headers and fork handling logic has been generalized. Clients by default now follow chain based on most work, not length.
• New wallet creation defaults to native segwit (bech32).
• RBF batching (opt-in): If the wallet has an unconfirmed RBF transaction, new payments will be added to that transaction, instead of creating new transactions.
• MacOS: support QR code scanner in binaries.
• hardware wallets:
   - Archos Safe-T mini: fix #4726 signing issue
   - KeepKey: full segwit support
   - Trezor: refactoring and compat with python-trezor 0.11
• Fix groestlcoin URI handling when app already running (#4796)
• Qt listings rewritten: the History tab now uses QAbstractItemModel, the other tabs use QStandardItemModel. Performance should be better for large wallets.
• Several other minor bugfixes and usability improvements.
• Improve network timeouts
• Prepend server transaction_broadcast error messages with explanatory message. Render error messages as plain text.
• Do not expose users to server error messages (#4968)
• Notify users of new releases. Release announcements must be signed, and they are verified by Electrum-GRS using a hardcoded Groestlcoin address.
• Display only QR code in QRcode Window
• Randomise locktime of transactions
• AppImage: we now also distribute self-contained binaries for x86_64 Linux in the form of an AppImage (#5042). The Python interpreter, PyQt5, libsecp256k1, PyCryptodomex, zbar, hidapi/libusb (including hardware wallet libraries) are all bundled. Note that users of hw wallets still need to set udev rules themselves.
• hw wallets: fix a regression during transaction signing that prompts the user too many times for confirmations (commit 2729909)
• Transactions now set nVersion to 2, to mimic Groestlcoin Core
• Fix Qt bug that made all hw wallets unusable on Windows 8.1 (#4960)
• Fix bugs in wallet creation wizard that resulted in corrupted wallets being created in rare cases (#5082, #5057)
• Fix compatibility with Qt 5.12 (#5109)

Changelog Electrum-GRS 3.2.3:
• hardware wallet: the Safe-T mini from Archos is now supported.
• BIP39 seeds: if a seed extension (aka passphrase) contained multiple consecutive whitespaces or leading/trailing whitespaces then the derived addresses were not following spec. This has been fixed, and affected should move their coins. The wizard will show a warning in this case.
• Revealer: the PRNG used has been changed (#4649)
• fix Linux distributables: 'typing' was not bundled, needed for python 3.4
• fix #4626: fix spending from segwit multisig wallets involving a Trezor cosigner when using a custom derivation path
• Several other minor bugfixes and usability improvements.

Changelog Electrum-GRS 3.2.2:
• Qt GUI: seed word auto-complete during restore
• performance improvements (wallet, and Qt GUI)
• hardware wallets: show debug message during device scan
• add regtest support (via --regtest flag)
• other minor bugfixes and usability improvements
• If present, libsecp256k1 is used to speed up elliptic curve operations. The library is bundled in the Windows, MacOS, and Android binaries. On Linux, it needs to be installed separately.
• Transactions that are dropped from the mempool are kept in the wallet as 'local', and can be rebroadcast. Previously these transactions were deleted from the wallet.
• The scriptSig and witness part of transaction inputs are no longer parsed, unless actually needed. The wallet will no longer display 'from' addresses corresponding to transaction inputs, except for its own inputs.
• The partial transaction format has been incompatibly changed. This was needed as for partial transactions the scriptSig/witness has to be parsed, but for signed transactions we did not want to do the parsing.  Users should make sure that all instances of Electrum-GRS they use to co-sign or offline sign, are updated together.
• Signing of partial transactions created with online imported addresses wallets now supports significantly more setups. Previously only online p2pkh address + offline WIF was supported.  Now the following setups are all supported:
 - online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline WIF,
 - online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline seed/xprv,
 - online {p2sh, p2wsh-p2sh, p2wsh}-multisig address + offline seeds/xprvs
 (potentially distributed among several different machines)
Note that for the online address + offline HD secret case, you need the offline wallet to recognize the address (i.e. within gap limit).  Having an xpub on the online machine is still the recommended setup, as this allows the online machine to generate new addresses on demand.
• Segwit multisig for bip39 and hardware wallets is now enabled (both p2wsh-p2sh and native p2wsh).
• Ledger: offline signing for segwit inputs (#3302) This has already worked for Trezor. Offline segwit signing can be combined with online imported addresses wallets.
• Added Revealer plugin. ( https://revealer.cc ) Revealer is a seed phrase back-up solution. It allows you to create a cold, analog, multi-factor backup of your wallet seeds, or of any arbitrary secret. The Revealer utilizes a transparent plastic visual one time pad.
• Fractional fee rates: the Qt GUI now displays fee rates with 0.1 gro/byte precision, and also allows this same resolution in the Send tab.
• Hardware wallets: a "show address" button is now displayed in the Receive tab of the Qt GUI. (#4316)
• Trezor One: implemented advanced/matrix recovery (#4329)
• Windows: use dnspython to resolve dns instead of socket.getaddrinfo (#4422)
• Importing minikeys: use uncompressed pubkey instead of compressed (#4384)
• SPV proofs: check inner nodes not to be valid transactions (#4436)
• Qt GUI: there is now an optional "dark" theme (#4461)
• Several other minor bugfixes and usability improvements.
• Fix DNS resolution on Windows
• Fix websocket bug in daemon

Changelog Electrum-GRS 3.1.2:
• Capital gains: For each outgoing transaction, the difference between the acquisition and liquidation prices of outgoing coins is displayed in the wallet history. By default, historical exchange rates are used to compute acquisition and liquidation prices. These values can also be entered manually, in order to match the actual price realized by the user. The order of liquidation of coins is the natural order defined by the blockchain; this results in capital gain values that are invariant to changes in the set of addresses that are in the wallet. Any other ordering strategy (such as FIFO, LIFO) would result in capital gain values that depend on the presence of other addresses in the wallet.
• Local transactions: Transactions can be saved in the wallet without being broadcast. The inputs of local transactions are considered as spent, and their change outputs can be re-used in subsequent transactions. This can be combined with cold storage, in order to create several transactions before broadcasting them. Outgoing
transactions that have been removed from the memory pool are also saved in the wallet, and can be broadcast again.
• Checkpoints: The initial download of a headers file was replaced with hardcoded checkpoints. The wallet uses one checkpoint per retargeting period. The headers for a retargeting period are downloaded only if transactions need to be verified in this period.
• The 'privacy' and 'priority' coin selection policies have been merged into one. Previously, the 'privacy' policy has been unusable because it was was not prioritizing confirmed coins. The new policy is similar to 'privacy', except that it de-prioritizes addresses that have unconfirmed coins.
• The 'Send' tab of the Qt GUI displays how transaction fees are computed from transaction size.
• The wallet history can be filtered by time interval.
• Replace-by-fee is enabled by default. Note that this might cause some issues with wallets that do not display RBF transactions until they are confirmed.
• Watching-only wallets and hardware wallets can be encrypted.
• The SSL checkbox option was removed from the GUI.
• The Trezor One and T hardware wallet is now supported.
• The Ledger hardware wallet is now supported.
• BIP84: native segwit p2wpkh scripts for bip39 seeds and hardware wallets can now be created when specifying a BIP84 derivation path. This is usable with Trezor and Ledger.
• Windows: the binaries now include ZBar, and QR code scanning should work.
• The Wallet Import Format (WIF) for private keys that was extended in 3.0 is changed. Keys in the previous format can be imported, compatibility is maintained. Newly exported keys will be serialized as "script_type:original_wif_format_key".
• BIP32 master keys for testnet once again have different version bytes than on mainnet. For the mainnet prefixes {x,y,Y,z,Z}|{pub,prv}, the corresponding testnet prefixes are {t,u,U,v,V}|{pub,prv}. Note that due to this change, testnet wallet files created with previous versions of Electrum must be considered broken, and they need to be recreated from seed words.
• A new version of the Electrum-GRS protocol is required by the client (version 1.2). Servers using older versions of the protocol will not be displayed in the GUI.

Changelog Electrum-GRS 3.0.6:
• Moved away from Linux binary file. Users must compile from source now.
• Moved away from electrum-grs-server codebase to electrumx-grs 1.2
• The source code is relicensed under the MIT Licence
• Separation between plugins and GUIs
• The command line uses jsonrpc to communicate with the daemon
• New command: 'notify <address> <url>'
• Alternative coin selection policy, designed to help preserve user privacy. Enable it by setting the Coin Selection preference to Privacy.
• The install wizard has been rewritten and improved
• Support minikeys for private key import and sweeping
• QT: add colors to labels
• The wallet file format has been upgraded. This upgrade is not backward compatible, which means that a wallet upgraded to the 2.7 format will not be readable by earlier versions of Electrum-GRS. Multiple accounts inside the same wallet are not supported in the new format; the Qt GUI will propose to split any wallet that has several accounts. Make sure that you have saved your seed phrase before you upgrade Electrum-GRS.
• This version introduces a separation between wallets types and keystores types. 'Wallet type' defines the type of Groestlcoin contract used in the wallet, while 'keystore type' refers to the method used to store private keys.
• Replace-By-Fee: RBF transactions are supported in Qt. A warning is displayed in the history for transactions that are replaceable, have unconfirmed parents, or that have very low fees.
• Qt GUI:
   - A fee slider is visible in the in send tab
   - The Address tab is hidden by default, can be shown with Ctrl-A
   - UTXOs are displayed in the Address tab
• Seed phrases can be extended with a user-chosen passphrase. The length of seed phrases is standardized to 12 words, using 132 bits of entropy. In the wizard, the type of the seed is displayed in the seed input dialog.
• Add number of confirmations to request status.
• In the GUI, refer to passphrase as 'seed extension'.
• Wizard: Hide seed options in a popup dialog.
• Separate sign and broadcast buttons in Qt tx dialog
• Allow spaces in private keys
• Add size to transaction details window
• Move plot plugin to main code
• Merge exchange_rate plugin with main code
• Faster synchronization and transaction creation
• Use fee slider for static fees
• Add fee slider to RBF dialog
• Simplify fee preferences.
• Add Testnet support
• Allow daemon to be launched in the foreground
• Qt: use separate tabs for addresses and UTXOs
• Qt: update fee slider with a network callback
• Enforce https on exchange rate APIs
• Use hardcoded list of exchanges
• Move 'Freeze' menu to Coins (utxo) tab
• Wallet file encryption using ECIES: A keypair is derived from the wallet password. Once the wallet is decrypted, only the public key is retained in memory, in order to save the encrypted file.
• The daemon requires wallets to be explicitly loaded before commands can use them. Wallets can be loaded using: 'electrum-grs daemon load_wallet [-w path]'. This command will require a password if the wallet is encrypted.
• Invoices and contacts are stored in the wallet file and are no longer shared between wallets. Previously created invoices and contacts files may be imported from the menu.
• Fees improvements:
    - Child Pays For Parent (CPFP) dialog in the GUI.
    - RBF is automatically proposed for low fee transactions.
• The GUI shows a blue icon when connected using a proxy.
• Show paid invoices in history tab
• Improve CPFP dialog
• Multiple Chain Validation: Electrum-GRS will download and validate block headers sent by servers that may follow different branches of a fork in the Groestlcoin blockchain. Instead of a linear sequence,block headers are organized in a tree structure. Branching points are located efficiently using binary search. The purpose of MCV is to detect and handle blockchain forks that are invisible to the classical SPV model.
• The desired branch of a blockchain fork can be selected using the network dialog. Branches are identified by the hash and height of the diverging block. Coin splitting is possible using RBF transaction
• MultiGroestl, Groestlwallet, Simple Groestlcoin support: If the user enters a BIP39 seed, the full derivation path is configurable in the install wizard.
• Option to send only confirmed coins
• Qt GUI:
    - Network dialog uses tabs and gets updated by network events.
    - The gui tabs use icons
• Daemon: The wallet password can be passed as parameter to the JSONRPC API.
• Validate contacts on import
• Command-line option for locktime
• Force headers download if headers file is corrupted
• Add websocket to windows builds
• The project was migrated to Python3 and Qt5. Python2 is no longer supported. If you cloned the source repository, you will need to run "python3 setup.py install" in order to install the new dependencies.
• Segwit support:
    - Native segwit scripts are supported using a new type of seed. The version number for segwit seeds is 0x100. The install wizard will not create segwit seeds by default; users must opt-in with the segwit option.
    - Native segwit scripts are represented using bech32 addresses, following BIP173. Please note that BIP173 is still in draft status, and that other wallets/websites may not support it. Thus, you should keep a non-segwit wallet in order to be able to receive groestlcoins during the transition period. If BIP173 ends up being rejected or substantially modified, your wallet may have to be restored from seed. This will not affect funds sent to bech32 addresses, and it will not affect the capacity of Electrum-GRS to spend these funds.
    - The BIP32 master keys of segwit wallets are serialized using new version numbers. The new version numbers encode the script type, and they result in the following prefixes:
         * xpub/xprv : p2pkh or p2sh
         * ypub/yprv : p2wpkh-in-p2sh
         * Ypub/Yprv : p2wsh-in-p2sh
         * zpub/zprv : p2wpkh
         * Zpub/Zprv : p2wsh
These values are identical for mainnet and testnet; tpub/tprv prefixes are no longer used in testnet wallets.
    - The Wallet Import Format (WIF) is similarly extended for segwit scripts. After a base58-encoded key is decoded to binary, its first byte encodes the script type:
         * 128 + 0: p2pkh
         * 128 + 1: p2wpkh
         * 128 + 2: p2wpkh-in-p2sh
         * 128 + 5: p2sh
         * 128 + 6: p2wsh
         * 128 + 7: p2wsh-in-p2sh
The distinction between p2sh and p2pkh in private key means that it is not possible to import a p2sh private key and associate it to a p2pkh address.
• A new version of the Electrum-GRS protocol is required by the client (version 1.1). Servers using older versions of the protocol will not be displayed in the GUI.
• By default, transactions are time-locked to the height of the current block. Other values of locktime may be passed using the command line.
• Sweeping minikeys: search for both compressed and uncompressed pubkeys
• Qt GUI: sweeping now uses the Send tab, allowing fees to be set
• Windows: if using the installer binary, there is now a separate shortcut for "Electrum-GRS Testnet"
• OS notifications for incoming transactions
• Better transaction size estimation:
    - fees for segwit txns were somewhat underestimated
    - some multisig txns were underestimated
    - handle uncompressed pubkeys
• The JSONRPC interface is password protected
• JSONRPC commands are disabled if the GUI is running, except 'ping', which is used to determine if a GUI is already running

Changelog Electrum-GRS 2.5.4:
• Linux binary file included
• Fixed sweeping private keys
• Fixed signing/verifying messages
• Electrum-GRS servers updated to 2.5.4
• Installwizard: do not allow direct copy-paste of the seed
• The QT GUI supports multiple windows in the same process. When a new Electrum-GRS instance is started, it checks for an already running Electrum-GRS process, and connects to it.
• The network layer uses select(), so all server communication is handled by a single thread. Moreover, the synchronizer, verifier, and exchange rate plugin now run as separate jobs within the networking thread instead of as their own threads.
• Plugins are revamped
• Simplified Chinese wordlist
• Dynamic Fees: using estimatefee value returned by server
• Various GUI improvements
• Arbitrary m-of-n multisig wallets are supported (n<=15).
• Transaction fees set manually in the GUI are retained, including when the user uses the '!' shortcut.
• New 'email' plugin, that enables sending and receiving payment requests by email.
• improvements to the transaction dialog:
    - request password after showing transaction
    - show change addresses in yellow color
• Improved logic for the network layer.
• More efficient coin selection. Spend oldest coins first, and minimize the number of transaction inputs.
• The command line accepts the '!' syntax to send the maximum amount available. It can be combined with the '--from' option. Example: 'payto <destination> ! --from <from_address>'
• The command line also accepts a '?' shortcut for private keys arguments, that triggers a prompt.
• Payment requests can be signed with a SSL certificate, and published as bip70 files in a public web directory.
• Show amounts (thousands separators and decimal point) according to locale in GUI
• Show unmatured coins in balance
• Faster startup, thanks to the following optimizations:
   1. Transaction input/outputs are cached in the wallet file
   2. Fast X509 certificate parser, not using pyasn1 anymore.
• The 'Invoices' and 'Send' tabs have been merged.
• Contacts are stored in a separate file, shared between wallets.
• A Search Box is available in the GUI (Ctrl-S)
• Own addresses are shown in green in the Transaction dialog.
• Address History dialog.
• The password dialog will ask for password again if the user enters a wrong password
• The Master Public Key dialog displays which keys belong to the wallet, and which are cosigners
• The transaction dialog will ask to save unsaved transaction received from cosigner pool, when user clicks on 'Close'
• The multisig restore dialog accepts xprv keys.

Features
• Encrypted wallet - the file that contains your groestlcoins is protected with a password. You are protected from thieves.
• Deterministic key generation - If you lose your wallet, you can recover it from its seed. You are protected from your own mistakes.
• Instant on - the client does not download the blockchain, it requests that information from a server. No delays, always up-to-date.
• Freedom and Privacy - The server does not store user accounts. You are not tied to a particular server, and the server does not need to know you.
• No scripts - Electrum-GRS does not download any script. A compromised server cannot send you arbitrary code and steal your groestlcoins.
• No single point of failure - The server code is open source, anyone can run a server.
• Transactions are signed locally - Your private keys are not shared with the server. You do not have to trust the server with your money.
• Firewall friendly - The client does not need to open a port, it simply polls the server for updates.
• Free software - Gnu GPL v3. Anyone can audit the code.
• Written in Python - The code is short, and easy to review.
• User Friendly - Support for Groestlcoin URIs, signed URIs and Groestlcoin aliases
• No Lock-In - You can export your private keys and use them in other groestlcoin clients.
• No Downtimes - Electrum-GRS servers are decentralized and redundant. Your wallet is never down.
• Proof Checking - Electrum-GRS Wallet verifies all the transactions in your history using SPV.
• Cold Storage - Keep your private keys offline, and go online with a watching-only wallet. Sign transactions from a computer taht is always offline. Broadcast them from a machine that does not have your keys.
• Multisign - Split the permission to spend your coins between several wallets using parallel BIP32 derivations and P2SH addresses ("2 of 2", "2 of 3"). Compact serialization format for unsigned or partially signed transactions, that includes the BIP32 master public key and derivation needed to sign inputs. Serialized transactions can be sent to cosigners or to cold storage using QR codes
• Cosigner Pool plugin - encrypted communication channel for multisign wallets, to send and receive partially signed transactions.
• Get noticed - Run a public Electrum-GRS server, publish your message and reach thousands of Groestlcoin users

It is appreciated if feedback of the following is provided:
1. Can you receive coins with legacy addresses? (small amounts to avoid losing them)
2. Can you receive coins with bech32 addresses? (small amounts to avoid losing them)
3. Can you receive coins with legacy testnet addresses? (small amounts to avoid losing them)
4. Can you receive coins with bech32 testnet addresses? (small amounts to avoid losing them)
5. Can you send coins with legacy addresses? (small amounts to avoid losing them)?
6. Can you send coins with bech32 addresses? (small amounts to avoid losing them)?
7. Can you send coins with legacy testnet addresses? (small amounts to avoid losing them)?
8. Can you send coins with bech32 testnet addresses? (small amounts to avoid losing them)?
9. Does the cosigner pool work when using a multi-signature wallet?
10. Does the virtual keyboard work when it asks to enter your wallet password?
11. Does it automatically detect servers under Tools - Network?
12. Are you able to sweep private keys?
13. Are you able to sign/verify messages?
14. Are you able to encrypt/decrypt messages?

This application is licensed under the GPL version 3. There is no warranty and no party shall be made liable to you for damages. If you lose coins due to this app, no compensation will be given. Use this app solely at your own risk.

The application may have unfound bugs and problems. To leave feedback: 
1. PM me
2. Email: groestlcoin@gmail.com
3. Post reports of erros in this topic.

Important:
Store your secret phrase somewhere safe!
The multi-signature and non native segwit addresses starts with a "3" and not with a "F".
Electrum-GRS creates an encrypted filename default_wallet instead of wallet.dat (like in Groestlcoin Core)
• Location Windows: Navigate to C:\Users\USER NAME\AppData\Roaming\Electrum-grs\wallets (or open windows explorer and enter %appdata%\Electrum-grs\wallets) and back up your default_wallet file by making a copy of it and moving it to a secure location.
• Location Mac: Navigate to ~/Library/Application Support/Electrum-grs/wallets and back up your default_wallet file by making a copy of it and moving it to a secure location.

You can download it using the links below and be up and running with Groestlcoin in 5 minutes.

Download the OSX wallet here: https://github.com/Groestlcoin/electrum-grs/releases/download/v3.3.4/electrum-grs-3.3.4.dmg

Download Windows installer here: https://github.com/Groestlcoin/electrum-grs/releases/download/v3.3.4/electrum-grs-3.3.4-setup.exe
Download Windows standalone wallet here: https://github.com/Groestlcoin/electrum-grs/releases/download/v3.3.4/electrum-grs-3.3.4.exe
Download Windows portable version here: https://github.com/Groestlcoin/electrum-grs/releases/download/v3.3.4/electrum-grs-3.3.4-portable.exe
                                       
Download Linux installere here: https://github.com/Groestlcoin/electrum-grs/releases/download/v3.3.4/electrum-grs-3.3.4-x86_64.AppImage

Source code:
GitHub Source server: https://github.com/Groestlcoin/electrumx-grs
Github Source server installer: https://github.com/Groestlcoin/electrumx-grs-installer
Github Source client: https://github.com/Groestlcoin/electrum-grs
Github Source Icons: https://github.com/Groestlcoin/electrum-grs-icons
Github Source locale: https://github.com/Groestlcoin/electrum-grs-locale
9
When's the next version planned for release, Gruve_p?

22 March 2019
10
Groestlcoin Development & Technical Discussion / Re: Electrum-GRS 3.2.2 released
« Last post by Bertram on March 02, 2019, 02:13:41 pm »
When's the next version planned for release, Gruve_p?
Pages: [1] 2 3 ... 10