📅 Original date posted:2016-10-16
📝 Original message:On Sun, Oct 16, 2016 at 10:58 PM, Tom Zander via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> On Sunday, 16 October 2016 12:49:47 CEST Douglas Roark via bitcoin-dev
> wrote:
> > It's not the website's fault if wallet devs aren't updating their
> > statuses. Besides, "WIP" can mean an awful lot of things.
>
> As I said, it would be nice to get an updated version so we can see more
> than 20% readyness of wallets.
> The wallet devs not caring enough to update the status should be a worrying
> sign, though.
>
WIP for TREZOR means that we've made that hard part already (firwmare) so
we know it is feasible, yet we didn't spend enough time on finalizing all
the stack like our web wallet because we don't see any actual release date
yet. Considering current battles on BU hashpower, we decided simply sit and
watch (I already have popocorn).
SegWit is probably the most disruptive and most invasive change ever made to
> Bitcoin. We have miners actively saying they don't like it and this makes
> it
> a contriversial upgrade which means the network may split and other issues.
>
>
There're also many wallets which are impatiently waiting for segwit to be
released. Segwit is blessing for hardware wallets for many reasons. I
actually think that rolling out Segwit will increase security, because it
will reduce huge complexity in hardware wallets as it is today.
Slush
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/93d827a9/attachment.html>;
Marek Palatinus [ARCHIVE] /
npub1xt…acz68
2023-06-07 17:54:05
in reply to nevent1q…7puq
Author Public Key
npub1xtqansnal58rjnnxvyke6kzuvxsz0twg4456awy6ff0525yqgjxqjacz68Seen on
wss://relay.nostr.bandPublished at
2023-06-07 17:54:05Event JSON
{
"id": "ba5f9c0db973f4ea8b3ce557874d3ad2d9f4d2df86b0dd074187e7391e92fb07",
"pubkey": "32c1d9c27dfd0e394e66612d9d585c61a027adc8ad69aeb89a4a5f455080448c",
"created_at": 1686160445,
"kind": 1,
"tags": [
[
"e",
"013851964e0006d489daca620e14c7c6c63358b79bff34620f9703c31bcdc761",
"",
"root"
],
[
"e",
"111c247ad580291ff707f307314f9e314240e18129ac8ddf7c9aa10939d4c19e",
"",
"reply"
],
[
"p",
"93f19c9fec7799ea61ec4c1090ae8661c1b1c4c2bfdc1417f982e68d89dc7f0b"
]
],
"content": "📅 Original date posted:2016-10-16\n📝 Original message:On Sun, Oct 16, 2016 at 10:58 PM, Tom Zander via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e On Sunday, 16 October 2016 12:49:47 CEST Douglas Roark via bitcoin-dev\n\u003e wrote:\n\u003e \u003e It's not the website's fault if wallet devs aren't updating their\n\u003e \u003e statuses. Besides, \"WIP\" can mean an awful lot of things.\n\u003e\n\u003e As I said, it would be nice to get an updated version so we can see more\n\u003e than 20% readyness of wallets.\n\u003e The wallet devs not caring enough to update the status should be a worrying\n\u003e sign, though.\n\u003e\n\nWIP for TREZOR means that we've made that hard part already (firwmare) so\nwe know it is feasible, yet we didn't spend enough time on finalizing all\nthe stack like our web wallet because we don't see any actual release date\nyet. Considering current battles on BU hashpower, we decided simply sit and\nwatch (I already have popocorn).\n\n\nSegWit is probably the most disruptive and most invasive change ever made to\n\u003e Bitcoin. We have miners actively saying they don't like it and this makes\n\u003e it\n\u003e a contriversial upgrade which means the network may split and other issues.\n\u003e\n\u003e\nThere're also many wallets which are impatiently waiting for segwit to be\nreleased. Segwit is blessing for hardware wallets for many reasons. I\nactually think that rolling out Segwit will increase security, because it\nwill reduce huge complexity in hardware wallets as it is today.\n\nSlush\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/93d827a9/attachment.html\u003e",
"sig": "52d0d325487047bcc1a87ee212574ea370bc67ac27b34c6bff5c2cf21e0862cb0f3e44b7e887b25a5aa2999f9b6f5a072f569c7901b760ba12ff822eb7596265"
}