Not at this time. Garena, the company providing League of Legends support does not have a public facing API yet. This is the case for most Asian countries.

Everything is progressing with DigiByte Gaming and we are adding several new features to the platform.  We are most definitely still paying out DigiBytes.  However, following several recent exploits we have had to significantly tighten the parameters of the payouts to prevent spam and significant abuse.

Upcoming Changes:

* Accounts are limited to 1 summoner account (no longer 5). (This along with the referral system was being significantly abused)
* Switch to the questing / leveling system
* Additional Games
* Gaming API
* Additional services

Yes, we are not going to add or support any gambling services through DigiByte Gaming.  Blockchain "cryptocurrency" technology is already in a gray enough area. But what people do with their DigiBytes is their own business.

Is your Steam account settings set to private? This has been the case with a few people. This prevents our system from pulling your stats.

Let us clear something up here to put this unnecessary flaming war to rest.  We have never claimed to be the inventors of multi-algo and we have repeatedly given credit to Myriadcoin for doing so.  Both in writing and in public presentations.  However, we were the first coin to go from a single mining algo to fork to a multi-algo setup which had its own unique challenges. If anything we certainly have helped bring more attention to the benefits multi-algo offers.

We feel there is a mutual synergy between DigiByte and Myriadcoin moving forward and we would like to collaborate to assist each other in the future.  We do not view the crypto world as a "winner" take all situation.  There need's to be multiple blockchains not only for security but also for development & experimentation.  This is what makes the blockchain world so exciting.

The DigiByte protocol is the heart of the DigiByte ecosystem. The DGB protocol will continue to evolve as time goes on. The primary means of improvements will be to take tested, useful and innovative additions found in multiple other coins and implement some of those changes into DGB. This will allow DigiByte to maintain a competitive advantage over the majority of other block chains without wasting time on implementing new changes that have never been proven or tested that could and often do lead to significant security vulnerabilities.  At the end of the day we can not afford even a single major security breach in the network (think DAO). We will give credit where credit is do in this process to other innovators for taking the initial risk. By taking ideas from multiple sources DigiByte itself will remain unique with many competitive advantages. At this point DigiByte is far enough along, with 2.5 years of invested resources (both time and money by people all over the world) that we can not afford to be reckless with unproven "additions" to the core protocol.

We would love to spend 100% of our resources on R&D but the reality is this is just not feasible.  By far the biggest challenge right now for every coin is user adoption and real-world utility.  You can have the most technologically advanced blockchain in the world with the most cutting-edge advancements.  But if no one knows about it what good is it?  Sure you will get a short term pump & dump in a tiny speculators market. But without making a coordinated, strategic move to gain news users outside of the "speculators" community its just not a viable long term solution.  

The DigiByte Protocol currently consists of 5 decentralized mining algorithms including; Sha256, Qubit, Skein, Groestl and Scrypt. The core DigiByte protocol is considered to be UTXO based and is different than the emerging “Virtual Machine” approach now pioneered by Ethereum. UTXO by companies such as Microsoft and IBM is considered to be the most secure and well-tested approach to blockchain development. The block timing is currently set at 15 seconds (40x faster than BTC) with 1 MB blocks.  Every 2 years the size of the blocks will double.  At this current rate we will match VISA with network transaction capacity by 2021. DigiByte currently implements the “DigiShield” and “MultiShield” difficulty adjustment code which has been proven to be highly reliable and has since been implemented into multiple other alt coins. DigiByte currently boasts over 8,000 nodes and in terms of absolute decentralization is the most secure blockchain on the planet. However without continued improvements for the remaining parts of 2016 and in to 2017 this edge will be lost.

Future Protocol Additions: Sync of DigiByte Core Protocol to BTC 0.12 core code.
1.   Libsecp256k1 Switch – This allows for a dramatic increase in the speed of validating ECDSA (Elliptic Curve Digital Signature Algorithm) public/private keys.  This will only enhance the speed of DigiByte transactions while reducing bandwidth and network latency.

2.   Headers 1st Sync – One issue DigiByte is currently facing is our blockchain is almost at a height of 3 million blocks. Bitcoin is still at 300K.  By allowing headers 1st sync our simplified wallets (Android, iOS) will be able to sync with the network much quicker. As well as regular nodes.  This code has already been tested and implemented to BTC.

3.   Block Pruning – It is not necessary to retain all information sent and received in a block for everyone on the network.  By pruning some previous block data we can help DigiByte scale without overloading users hard drives.

4.   CheckLockTimeVerify  - This op function allows sending a transaction that cannot be re-spent until a certain point in the future. This unlocks the potentially for advanced smart contract applications to be built upon the DigiByte blockchain as well as advanced security authentication procedures with platforms such as Digi-ID.

5.   Other Adjustments – Several other slight improvements to the protocol can be found in the 0.12 core sync.  It is important however to note several conflicts may potentially arise with some of our current custom implementations in our UTXO protocol such as MultiAlgo, DigiShield, block timing etc that still need to be worked through and tested.  This should not require a hard fork though.

6.      Addition of Segregated Witness Code – “SegWit” for short essentially allows for nodes on a network to be a witness to a transaction without having the ability to alter a transaction.  Hence the segregated nature.  This allows for the establishment of what is know as “Micro Payment Channels.” This is better compared to the way the Internet itself works with the DNS system.  By implementing the SegWit code into DigiByte we are setting the foundation and ability for the “Lightning Network” to be implemented. This means potentially hundreds of thousands of transactions per second worldwide for DigiByte. We have the ability to pull this off before Bitcoin if we can get the right resources in time.

7.       Algorithm Swap – In the past 16 months since DigiByte’s switch to multi-algorithm proof of work many new cryptocurrency mining algorithms have been created to help decentralize and set new coins apart. As DigiByte grows we will need to swap one algo out to send a message to ASIC manufacturers etc. that DigiByte will remain decentralized.

8.   Addition of Colored Coins Layer – This is a well establish layer that can be implemented on top of DigiByte to create a virtually unlimited amount of “Smart Contracts.” “The Blockchain of Things” brought the most impressive potential use case for adding the colored coins layer on top of DigiByte. By leveraging the headers of a transaction itself it is possible through an additional API layer to use DigiByte transactions not as we think of them today but more as a communications network that can contribute groundbreaking improvements to industries across the board in a decentralized manner all the while boosting DigiByte's real world utility around the globe.
 

We will be rolling out a more advanced leveling, questing and XP system here in the near future.  We also will be adding additional games and services to DigiByte Gaming.  We are also in the process of developing an API with some exciting functionality for DigiByte Gaming.

To give everyone a quick summary of what we are currently working toward:

DigiByte Gaming
- Questing System
- Leveling System
- Additional Games
- API

DiguSign
- Digi-ID
- Secure Document Handling
- Human Readable Document Handling

DigiByte Core Protocol
- Update to 0.12 Core Code base
- Addition of Segregated Witness
- Experimenting with colored coins adaptation and open assets for smart contracts (timelockverify)

Marketing Efforts
- Getting on a Chinese Exchange
- Strategic Partnerships Similar to the Microsoft One

DigiByte Wallets
- Gaming Wallet Upgrades
- Android Wallet Upgrades
- iOS Wallet Upgrades
- DigiByte Gaming iOS wallet release

DigiHash (All funds currently going to payouts to DigiByte Gaming, so mine here if you want to support adoption of DigiByte through Gaming)
- Upgrades

If anyone would like to help with the core upgrades please PM us.  We want this to be an open source effort. We have a lot of work left to do and will continue to be working hard each and every day on several projects.  With our Microsoft Azure partnership we have migrated several servers and core infrastructure over that has delayed other development for a couple weeks.

Thank you everyone for your continued support and make sure to join the telegram chat! (If someone could post an updated link to the chat following this it would be appreciated). We will keep posting updates as new developments and events occur.

There is no plan to wait until "after the halving."  We are working on several things at the moment but do not want to fuel any unnecessary pump & dump until we have solid news to share with everyone.

Please note that Bitebi was removed from the website. When transferring over from a back up to new Azure servers this was inadvertently turned on. We have several upgrades to the site planned.

Insight error should be fixed Are you on Android?

You can try this: https://github.com/bitpay/copay-recovery

Although we have never tried, but in theory it should work. We will look into forking this.

This was shared long ago on Twitter. Same agreement used for Azure BaaS.

First thank you for your concern and for supporting DigiByte. Now let's answer your question.

1) You cannot create a single 998,000 KB TX for free and expect any node to relay it. Every DGB client out there has this code in it: https://github.com/digibyte/digibyte/blob/master/src/main.h#L74

In case you are wondering that is 100 KB or 0.1 MB. No way you could actually create a TX that large and get it relayed.

Bloating the network with multiple transactions gets very expensive very fast (as will be demonstrated below). 

2) Each algo has a block timing of 1 min 15 seconds. Microsoft research showed on the BTC network it takes an average of 6.5 seconds for 50% of nodes to receive a new block. 95% in 40 seconds with a mean of 12 seconds. So our 1 min 15 second individual algo block time is well within this time frame.

http://www.tik.ee.ethz.ch/file/49318d3f56c1d525aabf7fda78b23fc0/P2P2013_041.pdf

In order to 51% attack DGB and fork the chain you would need to take over 93% of SHA256 and 51% of the other 4 algos at the same time. (virtually impossible) or else the difficulty adjustment (Multi-Shield) will easily prevent it.

3) With future modifications to DigiByte core things will get even faster as far as block validations are concerned (secp256k1)

Finally here is a screen shot from the live DigiByte network test after DigiSpeed (we did many similar tests internally on a test network before releasing the hard fork).

It is very difficult and expensive to send this many TX's in such a short amount of time. We pushed through almost 10,000 TX's in just over a minute and the network handled it just fine. In fact, the main worldwide DigiByte network performed better than our internal test network.

Check these blocks for yourself on DigiExplorer: http://digiexplorer.info/block/e5ff5243c291d088e286bbe5ea449100487c6346667fcfc84f89d85971074880



Now compare that to this recent snap shot of BTC blockchain with full blocks. It took over an hour just to process 5,000 TX's.

So DGB easily hits 10,000 TX's in 1 min.  BTC takes over an hour for 5,000 TX's. 

The proof is in the Blockchain.

Quick update! After officially partnering with Microsoft (Biz Spark +) we have received $120K USD in free hosting over the next 12 months on Azure. We are migrating all DigiByte servers to more improved hardware! This includes, DigiByte Gaming, DigiHash, DigiExplorer, Wallet services, Seed nodes and more! Stay tuned as we progress on these services and others.

And yes core protocol upgrades are underway!

Google recently updated Chrome and that is what is causing this issue. If you update your Chrome browser to the latest version the issue will go away. Google should force this auto update any day now. In the mean time you can download it here: https://www.google.com/chrome/browser/beta.html  Thank you for using DigiByte Gaming and let us know if you have any more questions!

We have put this project on hold for the time being. If anyone would like to help contribute please let us know.

We would love to get some updated mining feedback from people. What is working and what is not. As mentioned by Jumbley DigiByte has 5 separate mining algorithms.  Each other counts fo 20% of new blocks mined. Sha256 and Script are mined by Asics.

We would like to get feedback as to the success people are having on Skein, Groestle and Qubit.

Last week was a great week for DigiByte! We have met with a lot of major institutions. This process is a slow one as a lot of talking to the involves educating them.  The gist is we are positioning the benefits of DigByte as a public chain to them. Everyone wants a private centralised system, but the reality is only a public decentralised chain provides the security that "blockchain" has become synonymous for.

I would like to invite everyone to post any questions they may have here and I will answer them over the next few days. Thanks again everyone for being such an awesome community!  DigiByte on!

-  Jared

Also we would like to announce DigiByteTip is going to be merged into and under the DigiByte Gaming platform. Please withdraw your DigiBytes from the tipbot.

This is being done to consolidate resources and dramatically improve the DigiByte tipping user experience.

We aim to take the service offline by June 11th, please let us know if you have any questions or users. 

Everyone,

I wanted to give you all a quick update! I just got back to Hong Kong and will be getting everything reorganized with the team here. The last three months on the road have been great for DigiByte! Without a doubt the market is changing and "blockchain" is going mainstream. Everyone seems to want to be a part of this "blockchain" thing but most do not know how to go about it.

We have several ongoing discussions with many influential groups across the globe. When the time is right and we have something substantial to announce we will.

In the meantime we will be focusing on several protocol enhancements such as bringing our code base on par with 0.12 and more. Stay tuned this week for more details and our first newsletter.

While price does matter, it is not our primary focus. Our primary focus is on developing real world DigiByte use cases that can rapidly enhance worldwide adoption for security, transparency and financial and contractual transactions.

As stated many, many times we are in this for the long haul. We have our heads down, and we are working hard.

Cheers,

Jared

Sorry  to hear about your pc. Please log in to your DigiByteGaming.com account, go to settings and upload your new DigiByte address. Make sure to back up your seed phrase. Thanks for using DigiByte Gaming!

We want to let everyone know Jared will be presenting at Finovate in San Jose next week. Bigger than NYC event. Demonstrating, DiguSign potential as well as other innovations: http://spring2016.finovate.com/

For those interested in the verification process for Satoshi, this is how easy it is: http://www.digibyte.co/content/jared-tate-cryptographically-proves-he-digibyte-creator

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

Quick update from here in New Orleans CollisionConf: https://collisionconf.com/

This is by far the biggest event we have ever attended with over 10,000+ attendees. The event lasts for two more days and we are making the most of it. We have introduced many new people to DigiByte yesterday and are doing the same today. If anyone is here at the event or knows someone that is and would like to meet up please let us know.  Stay tuned for more updates!