[ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 185.

template

hero member

Activity: 1085

Merit: 500

DCR price move very slow (the tortoise) so if you are hasty man do not buy 2018-2019 you can see $5+
You can find fast profit with other coins myself get $5000 USD profit with PIVX within a week buy-sell
Buy little DCR for future Tongue

slow slow very slow

anarchrist

full member

Activity: 151

Merit: 100

I hope it reaches 3$ within this month lets see

Alexoz

sr. member

Activity: 248

Merit: 250

One World

All good it was just a warm up...

dbt1033

legendary

Activity: 1274

Merit: 1000

Quote from: dranster on March 05, 2017, 12:45:34 AM

Quote from: dbt1033 on March 04, 2017, 09:27:33 PM

Don't focus on the price... focus on what Decred will be capable of in 1/2 year. That should answer all of your questions.

Seriously dude WTF?

You were pro hyping this shitcoin constantly, and made over 50 BTC
.
You even created a speculation thread and pumped it up in btctalk.

Now you sold your bags and telling others to not focus on the price

So nice of you... Grin

Don't know what your problem is... I'm just trying to say don't be depressed about the price. Decred has a lot of good things coming that will propel it to the top of the food chain. I still have a ton of Decred. My signature is still Decred. I still work for Decred.

Chill out man.

dranster

hero member

Activity: 546

Merit: 500

Quote from: dbt1033 on March 04, 2017, 09:27:33 PM

Don't focus on the price... focus on what Decred will be capable of in 1/2 year. That should answer all of your questions.

Seriously dude WTF?

You were pro hyping this shitcoin constantly, and made over 50 BTC
.
You even created a speculation thread and pumped it up in btctalk.

Now you sold your bags and telling others to not focus on the price

So nice of you... Grin

IncludeBeer

legendary

Activity: 1164

Merit: 1010

Quote from: IncludeBeer on March 04, 2017, 03:13:09 PM

For the last 12+ hours, I've been getting stratum_subscribe timeout errors while trying to mine at Suprnova pools. The pool looks fine though...is it just me? I'm also mining XMG at Suprnova, and am having the same exact issue. Any ideas?

Update: Actually, I can't seem to mine at all. I tried different pools, then tried different coins. My connectivity is fine (been playing games and streaming tv all day). Any ideas what might be issue?

dbt1033

legendary

Activity: 1274

Merit: 1000

Don't focus on the price... focus on what Decred will be capable of in 1/2 year. That should answer all of your questions.

Praxis

legendary

Activity: 1118

Merit: 1004

Quote from: AncientEnemy on March 04, 2017, 01:05:33 PM

which price you think DCR can reach in the next few months?

Look at Dash, that will be DCR's price when people realize the potential of Decred is superior to what Dash accomplished Cheesy

IncludeBeer

legendary

Activity: 1164

Merit: 1010

For the last 12+ hours, I've been getting stratum_subscribe timeout errors while trying to mine at Suprnova pools. The pool looks fine though...is it just me? I'm also mining XMG at Suprnova, and am having the same exact issue. Any ideas?

EmilioMann

legendary

Activity: 2184

Merit: 1028

#mitandopelomundo

$10 dollars at the end of this year and $30 or more at the end of 2018

AncientEnemy

member

Activity: 108

Merit: 10

Quote from: Jumanji7 on March 04, 2017, 01:11:55 PM

15-20 USD

expensive! no? it's a dream btw.

Jumanji7

sr. member

Activity: 322

Merit: 250

15-20 USD

AncientEnemy

member

Activity: 108

Merit: 10

which price you think DCR can reach in the next few months?

Alexoz

sr. member

Activity: 248

Merit: 250

One World

Quote from: ytcoinartist on March 03, 2017, 08:14:42 PM

New Decred/Ubiq Collaborative Puzzle:

https://twitter.com/decredproject/status/837811331327754241

Ubiq made a nice blog post about the puzzle:
https://medium.com/the-ubiq-report/puzzle-with-mining-system-prize-c13de84d36c1#.qzxn35lki

TLDR: Puzzle Gif that rewards the solver with a new gpu mining system.

FWIW: Over the past year, Ubiq, a new ETH fork and previously known as Jumbucks, has been supporting the Decred community with an active DCR stake-pool and DCR help-desk. As of last Sunday, the two cryptos can be dual mined.

Link to puzzle gif download: https://i.cubeupload.com/VZZwNW.gif

Thanks to you!

ytcoinartist

jr. member

Activity: 46

Merit: 2

New Decred/Ubiq Collaborative Puzzle:

https://twitter.com/decredproject/status/837811331327754241

Ubiq made a nice blog post about the puzzle:
https://medium.com/the-ubiq-report/puzzle-with-mining-system-prize-c13de84d36c1#.qzxn35lki

TLDR: Puzzle Gif that rewards the solver with a new gpu mining system.

FWIW: Over the past year, Ubiq, a new ETH fork and previously known as Jumbucks, has been supporting the Decred community with an active DCR stake-pool and DCR help-desk. As of last Sunday, the two cryptos can be dual mined.

Link to puzzle gif download: https://i.cubeupload.com/VZZwNW.gif

Wheatclove

hero member

Activity: 606

Merit: 500

Quote from: bspus on March 03, 2017, 05:24:20 PM

Quote from: Wheatclove on March 03, 2017, 02:49:09 PM

Quote from: bspus on March 02, 2017, 09:19:20 AM

Quote

08:35:04 2017-03-02 [INF] WLLT: Connecting block 00000000000006c0af1d5bc56213a056d2ab7a239bead873336e8f26691949a9, height 111891
08:37:40 2017-03-02 [INF] WLLT: Voted on block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97 (height 111892) using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (vote hash: e7fa0202e8f8ccec0e6865ac77ec1cbe337c5aa7fc1e6335a0b763cb5b7856b3)
08:37:40 2017-03-02 [INF] WLLT: Connecting block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97, height 111892
08:43:19 2017-03-02 [INF] WLLT: Revoked missed ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (tx hash: 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662)
08:43:19 2017-03-02 [INF] WLLT: Connecting block 000000000000061a8113e68ef0ba67f0a6792e7a770f85bfa255efce5d5f24ae, height 111893
08:43:19 2017-03-02 [INF] TMGR: Inserting unconfirmed transaction 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662
08:57:22 2017-03-02 [ERR] WLLT: Cannot handle chain server voting notification MissedTickets: Error encountered attempting to create revocation using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103: -22: TX rejected: transaction already exists
08:57:22 2017-03-02 [INF] WLLT: Connecting block 00000000000003dec8ab8b1d56e08787bfa46ccb9e74d9ac8746a1e998cc7196, height 111894
09:00:13 2017-03-02 [INF] WLLT: Connecting block 0000000000000317128a57f9ac382523e5bc5554c9e802b32067cc350a6f1318, height 111895
09:03:50 2017-03-02 [INF] WLLT: Connecting block 0000000000000521fc1242064c8ceba8ba14235bb531053e3ec6458f47110842, height 111896

I had a ticket revoked this morning. I was online (solo staking) and this is what the wallet output looked like.
Can someone explain in plain english why this happened and what I could have done to avoid it?

(I'll link to slack as well)

I don't think it actually revoked. As far as I know, tickets only revoke if they reach their expiration without being used to vote. I think your ticket was called to vote one block before it expired. The unconfirmed vote blocked the ticket expiration/revocation. The wallet tried to revoke the ticket, but couldn't because it was just called to vote in the previous block.

I could be wrong

Missed tickets are also considered revoked... or is it the other way around?
From getstakeinfo I see that I have two tickets total that were both missed and revoked.

The first one was months ago. I had a computer crash and was offline several hours before I could tend to it.
The second was the one I posted about. Missed and revoked while wallet and daemon were online (and unlocked of course)

Yep I was wrong

bspus

legendary

Activity: 2165

Merit: 1002

Quote from: Wheatclove on March 03, 2017, 02:49:09 PM

Quote from: bspus on March 02, 2017, 09:19:20 AM

Quote

08:35:04 2017-03-02 [INF] WLLT: Connecting block 00000000000006c0af1d5bc56213a056d2ab7a239bead873336e8f26691949a9, height 111891
08:37:40 2017-03-02 [INF] WLLT: Voted on block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97 (height 111892) using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (vote hash: e7fa0202e8f8ccec0e6865ac77ec1cbe337c5aa7fc1e6335a0b763cb5b7856b3)
08:37:40 2017-03-02 [INF] WLLT: Connecting block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97, height 111892
08:43:19 2017-03-02 [INF] WLLT: Revoked missed ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (tx hash: 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662)
08:43:19 2017-03-02 [INF] WLLT: Connecting block 000000000000061a8113e68ef0ba67f0a6792e7a770f85bfa255efce5d5f24ae, height 111893
08:43:19 2017-03-02 [INF] TMGR: Inserting unconfirmed transaction 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662
08:57:22 2017-03-02 [ERR] WLLT: Cannot handle chain server voting notification MissedTickets: Error encountered attempting to create revocation using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103: -22: TX rejected: transaction already exists
08:57:22 2017-03-02 [INF] WLLT: Connecting block 00000000000003dec8ab8b1d56e08787bfa46ccb9e74d9ac8746a1e998cc7196, height 111894
09:00:13 2017-03-02 [INF] WLLT: Connecting block 0000000000000317128a57f9ac382523e5bc5554c9e802b32067cc350a6f1318, height 111895
09:03:50 2017-03-02 [INF] WLLT: Connecting block 0000000000000521fc1242064c8ceba8ba14235bb531053e3ec6458f47110842, height 111896

I had a ticket revoked this morning. I was online (solo staking) and this is what the wallet output looked like.
Can someone explain in plain english why this happened and what I could have done to avoid it?

(I'll link to slack as well)

I don't think it actually revoked. As far as I know, tickets only revoke if they reach their expiration without being used to vote. I think your ticket was called to vote one block before it expired. The unconfirmed vote blocked the ticket expiration/revocation. The wallet tried to revoke the ticket, but couldn't because it was just called to vote in the previous block.

I could be wrong

Missed tickets are also considered revoked... or is it the other way around?
From getstakeinfo I see that I have two tickets total that were both missed and revoked.

The first one was months ago. I had a computer crash and was offline several hours before I could tend to it.
The second was the one I posted about. Missed and revoked while wallet and daemon were online (and unlocked of course)

Wheatclove

hero member

Activity: 606

Merit: 500

Quote from: bspus on March 02, 2017, 09:19:20 AM

Quote

08:35:04 2017-03-02 [INF] WLLT: Connecting block 00000000000006c0af1d5bc56213a056d2ab7a239bead873336e8f26691949a9, height 111891
08:37:40 2017-03-02 [INF] WLLT: Voted on block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97 (height 111892) using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (vote hash: e7fa0202e8f8ccec0e6865ac77ec1cbe337c5aa7fc1e6335a0b763cb5b7856b3)
08:37:40 2017-03-02 [INF] WLLT: Connecting block 000000000000091b2b16580ded143bbb8e7fe224f868d6f87b44b00723676c97, height 111892
08:43:19 2017-03-02 [INF] WLLT: Revoked missed ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103 (tx hash: 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662)
08:43:19 2017-03-02 [INF] WLLT: Connecting block 000000000000061a8113e68ef0ba67f0a6792e7a770f85bfa255efce5d5f24ae, height 111893
08:43:19 2017-03-02 [INF] TMGR: Inserting unconfirmed transaction 763ee8603774c40a8f735621db7c8d199dff99e5f8b3214d6bcd09897a464662
08:57:22 2017-03-02 [ERR] WLLT: Cannot handle chain server voting notification MissedTickets: Error encountered attempting to create revocation using ticket bf87c95d568baa86a22b2d9b0338f903a98277968333911b0ff197e750301103: -22: TX rejected: transaction already exists
08:57:22 2017-03-02 [INF] WLLT: Connecting block 00000000000003dec8ab8b1d56e08787bfa46ccb9e74d9ac8746a1e998cc7196, height 111894
09:00:13 2017-03-02 [INF] WLLT: Connecting block 0000000000000317128a57f9ac382523e5bc5554c9e802b32067cc350a6f1318, height 111895
09:03:50 2017-03-02 [INF] WLLT: Connecting block 0000000000000521fc1242064c8ceba8ba14235bb531053e3ec6458f47110842, height 111896

I had a ticket revoked this morning. I was online (solo staking) and this is what the wallet output looked like.
Can someone explain in plain english why this happened and what I could have done to avoid it?

(I'll link to slack as well)

I don't think it actually revoked. As far as I know, tickets only revoke if they reach their expiration without being used to vote. I think your ticket was called to vote one block before it expired. The unconfirmed vote blocked the ticket expiration/revocation. The wallet tried to revoke the ticket, but couldn't because it was just called to vote in the previous block.

I could be wrong

pauloaragaomelo

sr. member

Activity: 546

Merit: 250