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

[DigiByte]

Anyone else having problems syncing. I am constantly getting stuck after 4 blocks:

"version" : 4000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 4,
"timeoffset" : 0,
"connections" : 8,

Been like that overnight, I deleted everything and started again and it is stuck again.

Alternately anyone have some good current nodes?

Thanks

This is the first we have heard of this issue. All the server upgrades we made (20 some wallets) worked without a problem. If you have continued issues let us know.

[DigiByte]

While we understand everyones frustration with the current sell off we look at this as a temporary set back. If we were able to control the price, DigiByte would not be an open source, decentralized worldwide digital currency. We would be a central bank.

There are undoubtedly multiple groups that go from alt coin to alt coin buying the "rumor" and "selling" the news when it comes to wallet upgrades and hard forks. We have watched this cycle rinse and repeat for several years now with a multitude of coins (most of which are dead now). Just look at what happened with the recent Ethereum & Bitshares releases. The good news is there is a consolidation occurring in the market place with people turning to older coins with a proven track record.

We estimate the active alt coin trading community to be roughly 20,000 - 30,000 people at most (Poloneix has roughly 42,000 users signed up, Cryptsy claims 270K signups but they are the oldest exchange). Bitcoin itself only has maybe a few hundred thousand active participants with a max of 2-3 million wallets created since 2009. This is a drop in the bucket compared to a current world population of 7+ billion people. If you do the math on that 7,000,000,000 / 3,000,000 that gives you 0.00042% of the worlds population that has ever participated in a digital currency. There is a tremendous growth potential here over the next few years.

When you look at main stream financial research such as this Bank of America Report you clearly begin to see all research points to the "millennial" consumer (born between 1980 - 2000) that will adopt digital currency in mass first. This trend has been pointed out in reports issued by Wells Fargo, Bank of England and many more.

Right now, we have only been actively marketing DigiByte Gaming for less than a week since leaving the testing phase. As of today we have 1200 active users on the platform. Most of these people are not only brand new to DigiByte, but to the whole concept of digital cryptocurrency. We are shooting for 100,000 users by March 1st of 2016.  We are targeting a game with 500 million worldwide players... and they are all millennials. What better way to reach out to real world consumers to encourage mass adoption. But we look at this as only the first step. Once we have a thriving, healthy user base of a few million users we can begin leveraging and working our way into traditional financial services. But that is no where near as exciting as the potential we have to begin disrupting industries such as legal services, security services and more by securing other data in the DigiByte blockchain (distributed hash tables, not full data files).

There has been some concern the DigiByte blockchain will become "bloated" right away with DigiSpeed. This is far from the truth. We have taken multiple steps to ensure this does not happen. Given the current size of our blockchain at 2 GB and the average new video game now being 15-20 gb we are well within a reasonable size even with a doubling or tripling.

We have development on all platforms planned throughout 2016. By mid 2016 we aim to have made several improvements to the core wallet to encourage user adoption and network security and to make it easier to use. These changes include block pruning, headers first syncing, a massive user interface overhaul and additional in wallet services.

As stated many, many times we are here for the long haul. We are dedicated to the vision of DigiByte and truly inspired by the opportunity and possibilities we have before us.

Cheers,

Jared

[ethought]

Anyone else having problems syncing. I am constantly getting stuck after 4 blocks:

"version" : 4000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 4,
"timeoffset" : 0,
"connections" : 8,

Been like that overnight, I deleted everything and started again and it is stuck again.

Alternately anyone have some good current nodes?

Thanks

This is the first we have heard of this issue. All the server upgrades we made (20 some wallets) worked without a problem. If you have continued issues let us know.

Issues continue.

Can you please provide a list of up to date nodes?

[DigiByte]

Issues continue.

Can you please provide a list of up to date nodes?

rpcuser=yourusername
rpcpassword=yourpassword
algo=scrypt
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=69.164.198.161
addnode=66.228.56.115
addnode=104.200.17.141
addnode=45.79.149.192
addnode=104.237.137.28
addnode=45.33.7.79
addnode=45.79.10.59

If anyone is running a dedicated node please quote this post with an IP if you would like to help seed the network in instances like this and be added to the OP and website.

[ethought]

Issues continue.

Can you please provide a list of up to date nodes?

rpcuser=yourusername
rpcpassword=yourpassword
algo=scrypt
rpcport=14022
port=12024
addnode=216.250.125.121
addnode=69.164.198.161
addnode=66.228.56.115
addnode=104.200.17.141
addnode=45.79.149.192
addnode=104.237.137.28
addnode=45.33.7.79
addnode=45.79.10.59

If anyone is running a dedicated node please quote this post with an IP if you would like to help seed the network in instances like this and be added to the OP and website.

Seems like all connections to nodes are getting refused.

Code:

$tail -n 200 debug.log 
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 482, prev=362a475393c6b3f3c7fff79f1e1b12a14d7be72db9be999d4c2811eeb0b4f785
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 483, prev=13004255db26881f4f86b0c72d41707871bf1163e939b5ab2e62b063ae13394c
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 484, prev=cafc82996eb4d40137a2c985578deee1f49efb748c442c51733b63466d8eb536
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 485, prev=273174ede619f24540f4b4508461f0a2948b95fd07a811f70e08906cc82140d7
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 486, prev=2d938089824f247d96b7da37e62d5e7bc9c9b5149dfcf7741cedbc2e2fa33c95
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 487, prev=f2fb6925ab495c0c260432ee229d18d933d9576ee44812a6a2e87e1bc95b4026
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 488, prev=42eeeb35c02962ed2d5a777c7bbbdd2f515ff2affe225759278dda4f37daaa56
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 489, prev=e1ba2e7300bdb1ead27e7bd269c80e3fce3068733af3639e845a13c1a3eac80f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 490, prev=76faf8053c36e1fbdf74218163d26f2fa42a50ce8da213849035c2fa343f44ce
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 491, prev=e002dc5c8646ba40de34602fdb01e3d5905cf080025cf5909b26e923ff464276
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 492, prev=0a461b59a20c100ae2f7844639881ed9aed0c44d00744438e0ffbd6007cef2bf
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 493, prev=b333dc30e63ea05b26e325bb46797320ea637a3cb3cdc37c423da2de9270de1f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 494, prev=737d352a7aaf52bb5f07b325d0faeda325e5212ee93a088df9351094f2da583f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 495, prev=f30de0dfbf9d8bf392cf899c36c4af12720af38218f1fcfa5257a79e2091bd3b
2015-11-27 06:16:28 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 496, prev=d2f8cbcf445d80cc7467f3fecbe3d412957c59a30fd87a810d4a208b4154e573
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 497, prev=8d3c2c5c08b50cace1c83e9410965804897df344004a4da8eb6331d7223397e3
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 498, prev=034955564faa6d1833d6d8098aa9a4d90677f6a19d5c6fb4d6c0343de59699f6
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 499, prev=93fa794939985ff63a798fe19d50beed8027ed3ae511dbc860d4d2ad1845365e
2015-11-27 06:16:29 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:29 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:29 connect() to 45.79.10.59:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:30 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:31 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:32 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:34 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:34 ProcessBlock: ORPHAN BLOCK 500, prev=c1e2073a2a133f85d20dd1c41b45317df85a2d183699f25766912860b68d9b2e
2015-11-27 06:16:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
...
2015-11-27 06:18:35 connect() to 69.164.198.161:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 66.228.56.115:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 104.200.17.141:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 45.79.149.192:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)

Any idea why this might be happening? I synced with no problems a few days ago on the last Digibyte version.

[DigiByte]

Code:

[quote author=ethought link=topic=408268.msg13081439#msg13081439 date=1448605468]

2015-11-27 06:18:35 connect() to 69.164.198.161:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 66.228.56.115:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 104.200.17.141:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 45.79.149.192:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)

Any idea why this might be happening? I synced with no problems a few days ago on the last Digibyte version.
[/quote]

It appears you are attempting to connect on port 12025. It should be 12024. 12025 is the testing port.

Did you compile the wallet yourself? Which branch did you use? The tesnet currently has 4 blocks on it I believe

[ethought]

Code:

[quote author=ethought link=topic=408268.msg13081439#msg13081439 date=1448605468]

2015-11-27 06:18:35 connect() to 69.164.198.161:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 66.228.56.115:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 104.200.17.141:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 45.79.149.192:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)

Any idea why this might be happening? I synced with no problems a few days ago on the last Digibyte version.
[/quote]

It appears you are attempting to connect on port 12025. It should be 12024. 12025 is the testing port.

Did you compile the wallet yourself? Which branch did you use? The tesnet currently has 4 blocks on it I believe

I was using the digispeed branch, looking at the commits for digispeed-release it is clear I should be using the digispeed-release branch. Might be worth making that clear on the Github page.

[Bluestreet]

* Transaction propagation changes based upon Microsoft research

Can the development team elaborate more on this point?

Not sure if I got a response to my question but what exactly does the above point mean? Is this something bitcoin does not have yet?

This is the non hyped version of the changes.

* Changes occur @ block 143,000
* 15 Second Blocks
* MultiAlgo Difficulty adjustment code changed to make 51% attack much, much harder (See commit explanation) Thanks to MentalCollatz who did the change for myraidcoin first.

Big thanks to MentalCollatz for proposing the difficulty changes!

As for the transaction propagation changes, think of it like this. Before the hard fork a client will only relay a block onto its peers once it has been fully validated. This was a huge bottleneck in network propagation that Microsofts researchers identified. The new changes allow blocks to be received and relayed simultaneously. However, each client still conducts a full, proper set of checks for each block and TX without any decreased security risk. If a block is orphaned or found to be invalid a client will relay that to its peers.

Thanks for the response Jared.

[Sumo]

While we understand everyones frustration with the current sell off we look at this as a temporary set back. If we were able to control the price, DigiByte would not be an open source, decentralized worldwide digital currency. We would be a central bank.

There are undoubtedly multiple groups that go from alt coin to alt coin buying the "rumor" and "selling" the news when it comes to wallet upgrades and hard forks. We have watched this cycle rinse and repeat for several years now with a multitude of coins (most of which are dead now). Just look at what happened with the recent Ethereum & Bitshares releases. The good news is there is a consolidation occurring in the market place with people turning to older coins with a proven track record.

We estimate the active alt coin trading community to be roughly 20,000 - 30,000 people at most (Poloneix has roughly 42,000 users signed up, Cryptsy claims 270K signups but they are the oldest exchange). Bitcoin itself only has maybe a few hundred thousand active participants with a max of 2-3 million wallets created since 2009. This is a drop in the bucket compared to a current world population of 7+ billion people. If you do the math on that 7,000,000,000 / 3,000,000 that gives you 0.00042% of the worlds population that has ever participated in a digital currency. There is a tremendous growth potential here over the next few years.

When you look at main stream financial research such as this Bank of America Report you clearly begin to see all research points to the "millennial" consumer (born between 1980 - 2000) that will adopt digital currency in mass first. This trend has been pointed out in reports issued by Wells Fargo, Bank of England and many more.

Right now, we have only been actively marketing DigiByte Gaming for less than a week since leaving the testing phase. As of today we have 1200 active users on the platform. Most of these people are not only brand new to DigiByte, but to the whole concept of digital cryptocurrency. We are shooting for 100,000 users by March 1st of 2016.  We are targeting a game with 500 million worldwide players... and they are all millennials. What better way to reach out to real world consumers to encourage mass adoption. But we look at this as only the first step. Once we have a thriving, healthy user base of a few million users we can begin leveraging and working our way into traditional financial services. But that is no where near as exciting as the potential we have to begin disrupting industries such as legal services, security services and more by securing other data in the DigiByte blockchain (distributed hash tables, not full data files).

There has been some concern the DigiByte blockchain will become "bloated" right away with DigiSpeed. This is far from the truth. We have taken multiple steps to ensure this does not happen. Given the current size of our blockchain at 2 GB and the average new video game now being 15-20 gb we are well within a reasonable size even with a doubling or tripling.

We have development on all platforms planned throughout 2016. By mid 2016 we aim to have made several improvements to the core wallet to encourage user adoption and network security and to make it easier to use. These changes include block pruning, headers first syncing, a massive user interface overhaul and additional in wallet services.

As stated many, many times we are here for the long haul. We are dedicated to the vision of DigiByte and truly inspired by the opportunity and possibilities we have before us.

Cheers,

Jared

Get into some game conferences. Make a presence at e3!!

[MaxDZ8]

Get into some game conferences. Make a presence at e3!!

Side note: Ripple labs was present at cppcon 2015 with very interesting and generic presentations.

[Telenong]

many people sell dgb to get btc, btc uptrend this week
what dgb community commit about this situation

[SSG69]

Thats one factor. The other was that, after the pump the price was simply too high for a coin that produces a few dozen million coins a month. This is not yet the bottom. We can be happy if it stops at 25-30.

[ontopicplease]

I have been reading this thread for a couple of hours now, but I couldn't find any info about the source from which the LOL-players are paid their DGB winnings.

[OZmaster]

quick question, why are the dgbgaming payouts beeing ocasionaly rejected since yesterday?

[24hralttrade]

I have been reading this thread for a couple of hours now, but I couldn't find any info about the source from which the LOL-players are paid their DGB winnings.

Here i am!
www.Digibytegaming.com - www.bluejeansonline.nl

30% discount today on all products @ blackfriday
https://twitter.com/Bluejeansdorp/status/670204640890372096

[ontopicplease]

I have been reading this thread for a couple of hours now, but I couldn't find any info about the source from which the LOL-players are paid their DGB winnings.

Here i am!
www.Digibytegaming.com - www.bluejeansonline.nl

30% discount today on all products @ blackfriday
https://twitter.com/Bluejeansdorp/status/670204640890372096

Thanks for the quick reaction, I really love this project. I see the talking about having about 1M LOL-players collecting DGB. I mean how can someone provide/give away so many coins. What's the business deal behind it?

[24hralttrade]

I have been reading this thread for a couple of hours now, but I couldn't find any info about the source from which the LOL-players are paid their DGB winnings.

Here i am!
www.Digibytegaming.com - www.bluejeansonline.nl

30% discount today on all products @ blackfriday
https://twitter.com/Bluejeansdorp/status/670204640890372096

Thanks for the quick reaction, I really love this project. I see the talking about having about 1M LOL-players collecting DGB. I mean how can someone provide/give away so many coins. What's the business deal behind it?

Advertising:
Open the Gaming wallet and see,  you see my store/webshop...
Tip on twitter and you see a link to my store/webshop
Open digibytegaming.com and you see a big picture and link to my store/webshop , Go on and on and on

Now imagine 100k players and a huge company advertising.... They need to buy the dgb somewhere right ? And to pay 100k players for a month,,,, You gonna need "some" Digibytes

[hardcoreprime]

Any reason why Digibyte is not listed at https://www.coinpayments.net/supported-coins

[24hralttrade]

Any reason why Digibyte is not listed at https://www.coinpayments.net/supported-coins

I believe they ask allot of money to ad Digibyte and we need minimal $5k transactions per month.

https://www.coinpayments.net/addcoin

[iikun]

Any reason why Digibyte is not listed at https://www.coinpayments.net/supported-coins

DigiByte is listed on their "requested coins" page. It would appear they only add coins which they get "incentivized" to add (ie paid to)