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

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.

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

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.

Yes, this can be done without a hardfork. At the current rate DigiByte will need to hit a $60 million USD market cap before the current fee is worth $0.01. At a $600 million USD market cap that would be $0.10. We surely would lower the fees by then.

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.

 

Release Notes:
* Changes occur @ block 1,430,000
* 15 Second Blocks
* Scalability to match Visa TPS by 2021 & continued scaling through 2035 (See scalability projections here)
* Minimum TX & Relay Fee set to 1 DGB to prevent attacks
* MultiAlgo Difficulty adjustment code changed to make 51% attack much, much harder (See commit explanation)
* Transaction propagation changes based upon Microsoft research (Microsoft Research)
* Reward adjusted to accommodate faster blocks, still stays the same (21 billion DGB in 21 years)
* OP_RETURN data increased to 80 bytes to allow embedding more data (like document hashes)
* Safe mode warning error fixed
* Check point added
* Private key compatibility issue fixed ( addresses from the DGB paper wallet address generator now work properly)

After much testing we are ready to get 4.0.0 into the wild! Please help spread the word and help get all mining pools & exchanges to update. As soon as an exchange or pool has updated please notify us and we will update our main list!

 

Release Notes:
* Changes occur @ block 1,430,000
* 15 Second Blocks
* Scalability to match Visa TPS by 2021 & continued scaling through 2035 (See scalability projections here)
* Minimum TX & Relay Fee set to 1 DGB to prevent attacks
* MultiAlgo Difficulty adjustment code changed to make 51% attack much, much harder (See commit explanation)
* Transaction propagation changes based upon Microsoft research (Microsoft Research)
* Reward adjusted to accommodate faster blocks, still stays the same (21 billion DGB in 21 years)
* OP_RETURN data increased to 80 bytes to allow embedding more data (like document hashes)
* Safe mode warning error fixed
* Check point added
* Private key compatibility issue fixed ( addresses from the DGB paper wallet address generator now work properly)

After much testing we are ready to get 4.0.0 into the wild! Please help spread the word and help get all mining pools & exchanges to update. As soon as an exchange or pool has updated please notify us and we will update our main list!

A public buy order for future digis4commits will be fair. Publicly DigiByte funded projects will go a long ways. Because it releases more developers than us. Either way it is good to see you here a year later

Thanks for all the hash help!

We have now turned the pool and explorer off to begin testing the v 4.0.0 release wallet with the main DigiByte network.

DigiByte w/ DigiSpeed pushed through 25,130 tx's in about 9 minutes without a problem. How many can BTC handle in that amount of time?

Thanks! Flooding testnet with 50,000 + tx's as we speak: http://45.33.31.149/

Thanks for the help! Yes we need more skein and groestl hash. We just reset the blockchain with a new test.

For those that are interested we are sending 140 txs per second over the test net: http://45.33.31.149/blocks and the network is handling it beautifully with 15 second blocks.

DigiHash Test Pool
DigiExplorer Test Explorer
DigiByte Block Size Projection through 2035

Everyone, we are very close to rolling out the Hard Fork and could use your help with extra miners on the network for one final large test. We could use help specifically on Skein and Groestl but hash on all algos is welcome.

Behind the scenes we have been exploring some of the consequences of raising the block size to 8 MB right away. Through our tests, and there have been several we have decided that raising to 8 MB blocks opens the network to unnecessary attack vectors right away.

With this in mind we have decided on a "Disciplined & Planned" approach to scaling the DigiByte Blockchain through 2035. This can be seen in this spreadsheet here: DigiByte Block Size Projection through 2035

The idea is we stick at 1 MB blocks with 15 second blocks until 2017. Then the block size doubles to 2 mb and then doubles every year through 2035. This allows continued DigiByte growth as bandwidth, hardware and more naturally grows. For instance in the year 2025 it is predicted we will see 100 TB harddrives.100 TB Harddrives

The reward amount will stay the same. We have a lot of room to grow with out current setup, but we want to make sure we have no issues in the future. The safemode warning as well as an issues some users were having with private keys will be fixed in this release as well.

Everyone,

We have updated the DigiBit wallet to get it to properly sync as several people were having issues getting connections. Make sure to back up your wallet before installing.

Windows:

Linux:

For those that have been having issues with DigiBit please let us know that this helped you fix the issue.

Cheers,

We pushed out a new update to DigiByte Gaming that fixed all payout issues some people were having (growing pains as more users sign up). DGB Gaming is now running at 110%. We are now at 1,000 users. Help spread the word and lets get to 10,000 by Christmas!

Everyone, we have pushed an updated for the DigiByte Android wallet to the play store. This wallet has a more recent checkpoint and should sync very quickly. Some people were having issues with the wallet syncing. If for some reason you still have issues go into the wallet and clicks -> settings -> Reset Blockchain to reset the blockchain. This should discover any transactions that are not appearing. We are also upgrading the wallet to HD along with other improvements. Shooting for Q1 2016. Also we have someone working on the iOS wallet update. Stay tuned for that.

Thanks for signing up and supporting DigiByte!

Can you PM us your summoner name and email account you used to sign up so we can take a look?

Cheers,