★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit

[simongoat]

well done to digibyte for not paying the $100,000 fee to be listed on binance. There should be more coins rejecting this ridiculous fee.

From Telegram:

A note from Jared on DGB getting listed on Binance exchange that so many people are asking for:

"Binance, in my opinion, is the worst exchange in the crypto world. I am glad if DGB never gets listed there. They have added way too many scammy pump & dump ICOs and I doubt they will be around 2 years from now. I will not push or support DGB being listed there. Plus they wanted a $100,000 ludicrous bribe. Do you know how effective that money would be if we took that money and applied it to development?"

Not sure how I feel about this... Binance is pretty solid, just Chinese af not really fair to say this exchange is full of scammy icos when DGB is listed on plenty of less reputable markets (so is every other coin lol). Yeah 100k is alot of money but if all of DGBs competitors are there (DASH.BTC.LTC) then it would make sense to cut that check. Also liquidity is EXTREMELY important and Binance has alot of that.

It goes against the idea of decentralisation, having to pay the most popular exchange at the moment to be listed. Surely Binance makes enough money as it is. Its not right is it. The point of crypto currency is to that there is an alternative to this type of behaviour. So don't pay.

[1714098851]

1714098851

[1714098851]

1714098851

[1714098851]

1714098851

[1714098851]

1714098851

[1714098851]

1714098851

[Wawaji]

The problem here is that Jared is right, Binance chose to list tons of Scam Ethereum ICOs before many solid projects that are in development for many years now.

Binance cares about profit, not the community or development of the coin. The majority of the crypto space unfortunately is still made of stupid kids who want to make a quick buck following youtube and twitter tips.

[tross]

https://clutzykid.com/



DGB to my pool so the asic have another place to mine. I run a pool that is fair and centered on the miners!
Over time will reconstruct this pool to be different from all the rest. Come out give us a try!

discord

https://discord.gg/muRTtQs


We are also looking into air drops and other ways to reward miners!

[muleroaa]

well done to digibyte for not paying the $100,000 fee to be listed on binance. There should be more coins rejecting this ridiculous fee.

From Telegram:

A note from Jared on DGB getting listed on Binance exchange that so many people are asking for:

"Binance, in my opinion, is the worst exchange in the crypto world. I am glad if DGB never gets listed there. They have added way too many scammy pump & dump ICOs and I doubt they will be around 2 years from now. I will not push or support DGB being listed there. Plus they wanted a $100,000 ludicrous bribe. Do you know how effective that money would be if we took that money and applied it to development?"

I think he is right on the issue of having to pay $100k, but he is not right about the Binance exchange itself. If anything they want to foster the projects that they add to their exchange. There needs to be some element of quality to it, a longer term viability for investors and just generally a good project. I think DGB ticks all these boxes. It might be a good idea to see if we can get in the community vote? The winner of the vote does not have to pay a listing fee.

More on the views of the CEO of Binance, this is regarding to ICO's but the principles remain the same:

https://steemit.com/binance/@czbinance/5mm9uo-i-don-t-like-big-icos

[DigiByte]

We would like to announce the latest version of the DigiByte protocol has arrived in with v6.16.1 beta.  You can learn more here: https://github.com/digibyte/digibyte/releases/tag/v.6.16.1

[DigiByte]

https://twitter.com/DigiByteCoin/status/965792518032973824

"#DigiByte v6.16.1 Release summary: Worlds 1st #SegWit GUI wallet! Over 100,000 lines of code changed. 3 new GUI Themes (White, Blue, Black). Speed enhancements. New $DGB address prefix "dgb1" to prevent sending to wrong #blockchain. On par with $BTC 0.16. #P2SH changed '3' to 'S'"

[DigiByte]

https://github.com/digibyte/digibyte/releases/tag/v.6.16.1

Code:

DigiByte Core v6.16.1 Beta Test Release
=========================
Change Summary
-------------------
Over 100,000 lines of code changed in this release.

Initial Sync Performance Increase (Relay 10,000 headers now vs 2,000)

Add Additional Dedicated Seed Nodes

Fix Peer Connectivity Issues

Add Three DigiByte GUI Themes (White, Black, Blue... can be set in wallet preferences)

Change DGB p2sh Address Prefixes from "3" to "S". This prevents confusion with Bitcoin p2sh addresses. 

Add Support for future bech32 DigiByte Addresses (Future DGB addresses will start with "dgb1" all lowercase)
   - This is disabled by default and wallet will generate "D" addresses until more compatibility arrives in mobile and exchange wallets. For now add "addresstype=bech32" or "addresstype=p2sh-segwit" in your digibyte.conf to test these changes and generate these address types. WARNING: all other wallets do not yet support this address type.


Merge Improvements from Bitcoin Core 0.16.0 

Merge Improvements from Bitcoin Core 0.15.0

Notable changes 6.16.1 (On par with BTC 0.16)
===============

Wallet changes
---------------

### Segwit Wallet

DigiByte Core 6.16.1 introduces full support for segwit in the wallet and user interfaces. A new `-addresstype` argument has been added, which supports `legacy`, `p2sh-segwit` (default), and `bech32` addresses. It controls what kind of addresses are produced by `getnewaddress`, `getaccountaddress`, and `createmultisigaddress`. A `-changetype` argument has also been added, with the same options, and by default equal to `-addresstype`, to control which kind of change is used.

A new `address_type` parameter has been added to the `getnewaddress` and `addmultisigaddress` RPCs to specify which type of address to generate.
A `change_type` argument has been added to the `fundrawtransaction` RPC to override the `-changetype` argument for specific transactions.

- All segwit addresses created through `getnewaddress` or `*multisig` RPCs explicitly get their redeemscripts added to the wallet file. This means that downgrading after creating a segwit address will work, as long as the wallet file is up to date.
- All segwit keys in the wallet get an implicit redeemscript added, without it being written to the file. This means recovery of an old backup will work, as long as you use new software.
- All keypool keys that are seen used in transactions explicitly get their redeemscripts added to the wallet files. This means that downgrading after recovering from a backup that includes a segwit address will work

Note that some RPCs do not yet support segwit addresses. Notably, `signmessage`/`verifymessage` doesn't support segwit addresses, nor does `importmulti` at this time. Support for segwit in those RPCs will continue to be added in future versions.

P2WPKH change outputs are now used by default if any destination in the transaction is a P2WPKH or P2WSH output. This is done to ensure the change output is as indistinguishable from the other outputs as possible in either case.

### BIP173 (Bech32) Address support ("dgb1..." addresses)

Full support for native segwit addresses (BIP173 / Bech32) has now been added.
This includes the ability to send to BIP173 addresses (including non-v0 ones), and generating these
addresses (including as default new addresses, see above).

A checkbox has been added to the GUI to select whether a Bech32 address or P2SH-wrapped address should be generated when using segwit addresses. When launched with `-addresstype=bech32` it is checked by default. When launched with `-addresstype=legacy` it is unchecked and disabled.

### HD-wallets by default

Due to a backward-incompatible change in the wallet database, wallets created
with version 0.16.0 will be rejected by previous versions. Also, version 0.16.0
will only create hierarchical deterministic (HD) wallets. Note that this only applies
to new wallets; wallets made with previous versions will not be upgraded to be HD.

### Replace-By-Fee by default in GUI

The send screen now uses BIP125 RBF by default, regardless of `-walletrbf`.
There is a checkbox to mark the transaction as final.

The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` or
use the `replaceable` argument for individual transactions.

### Wallets directory configuration (`-walletdir`)

DigiByte Core now has more flexibility in where the wallets directory can be
located. Previously wallet database files were stored at the top level of the
DigiByte data directory. The behavior is now:

- For new installations (where the data directory doesn't already exist),
  wallets will now be stored in a new `wallets/` subdirectory inside the data
  directory by default.
- For existing nodes (where the data directory already exists), wallets will be
  stored in the data directory root by default. If a `wallets/` subdirectory
  already exists in the data directory root, then wallets will be stored in the
  `wallets/` subdirectory by default.
- The location of the wallets directory can be overridden by specifying a
  `-walletdir=<path>` option where `<path>` can be an absolute path to a
  directory or directory symlink.

Care should be taken when choosing the wallets directory location, as if it
becomes unavailable during operation, funds may be lost.

Build: Minimum GCC bumped to 4.8.x
------------------------------------
The minimum version of the GCC compiler required to compile DigiByte Core is now 4.8. No effort will be
made to support older versions of GCC. See discussion in issue #11732 for more information.
The minimum version for the Clang compiler is still 3.3. Other minimum dependency versions can be found in `doc/dependencies.md` in the repository.

Support for signalling pruned nodes (BIP159)
---------------------------------------------
Pruned nodes can now signal BIP159's NODE_NETWORK_LIMITED using service bits, in preparation for
full BIP159 support in later versions. This would allow pruned nodes to serve the most recent blocks. However, the current change does not yet include support for connecting to these pruned peers.

Performance: SHA256 assembly enabled by default
-------------------------------------------------
The SHA256 hashing optimizations for architectures supporting SSE4, which lead to ~50% speedups in SHA256 on supported hardware (~5% faster synchronization and block validation), have now been enabled by default. In previous versions they were enabled using the `--enable-experimental-asm` flag when building, but are now the default and no longer deemed experimental.

GUI changes
-----------
- Uses of "µDGB" in the GUI now also show the more colloquial term "digis", specified in BIP176.
- The option to reuse a previous address has now been removed. This was justified by the need to "resend" an invoice, but now that we have the request history, that need should be gone.
- Support for searching by TXID has been added, rather than just address and label.
- A "Use available balance" option has been added to the send coins dialog, to add the remaining available wallet balance to a transaction output.
- A toggle for unblinding the password fields on the password dialog has been added.

RPC changes
------------

### New `rescanblockchain` RPC

A new RPC `rescanblockchain` has been added to manually invoke a blockchain rescan.
The RPC supports start and end-height arguments for the rescan, and can be used in a
multiwallet environment to rescan the blockchain at runtime.

### New `savemempool` RPC
A new `savemempool` RPC has been added which allows the current mempool to be saved to
disk at any time to avoid it being lost due to crashes / power loss.

### Safe mode disabled by default

Safe mode is now disabled by default and must be manually enabled (with `-disablesafemode=0`) if you wish to use it. Safe mode is a feature that disables a subset of RPC calls - mostly related to the wallet and sending - automatically in case certain problem conditions with the network are detected. However, developers have come to regard these checks as not reliable enough to act on automatically. Even with safe mode disabled, they will still cause warnings in the `warnings` field of the `getneworkinfo` RPC and launch the `-alertnotify` command.

### Renamed script for creating JSON-RPC credentials

The `share/rpcuser/rpcuser.py` script was renamed to `share/rpcauth/rpcauth.py`. This script can be
used to create `rpcauth` credentials for a JSON-RPC user.

### Validateaddress improvements

The `validateaddress` RPC output has been extended with a few new fields, and support for segwit addresses (both P2SH and Bech32). Specifically:
* A new field `iswitness` is True for P2WPKH and P2WSH addresses ("dgb1..." addresses), but not for P2SH-wrapped segwit addresses (see below).
* The existing field `isscript` will now also report True for P2WSH addresses.
* A new field `embedded` is present for all script addresses where the script is known and matches something that can be interpreted as a known address. This is particularly true for P2SH-P2WPKH and P2SH-P2WSH addresses. The value for `embedded` includes much of the information `validateaddress` would report if invoked directly on the embedded address.
* For multisig scripts a new `pubkeys` field was added that reports the full public keys involved in the script (if known). This is a replacement for the existing `addresses` field (which reports the same information but encoded as P2PKH addresses), represented in a more useful and less confusing way. The `addresses` field remains present for non-segwit addresses for backward compatibility.
* For all single-key addresses with known key (even when wrapped in P2SH or P2WSH), the `pubkey` field will be present. In particular, this means that invoking `validateaddress` on the output of `getnewaddress` will always report the `pubkey`, even when the address type is P2SH-P2WPKH.

### Low-level changes

- The deprecated RPC `getinfo` was removed. It is recommended that the more specific RPCs are used:
  * `getblockchaininfo`
  * `getnetworkinfo`
  * `getwalletinfo`
  * `getmininginfo`
- The wallet RPC `getreceivedbyaddress` will return an error if called with an address not in the wallet.
- The wallet RPC `addwitnessaddress` was deprecated and will be removed in version 0.17,
  set the `address_type` argument of `getnewaddress`, or option `-addresstype=[bech32|p2sh-segwit]` instead.
- `dumpwallet` now includes hex-encoded scripts from the wallet in the dumpfile, and
  `importwallet` now imports these scripts, but corresponding addresses may not be added
  correctly or a manual rescan may be required to find relevant transactions.
- The RPC `getblockchaininfo` now includes an `errors` field.
- A new `blockhash` parameter has been added to the `getrawtransaction` RPC which allows for a raw transaction to be fetched from a specific block if known, even without `-txindex` enabled.
- The `decoderawtransaction` and `fundrawtransaction` RPCs now have optional `iswitness` parameters to override the
  heuristic witness checks if necessary.
- The `walletpassphrase` timeout is now clamped to 2^30 seconds.
- Using addresses with the `createmultisig` RPC is now deprecated, and will be removed in a later version. Public keys should be used instead.
- Blockchain rescans now no longer lock the wallet for the entire rescan process, so other RPCs can now be used at the same time (although results of balances / transactions may be incorrect or incomplete until the rescan is complete).
- The `logging` RPC has now been made public rather than hidden.
- An `initialblockdownload` boolean has been added to the `getblockchaininfo` RPC to indicate whether the node is currently in IBD or not.
- `minrelaytxfee` is now included in the output of `getmempoolinfo`

Other changed command-line options
----------------------------------
- `-debuglogfile=<file>` can be used to specify an alternative debug logging file.
- DigiByte-cli now has an `-stdinrpcpass` option to allow the RPC password to be read from standard input.
- The `-usehd` option has been removed.
- DigiByte-cli now supports a new `-getinfo` flag which returns an output like that of the now-removed `getinfo` RPC.


Notable changes  n6.16.1 Release (on par with BTC 0.15 merge)
===============

Network fork safety enhancements
--------------------------------

A number of changes to the way DigiByte Core deals with peer connections and invalid blocks
have been made, as a safety precaution against blockchain forks and misbehaving peers.

- Unrequested blocks with less work than the minimum-chain-work are now no longer processed even
if they have more work than the tip (a potential issue during IBD where the tip may have low-work).
This prevents peers wasting the resources of a node. 

- Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.

- For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it
doesn't, and if we still haven't heard about a block with sufficient work after a 20 minute timeout, then we send
a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient
work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent
excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable
number of nodes not known to be on bogus chains.

- Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact
block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them)
will now be disconnected.

- If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect
to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect
the peer that least recently announced a new block.

- The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be
invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that
descends from an invalid block is marked as such.


Miner block size limiting deprecated
------------------------------------

Though blockmaxweight has been preferred for limiting the size of blocks returned by
getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished
to limit their block size directly. Using this option resulted in a few UI issues as
well as non-optimal fee selection and ever-so-slightly worse performance, and has thus
now been deprecated. Further, the blockmaxsize option is now used only to calculate an
implied blockmaxweight, instead of limiting block size directly. Any miners who wish
to limit their blocks by size, instead of by weight, will have to do so manually by
removing transactions from their block template directly.


GUI settings backed up on reset
-------------------------------

The GUI settings will now be written to `guisettings.ini.bak` in the data directory before wiping them when
the `-resetguisettings` argument is used. This can be used to retroactively troubleshoot issues due to the
GUI settings.


Duplicate wallets disallowed
----------------------------

Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing
issues when both were opened simultaneously. It is no longer possible to open copies of the same wallet.


Debug `-minimumchainwork` argument added
----------------------------------------

A hidden debug argument `-minimumchainwork` has been added to allow a custom minimum work value to be used
when validating a chain.


Low-level RPC changes
----------------------

- The "currentblocksize" value in getmininginfo has been removed.

- `dumpwallet` no longer allows overwriting files. This is a security measure
  as well as prevents dangerous user mistakes.

- `backupwallet` will now fail when attempting to backup to source file, rather than
  destroying the wallet.

- `listsinceblock` will now throw an error if an unknown `blockhash` argument
  value is passed, instead of returning a list of all wallet transactions since
  the genesis block. The behaviour is unchanged when an empty string is provided.

[gooldbitx103]

https://twitter.com/DigiByteCoin/status/965792518032973824

"#DigiByte v6.16.1 Release summary: Worlds 1st #SegWit GUI wallet! Over 100,000 lines of code changed. 3 new GUI Themes (White, Blue, Black). Speed enhancements. New $DGB address prefix "dgb1" to prevent sending to wrong #blockchain. On par with $BTC 0.16. #P2SH changed '3' to 'S'"

Good job congrats. Keep up the good work!

[ecopointberg]

Я дyмaю y DigiByte  ecть бyдyщee...

[dagoz87]

DIGIBYTE (DGB) MINING POOL

http://miningpool.shop

Based on Yiimp pool (No Registration Needed)
Fee  : 0.9% Only (Lowest Fee)

Ddos Protection Server ( Uptime 99.99%)
Powered by Amazon Web Service (AWS)

Code:

-o stratum+tcp://stratum.miningpool.shop:20009 -u <WALLET_ADDRESS> -p x

NICEHASH / MININGRIGRENTAL

Code:

Pool host: stratum.miningpool.shop
Pool port: 20009
Pool user: Your_Wallet_Address
Pool pass: w=worker01
Algorithm: SCRYPT

Support Live Chat

Discord Support Chat

[Onizuka3024]

Going back $0.01 really.. Miner selling at any price lol.. Or possibly  whale cashing out to collect bag of $etc $zcl airdrop?

[gooldbitx103]

A spanish company accepting Litecoin & Digibyte and explaining the reasons why (for spanish readers ) :
https://www.devina.es/economia/una-empresa-vinarocense-la-primera-la-comunitat-valenciana-aceptar-pagos-digibyte/
(you can translate in your language at https://translate.google.com/ )
source: Digibyte retweet https://twitter.com/DeVinaonline/status/967133110008762370

[Elder III]

Going back $0.01 really.. Miner selling at any price lol.. Or possibly  whale cashing out to collect bag of $etc $zcl airdrop?

It's $0.034 right now....?

[gooldbitx103]

Interesting post by Josiah Spackman (DigiByte Foundation Ambassador)
https://medium.com/@josiah_digibyte/digibyte-vs-bitcoin-transaction-fees-12129d85f771

[metallicelmo]

So there is a new wallet release coming up?

[rade]

So there is a new wallet release coming up?

it is out
https://digibyte.io/digibyte-wallet-downloads#

[iikun]

So there is a new wallet release coming up?

it is out
https://digibyte.io/digibyte-wallet-downloads#

Thought it was still in Beta. I'll have to give it a whirl, thx for posting

[mohsin111]

https://twitter.com/jaredctate/status/968204153427320832

Oculus and HTC Vive. That's a biggy.

[SpudroForEveryone]

Any news or development?  What happend to that marketing bounty that was collected? I guess the dev team dumped that DGB in the exchange and wen't to the Bahamas  Lol I'm obviously joking! I called my first target 310 sat and and it went very close to that on Poloniex. I can't wait it will go sub 200    I'll buy BIG TIME then. 

[LazyBitInvestor]

So there is a new wallet release coming up?

I heard info that Digibyte wallet for iOS will be released soon... I hold DGB > than half a year, I believe in its future. Its speed is ~280 trans per sec and it is 14x more than ETH speed.