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

[Jumbley]

Looks like the price is on it's way back down.

yes, we was pumped again. Crypto is a mine field! Be very aware people about buying something rapidly rising and take a good look before jumping in.

DigiByte tries very hard not to encourage p&d activity but it is powerless to stop it!

This is a very good reason not to buy a coin based on price movement. Long term, I don't believe DigiByte has ever seen any price that isn't recoverable but if you don't know what you are buying you shouldn't buy it.

[1714929381]

1714929381

[1714929381]

1714929381

[1714929381]

1714929381

[1714929381]

1714929381

[1714929381]

1714929381

[1714929381]

1714929381

[peonminer]

Looks like the price is on it's way back down.

yes, we was pumped again. Crypto is a mine field! Be very aware people about buying something rapidly rising and take a good look before jumping in.

DigiByte tries very hard not to encourage p&d activity but it is powerless to stop it!

Builds strength, not really pumped, just more attention brought to. The dumping had open hands ready, even with bitcoin being up $150.

[Jumbley]

Looks like the price is on it's way back down.

yes, we was pumped again. Crypto is a mine field! Be very aware people about buying something rapidly rising and take a good look before jumping in.

DigiByte tries very hard not to encourage p&d activity but it is powerless to stop it!

Builds strength, not really pumped, just more attention brought to. The dumping had open hands ready, even with bitcoin being up $150.

This may be partly true in the f'd up world we live in and is mostly greedy people ripping off other greedy people but it's not anything to be proud of.

[DigiByte]

A Few Thoughts on DigiSpeed & Blockchain Scalability

Question #1: Why does DigiByte need to be able to match Visa's average transactions per second?

Short answer: Utility, usability, marketability and growth well into the future. "DigiSpeed" has already became a buzzword in the crypto community and has a very marketable appeal moving forward. More importantly DigiByte takes a bold step forward with DigiSpeed to dramatically scale a blockchain with multi-algorithim mining. However, this does not mean the DigiByte blockchain size will jump dramatically over night.

Question #2: I can't afford to mine and run 8 MB blocks on my PC?

Short Answer: We are a long way off from hitting 8 MB blocks. We are not even coming close to filling 1 MB blocks. This change simply removes a cap that Satoshi himself even admitted was an arbitrary limit he put together on the fly. Our assumption is we will not see 8 MB blocks until several years from now.

Question #3: What incentive will people have in the future to run a full DigiByte node when there is a large amount of data in the blockchain?

Short answer: The "DigiSize v5.0 wallet we are planning for mid-late 2016 will tackle this issue head on. This will include advanced pruning and syncing features as well as some increased incentives for running a full node. We are tossing around several ideas for what this incentive might look at. Perhaps a staking feature, perhaps a new type of mining algorithim or perhaps some other feature yet to be thought up. We would like all the input we can get on this topic. In the end the key to long term survival and network security is tens of thousands of people around the world running full DigiByte nodes.

Question #4: Wont people attack the chain with bloated transactions and OP RETURN data?

Short Answer: This is a very real possibility that we are going to mitigate up front by increasing the average transaction fee (still a very small amount). And we open the amount of this increase up to debate. The best way to explain this is if someone wanted to fill up an 8MB with thousands of small transactions in theory they could. But if it cost them exponentially more to carry this out the attack vector is mitigated. As for OP RETURN data, we will be keep this as is. Future security applications that embed data in OP RETURN should make use of distributed hash tables, not storing data directly on the chain.

Question #5: Transactions are becoming larger than 250 kb, wont this make the issue worse?

Short Answer: Yes some transactions are indeed larger than 250 KB and the average transaction size in the future will undoubtedly be larger but for now its a solid number to work from for averages.

Question #6: With such fast block times and sizes wont transactions be "lost"?

Short Answer: With multi-algorithm mining we are actually in a unique position compared to other coins who have tried with very fast block times. Even though the DigiByte network as a whole will see 15 second block times, each individual algo and mining pool actually is generating 1 minute 15 second blocks. Meaning each block has over a minute to pick up transactions. Some great data on network propagation can be found here: Microsoft Research: http://www.tik.ee.ethz.ch/file/49318d3f56c1d525aabf7fda78b23fc0/P2P2013_041.pdf

Question #7: Are you testing massive swings in difficulty?

Short Answer: Absolutely. But after DigiShield and Multi shield this is much less of an issue than the Bitcoin test data that was shown for BTC that showed this to be a problem with larger blocks. Bitcoin still retargets every 2 weeks.

Question #8: Where is the test data for DigiSpeed?

Short Answer: Before releasing the hard fork wallets we will release data on the following points:
*Transaction Times
*Block Times
*Algo Distribution
*Transaction Sizes
*Other data we find useful

Question #9: Why not release DigiSpeed by using a timestamp in the future or by network consensus instead of making network changes occur at a specific block?

Short Answer: By using a specific block everyone knows exactly when the changes to the network will occur. This dramatically mitigates several attack vectors. It also gives people the choice to opt out ahead of time if they so chose. It is also important to note this will be DigiBytes fourth hard fork. The previous three were carried out successfully in the same manner.

Question #10: With block-speed doubling wont that mean twice as many DigiBytes will be coming in to circulation each day?

Short Answer: No. At the hardfork point the reward will be cut in half so the same amount of daily DigiBytes will be mined.


In closing it is important to note we are not going to rush anything here until we are 100% happy with our test data and have addressed all of the communities questions. We would also encourage everyone to read this blog post by the Bitcoin developer Mike Hearn: https://medium.com/@octskyward/on-block-sizes-e047bc9f830

Let us know other technical questions you have and as they come in we will post replies below here:

[cliffmadsen]

Hey this is probably a stupid question, but I have finally, installed Linux, and need help.
which miner should I use to mine skein in linux.
sudo this and sudo That
I feel so stupid,is there a tutorial for beginners:)

[dgbpool]

Hey this is probably a stupid question, but I have finally, installed Linux, and need help.
which miner should I use to mine skein in linux.
sudo this and sudo That
I feel so stupid,is there a tutorial for beginners:)

AMD   -> https://www.nicehash.com/?p=software#amdgpu

nvidia -> https://www.nicehash.com/?p=software#nvidiagpu

miner config:

     readme.txt or readme.md

pool:

      http://www.digihash.co

[cliffmadsen]

Hey this is probably a stupid question, but I have finally, installed Linux, and need help.
which miner should I use to mine skein in linux.
sudo this and sudo That
I feel so stupid,is there a tutorial for beginners:)

AMD   -> https://www.nicehash.com/?p=software#amdgpu

nvidia -> https://www.nicehash.com/?p=software#nvidiagpu

miner config:

     readme.txt or readme.md

pool:

      http://www.digihash.co

Thank you very much

[bogglor]

Question #4: Wont people attack the chain with bloated transactions and OP RETURN data?

Short Answer: This is a very real possibility that we are going to mitigate up front by increasing the average transaction fee (still a very small amount). And we open the amount of this increase up to debate. The best way to explain this is if someone wanted to fill up an 8MB with thousands of small transactions in theory they could. But if it cost them exponentially more to carry this out the attack vector is mitigated. As for OP RETURN data, we will be keep this as is. Future security applications that embed data in OP RETURN should make use of distributed hash tables, not storing data directly on the chain.

I've been mining DGB since March 2014. My core wallet has over 20000 transactions in it, most are very small (less than 50 dgb) because I don't have alot of mining power and I have mined on pools that pay out immediately instead of waiting and sending in big chunks.

I'm going to be penalized with a higher transaction fee for spending these? Sounds like it's in my best interest to send them to myself now in large chunks before the automatic transactions fees go higher.

[bogglor]

Hey this is probably a stupid question, but I have finally, installed Linux, and need help.
which miner should I use to mine skein in linux.
sudo this and sudo That
I feel so stupid,is there a tutorial for beginners:)

For skein, I use https://github.com/reorder/cgminer_skein on my Linux miner.

At your linux prompt, do these commands in bold:

git clone https://github.com/reorder/cgminer_skein

a few lines of things will happen

cd cgminer_skein

./autogen.sh --enable-skein --enable-opencl

alot of stuff will scroll by, might take a minute or so

make

alot more stuff will scroll by, should take less than a minute

If everything went well, then you should be able to mine with your GPUs now...

./cgminer --skein -o stratum+tcp://pool.address.com:1234 -u username -p password

If something fails in one of these steps, then you probably don't have the right linux program dependencies installed.

[iikun]

Question #4: Wont people attack the chain with bloated transactions and OP RETURN data?

Short Answer: This is a very real possibility that we are going to mitigate up front by increasing the average transaction fee (still a very small amount). And we open the amount of this increase up to debate. The best way to explain this is if someone wanted to fill up an 8MB with thousands of small transactions in theory they could. But if it cost them exponentially more to carry this out the attack vector is mitigated. As for OP RETURN data, we will be keep this as is. Future security applications that embed data in OP RETURN should make use of distributed hash tables, not storing data directly on the chain.

I've been mining DGB since March 2014. My core wallet has over 20000 transactions in it, most are very small (less than 50 dgb) because I don't have alot of mining power and I have mined on pools that pay out immediately instead of waiting and sending in big chunks.

I'm going to be penalized with a higher transaction fee for spending these? Sounds like it's in my best interest to send them to myself now in large chunks before the automatic transactions fees go higher.

I admit I'm speaking without knowledge of what the planned transaction fees exactly are but I would doubt that such significant increases are planned. So saying, if you're able to send them in larger chunks now (as you wrote) then it wouldn't hurt to do so would it?

[bogglor]

Question #4: Wont people attack the chain with bloated transactions and OP RETURN data?

Short Answer: This is a very real possibility that we are going to mitigate up front by increasing the average transaction fee (still a very small amount). And we open the amount of this increase up to debate. The best way to explain this is if someone wanted to fill up an 8MB with thousands of small transactions in theory they could. But if it cost them exponentially more to carry this out the attack vector is mitigated. As for OP RETURN data, we will be keep this as is. Future security applications that embed data in OP RETURN should make use of distributed hash tables, not storing data directly on the chain.

I've been mining DGB since March 2014. My core wallet has over 20000 transactions in it, most are very small (less than 50 dgb) because I don't have alot of mining power and I have mined on pools that pay out immediately instead of waiting and sending in big chunks.

I'm going to be penalized with a higher transaction fee for spending these? Sounds like it's in my best interest to send them to myself now in large chunks before the automatic transactions fees go higher.

I admit I'm speaking without knowledge of what the planned transaction fees exactly are but I would doubt that such significant increases are planned. So saying, if you're able to send them in larger chunks now (as you wrote) then it wouldn't hurt to do so would it?

I'd have to sit down and spend several hours to do this. Working with a wallet with thousands of transactions is extremely slow.

In fact the other day I was messing around with my wallet, and tried to select about 10000 transactions just to see how it would react. After waiting 45 minutes with my wallet not responding, I just ended the process to close the wallet.

[bogglor]

What I'd really like to know is how are automatic transaction fees determined.

Can someone with knowledge of the how it's coded post this?

Something like: If a transaction is older than X days and/or has less than Y digibytes, then there is an automatic transaction fee of Z DGB.

This would help alot for me to determine which transactions have fees and which don't.

[Jumbley]

What I'd really like to know is how are automatic transaction fees determined.

Can someone with knowledge of the how it's coded post this?

Something like: If a transaction is older than X days and/or has less than Y digibytes, then there is an automatic transaction fee of Z DGB.

This would help alot for me to determine which transactions have fees and which don't.

I think it is like this:  Up to 6 inputs  = No fee
                            Up to 12 inputs = 0.04 DGB
                            and then an additional 0.02 DGB for each additional 6 inputs until transaction is too large.

                            something like that!

[jwinterm]

...Even though the DigiByte network as a whole will see 15 second block times, each individual algo and mining pool actually is generating 1 minute 15 second blocks...

IMO the issue isn't that transactions will be "lost", it's that the probability of orphaned blocks will rise dramatically, especially if blocks go up to 8 MB. The bitcoin small blockers are (nominally) worried about 8 MB block propagation with a ten minute block time, and somehow you think it will be no problem to propagate 8 MB blocks with an effective 15 s block time. I would think it would also make a double spend easier to pull off unless you double the number of required confirmations. And I feel like there could be some interplay between those two issues (block propagation and 51% attack), like if an attacker with a large hashrate on more than one algo jumps on and starts spitting out several 8 MB blocks, will the long block propagation time make it even easier for the attacker to build several more blocks while his first few propagate around the network and possibly orphan other legitimate blocks?

[GigaBit]

Well, I took a couple of days off my busy week to deal with this specific issue... plus I got date with the hot dentist tomorrow.
Basically it just means I get to deal with shit I don't want to deal with when I am in production mode.
I don't want to sell any but I would prefer my stash went to someone from the community rather than gobbled up by an exchange or negative parties.
Too much in mind right now to be inserting every comment I want to reply to but I'll do it contextually.

You're right though, I might be jumping ship way too early... but it's typical me; when you have a problem eliminate it, shoot now ask questions later.
Thing is, I don't want to sellout and I do care about DigiByte, that's why I came here to find it a good home; potentially someone could make sense of it all.
I'm also not so much a man of words, more a man of action so if I am presented with options I didn't know exist then I'll think twice.

If DigiByte's information is accurate above, I got tons of time before larger blocks are needed and the core becomes too heavy for me to run.
However, I'ma firm believer of the limited dynamic blocks... create the size you need, as you need up to a certain limit.
The faster blocks could mean we may never need bigger blocks, since more blocks more often can move a lot more coin faster.
Let's call it, contingency for the future... so we don't run into the block debates down the road like in BTC... but their blocktime is 10 minutes though.
Thank you guys for understanding my internet issue, I run my mine off of an LTE Hub and day to day activities is on satellite; it's a challenge.
My average bill is $135.00 and with bigger blocks would be... well, you do the math anything above 20Gb is $10 per Mb (yes, per megabyte)
Cool this is when others have Internet or power issues, I am unaffected  
I live right next to heaven here as far as I'm concerned, the downside is everything is expensive.

I am also looking at other storage options like Cryptsy Lock Box... but not sure if I can trust it though.  
I like the idea of just saving the wallet.dat too but then I still need to download the whole core again later anyways so... it's just a worst case scenario option.
Then again, I like the idea of selling too, let another generation enjoy it... I'll always own a bunch DGB's anyways, I still got a few hundred K's in pools.
Besides, I got other profitable shenanigans that need funding.
Then I am tempted by Sharky's respectable offer... not every day you get a BTC10 bone dangling in your face.
If I refuse it, would the greatest money amount I refuse.... but I am also tempted into have a dumping party, it's so fun!
Then there are many exchanges that trade DGB so I can distribute the damage and run the chance to make a lot more than selling wholesale.
Like I say, there's a logical solution to every problem... sometimes, all I need is to be explained things in complete detail.... and to sleep on it a few times.

MyriadCoin, you're drunk, go back to your boring-ass thread or join us.... admit it, you know you wanna!  

[yoyoamigo]

Well, I took a couple of days off my busy week to deal with this specific issue... plus I got date with the hot dentist tomorrow.
Basically it just means I get to deal with shit I don't want to deal with when I am in production mode.
I don't want to sell any but I would prefer my stash went to someone from the community rather than gobbled up by an exchange or negative parties.
Too much in mind right now to be inserting every comment I want to reply to but I'll do it contextually.

You're right though, I might be jumping ship way too early... but it's typical me; when you have a problem eliminate it, shoot now ask questions later.
Thing is, I don't want to sellout and I do care about DigiByte, that's why I came here to find it a good home; potentially someone could make sense of it all.
I'm also not so much a man of words, more a man of action so if I am presented with options I didn't know exist then I'll think twice.

If DigiByte's information is accurate above, I got tons of time before larger blocks are needed and the core becomes too heavy for me to run.
However, I'ma firm believer of the limited dynamic blocks... create the size you need, as you need up to a certain limit.
The faster blocks could mean we may never need bigger blocks, since more blocks more often can move a lot more coin faster.
Let's call it, contingency for the future... so we don't run into the block debates down the road like in BTC... but their blocktime is 10 minutes though.
Thank you guys for understanding my internet issue, I run my mine off of an LTE Hub and day to day activities is on satellite; it's a challenge.
My average bill is $135.00 and with bigger blocks would be... well, you do the math anything above 20Gb is $10 per Mb (yes, per megabyte)
Cool this is when others have Internet or power issues, I am unaffected  
I live right next to heaven here as far as I'm concerned, the downside is everything is expensive.

I am also looking at other storage options like Cryptsy Lock Box... but not sure if I can trust it though.  
I like the idea of just saving the wallet.dat too but then I still need to download the whole core again later anyways so... it's just a worst case scenario option.
Then again, I like the idea of selling too, let another generation enjoy it... I'll always own a bunch DGB's anyways, I still got a few hundred K's in pools.
Besides, I got other profitable shenanigans that need funding.
Then I am tempted by Sharky's respectable offer... not every day you get a BTC10 bone dangling in your face.
If I refuse it, would the greatest money amount I refuse.... but I am also tempted into have a dumping party, it's so fun!
Then there are many exchanges that trade DGB so I can distribute the damage and run the chance to make a lot more than selling wholesale.
Like I say, there's a logical solution to every problem... sometimes, all I need is to be explained things in complete detail.... and to sleep on it a few times.

MyriadCoin, you're drunk, go back to your boring-ass thread or join us.... admit it, you know you wanna!  

whatever scenario or situation you are in, always have >=1 million DGB for the looooooooong run.  

kinda like a failproof plan...erm...not sure how to explain.

keep it in a trezor or safe/lockbox....come back years later....viola. don't end up like some dude who mined and threw the ext hdd and desperately went looking for it in the dump. back then, there were little options. but now...we have better options, solutions, ideas, etc. Next year...even more.

how much diff is 9btc to 10btc to you btw? do you really need every single bit of 10 btc? do consider carefully. hopefully there is room to save some.
and yea...might be too early to jump ship. DigiSpeed isn't release yet. although i can see that you may want to just be way prepared and not wait for when the situation comes.

OH and stay away from Cryptsy for the time being. the air isn't clear yet. they are still quite stuck in a muddy situation.

Cheers!

[Tyke]

This is the final cover for the upcoming book on DigiByte:

[Fenix_One]

Is there any information on Digibyte Market launch?

[Lovethecoins]

This is the final cover for the upcoming book on DigiByte:

Should be a good read can't wait

[pringles1901]

This is the final cover for the upcoming book on DigiByte:

Its going to look a bit naff mate the back cover is smaller than the front
On the subject of naff were is all the buy support gone for DGB its a bit thin....just goes to show BTC is king