Quote from: thd26bct on November 27, 2017, 07:55:41 AM

Quote from: tm2013 on November 26, 2017, 10:10:55 PM

By looking at the BitSend SegWit code, I'm going to guess that SegWit is not yet active. BitSend miners have been signaling via a version bit that the wallet's BIP 9 requirements aren't aware of (BIP 91 from a poorly-maintained pool? Not sure; it is the cause of the current wallet warning). But, at least 1 block has been mined in the last 1728 blocks that signals the correct BIP 9 version bit. That should mean SegWit will fully activate on BitSend in roughly 2.5 days. Maybe one of the devs who implemented the code this way can confirm, but I am 99% sure that this is the current case.

I am not coder, so I can not really understand what you mentioned there. Have the Segwit finally finished? Thank you.

The first features now online. Segwit is just "locked in" now. We need nore a signal block.

Code:

{
"chain": "main",
"blocks": 400706,
"headers": 400706,
"bestblockhash": "000000000272fb74e60e8c18e889170f19c50c5e3d9ed32bd846da97b5165c1d",
"difficulty": 96.9704816456757,
"mediantime": 1511771235,
"verificationprogress": 1,
"chainwork": "000000000000000000000000000000000000000000000000009af9536db98302",
"pruned": false,
"softforks": [
{
"id": "bip34",
"version": 2,
"reject": {
"status": true
}
},
{
"id": "bip66",
"version": 3,
"reject": {
"status": true
}
},
{
"id": "bip65",
"version": 4,
"reject": {
"status": true
}
}
],
"bip9_softforks": {
"csv": {
"status": "active",
"startTime": 1503255158,
"timeout": 1607990400,
"since": 366336
},
"segwit": {
"status": "started",
"bit": 1,
"startTime": 1503255158,
"timeout": 1607990400,
"since": 355968
}
}
}

Best Regards Christian