So, is there a way of unlocking the "secret area"? (other than referring a smurf account and play 3 matches)
I've been referring people to DGB for weeks and none of them really find it appealing enough to grant me access at all.
Is that area really worth it?
Edit: the "invitation by mail" make people think that it's somekind of scam/phishing/mailing list gathering scheme. Really hard to apply when one is trying to introduce people into the Cryptocurrencies community.
Thank you for the feedback. This is very valuable to us. Thanks for referring people! This is a work in progress, we are working around the clock. |
|
|
|
Thanks for posting links! We should get a running list going somewhere. Anyone know of an easy and quick way to do this so anyone can submit content? Cheers, Jared |
|
|
|
@DigiByte,
If i understand correctly, you are going to pay per kill,hour etc, in counterstrike. What do you think about "pay per Match". Let me explain in short.
Two CS:Go teams(clans), will arrange match for reward. Lets say they make the deal for 1mil DGB for winer. This 1mil DGB will be deposited to Escrow address(or any other technological solution which will work). After the match, reward will be automatically send to winner team wallet address. You can make the leaderboard of earnings/winnings of clans whatever, there are endless possibilities with CS, You can make even DigiByte League. This will attract a lot of CounterStrike clans, which are backbone of whole CS scene. More famous clan you will attract more new people will be interested in DGB Gaming. Where are money, there are professional CS clans... And this clans have millions of followers.
Maybe You Can think about this.
Regards,
Nyo
Nyo, Thank you very much for explaining this to us. As we have only played the game a few times this kind of insight and suggestion is very helpful! |
|
|
|
Take the DigiByte Quiz
First Person to Answer all Questions Correctly Earns
50,000 DigiBytes! 1) What is a block? 2) What is a blockchain? 3) When was DigiByte launched? 3.1) What is a genesis block? 3.5) What was the news headline hashed into the DigiByte genesis block? 4) How fast are DigiByte block times? 5) How many mining algorithms does DigiByte have? 6) Name all the DigiByte mining algorithms: 7) How many DigiBytes will be generated total?  How long will DigiBytes be generated for? 9) How many DigiByte transactions can DGB currently handle? 10) How many transactions can DGB handle by 2021? 11) How many transactions can DGB handle by 2035? 12) How many hard forks has DigiByte intentionally experienced? 13) Name all of the DigiByte hard fork release titles: 14) What is the DigiByte monthly reductions rate for how many DigiBytes are generated each month? 15) How can documents be embedded in the DigiByte blockchain? 16) What is the command to reindex a DigiByte wallet on windows? 17) What is a DigiByte node? 18) What is the command to reindex a DigiByte wallet on Mac OSX? 18.5) What is digibyted? 19) What is an RPC command? 20) What is digibyte.conf? 21) What is wallet.dat? 22) Where is wallet.dat stored on windows? 23) Where is wallet.dat stored on a mac? 24) What is the most useful RPC command? 25) What is a difficulty adjustment? 26) What is OP_RETURN? 27) What is the difference between a full node an an SPV wallet? 28) What is a deterministic wallet? 29) Explain the difference between a public and private blockchain 30) Explain the difference between a permissioned and permissionless blockchain 31) Name three exchanges where people can buy DigiBytes: 32) Name three places people can spend DigiBytes: 33) What is the current block reward? |
|
|
|
DigiByte Official Telegram Chat Group We have set up an official public telegram chat group for everyone to join and talk with other people from the DigiByte community. Most senior community members are present and so is Jared so join if you want to have a chat with us or want to raise issues. You can also chat with DigiBot to get your up to date DigiStats and market data. Is the link still working for everyone? |
|
|
|
DigiByte Official Telegram Chat Group We have set up an official public telegram chat group for everyone to join and talk with other people from the DigiByte community. Most senior community members are present and so is Jared so join if you want to have a chat with us or want to raise issues. You can also chat with DigiBot to get your up to date DigiStats and market data. Thank you for setting this up! Telegram is a very effective way for all of us to communicate very quickly. We encourage those who are interested to join the chat. |
|
|
|
For example, and I've mentioned it before on this thread: do you think it's acceptable to shrug off the fact that DiguSign returns errors when trying to search for signed embedded documents? That was first reported at the end of January. I've reported several other issues as well, just not here on this thread, not yet anyway, since I'm really curious to see if there is anyone else actually using the products and coming across these issues.
You consider this drama? The drama is the situation where 1/2 functional products are developed and nobody cares, and then everyone gets in a huff when someone brings up real issues that should be fixed in priorty fashion.
I think you've got the world turned upside down, but hey, that's just my opinion and you're entitled to continue thinking as you please.
We all make our own choices, and we're also responsible for our decisions.
As for me, I'll continue to bring serious thinking to this thread, even if it means pointing out flaws, since they can never be fixed if not first seen and identified. Again, anyone who feels the need to clearly let the world know that they have no interest in improving shortcomings, by all means, be our guest, and when frivolity fails, keep moaning and groaning and letting the insults and attacks flow against those who want something better than half-baked.
Please note we are constantly reading the forum and taking input from people through PM's, tweets, emails etc as this is our best way of discovering issues. We have a new version of DiguSign thats been under development for some time addressing these issues and more. Thank you everyone for giving feedback on multiple platforms and helping us iron out some of these issues. |
|
|
|
I this is HUUUUGE, why is this not promoted?
Good question. Could a possible answer be the fear of success? Or just the need to keep accumulating DGB on the cheap? Or ...? Truth is, they're pretty much leaving it up to people's imaginations (not just with this - it happens all the time, witness the most recent example in South Africa), with the exception of a few dots that the well informed and studious can connect . . . Or because its not completed yet and there seems to be no way to earn any Digibytes from playing it yet?? I've just linked mine and my sons steam accounts, so we will see if there are any payouts Edit My son played CSGO for a few hours this morning and so far, no stats have updated on the digibyte gaming site. The payouts for CS GO have not been activated. We have been testing the CSGO steam login functionality and connectivity with their API. Stay tuned for an official release in the coming days. |
|
|
|
Thank you to everyone for your continued support and your passion for DigiByte. 2016 is on track to be a huge year for DigiByte. The timing just could not be better. Every major bank and company in the world is looking at blockchain tech, and they are looking outside of Bitcoin. We are going to put Digibyte in front of them. Our next event will be FinDev in New York City on March 29th. Between now and then expect more updates and news!
Cheers,
Jared
Thank you Jared for this neat update ! We are all behind you in your "SpreadDGB around the world quest". What a challenge this conference !! Looking forward to see you rocking the places again somewhere else in the world ! I will be talking about Digibyte in local events for Bitcoin in France! If any other french people want to contact me. You'll be very welcome. I can even tip french ambassadors if needed ! Please let everyone know when these local events occur so we can help promote them over social media. We would like to see as many DigiByte Ambassadors as we can across the world. Does anyone have any ideas for a unique, more formal "DigiByte Ambassador" program? This can be away to get more people involved and a more formal outreach. Perhaps we could use the list of events found on bitcoin.org and coindesk and get people to start attending local events. |
|
|
|
It is my pleasure to let everyone know the conference in South Africa went very well for DigiByte. The videos should be online soon. We will post links to them as soon as we get word they are posted. Many new people were introduced to DigiByte and we have made several new influential connections on the African continent. Overall the SA event was far more professional than many Bitcoin and blockchain events I have attended in the past. The organizers were professional and very warm and welcoming. Overall I was very impressed with how warm and welcoming the South African people were. There seemed to be an excitement in the air for the positive change this technology is bringing to Africa. The majority of the attendees were bankers, government officials and business tech professionals. It was nice to see such a vested interest in blockchain technology and the impact it can have on Africa. Africa is in a much better position to begin adopting DigiByte and blockchain technology than the rest of the world. More importantly there seems to be a hunger for change and a will to explore new ideas that you just don’t see in other western countries. In the US and Europe you have a lot of legacy infrastructure that companies have spent billions of dollars developing in the past twenty years that is now obsolete. Given such a hefty investment many companies with this tech "debt" are not easily swayed to move beyond their legacy infrastructure. Africa does not have this issue given its lack of infrastructure in many areas. They are well positioned to "leapfrog" the rest of the world with wide spread blockchain tech adoption. However there still are some technical issues for Africa to overcome before widely adopting blockchain technology. The main one being wide spread internet access. What was interesting to note is most people felt this would not be an issue for very long as Africa is rapidly getting continent wide mobile internet access. This highlights the importance of DigiByte developing and maintaining mobile SPV wallets, as most Africans will not be using desktop computers. The blockchain and DigiBye can help bring three things to Africa; Transparency & Security, Innovation and Standardization. The transparency of the blockchain/bitcoin is already making a big impact in Africa through companies such as BitPesa. For those not familiar with BitPesa I would highly encourage you to check out their story. The CEO Elizabeth is a fantastic speaker with more insight into Africa on a country-by-country basis than anyone I have heard speak on the matter. https://www.bitpesa.co/There are some fascinating and exciting projects underway to help bring this exciting technology to Africa by local people. The one I was most impressed with is known as the SatoshiCentre in in Botswana founded by Mrs. Alakanani Itireleng. I would encourage everyone to check them out and engage with them on Twitter: https://twitter.com/SatoshicentreBw They are encouraging the adoption of Blockchain tech and are working to teach kids and people to code in Africa on a very grass roots level. After speaking with Alakanani she is more than happy to help introduce people to DigiByte if we send her and the Centre some DGB ☺ Another very good speech was by the gentlemen behind BitFinance and how blockchain/bitcoin is being used in Zimbabwe. When the video comes out I would recommend people watch their presentation to get a sense for the true impact blockchain tech can bring to Africa. I was also able to check out my first "accelerator" lab put on by Barclays in Capetown. As we move DigiByte forward through 2016 and look to get DGB tech adopted by banks and other larger corporations it is becoming apparent there are "channels" to help speed this process up and make things happen quicker. Over the next several months DigiByte will be represented at several more events to help facilitate this. If anyone has any suggestions, ideas or contacts for these events please let us know. We would also like to encourage people to start representing DigiByte at local blockchain/bitcoin events throughout the world. We feel this is a very important step in growing DigiByte as DGB is much larger than anyone person or group. A prime example of the power this can have is if you look at Ethereum/ Factom and the conference networking they have done and are doing. So what did this event mean for DigiByte? First of all hundreds of new people across the African continent have been exposed to what we are working toward in a professional manner & environment and are looking closely at what we are doing. This includes major financial institutions (every major SA bank plus the SA Government) and many tech companies. This impact may not materialize right away but it will no doubt help us moving forward in the long run. It has come to my attention some people are concerned with the lack of communication. I want to let everyone know we will be addressing this and opening up more channels in the future. This Africa event was a bit hard as the internet in many places was very slow and limited. Combine that with a very busy schedule and the fact I was traveling alone in remote areas down here makes constant updates very tough. Its important to maximize the networking time while in a place like this as who knows when we will be back. Thank you to everyone for your continued support and your passion for DigiByte. 2016 is on track to be a huge year for DigiByte. The timing just could not be better. Every major bank and company in the world is looking at blockchain tech, and they are looking outside of Bitcoin. We are going to put Digibyte in front of them. Our next event will be FinDev in New York City on March 29th. Between now and then expect more updates and news! Cheers, Jared |
|
|
|
Is DigiByteTip withdrawal broken? I've got an "Awaiting transaction response" that's been sitting there since Feb. 17 . . .
This was reported for the first time on this thread on the 20th, but since there's been no response either public or private, I ask again.
Please check the logs for pending withdrawals awaiting transaction response.
TIA
Hmm i dont know HR and last month Jared and team are very busy preparing for the events next friday and end of the month All will be sorted out asap. I just tried to withdraw a lesser amount - I was trying to withdraw my entire balance without success - and it went through, so it looks like it's working okay as long as it's not the entire balance. Edit: looking at my balance, it looks like there was a 2 DGB fee that was charged, and that's most likely the reason the entire amount for withdrawal was being held up even though there was no message alerting to that fact. Thank you for bringing this to our attention. Will get the team on it. |
|
|
|
Removed it for the time being, until this is cleared up o0o0. As much as I like this idea, I would have trouble supporting it after everything that has happened to customers of cryptsy, if what you say is true!
Just saying check all the topics out... its a hot conversation piece.... bitebi9 was registered by project investors which is paul vernon. He's run a series of other ventures that fell on their ass... penny auction sites, think there was some adult entertainment in there too. Paul vernon was also conversing with josh garza and cryptsy was gifted a prime controller. Josh garza was using cryptsy as his dumping grounds of choice... paul knew all about it... xpy was added rather fast to the exchange on release. Paul's fingers are in a lot of out of date expired pies... He lied to customers for years about no hacks... shot down coinfires allegations when he knew some of their comments had merit and their head of investigations Horus is now in hiding (Horus btw owned the cryptsy.ca canada arm of it... site is now down). Its one big clusterfuck. With digibyte branching into gaming and other such ventures i don't recommend any advertising of things that can give negative publicity considering all the effort you guys put in. I don't have any digibyte anymore cleared out a while a go but i do like the coin still. I urge Jared or whoever is using the Digibyte forum account here to look into bitebi9 and paul vernon of cryptsy and modify the post as required so its not quoted and relinked.. i'll modify mine. Thank you for sharing your concerns with the community. While we do not know the exact situation for sure, we are approaching with caution. We have been told by the people running the exchange it was purchased from "another" exchange. We all know that exchange was Cryptsy. The question is does anyone from Cryptsy still run this exchange. |
|
|
|
The new website has been launched! http://digibyte.co/We are still working on adding more things in the next few days before the South African conference. Please let us know how we can improve things. More blog posts, details and events will be listed. If anyone would like to be listed on this page: http://digibyte.co/content/digibyte-contributors as a "DigiByte Ambassador" and would be willing to submit your first name, a photo and potentially your LinkedIn page we would love to have as many active people as possible on there to show the world we are growing and who is involved. |
|
|
|
My core wallet is stuck at block 1441636, I've reindexed it 3 times, anyone any ideas?
Have you tried deleting the chain and resyncing from the beginning? |
|
|
|
Okay, pretty much what I thought: those magic knights don't exist, and the level of understanding about the second most important aspect of DigiByte is, in general, close to zero.
Considering just how important it is to have a good understanding of this, would it be too much to ask for an explanation in layman's terms?
As a guide, not that you need it as you clearly answered both with your posting of the respective codes, but in order to help with the framing of that explanation for the average person, I'll remind of the framing of the last questions:
We know that before the most recent hardfork, global network hashrate (that is the combined total of the 5 algos) was key, and that all the algos diffs adjusted in response to changes in aggregate hashrate. The question is how much did that change? To what precise degree are the algos currently independent, and to what degree are they still inter-dependent?
Looks to me like the overall relationship is still very similar, in that all 5 algos have their difficulties to mine calculated from the same base input, but, not being an expert, I don't want to misrepresent the facts and prefer to hear your, expert, explanation for the masses.
More than anything because I could be wrong. As I said, I'm not an expert, and in this matter I consider myself to be a member of the masses.
Very much appreciated!
A great place to begin answering this question is with MentalCollatz's original post on the GitHub repo. And also many, many thanks to MentalCollatz for contributing this code and insight to DigiByte. https://github.com/digibyte/digibyte/pull/36First off, this will fix the safe mode warnings once and for all. But it does so much more than that. Currently, an attacker can 51% attack the network with roughly 60% of SHA256D and nothing else. After this change, an attacker with 90% of the SHA256D hashrate and 33% of each of the other 4 algorithms would have insufficient hashpower to mount a 51% attack.
The new formula was chosen as a function of the difficulties and based on these criteria:
1. It should be a symmetric funtion
2. It should be order 1 homogenous
3. It should be homogenous with respect to each variable
Or in plain English:
1. There should be nothing algorithm-specific (such as per-algorithm weights) nor should it depend on which algorithm actually solved the block.
2. If all difficulties double, the block work should double
3. If one difficulty doubles, the block work should change by some constant factor
There is only one function (save multiplication by a constant factor) satisfying all 3 conditions: the geometric mean. As an added bonus, because of how the difficulty algorithm works the geometric mean can change by at most 3% from block to block (which addresses the safe-mode warning issue).
In order to 51% attack the network, the product of the attacker's hashrates must exceed the product of the network's hashrates. In particular, the attacker must have some hashrate in all 5 algorithms. So to summarise, there is no longer an individual algorithm weighting (workfactor) but a geometric mean (nthRoot) of all algos. This allows for five birds to be killed with one stone; preventing time warp attacks, eliminating safe mode error, improving difficulty adjustments, making sure each algo is only getting 20% of all the blocks and dramatically increasing the difficulty of a 51% attack. If you look back at the previous several thousand blocks and calculate the average % of each algo you will get the 20% average. Things are working as expected in that regard. Now as to electrical efficiency of each mining setup. ASIC's are by their very nature designed to be highly efficient: https://en.wikipedia.org/wiki/Application-specific_integrated_circuitThe original idea was to allow for people with both used, obsolete ASIC's and GPU's as well as some CPU's to be able to mine. As time has gone on the mining scene has undoubtedly changed and we now have two algos (Sha256 and Scrypt) dominated by ASIC's. As time goes on these two algos miners will get more electrically efficient but still only account 40% of new DGB coming into circulation. The other 60% is up for grabs from GPU's. As ASIC's get cheaper and more efficient it will be easier to distribute ASIC miners to people such as gamers. Remember the only thing a Sha256 or Scrypt ASIC can be used for is to mine a digital currency. Does this answer everyones questions? This is a very complex topic so we understand the confusion. We are always open to new ideas and suggestions as technology is rapidly changing. |
|
|
|
iOS Wallet update: Our test wallet has been approved by the Apple iTunes store. If you have DigiBytes stuck in the old iOS wallet and would like to help us test the new wallet please email dev@digibyte.co your Apple ID email and we will add you to the Test Flight list. Cheers, |
|
|
|
Here is the first weighting code (pre DigiSpeed): https://github.com/digibyte/digibyte/blob/master/src/main.h#L866 int GetAlgoWorkFactor() const
{
if (!TestNet() && (nHeight < multiAlgoDiffChangeTarget))
{
return 1;
}
if (TestNet() && (nHeight < 100))
{
return 1;
}
switch (GetAlgo())
{
case ALGO_SHA256D:
return 1;
// work factor = absolute work ratio * optimisation factor
case ALGO_SCRYPT:
return 1024 * 4;
case ALGO_GROESTL:
return 64 * 8;
case ALGO_SKEIN:
return 4 * 6;
case ALGO_QUBIT:
return 128 * 8;
default:
return 1;
}
} New Adjusted Weighting Code (Post DigiSpeed): CBigNum GetBlockWorkAdjusted() const
{
if (nHeight < workComputationChangeTarget)
{
CBigNum bnRes;
bnRes = GetBlockWork() * GetAlgoWorkFactor();
return bnRes;
}
else
{
CBigNum bnRes = 1;
CBlockHeader header = GetBlockHeader();
// multiply the difficulties of all algorithms
for (int i = 0; i < NUM_ALGOS; i++)
{
unsigned int nBits = GetNextWorkRequired(pprev, &header, i,false);
CBigNum bnTarget;
bnTarget.SetCompact(nBits);
if (bnTarget <= 0)
return 0;
bnRes *= (CBigNum(1)<<256) / (bnTarget+1);
}
// Compute the geometric mean
bnRes = bnRes.nthRoot(NUM_ALGOS);
// Scale to roughly match the old work calculation
bnRes <<= 7;
return bnRes;
}
} |
|
|
|
HR as far as I understand it 20% of the blocks are ASIC, 20% are Scrypt, 60% are GPU (I do not know if these are equally distributed).
That's not the issue. The block find distribution is 20/20/20/20/20. About that there is no doubt. The question is how does MultiShield adjust each algo's diff and as a function of exactly what? We know that before the most recent hardfork, global network hashrate (that is the combined total of the 5 algos) was key, and that all the algos diffs adjusted in response to changes in aggregate hashrate. The question is how much did that change? To what precise degree are the algos currently independent, and to what degree are they still inter-dependent? Yes block distribution is 20/20/20/20/20. To compare the exact changes in the last hard fork compare GetNextWorkRequiredV3 to GetNextWorkRequiredV4. Current difficulty adjustment code: https://github.com/digibyte/digibyte/blob/master/src/main.cpp#L1670static unsigned int GetNextWorkRequiredV4(const CBlockIndex* pindexLast, const CBlockHeader *pblock, int algo,bool log)
{
unsigned int nProofOfWorkLimit = Params().ProofOfWorkLimit(algo).GetCompact();
// Genesis block
if (pindexLast == NULL)
return nProofOfWorkLimit;
if (TestNet())
{
// Special difficulty rule for testnet:
// If the new block's timestamp is more than 2* 10 minutes
// then allow mining of a min-difficulty block.
if (pblock->nTime > pindexLast->nTime + nTargetSpacing*2)
return nProofOfWorkLimit;
else
{
// Return the last non-special-min-difficulty-rules-block
const CBlockIndex* pindex = pindexLast;
while (pindex->pprev && pindex->nHeight % nInterval != 0 && pindex->nBits == nProofOfWorkLimit)
pindex = pindex->pprev;
return pindex->nBits;
}
}
if(log)
{
LogPrintf("GetNextWorkRequired RETARGET\n");
LogPrintf("Algo: %s\n", GetAlgoName(algo));
LogPrintf("Height (Before): %s\n", pindexLast->nHeight);
}
// find first block in averaging interval
// Go back by what we want to be nAveragingInterval blocks per algo
const CBlockIndex* pindexFirst = pindexLast;
for (int i = 0; pindexFirst && i < NUM_ALGOS*nAveragingInterval; i++)
{
pindexFirst = pindexFirst->pprev;
}
const CBlockIndex* pindexPrevAlgo = GetLastBlockIndexForAlgo(pindexLast, algo);
if (pindexPrevAlgo == NULL || pindexFirst == NULL)
{
if(log)
LogPrintf("Use default POW Limit\n");
return nProofOfWorkLimit;
}
// Limit adjustment step
// Use medians to prevent time-warp attacks
int64_t nActualTimespan = pindexLast-> GetMedianTimePast() - pindexFirst->GetMedianTimePast();
nActualTimespan = nAveragingTargetTimespanV4 + (nActualTimespan - nAveragingTargetTimespanV4)/4;
if(log)
LogPrintf("nActualTimespan = %d before bounds\n", nActualTimespan);
if (nActualTimespan < nMinActualTimespanV4)
nActualTimespan = nMinActualTimespanV4;
if (nActualTimespan > nMaxActualTimespanV4)
nActualTimespan = nMaxActualTimespanV4;
//Global retarget
CBigNum bnNew;
bnNew.SetCompact(pindexPrevAlgo->nBits);
bnNew *= nActualTimespan;
bnNew /= nAveragingTargetTimespanV4;
//Per-algo retarget
int nAdjustments = pindexPrevAlgo->nHeight + NUM_ALGOS - 1 - pindexLast->nHeight;
if (nAdjustments > 0)
{
for (int i = 0; i < nAdjustments; i++)
{
bnNew *= 100;
bnNew /= (100 + nLocalTargetAdjustment);
}
}
else if (nAdjustments < 0)//make it easier
{
for (int i = 0; i < -nAdjustments; i++)
{
bnNew *= (100 + nLocalTargetAdjustment);
bnNew /= 100;
}
}
if (bnNew > Params().ProofOfWorkLimit(algo))
{
if(log)
{
LogPrintf("bnNew > Params().ProofOfWorkLimit(algo)\n");
}
bnNew = Params().ProofOfWorkLimit(algo);
}
if(log)
{
LogPrintf("nAveragingTargetTimespanV4 = %d; nActualTimespan = %d\n", nAveragingTargetTimespanV4, nActualTimespan);
LogPrintf("Before: %08x %s\n", pindexPrevAlgo->nBits, CBigNum().SetCompact(pindexPrevAlgo->nBits).getuint256().ToString());
LogPrintf("After: %08x %s\n", bnNew.GetCompact(), bnNew.getuint256().ToString());
}
return bnNew.GetCompact();
}
|
|
|
|
|
Show Posts
