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

[ocminer]

hello i just mining decred using cpuminer-opt with suprnova pool but somehow it's not getting properly, my question is , what is wrong?

this is my setting, can someone tell me whats wrong with my setting??

./cpuminer -a blake -o stratum+tcp://dcr.suprnova.cc:2252 -u xxxxx.satu -p satu -t 7

thanks

It's not blake, it's blake256  or maybe even decred in cpuminer

[TTRAIN]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

[francism]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

When DCR reach the top 10 on coinmarketcap it will get some attention. Yobit might immediately fix the wallet issue.

[gtzanap]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

Not likely. They have other bad wallets too, which they never bothered fixing even after many months.

If I were you, I'd put a sell order for everything at or slightly below market price. Eventually it would get fullfilled. Then I would withdraw the btc into another Exchange to buy back dcr

[algreen]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

Dont worry, DCR on Yobit catching up with the price indices of other stock exchanges late, so no need to hurry, when the price will grow you can sell DCR on Yobit with profit, but you need to wait a little more time.

[irukandji]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

When DCR reach the top 10 on coinmarketcap it will get some attention. Yobit might immediately fix the wallet issue.

Is that still not fixed? Those guys are fools to themselves (as Roy Slaven and HG Nelson would say)

[Alexoz]

Way more than $5... Re-do the math!

[Penttikuisma]

I have a few hundred dcr on yobit. You think any chance you think they'll ever fix their wallet?

If you decide to wait, you might be waiting forever. Consider selling with little loss and withdraw your Btc to another exchange.

[Penttikuisma]

https://hardforkdemo.decred.org/ Waiting with interest, when first voting starts in mainnet. Also Coinbase presentation is getting closer and the new release https://github.com/decred/dcrd/milestone/15 Big and good things ahead for Dcr this year.

[testlabstake]

Good job decred. Need more marketing ihmo.

[EmilioMann]

Awesome video from our Brazilian Community.  Subtitled in English.  Check it out!

https://www.youtube.com/watch?v=dsGjQgV8xcY

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

[testlabstake]

Cool video. good job.

[pauloaragaomelo]

Awesome video from our Brazilian Community.  Subtitled in English.  Check it out!

https://www.youtube.com/watch?v=dsGjQgV8xcY

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

Good video, Emil!
It's very explicative for us

#GoDecred

[dbt1033]

Definitely some fractal similarities here to our last pump... that head and shoulders fear formation that mewns

[testlabstake]

Great team working on decred. But marketing needed.

[Alexoz]

Great team working on decred. But marketing needed.

We do... We do!

[bspus]

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)

[rotzbouf]

Looking the ticket price, I noticed that it is quite stable the last time.
Just wondering why it got stable at this rate while before it was highly volatile.

[MarSas]

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)

Take a look at block times. Extremely fast, less than a minute. I guess that is the reason the ticket expired. Network latency.

[bspus]

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)

Take a look at block times. Extremely fast, less than a minute. I guess that is the reason the ticket expired. Network latency.

Blocks at 8:35:04, 8:37:40 (vote), 8:43:19 (revocation). 8:57:22

I don't see those extremely fast ones you mention