Topic: [ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 186. (Read 1201327 times)
March 03, 2017, 09:04:01 AM
nope
March 03, 2017, 09:02:16 AM
Decred followers, why don`t you add Decred to shapeshift.io?
They don't accept any request at the moment!
Early March for Coinbase
Oh did it already happen?
March 03, 2017, 08:52:53 AM
Decred followers, why don`t you add Decred to shapeshift.io?
They don't accept any request at the moment!
Early March for Coinbase
March 03, 2017, 07:43:40 AM
Decred followers, why don`t you add Decred to shapeshift.io?
March 03, 2017, 07:42:29 AM
Great team working on decred. But marketing needed.
More marketing will come... Have some patience, we just did a huge marketing blitz. Remember, we present at coinbase very soon 😉
But how soon? ...no answer.
March 03, 2017, 07:37:01 AM
Join us on slack 900 people already! slack.decred.org
March 03, 2017, 03:31:36 AM
Great team working on decred. But marketing needed.
More marketing will come... Have some patience, we just did a huge marketing blitz. Remember, we present at coinbase very soon 😉
March 03, 2017, 03:30:15 AM
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.
Just wondering why it got stable at this rate while before it was highly volatile.
I think some large holders are trying to stabilize the price so that everyone can have reasonable fees 😀
March 02, 2017, 10:26:09 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
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
March 02, 2017, 09:59:03 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
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.
March 02, 2017, 09:46:44 AM
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.
Just wondering why it got stable at this rate while before it was highly volatile.
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
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)
March 02, 2017, 12:00:00 AM
Great team working on decred. But marketing needed.
We do... We do!
March 01, 2017, 06:24:15 PM
Great team working on decred. But marketing needed.
March 01, 2017, 04:06:03 PM
Definitely some fractal similarities here to our last pump... that head and shoulders fear formation that mewns
February 28, 2017, 02:20:34 PM
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
https://www.youtube.com/watch?v=dsGjQgV8xcY
https://twitter.com/decredproject/status/835571055565684736
Good video, Emil!
It's very explicative for us
#GoDecred
February 28, 2017, 01:36:52 PM
Cool video. good job.
February 28, 2017, 01:34:39 PM
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
https://www.youtube.com/watch?v=dsGjQgV8xcY
https://twitter.com/decredproject/status/835571055565684736
February 28, 2017, 12:44:17 PM
Good job decred. Need more marketing ihmo.
February 28, 2017, 10:17:57 AM
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.
Jump to: