Still amazed at how fast a complete sync from scratch is.
Other coins with almost a year's worth of blocks take hours and hours.
And all my problems with balance were fixed as expected
Topic: [ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 194. (Read 1201380 times)
February 14, 2017, 06:16:46 AM
February 14, 2017, 03:54:52 AM
impressive work on rebranding, congrats
https://medium.com/eeter/decred-developing-identity-and-design-system-for-a-digital-currency-17df76ab67c8#.6f6otpcyg
https://medium.com/eeter/decred-developing-identity-and-design-system-for-a-digital-currency-17df76ab67c8#.6f6otpcyg
February 14, 2017, 03:48:15 AM
Roll baby Roll!!! 
Still a good entry point 
Still a good entry point 
February 14, 2017, 03:20:51 AM
February 14, 2017, 02:40:01 AM
The update to 0.8.0 was done within a couple of minutes. Node is up again.
I noticed some commands slightly changed, ex: dcrctl getbalance, but this should net be of any problem to sort out. Just updating some scripts today and i'm fine.
I noticed some commands slightly changed, ex: dcrctl getbalance, but this should net be of any problem to sort out. Just updating some scripts today and i'm fine.
February 13, 2017, 08:02:18 PM
What! 62K downloads? BTW, that link doesn't work.
Hmm, works for me? Unless you are referring to the 62k link. It's not supposed to link to anything
The one above links to downloads, although I suppose linking both to downloads wouldn't hurt. 
February 13, 2017, 07:57:22 PM
What! 62K downloads? BTW, that link doesn't work.
February 13, 2017, 07:48:38 PM
If you would like to participate in the Hard Fork Voting test, you can receive testnet tokens here: https://faucet.decred.org/
To monitor the progress of the test vote, use this page: https://hardforkdemo.decred.org/
To monitor the progress of the test vote, use this page: https://hardforkdemo.decred.org/
February 13, 2017, 07:03:46 PM
February 13, 2017, 06:40:21 PM
https://twitter.com/decredproject/status/831285069813788672
BIG update just dropped.
https://forum.decred.org/threads/dd-21-v0-8-0-02-13-17.5111/
A lot has happened in the past several weeks since the 0.7.0 release of Decred. On the valuation front, the exchange rate has gone up substantially from a low of approximately USD 0.43 on December 28th to an all-time-high of USD 3.31 on February 5th, which has since settled around USD 2.50. The number of downloads of binaries from GitHub for the 0.7.0 release has gone up by a factor of 5 or more, and we have a substantially larger number of users in Slack and other chat channels. This substantial improvement in valuation, exposure and community engagement is due mainly to our recent work with several marketing contractors via the dev org, DHG, which I will say more about below.
Beyond matters related to Decred's valuation, there has been substantial progress on several of our software projects and with their documentation. The bulk of the code needed to enable hard fork voting has been completed, and it will be demonstrated live on testnet over the next few weeks, via a corresponding website that shows its progress. A substantial design overhaul has been completed during the past several months, which includes a new logo and changes to every project website. decrediton, the cross platform GUI, has made a huge amount of progress, going from an alpha project to a solid beta in a single release. Paymetheus, the native Windows wallet, now uses the new stakepool API integration to simplify setting up ticket buying with a stakepool. Several additions and updates have been made to the Decred documentation site by documentation contractors. More detailed descriptions of our progress can be found below.
Marketing, Documentation and Development Contractors
Per the recent 2017 Decred Roadmap, a deliverables-driven RFP process did not end up working out very well, so we have since changed our RFP process to be need-driven by domain. The dev org, DHG, has contracted 5 people to do marketing, 2 to do documentation and 3 to do development work. So far, this arrangement is working out very well and has led to substantial progress on the marketing and documentation fronts.
The marketing contractors have met with considerable success in increasing awareness, engagement and generally creating demand for decred. The puzzles created by @coin_artist have been particularly effective at drawing new users to our Slack channels and creating a general buzz about Decred. The efforts of @Daniel, @Emilio Mann, @Tivra and @Dyrk have served to grow our community, engage new users, create additional demand, support regional markets and broaden our social media support. Overall, this marketing work has been very successful to date.
The documentation and development contractors have started doing work more recently, so they haven't had as much time as the marketing contractors to get their deliverables flowing. @gratefulcheddar and @Shadowlance have been pushing out a lot of new and updated documentation over the past few weeks, and their output should become much more apparent over the next few months as they shore up the Decred documentation. @karamble has pushed out a lot of web development work in the past couple weeks, which has made an otherwise monolithic release much more manageable. @raedah has submitted several pull requests that improve dcrwallet's ticketbuyer, which should lead to improvements in the fee market for tickets. We expect the contributions from our documentation and development contractors to become more apparent in the coming months.
Substantial Design Update
A design overhaul of Decred was initiated in RFP-7 several months ago with @linnutee, and it is being brought to completion with the 0.8.0 release. The work includes a new logo, design updates for every project website and a branding package for other Decred-related projects to use. As you can imagine, updating every website the project maintains is a pretty daunting task, so beyond @linnutee and sander doing all the design and coding, we had @karamble integrate and audit their work, and @Shadowlance contributed text copy in several places.
For those who are interested in the details of this work, I recommend you give @linnutee's recent Medium post a read.
Hard Fork Voting Demo
While it's certainly less tangible than a surge in the exchange rate, the core of Decred is based around decentralization as a process, and the first major step in that process, hard fork voting, has been prepared for a demo on testnet. Stakeholders will soon have the ability to vote on defined issues in dcrwallet, and this will allow Decred to episodically hard fork based on how its stakeholders vote. If 75% or more of the stakeholders vote “yes” for a given issue during a voting period, it will go into effect approximately 4 weeks later (on mainnet), and this includes “hard fork” consensus changes. Getting this code ready has been particularly challenging since it is all consensus-related code, which is notoriously unforgiving when it comes to bugs.
The testnet demo has an accompanying webpage that allows users to watch each step in the voting process occur. We chose to have a single issue for the demo, to increase the block size from 1 MiB to 1.25 MB, and we felt this was appropriate since the block size has been so contentious for Bitcoin. There are 3 stages to hard fork voting, which is reflected on the demo website, and this process draws from some parts of the BIP0009 soft fork process from Bitcoin. First, Proof-of-Work miners must update their dcrds to the latest release until a threshold percentage, 75% in the case of testnet, of blocks in a rolling window show the new block version in their header. Second, Proof-of-Stake miners, i.e. stakeholders, must update their voting wallets to the latest release of dcrwallet until a threshold percentage, 75% for testnet, of votes in blocks in a fixed window show the new vote version. At the end of the first interval with 75% or greater support for the new vote version, the stake version is incremented to the new version and a voting period begins. Once a voting period comes to an end, any issues that receive 75% or greater 'yes' votes are considered complete and will become active after a lock-in period. Issues that receive 75% or greater 'no' votes are considered dead and will not be voted on further. If an issue does not receive a 75% or greater vote either direction, the issue remains up for voting in future voting periods until an expiration time is reached. The process of upgrading PoW miners, PoS miners and voting will occur on an ongoing episodic basis and allow Decred's consensus code to evolve over time, according to the will of its stakeholders. We estimate that it will take 3-6 weeks for the testnet demo to have the block size increase voted in and for the hard fork to occur, so users can stop by and check the progress on the webpage.
Major GUI Wallet Progress
Until this release, only Windows users had the option of running a self-contained GUI wallet with Paymetheus, so we are pleased to announce that decrediton, a cross platform GUI wallet, is ready for use on Linux and OS X. decrediton now supports all the basic wallet functions and delivers most of what users would expect a GUI wallet: it is simple to install, has a graphical setup wizard, can restore from existing wallet seeds, and can send and receive payments. Considering that the 0.7.0 release of decrediton was in a very much “alpha” state, this release constitutes a huge leap forwards in terms of improved user experience.
Beyond the decrediton progress, Paymetheus has added support for a new stake pool integration API, which simplifies the process of using a stake pool with Paymetheus. Once a user has registered an account at a stake pool, they can copy an API key from their stake pool login into Paymetheus, and then Paymetheus handles the rest of the stake pool setup. Prior to adding this API to stake pools, the user would have to generate a pubkey, copy and paste it to the stakepool, hit a button, and then copy and paste the multisig address back into Paymetheus. We had originally wanted to make even signup for a stake pool possible via this API, however, this created an obvious Denial-of-Service vector and had to be removed. The new process for using a stake pool is much less error prone and avoids confusion on part of users, so it is a notable improvement.
By the next release, both Paymetheus and decrediton will support automatic ticket buying and have an interface for users to set their voting preferences. Between this release and the next, we will make minor releases that include these new features in the GUI wallets, so that users can test them and give us feedback. We will announce these minor releases and provide updated binaries to make it easy for everyone to test out the new features as they are added.
Public keys
The file cmd/dcrinstall/pubkey.go contains the decred public key which is used to check the signed manifest in the release. You can compare the contents of this file to what you get from a keyserver to confirm that dcrinstaller is using the proper key.
BIG update just dropped.
https://forum.decred.org/threads/dd-21-v0-8-0-02-13-17.5111/
A lot has happened in the past several weeks since the 0.7.0 release of Decred. On the valuation front, the exchange rate has gone up substantially from a low of approximately USD 0.43 on December 28th to an all-time-high of USD 3.31 on February 5th, which has since settled around USD 2.50. The number of downloads of binaries from GitHub for the 0.7.0 release has gone up by a factor of 5 or more, and we have a substantially larger number of users in Slack and other chat channels. This substantial improvement in valuation, exposure and community engagement is due mainly to our recent work with several marketing contractors via the dev org, DHG, which I will say more about below.
Beyond matters related to Decred's valuation, there has been substantial progress on several of our software projects and with their documentation. The bulk of the code needed to enable hard fork voting has been completed, and it will be demonstrated live on testnet over the next few weeks, via a corresponding website that shows its progress. A substantial design overhaul has been completed during the past several months, which includes a new logo and changes to every project website. decrediton, the cross platform GUI, has made a huge amount of progress, going from an alpha project to a solid beta in a single release. Paymetheus, the native Windows wallet, now uses the new stakepool API integration to simplify setting up ticket buying with a stakepool. Several additions and updates have been made to the Decred documentation site by documentation contractors. More detailed descriptions of our progress can be found below.
Marketing, Documentation and Development Contractors
Per the recent 2017 Decred Roadmap, a deliverables-driven RFP process did not end up working out very well, so we have since changed our RFP process to be need-driven by domain. The dev org, DHG, has contracted 5 people to do marketing, 2 to do documentation and 3 to do development work. So far, this arrangement is working out very well and has led to substantial progress on the marketing and documentation fronts.
The marketing contractors have met with considerable success in increasing awareness, engagement and generally creating demand for decred. The puzzles created by @coin_artist have been particularly effective at drawing new users to our Slack channels and creating a general buzz about Decred. The efforts of @Daniel, @Emilio Mann, @Tivra and @Dyrk have served to grow our community, engage new users, create additional demand, support regional markets and broaden our social media support. Overall, this marketing work has been very successful to date.
The documentation and development contractors have started doing work more recently, so they haven't had as much time as the marketing contractors to get their deliverables flowing. @gratefulcheddar and @Shadowlance have been pushing out a lot of new and updated documentation over the past few weeks, and their output should become much more apparent over the next few months as they shore up the Decred documentation. @karamble has pushed out a lot of web development work in the past couple weeks, which has made an otherwise monolithic release much more manageable. @raedah has submitted several pull requests that improve dcrwallet's ticketbuyer, which should lead to improvements in the fee market for tickets. We expect the contributions from our documentation and development contractors to become more apparent in the coming months.
Substantial Design Update
A design overhaul of Decred was initiated in RFP-7 several months ago with @linnutee, and it is being brought to completion with the 0.8.0 release. The work includes a new logo, design updates for every project website and a branding package for other Decred-related projects to use. As you can imagine, updating every website the project maintains is a pretty daunting task, so beyond @linnutee and sander doing all the design and coding, we had @karamble integrate and audit their work, and @Shadowlance contributed text copy in several places.
For those who are interested in the details of this work, I recommend you give @linnutee's recent Medium post a read.
Hard Fork Voting Demo
While it's certainly less tangible than a surge in the exchange rate, the core of Decred is based around decentralization as a process, and the first major step in that process, hard fork voting, has been prepared for a demo on testnet. Stakeholders will soon have the ability to vote on defined issues in dcrwallet, and this will allow Decred to episodically hard fork based on how its stakeholders vote. If 75% or more of the stakeholders vote “yes” for a given issue during a voting period, it will go into effect approximately 4 weeks later (on mainnet), and this includes “hard fork” consensus changes. Getting this code ready has been particularly challenging since it is all consensus-related code, which is notoriously unforgiving when it comes to bugs.
The testnet demo has an accompanying webpage that allows users to watch each step in the voting process occur. We chose to have a single issue for the demo, to increase the block size from 1 MiB to 1.25 MB, and we felt this was appropriate since the block size has been so contentious for Bitcoin. There are 3 stages to hard fork voting, which is reflected on the demo website, and this process draws from some parts of the BIP0009 soft fork process from Bitcoin. First, Proof-of-Work miners must update their dcrds to the latest release until a threshold percentage, 75% in the case of testnet, of blocks in a rolling window show the new block version in their header. Second, Proof-of-Stake miners, i.e. stakeholders, must update their voting wallets to the latest release of dcrwallet until a threshold percentage, 75% for testnet, of votes in blocks in a fixed window show the new vote version. At the end of the first interval with 75% or greater support for the new vote version, the stake version is incremented to the new version and a voting period begins. Once a voting period comes to an end, any issues that receive 75% or greater 'yes' votes are considered complete and will become active after a lock-in period. Issues that receive 75% or greater 'no' votes are considered dead and will not be voted on further. If an issue does not receive a 75% or greater vote either direction, the issue remains up for voting in future voting periods until an expiration time is reached. The process of upgrading PoW miners, PoS miners and voting will occur on an ongoing episodic basis and allow Decred's consensus code to evolve over time, according to the will of its stakeholders. We estimate that it will take 3-6 weeks for the testnet demo to have the block size increase voted in and for the hard fork to occur, so users can stop by and check the progress on the webpage.
Major GUI Wallet Progress
Until this release, only Windows users had the option of running a self-contained GUI wallet with Paymetheus, so we are pleased to announce that decrediton, a cross platform GUI wallet, is ready for use on Linux and OS X. decrediton now supports all the basic wallet functions and delivers most of what users would expect a GUI wallet: it is simple to install, has a graphical setup wizard, can restore from existing wallet seeds, and can send and receive payments. Considering that the 0.7.0 release of decrediton was in a very much “alpha” state, this release constitutes a huge leap forwards in terms of improved user experience.
Beyond the decrediton progress, Paymetheus has added support for a new stake pool integration API, which simplifies the process of using a stake pool with Paymetheus. Once a user has registered an account at a stake pool, they can copy an API key from their stake pool login into Paymetheus, and then Paymetheus handles the rest of the stake pool setup. Prior to adding this API to stake pools, the user would have to generate a pubkey, copy and paste it to the stakepool, hit a button, and then copy and paste the multisig address back into Paymetheus. We had originally wanted to make even signup for a stake pool possible via this API, however, this created an obvious Denial-of-Service vector and had to be removed. The new process for using a stake pool is much less error prone and avoids confusion on part of users, so it is a notable improvement.
By the next release, both Paymetheus and decrediton will support automatic ticket buying and have an interface for users to set their voting preferences. Between this release and the next, we will make minor releases that include these new features in the GUI wallets, so that users can test them and give us feedback. We will announce these minor releases and provide updated binaries to make it easy for everyone to test out the new features as they are added.
Public keys
The file cmd/dcrinstall/pubkey.go contains the decred public key which is used to check the signed manifest in the release. You can compare the contents of this file to what you get from a keyserver to confirm that dcrinstaller is using the proper key.
February 13, 2017, 05:37:42 PM
Here I wrote out 8 points why I like DCR, https://bitcointalksearch.org/topic/dcr-decentralized-credits-decred-2017s-dark-horse-08-update-1788901 feel free to read brothers.
Nice to see your point of view!!! Let's upgrade now, I can't wait XD
February 13, 2017, 02:26:01 PM
Here I wrote out 8 points why I like DCR, https://bitcointalksearch.org/topic/dcr-decentralized-credits-decred-2017s-dark-horse-08-update-1788901 feel free to read brothers.
February 13, 2017, 11:39:39 AM
Hope Decred wallet v 0.8.0 will be released tonight. I want to try new features and buy some tickets from the new wallet. Its really the long-awaited update in Decred history.
February 13, 2017, 10:44:53 AM
btw, if I want to run the daemon and wallet on two separate machines (different location and ISPs) would that cause a problem?
I will be staking on both too
I will be staking on both too
I have only used similar setup (daemon and wallet on separate machines) trough LAN. But if your wallet is succesfully connected to daemon trough rpc, i don't see any problem there. Maybe you should ask devs in slack about that, to be sure.
I did not phrase this correctly. Sorry about that.
What I meant is I want to run a daemon and a wallet on one machine and on the other machine, another instance of the daemon and that same wallet.
I'll ask on slack too
If you use same seed on two wallets, yes it causes issues. Use different wallet in another one.
February 13, 2017, 10:34:27 AM
btw, if I want to run the daemon and wallet on two separate machines (different location and ISPs) would that cause a problem?
I will be staking on both too
I will be staking on both too
I have only used similar setup (daemon and wallet on separate machines) trough LAN. But if your wallet is succesfully connected to daemon trough rpc, i don't see any problem there. Maybe you should ask devs in slack about that, to be sure.
I did not phrase this correctly. Sorry about that.
What I meant is I want to run a daemon and a wallet on one machine and on the other machine, another instance of the daemon and that same wallet.
I'll ask on slack too
February 13, 2017, 10:02:19 AM
is release 0.8.0 already out. Just checked on the official decred forum and it still says 0.7.0
February 13, 2017, 09:55:30 AM
btw, if I want to run the daemon and wallet on two separate machines (different location and ISPs) would that cause a problem?
I will be staking on both too
I will be staking on both too
I have only used similar setup (daemon and wallet on separate machines) trough LAN. But if your wallet is succesfully connected to daemon trough rpc, i don't see any problem there. Maybe you should ask devs in slack about that, to be sure.
February 13, 2017, 09:33:59 AM
btw, if I want to run the daemon and wallet on two separate machines (different location and ISPs) would that cause a problem?
I will be staking on both too
I will be staking on both too
February 13, 2017, 08:46:54 AM
I was trying to buy tickets a few hours ago, through the command line as I usually do. For solo mining
But this time, something went wrong with the transactions. It complained that the address does not exist or something.
But it's the same address I always use. I have batch files ready that I have used for months, no chance of a typo.
It seems one ticket transaction went through, but another three didn't and the coins have disappeared from my balance. In fact for all 4 transactions.
I am now almost 145 below what I should be in balance and have 1 ownmempoolticks in getstakeinfo
I restarted daemon and wallet but it didn't help.
What can I do? Is it possible that the coins just vanished?
I'll link this to slack as well to increase my chances of getting an answer
But this time, something went wrong with the transactions. It complained that the address does not exist or something.
But it's the same address I always use. I have batch files ready that I have used for months, no chance of a typo.
It seems one ticket transaction went through, but another three didn't and the coins have disappeared from my balance. In fact for all 4 transactions.
I am now almost 145 below what I should be in balance and have 1 ownmempoolticks in getstakeinfo
I restarted daemon and wallet but it didn't help.
What can I do? Is it possible that the coins just vanished?
I'll link this to slack as well to increase my chances of getting an answer
Have you already tried to recreate your wallet from seed?
I figure at this point, either the coins are safe and a reseed will show them (most likely scenario) or they are lost somehow (unlikely though)
Since the new wallet will be released very soon I'll just wait for it and do a reseed and also sync from scratch
I don't believe that you have lost anything. The coins won't leave your wallet, when purchasing tickets. When you recreate wallet, just make sure, that daemon is fully synced before reseed.
February 13, 2017, 08:33:52 AM
I was trying to buy tickets a few hours ago, through the command line as I usually do. For solo mining
But this time, something went wrong with the transactions. It complained that the address does not exist or something.
But it's the same address I always use. I have batch files ready that I have used for months, no chance of a typo.
It seems one ticket transaction went through, but another three didn't and the coins have disappeared from my balance. In fact for all 4 transactions.
I am now almost 145 below what I should be in balance and have 1 ownmempoolticks in getstakeinfo
I restarted daemon and wallet but it didn't help.
What can I do? Is it possible that the coins just vanished?
I'll link this to slack as well to increase my chances of getting an answer
But this time, something went wrong with the transactions. It complained that the address does not exist or something.
But it's the same address I always use. I have batch files ready that I have used for months, no chance of a typo.
It seems one ticket transaction went through, but another three didn't and the coins have disappeared from my balance. In fact for all 4 transactions.
I am now almost 145 below what I should be in balance and have 1 ownmempoolticks in getstakeinfo
I restarted daemon and wallet but it didn't help.
What can I do? Is it possible that the coins just vanished?
I'll link this to slack as well to increase my chances of getting an answer
Have you already tried to recreate your wallet from seed?
I figure at this point, either the coins are safe and a reseed will show them (most likely scenario) or they are lost somehow (unlikely though)
Since the new wallet will be released very soon I'll just wait for it and do a reseed and also sync from scratch
Jump to: