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

[Ryven Cedrylle]

Digibyte, Need feedback to make this happen.

Yep. Got my finger on the proverbial trigger, just waiting.

[1715205274]

1715205274

[1715205274]

1715205274

[1715205274]

1715205274

[1715205274]

1715205274

[ReSl]

Look's good!
Like to see youre updates working with Digibyte.

Will take a while. Im moving into new flat next month and work is not getting less, cause of broken wrist from my colleague last weekend ....

[24hralttrade]

Look's good!
Like to see youre updates working with Digibyte.

Will take a while. Im moving into new flat next month and work is not getting less, cause of broken wrist from my colleague last weekend ....

Aii, Good luck!

[24hralttrade]

This is will bring some real value!
Coming this week.

[ReSl]

Do you want to getting DGB into easy mining for all?

http://www.reddit.com/r/Digibyte/comments/2gl1p7/interface_between_the_user_and_whatever_mining/

Just join the party Waiting for your comments!

[SSG69]

Count me in and it is a great idea... This will show dgb is serious coin and has a great community and dev team...

Person above trying to fud is looking for cheap dgb but as i said it will not go lower than 25 unless someone intentinally dumps.

Either the weather changes or it stays like it is

Can you dump accidently too?

just kidding mate

2cents

closing in to 23 mintpal...

i thought u buy it all.. you disappoint me

21 now very possible

id buy that

[24hralttrade]

Do you want to getting DGB into easy mining for all?

http://www.reddit.com/r/Digibyte/comments/2gl1p7/interface_between_the_user_and_whatever_mining/

Just join the party Waiting for your comments!

This is really nice and thank you for taking action!
Do you have any idea how much the funding will be?


24

[ReSl]

This is really nice and thank you for taking action!
Do you have any idea how much the funding will be?

No, but i can asked him. Just waiting how much people responding on this.

[24hralttrade]

https://bittrex.com/Market/Index?MarketName=BTC-DGB

Works again.

[flound1129]

★★ DigiByte v3.0.2 Coming Soon!★★

We have decided to release a version 3.0.2 wallet after the BTC China expo. This wallet will feature two main changes and will require mining pools to update:


1) A standardized Chinese name for "DigiByte" in the DGB wallet. We will be asking several native Chinese speakers at the conference what the proper translation for "DigiByte" into Chinese characters should be. Once we decide on the correct characters we will put it into the wallet. This will dramatically help DigiByte enter the Chinese market place.

2) We will be issuing a fix for the Scrypt block issue as well as the daemon rejection issue several pools are experiencing. In the mean time we would like some feedback & help testing this fix. A big shout-out to Thrassos for pointing this out and helping us figure out this issue!


The Scrypt block & daemon rejection issue:
Scrypt blocks are being rejected do to this code: "if (block.nVersion < 2)"
https://github.com/digibyte/DigiByteProject/blob/1dda53450ca9b2d0aad767007f01f12578b7f39e/src/main.cpp#L2576

Code:

      // Reject block.nVersion=1 blocks when 95% (75% on testnet) of the network has upgraded:
        if (block.nVersion < 2)
        {
            if ((!TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 950, 1000)) ||
                (TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 75, 100)))
            {
                return state.Invalid(error("AcceptBlock() : rejected nVersion=1 block"),
                                     REJECT_OBSOLETE, "bad-version");
            }
        }

The fix should be simple by changing BLOCK_VERSION_DEFAULT from 1-2. If anyone knows of any issues we might see with this please let us know.
https://github.com/digibyte/DigiByteProject/blob/master/src/core.h#L30

Code:

{
    // primary version
    BLOCK_VERSION_DEFAULT        = 2,

    // algo
    BLOCK_VERSION_ALGO           = (7 << 9),
    BLOCK_VERSION_SHA256D        = (1 << 9),
    BLOCK_VERSION_GROESTL        = (2 << 9),
    BLOCK_VERSION_SKEIN          = (3 << 9),
    BLOCK_VERSION_QUBIT          = (4 << 9),
};

The github account has been updated with this change. If we could get some mining pools to test this change & report back it would be much appreciated! Thank you all!

It would be great if you could tag the releases in github.  3.0.1 was never tagged, compiling git head gives a wallet version (in getinfo) different than the version reported by the binary downloads.  Please tell me how to get a proper source tree for 3.0.1 so I can make this change.

[ycagel]

Nice to see this resolved. Appreciate you reaching out to them.

YC

https://bittrex.com/Market/Index?MarketName=BTC-DGB

Works again.

[ycagel]

This is some of the impact a BTC38 can have:

Blackcoin Price Blasts Off

Just last week, CCN profiled Blackcoin’s the moderate price rise which pulled the altcoin out of a significant price downtrend.

On September 11–when CCN last examined the Blackcoin price–the coin was valued at 9,736 satoshis, a 14% rise over the previous day. The Blackcoin price continued to increase over the next two days, peaking at 13,227 satoshis before cooling off to 11,083 on September 14.

At 10:00 pm EST on September 14, Blackcoin was trading at an average of 10,911 satoshis. By 11:15, the coin had increased 9% to 11,986. The price remained fairly consistent until 4:30 am on September 15. At that point, the Blackcoin price began to explode.

Within 3 hours, Blackcoin’s value increased an astounding 20% to 14,911 satoshis. The price continued to increase until 9 am, where it peaked at 17,082 satoshis.

Following this dramatic rise, the Blackcoin price declined a bit to its current position at 15,712 satoshis. Despite the mild decline from its recent peak, Blackcoin’s September 15 price-rally is nothing short of impressive. Over a 24-hour span, the Blackcoin price increased nearly 43%. Blackcoin’s market cap increased to ~$5.7 million,  placing it thirteenth in market cap and just $600,000 behind twelfth-place Counterparty.

Blackcoin Price Analysis

The recent Blackcoin price increase was ignited by an infusion of Chinese investments. More than 64% of Blackcoin’s 24-hour volume is centralized on the Chinese BTC38 exchange. At present, Blackcoin comprises nearly  11% of BTC38’s total volume, trailing only Dogecoin (51%) and BitSharesX (17%).

Blackcoin price btc38 exchange volume
Breakdown of Top 5 Coin Volumes on BTC38 According to CoinMarketCap. Blackcoin currently ranks 3rd on the popular Chinese exchange.
The increased Blackcoin exchange volume has raised Blackcoin’s CoinGecko metric score as well. On September 11, Blackcoin’s scored 47% with a 42% community, a 62% developer, and a 43% liquidity score. Blackcoin’s community and developer scores remain unchanged since then, but the extra exchange volume increased the coin’s liquidity score to 43% and its overall score to 49%.

CCN’s last article on Blackcoin noted that the coin’s metric score was five spots higher than its market cap ranking, which can sometimes indicate a coin is out-performing its market cap and could be poised for a price rise. In this particular case, the Blackcoin price trend confirmed that theory, as Blackcoin rose to thirteenth in market cap–just behind its twelfth-place metric rank. Since Blackcoin is now ranked comparably to its overall coin health, traders should not invest on the assumption that Blackcoin is underperforming.

Investors should also be wary of a cooling-off period, which is liable to happen after frantic price rises such as the one Blackcoin has experienced. After the coin’s value rose more than 40% in a single day, many investors will be tempted to sell their holdings at a huge profit. Short-term investors should keep this in mind before buying Blackcoins at what could be a temporary price-peak, and long-term investors should remember this before panicking if Blackcoin undergoes a moderate price-correction.

Disclosure: The author does not have any Blackcoin investments or affiliations.

Source: http://www.cryptocoinsnews.com/chinese-investment-fuels-blackcoin-price-explosion/

[rayaodi]

★★ DigiByte v3.0.2 Coming Soon!★★

We have decided to release a version 3.0.2 wallet after the BTC China expo. This wallet will feature two main changes and will require mining pools to update:


1) A standardized Chinese name for "DigiByte" in the DGB wallet. We will be asking several native Chinese speakers at the conference what the proper translation for "DigiByte" into Chinese characters should be. Once we decide on the correct characters we will put it into the wallet. This will dramatically help DigiByte enter the Chinese market place.

2) We will be issuing a fix for the Scrypt block issue as well as the daemon rejection issue several pools are experiencing. In the mean time we would like some feedback & help testing this fix. A big shout-out to Thrassos for pointing this out and helping us figure out this issue!


The Scrypt block & daemon rejection issue:
Scrypt blocks are being rejected do to this code: "if (block.nVersion < 2)"
https://github.com/digibyte/DigiByteProject/blob/1dda53450ca9b2d0aad767007f01f12578b7f39e/src/main.cpp#L2576

Code:

      // Reject block.nVersion=1 blocks when 95% (75% on testnet) of the network has upgraded:
        if (block.nVersion < 2)
        {
            if ((!TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 950, 1000)) ||
                (TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 75, 100)))
            {
                return state.Invalid(error("AcceptBlock() : rejected nVersion=1 block"),
                                     REJECT_OBSOLETE, "bad-version");
            }
        }

The fix should be simple by changing BLOCK_VERSION_DEFAULT from 1-2. If anyone knows of any issues we might see with this please let us know.
https://github.com/digibyte/DigiByteProject/blob/master/src/core.h#L30

Code:

{
    // primary version
    BLOCK_VERSION_DEFAULT        = 2,

    // algo
    BLOCK_VERSION_ALGO           = (7 << 9),
    BLOCK_VERSION_SHA256D        = (1 << 9),
    BLOCK_VERSION_GROESTL        = (2 << 9),
    BLOCK_VERSION_SKEIN          = (3 << 9),
    BLOCK_VERSION_QUBIT          = (4 << 9),
};

The github account has been updated with this change. If we could get some mining pools to test this change & report back it would be much appreciated! Thank you all!

we use '极特币' for digibyte in china . and also btc38 .
and it's a  great chinese name for digibyte  .

[ycagel]

Rayaodi,
 Good to have you here. Do you have any contacts to Chinese exchanges there?

YC

★★ DigiByte v3.0.2 Coming Soon!★★

We have decided to release a version 3.0.2 wallet after the BTC China expo. This wallet will feature two main changes and will require mining pools to update:


1) A standardized Chinese name for "DigiByte" in the DGB wallet. We will be asking several native Chinese speakers at the conference what the proper translation for "DigiByte" into Chinese characters should be. Once we decide on the correct characters we will put it into the wallet. This will dramatically help DigiByte enter the Chinese market place.

2) We will be issuing a fix for the Scrypt block issue as well as the daemon rejection issue several pools are experiencing. In the mean time we would like some feedback & help testing this fix. A big shout-out to Thrassos for pointing this out and helping us figure out this issue!


The Scrypt block & daemon rejection issue:
Scrypt blocks are being rejected do to this code: "if (block.nVersion < 2)"
https://github.com/digibyte/DigiByteProject/blob/1dda53450ca9b2d0aad767007f01f12578b7f39e/src/main.cpp#L2576

Code:

      // Reject block.nVersion=1 blocks when 95% (75% on testnet) of the network has upgraded:
        if (block.nVersion < 2)
        {
            if ((!TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 950, 1000)) ||
                (TestNet() && CBlockIndex::IsSuperMajority(2, pindexPrev, 75, 100)))
            {
                return state.Invalid(error("AcceptBlock() : rejected nVersion=1 block"),
                                     REJECT_OBSOLETE, "bad-version");
            }
        }

The fix should be simple by changing BLOCK_VERSION_DEFAULT from 1-2. If anyone knows of any issues we might see with this please let us know.
https://github.com/digibyte/DigiByteProject/blob/master/src/core.h#L30

Code:

{
    // primary version
    BLOCK_VERSION_DEFAULT        = 2,

    // algo
    BLOCK_VERSION_ALGO           = (7 << 9),
    BLOCK_VERSION_SHA256D        = (1 << 9),
    BLOCK_VERSION_GROESTL        = (2 << 9),
    BLOCK_VERSION_SKEIN          = (3 << 9),
    BLOCK_VERSION_QUBIT          = (4 << 9),
};

The github account has been updated with this change. If we could get some mining pools to test this change & report back it would be much appreciated! Thank you all!

we use '极特币' for digibyte in china . and also btc38 .
and it's a  great chinese name for digibyte  .

[rayaodi]

to YC :

no , but there has vote on btc38 , you can check this :

http://www.btc38.com/trade/vote_for_trade.html

and you can see digibyte is 39 .

and you can pull digibyte just use btc.

37   矿石币MIN   Minerals   123   0.00020 本期 0.00000   未登录   
38   字节币BCN   Bytecoin   119   0.00025 本期 0.00000   未登录   
39   极特币DGB   DigiByte   118   0.00010 本期 0.00000   未登录   
40   大奖币JPC   JackpotCoin   117   0.00100 本期 0.00000   未登录   
41   火炉币BURN   BurnerCoin   115   0.00010 本期 0.00000   未登录   

[sucksyd]

he definitely has none

[andr0x]

I'm glad to write here again : my last post  was 6 months: https://bitcointa.lk/threads/digibyte-dgb-digishield-v2-0-now-live-mandatory-update.233281/page-373   

Well in this time, I'm posting a guide to compile Digibyte on FreeBSD 10 x86-64, using stock C/C++ compiler (Clang) :


How to build Digibyte on FreeBSD 10 x86 64


1) cd /usr/src/ports/devel/boost-all/ && make install clean

2) cd /usr/src/ports/databases/db48/ && make install clean

3) cd /usr/src/ports/devel/protobuf/ && make install clean

4) Download Digibyte from GitHub

   4.1) git clone https://github.com/digibyte/DigiByteProject.git

5) Apply patches :

5.1) cd DigibyteProject/src
5.2) patch scrypt-sse2.cpp < patch_scrypt-sse2.cpp.diff
5.3) patch scrypt.cpp < patch_scrypt.cpp.diff
5.4) patch scrypt.h < patch_scrypt.h.diff
5.5) patch util.h < patch_util.h.diff

6) Compile Digibiyte :

6.1) cd ..
6.2) ./autogen.sh
6.3) ./configure --disable-tests
6.4) gmake -j [number of cpu cores]

7) Manual install binary:

7.1) cd src && cp -v digibyte* [ your location/directory ] 

Create a digibyte.conf file in the binary file location , for example:

8.1) nano /home/digibyte/.digibyte/digibyte.conf

add:

rpcallowip=*
rpcuser=yourusername
rpcpassword=yourpassword
server=1
daemon=1
txindex=1
debug=1
algo=scrypt [this option could be : sha256d, qubit, skein, scrypt or groestl]
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=74.208.230.160
addnode=69.164.206.169
addnode=192.99.215.234
addnode=54.204.36.33
addnode=192.99.41.108
addnode=199.83.128.91
addnode=199.83.132.91


9) run digibyted, wait for client sync

10) You can manage digibyte wallet with digibyte-cli for example

./digibyte-cli -rpcconnect=192.168.0.10 -rpcport=14022 -rpcuser=yourusername -rpcpassword=yourpassword [command]

or

./digibyte-cli -rpcconnect=192.168.0.10 -rpcport=14022 -rpcuser=yourusername -rpcpassword=yourpassword help


11) and Enjoy ...


Patch files:

patch_scrypt-sse2.cpp.diff  : http://www.heypasteit.com/clip/1JK6
patch_scrypt.cpp.diff :  http://www.heypasteit.com/clip/1JK7
patch_scrypt.h.diff :  http://www.heypasteit.com/clip/1JK8
patch_util.h.diff :  http://www.heypasteit.com/clip/1JK9

[restless]

Is there some kind of calculator to compare profit of different algos?

[fredeq]

Is there any explorer / other kind of api with stats for every algo? Myr has this on their site, allows me to quickly get difficulty/blockcount for every algo

[rossr1]

is there a link to the dgb top wallets list someone can point me too, cheers