whats wrong with the digihash?
The pool has been reset and is working properly now. Thanks for mining on DigiHash and supporting future DigiByte development! |
|
|
|
Beware of scammers spoofing @digibyte.io email addresses & sending phishing emails with malware to targeted individuals. Never open unknown emails & attachments. Always check the sender's address. We are working to add a DMARC record to the domain. https://dmarc.org/ |
|
|
|
I have not heard about DGB for a long time. Hope there is an update from the dev team. Maybe this month there is good news from DGB that I expect.  The best thing to do is to join their Telegram group https://t.me/DGBalerts, they are very active and post a lot. Yes indeed, the most direct way to get real-time news & information on the DigiByte Blockchain is to follow the DGB Alerts channel on @telegram https://t.me/DGBalertsWe no longer check this thread often. |
|
|
|
Can anyone tell me if this is for real, I've seen it on another altcoin tweet where you send 1 altcoin and get 10 back in return, now I see it in the DGB twitter. I always thought if it was too good to be true it usually is. "ĐiԍiByte @DigiBaite 4h4 hours ago Replying to @DigiByteCoin Juѕt fօr tօdaу WE аre gіve awaу 5.000 ΕТН tօ our faոѕ. You can sеnd 0.5-5.0 ΕТН tօ our addrеѕѕ aոd We will ѕеոd уօu back 5-50 ΕТН. Details below!" https://twitter.com/DigiByteCoin/status/972219528167022593This is fake, please report these accounts when you see them. Always check the username, a dead giveaway is usually the username is 1 letter or character off and they have almost no followers. On a daily basis, we are seeing people making fake DigiByte accounts and fake Jared accounts asking people to send ETH or DGB. Twitter really needs to address this as almost every prominent figure in the industry now has this problem. The official Twitter account is @DigiByteCoin: https://twitter.com/DigiByteCoin |
|
|
|
The Digibyte community deserves answers. What the hell is going on?
Thanks to everyone here for supporting DigiByte and thank you for your concern. The above issue has been resolved and was a result of miscommunication between several individuals. No one is embezzling funds. Many volunteers have donated their own time and money to get DGB where it is today. For those that are new here please note the majority of the DGB community now interacts on Telegram and not on this message board. As always FUD rises when we experience market pullbacks. DigiByte is very much alive and there are several exciting things going on. New wallets, new exchanges and new marketing efforts. You can find out more here and where to get involved: https://www.digibyte.io/digibyte-communityWe will be updating the foundation website with more information about current progress and updates over the next couple days to bring 100% transparency to the three donation funds we have started. In the meantime please help us get a better idea of what algo people are actively mining on DGB by voting if you are a miner here in this Twitter poll: https://twitter.com/DigiByteCoin/status/972158933803683843 |
|
|
|
https://github.com/digibyte/digibyte/releases/tag/v.6.16.1DigiByte 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.
|
|
|
|
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'"
|
|
|
|
A note from Jared on Telegram alerts which you can follow here: https://t.me/DGBalertsA note to all DigiByte investors. Days like today happen, and they are outside of our control. These cycles have been occurring in crypto markets for the last half-decade. This pullback was forecasted by many.
We are also coming up on Chinese Lunar New Year. Combine that with regulatory uncertainty across Asia and this pullback undoubtedly started there. Market pullbacks are an excellent opportunity for new market participants to get involved.
We have many exciting developments underway now! New wallets, new exchanges, and new platforms and services built on top of DGB. 100's of people are working hard each and every day to make DigiByte better.
Rome was not built in a day and we will continue doing like we have the past four years. Keeping our head down and focused on building real-world DigiByte utility. That is what really matters for long-term sustained growth.
2018 is going to be a great year! Stay tuned for more daily updates and news! Thank you all for continuing to support DigiByte!
- Jared
DigiByte Founder |
|
|
|
Hi who can help me with addnode and how too ad it in debug console
I can not sync there is no peers
Make sure your firewall and or local network is not blocking peers. You can always find a real time list of peers here: https://www.whatsmydns.net/#A/seed.digibyte.ioGo to Help -> debug console. Use a command like this: |
|
|
|
OK, I stand corrected!  While we are here, can we go into this a little further and spell out where and what changes Ian will need to make please? I can see how the above conversation could lead to more mining on the DigiByte network. I know how so many people hate asking questions but can’t wait to hear the answers, so they can try things for themselves without looking foolish. Oh by the way this is an open question, anyone with the answers can butt in and explain with their community spirit. It doesn't have to be Jared who possibly just went to bed at 5am, if he's in HK.  Once you have 5 data directories setup you can make a shell script like below: digibyted --datadir=/root/data/sha256d/
sleep 2
digibyted --datadir=/root/data/scrypt/
digibyted --datadir=/root/data/qubit/
sleep 2
digibyted --datadir=/root/data/skein/
sleep 2
digibyted --datadir=/root/data/groestl/
Note: calling digibyted only works to start wallet. To execute commands run a script like below by calling "digibyte-cli": /root/digibyte/src/digibyte-cli -datadir=/root/data/sha256d/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/scrypt/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/qubit/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/skein/ stop
sleep 2
/root/digibyte/src/digibyte-cli -datadir=/root/data/groestl/ stop
Each instance of digibyted needs to run on a different RPC port. What we do is we run 4 out of the 5 algos with the "prune=550" command to keep from bloating the server. All data comes from one algo and gets relayed to other 4 algos locally. Example Sha256 config: rpcuser=user
rpcpassword=password
port=14012
rpcport=14011
daemon=1
server=1
algo=sha256d
maxconnections=500
prune=550
The prune=550 command purges data beyond 550mb of the most recent blocks and txs. It is not enabled be default. |
|
|
|
I am trying to setup a mining pool with 2 algorithms. I have 2 data directory, 2 different conf files. When I start the second process the debug.log shows
CDBEnv::Open: LogDir=/home/test/.digibytescrypt/database ErrorFile=/home/test/.digibytescrypt/db.log
2017-11-27 19:38:22 Selected Algo: scrypt
2017-11-27 19:38:22 Unable to bind to [::]:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Unable to bind to 0.0.0.0:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Error: Unable to bind to 0.0.0.0:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Error: Failed to listen on any port. Use -listen=0 if you want this.
Is it possible to run 2 digitbyte processes on the same server so that 2 algo could be mined at the same time?
Ian
This is most definitely possible, you just need to specify separate data directories for each algo. We do 5 on one server for DigiHash. You could be trying to start two separate instances from the same directory. That's what that error looks like. Note: You need to make sure each daemon runs on a different port aka deamon 1 on 14030, 2 14033 and so on. |
|
|
|
I am trying to setup a mining pool with 2 algorithms. I have 2 data directory, 2 different conf files. When I start the second process the debug.log shows
CDBEnv::Open: LogDir=/home/test/.digibytescrypt/database ErrorFile=/home/test/.digibytescrypt/db.log
2017-11-27 19:38:22 Selected Algo: scrypt
2017-11-27 19:38:22 Unable to bind to [::]:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Unable to bind to 0.0.0.0:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Error: Unable to bind to 0.0.0.0:12024 on this computer. DigiByte Core is probably already running.
2017-11-27 19:38:22 Error: Failed to listen on any port. Use -listen=0 if you want this.
Is it possible to run 2 digitbyte processes on the same server so that 2 algo could be mined at the same time?
Ian
This is most definitely possible, you just need to specify separate data directories for each algo. We do 5 on one server for DigiHash. You could be trying to start two separate instances from the same directory. That's what that error looks like. |
|
|
|
Why can't I see the digibyte-qt inside digibyte-6.14.2-aarch64-linux-gnu.tar.gz (it's the latest Linux wallet, AFAIK)? p.s. it's better for Digibyte team to correct the download links at Digibyte.co. I found a proper wallet for linux only here: https://github.com/digibyte/digibyte/releasesThis issue has been corrected. The proper links are now on the website. |
|
|
|
We most definitely are talking about potential algo swaps. We would love to hear peoples suggestions for other algos. |
|
|
|
|
For those new to DigiByte please disregard the trolls that pop up here under freshly created accounts. Simply look at their past posts. This same trend happens everytime DGB is moving downward. The Same process happens with other altcoins. This is often done by paid trolls and fake accounts trying to force the price down to buy in lower. This is a well-known practice in this industry. Please do your own research and make your own informed decisions. We are working hard every day to make DGB better and will continue to do so. Simply look through the past 3.5 years of history on this thread.
|
|
|
|
|
Show Posts
