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

[ACP]

https://github.com/digibyte/digibyte.git can we compile from this or is this still being updated?

[Jumbley]

https://github.com/digibyte/digibyte.git can we compile from this or is this still being updated?

Yes, Looks good to me, updates will be soft forked. Wallets may also be downloaded from here http://www.digibyte.co/digibyte-wallets   (there are MD5 check sums to make sure you have good copies)

[esotericizm]

https://github.com/digibyte/digibyte.git can we compile from this or is this still being updated?

Please use https://github.com/digibyte/digibyte-old if you are compiling from source until we announce an official release.

Cheers

[Jumbley]

https://github.com/digibyte/digibyte.git can we compile from this or is this still being updated?

Please use https://github.com/digibyte/digibyte-old if you are compiling from source until we announce an official release.

Cheers

or follow this advice clearly stated in README.md and now directly from one of the devs working on the code.    Thx G.

[testcoin]

https://github.com/digibyte/digibyte.git can we compile from this or is this still being updated?

Please use https://github.com/digibyte/digibyte-old if you are compiling from source until we announce an official release.

Cheers

or follow this advice clearly stated in README.md and now directly from one of the devs working on the code.    Thx G.

Nice, we finally have some wallet upgrade for DGB

Where can I find the list of changes for the new upgrade?

[morningman]

Having issue with wallet. Running latest Windows 64 bit wallet. Wallet has been operating fine since download last year. This weekend I tried opening it but I receive a window that reads, "cannot read blocks".
Can someone tell Me how to fix this problem?

[ReSl]

Yes, please add other nodes and start your client with the -reindex command-line option

46.4.66.6
134.255.221.7
178.33.228.14
95.47.155.37
176.9.61.40
54.89.21.44
68.63.19.64
108.61.10.90
213.73.136.90
60.205.112.102
104.238.187.114
86.31.44.129
86.31.245.140
185.128.41.158
162.243.59.178
176.31.126.191
104.131.142.198
173.212.199.201
130.240.22.202
93.113.101.229

The new wallet currently being tested will overcome your issues but for now you need patience.
Anyone having trouble with core wallet connecting, you may need to add seed nodes.
1.   Help
2.   Debug window
3.   Console and enter

addnode “[any of the above IPs]” “add”
eg.   addnode “93.113.101.229” “add”

[Jumanji7]

Any roadmap for the short term?

[lionhead666]

What are the three best things about Digibyte?

Security - real decentralization with Multi-Algo support and Digi-Shield
Speed - very fast transactions
Commited development team

[cryptmebro]

What are the three best things about Digibyte?

Security - real decentralization with Multi-Algo support and Digi-Shield
Speed - very fast transactions
Commited development team

cheap as fuck
best potential for ROI of nearly any alt on poloniex.
it works, fast
supports a trillion lot of TPS. more than will be needed for a long time. Furthermore, it's already programmed to increase with time. No scaling issues here.

[connexus]

Any roadmap for the short term?

There isn't any at the moment, the current roadmap is strategically plan for long term.

[Jumbley]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

[Jonesd]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

Only sensible thinkers? Too bad. Let me know when you also accept unreasonably optimistic people. :-D

[Jumbley]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

Only sensible thinkers? Too bad. Let me know when you also accept unreasonably optimistic people. :-D

They are up now. 

[cryptmebro]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

completely unnecessary. DGB does not need a new scaling solution, it already has the best on chain scaling of any coin right now and can handle far more transactions on chain than any other coin, and any other coin + Segwit.

[HR]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

completely unnecessary. DGB does not need a new scaling solution, it already has the best on chain scaling of any coin right now and can handle far more transactions on chain than any other coin + Segwit.

I agree. No need for immediate activation. The fact that it's there for the future, if and when needed, is good enough for now. It's never a good idea to unnecessarily complicate things, and if it's needed for marketing purposes, "Segwit Ready" or "Segwit Capable" or something similar should get the job done, as well as implicitly saying that it isn't necessary at this time. Win-Win. :-)

[Jumbley]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

completely unnecessary. DGB does not need a new scaling solution, it already has the best on chain scaling of any coin right now and can handle far more transactions on chain than any other coin + Segwit.

I agree. No need for immediate activation. The fact that it's there for the future, if and when needed, is good enough for now. It's never a good idea to unnecessarily complicate things, and if it's needed for marketing purposes, "Segwit Ready" or "Segwit Capable" or something similar should get the job done, as well as implicitly saying that it isn't necessary at this time. Win-Win. :-)

I'm inclined to agree but I think activation should happen in the region of 65% of miners. Here are some of the reasons stated by Jared on the subject.

Digi Tater, [20.03.17 14:16]
Segwit has many benefits besides simply increasing scalability

Digi Tater, [20.03.17 14:16]
it fixes the transaction malleability issue

Digi Tater, [20.03.17 14:17]
it allows for roughly 4mb worth of transactions in the same space as 1 mb takes now

Digi Tater, [20.03.17 14:17]
most importantly it allows for a future of on chain "smart" contracts on UTXO based blockchains

Digi Tater, [20.03.17 14:17]
so from an applications standpoint it opens many doors

Digi Tater, [20.03.17 14:18]
It actually makes the most sense to combine both approaches, Segwit + increased block sizes

[Jonesd]

What are the disadvantages of implementing it? Bloating the chain with too big blocks?

[cryptmebro]

community thoughts on activation of segwit on DigiByte chain and consensus of community. All sensible thinkers welcome to comment.  https://t.me/DigiByteCoin

completely unnecessary. DGB does not need a new scaling solution, it already has the best on chain scaling of any coin right now and can handle far more transactions on chain than any other coin + Segwit.

I agree. No need for immediate activation. The fact that it's there for the future, if and when needed, is good enough for now. It's never a good idea to unnecessarily complicate things, and if it's needed for marketing purposes, "Segwit Ready" or "Segwit Capable" or something similar should get the job done, as well as implicitly saying that it isn't necessary at this time. Win-Win. :-)

I'm inclined to agree but I think activation should happen in the region of 65% of miners. Here are some of the reasons stated by Jared on the subject.

Digi Tater, [20.03.17 14:16]
it fixes the transaction malleability issue

Digi Tater, [20.03.17 14:17]
it allows for roughly 4mb worth of transactions in the same space as 1 mb takes now

Digi Tater, [20.03.17 14:17]
most importantly it allows for a future of on chain "smart" contracts on UTXO based blockchains

Digi Tater, [20.03.17 14:17]
so from an applications standpoint it opens many doors

Digi Tater, [20.03.17 14:18]
It actually makes the most sense to combine both approaches, Segwit + increased block sizes

Only for segwit transactions

Best case scenario 4MB, and segwit saves space by removing the signature data to save KB in block space. This technically makes the coins spendable by anyone.

Segwit in itself does not do this. It's the byproduct of a malleability fix.

It finally opened the door for a much need hard fork for Bitcoin, yes. It's so bad people will now FINALLY hard fork the block size for bitcon; something Digibyte has already successfully done.
For litecoin, not so many doors.
It's already falied twice. No need to bring the failure and drama to Digibyte.

Again, Segwit is so overly complex it actually does not make sense.

I understand why jared is pro segwit, it's good for "marketing", but from a technical standpoint, its absolutely terrible.

Please read this with an open mind

http://www.wallstreettechnologist.com/2016/12/03/core-segwit-you-need-to-read-this/

[esotericizm]

I understand why jared is pro segwit, it's good for "marketing", but from a technical standpoint, its absolutely terrible.

Not going to disagree with anything else that's been said but the dev team is not 'pro segwit'.

We have a more than adequate fix for tx scaling via our increased speed and block sizes. I'm Far more interested in keeping our bloat down and in on-chain smart contracts.