Time for some new bounties? The list is long and there haven't been any lately.
Very good idea. We will work on getting some lined up. Anyone have any suggestions, what could we use right now for a boost? 
Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1403. (Read 3058812 times)
April 15, 2014, 10:18:55 PM
April 15, 2014, 07:36:54 PM
DigiByte is now live @CryptoCzar! Very professional exchange team we met at the NYC convention! https://cryptoczar.com/market
April 15, 2014, 07:30:10 PM
Time for some new bounties? The list is long and there haven't been any lately.
April 15, 2014, 06:04:39 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
its NOT safe. Needs update AS SOON AS POSSIBLE
good!
I am by no means ultimately-informed -> however, it was my understanding that the heart bleed bug would not affect your average user.
If you aren't using SSL for rpc'ing to a server or some such application, and connecting using SSL to an unknown or untrustworthy host, your memory data should not be exposed (at least that was how I understood it). Further, even if some of your memory was exposed, it would take a concerted attack to expose many small chunks of memory to ever get the key and break the security entirely.
I might be mistaken, but I have not changed any of my behavior because of the bug, as I do not see it as such an issue concerning general usage.
yes but nevertheless it should be fixed.
Indeed, a fix is being built as we speak
April 15, 2014, 06:02:40 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
its NOT safe. Needs update AS SOON AS POSSIBLE
good!
I am by no means ultimately-informed -> however, it was my understanding that the heart bleed bug would not affect your average user.
If you aren't using SSL for rpc'ing to a server or some such application, and connecting using SSL to an unknown or untrustworthy host, your memory data should not be exposed (at least that was how I understood it). Further, even if some of your memory was exposed, it would take a concerted attack to expose many small chunks of memory to ever get the key and break the security entirely.
I might be mistaken, but I have not changed any of my behavior because of the bug, as I do not see it as such an issue concerning general usage.
yes but nevertheless it should be fixed.
April 15, 2014, 06:02:12 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
its NOT safe. Needs update AS SOON AS POSSIBLE
good!
I am by no means ultimately-informed -> however, it was my understanding that the heart bleed bug would not affect your average user.
If you aren't using SSL for rpc'ing to a server or some such application, and connecting using SSL to an unknown or untrustworthy host, your memory data should not be exposed (at least that was how I understood it). Further, even if some of your memory was exposed, it would take a concerted attack to expose many small chunks of memory to ever get the key and break the security entirely.
I might be mistaken, but I have not changed any of my behavior because of the bug, as I do not see it as such an issue concerning general usage.
April 15, 2014, 05:25:10 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
its NOT safe. Needs update AS SOON AS POSSIBLE
April 15, 2014, 05:24:53 PM
I would like access to the media packet as I would like to take initiative to contact some publications to do a story on Digibyte. Also, it would be beneficial for the community to use Reddit as the main central area to discuss. Let's keep pushing forward.
Kind Regards,
YC
Kind Regards,
YC
Today We are Kicking off a Digi-Awareness Campaign for the next 6 weeks!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
+1
I can help with this as well.
April 15, 2014, 05:06:07 PM
I'm doing a research project on coin distribution for both older and new coins. I'm interested on gathering some data for top addresses and how much of the coins the top100 have. This along with the number of people (addresses) actually holding any amount of coins.
I have some info from bitinfocharts on a few coins but I really do need some data on other coins along with less exposed or new ones.
If anyone knows an explorer with this feature drop a line.
I have some info from bitinfocharts on a few coins but I really do need some data on other coins along with less exposed or new ones.
If anyone knows an explorer with this feature drop a line.
niothor u are a cuty pie icebear
April 15, 2014, 05:05:17 PM
I'm doing a research project on coin distribution for both older and new coins. I'm interested on gathering some data for top addresses and how much of the coins the top100 have. This along with the number of people (addresses) actually holding any amount of coins.
I have some info from bitinfocharts on a few coins but I really do need some data on other coins along with less exposed or new ones.
If anyone knows an explorer with this feature drop a line.
I have some info from bitinfocharts on a few coins but I really do need some data on other coins along with less exposed or new ones.
If anyone knows an explorer with this feature drop a line.
April 15, 2014, 04:45:55 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
its NOT safe. Needs update AS SOON AS POSSIBLE
April 15, 2014, 04:44:45 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
The 2.0.0 version of the windows wallet uses OpenSSL 1.0.1e, and you are saying this is safe?
Even though on www.heartbleed.com it says:
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
I just want to be clear on this. I'm not trying to argue with you, it just seems like conflicting information.
April 15, 2014, 03:44:42 PM
I would like access to the media packet as I would like to take initiative to contact some publications to do a story on Digibyte. Also, it would be beneficial for the community to use Reddit as the main central area to discuss. Let's keep pushing forward.
Kind Regards,
YC
Kind Regards,
YC
Today We are Kicking off a Digi-Awareness Campaign for the next 6 weeks!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
April 15, 2014, 01:38:12 PM
I think changin to pos is a no brainer. Those are the coins people are looking for at the moment.
I'm not sold on PoS. At least not as the sole way of mining/minting. PoS wants people to hoard coins, which is not helpful for an economy (look at Japan) and if I'm going to leave my money sitting somewhere, there are better financial instruments out there which will pay more than the 1% POS tends to pay out. Heck, even buying gold beats that. PoS is a fine and worthy adjunct to PoT/PoW but I'd hate to see DGB go full PoS.
April 15, 2014, 01:09:42 PM
I think changin to pos is a no brainer. Those are the coins people are looking for at the moment.
I'm not sold on PoS. At least not as the sole way of mining/minting. PoS wants people to hoard coins, which is not helpful for an economy (look at Japan) and if I'm going to leave my money sitting somewhere, there are better financial instruments out there which will pay more than the 1% POS tends to pay out. Heck, even buying gold beats that. PoS is a fine and worthy adjunct to PoT/PoW but I'd hate to see DGB go full PoS.
April 15, 2014, 01:07:35 PM
Help Start the Digi-Awareness Campaign! Share DigiByte with everyone you know and lets keep DigiByte heading to the moon!
April 15, 2014, 12:48:00 PM
Today We are Kicking off a Digi-Awareness Campaign for the next 6 weeks!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
Advertising Goals:
1) Finish a Media Packet to send to reporters/ regulators & more investors!
2) Launch a YouTube video series with the founder of DigiByte to explain things in detail and to give people a personalized insight into the crypto world & DigiByte
3) How-to beginner guides on the website as well as other website upgrades.
4) Continue meetings & discussions with investors to get Digi-Pay.com off the ground
5) Establish a Marketing & PR Team
Tech Goals
1) Finish 2.9.1 OpenSSL upgrade & fix
2) Reach a final decision on the algorithm change.
How You Can Help:
1) Spread the word!
2) Create DigiByte content & resources to share
3) Get to know us better!
April 15, 2014, 12:37:22 PM
We will have the updated client that fixes the ssl bug out later today. The URI payment protocol in the new client (2.9.0) is affected. I'm unaware of any web services for DigiByte that implements the payment protocol so risk should be very low. Once the new client is released if you were using 2.9.0 it would be best to send your DigiBytes to a completely new wallet and delete the old one. While this step isn't required I always err on the side of caution.
If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
Regarding the Open SSL issue. The older client is not at risk like the 0.9 client is / was. If your still using DigiByte 2.0.0 you should have no issues but coin control in the new client alone makes the update worth it.
April 15, 2014, 12:35:44 PM
Good morning! It's very interesting all the trouble they are having with KGW coins. Many coins are applying digishield to fix the vulnerability.
Maybe we should take advantage of this opportunity to advertise more digibyte. . The developers could create a thread so that everyone knows that solves the problem digishield KGW.
By the way, good luck in the crypto convention Wednesday!
Maybe we should take advantage of this opportunity to advertise more digibyte. . The developers could create a thread so that everyone knows that solves the problem digishield KGW.
By the way, good luck in the crypto convention Wednesday!
The DigiShield doesn't solve anything. KGW is/was vulnerable to a timewarp. DigiShield is vulnerable to a timewarp.
Could you explain this more in detail? Do you have a link to a more detail explanation. Technically speaking all coins are susceptible to a time warp attack when a 51% attack occurs.
April 15, 2014, 09:34:36 AM
I'm curious, I just downloaded the windows wallet from the Digibyte website and it's using OpenSSL 1.0.1e. I did this on a computer that I don't use, so that it was a fresh install and wouldn't affect my actual wallet.
I thought that OpenSSL version 1.0.1f and earlier was vulnerable to Heartbleed.
Is the wallet going to be updated with a newer version of OpenSSL?
I haven't opened my wallet to sync in 5-6 days, and would like to know that it's safe before I do it.
I thought that OpenSSL version 1.0.1f and earlier was vulnerable to Heartbleed.
Is the wallet going to be updated with a newer version of OpenSSL?
I haven't opened my wallet to sync in 5-6 days, and would like to know that it's safe before I do it.
Jump to: