Since the SW is activated, how can a user now send a SW transaction? E.g., I'm using an Electrum wallet, a BitPie wallet, and have a qt full node, and sometimes I also send from/to an exchange or shapeshift. That whether a transaction is SW or not, depends on the sending address, receiving address, or both? How can I create a SW transaction to lower the fee?
Ledger has supported Segwit recently. Bitcoin Core is another option but you can only do so using CLI at the moment. Electrum dev said on github that next version will be released soon letting you create and send segwit addresses.
IMO, most major wallets are ready for segwit. They just didn't let you do so before Segwit finally activated.
Post
Topic
BoardDevelopment & Technical Discussion
Re: Post your SegWit questions here - open discussion - big week for Bitcoin!
by
hudd
on 24/08/2017, 11:09:29 UTC
My question: How can I know if one transaction is Segwit transaction or not. As far as I know, not all P2SH addresses are segwit addresses.
Post
Topic
BoardDevelopment & Technical Discussion
Re: Post your SegWit questions here - open discussion - big week for Bitcoin!
In that case, I don't think you'll ever get a chance of buying it.
Buy now at lower price, I don't think so that there is going to be any decline after maximum of 0.0003.
I'm seeing 0.000399998 right now. Good luck catching the knife at 0.0003. It won't stop at even 0.0001.
Both ZEC and ZCL was over hyped and now are slowly bleeding due to inflation, 7200 new coins are being mined everyday until the halving in next 4 years. We will have 10.5 million coins in circulation after 4 years instead of 750k at the moment.
However that's just the fork-ready code, the actual activation would take several months:
Quote
Dates with an asterisk are when we expect to release soft fork-ready code. The code will not be released until it has been well reviewed, and the actual fork will take time to activate
I would expect about 70 min for a 200 GB HDD to refresh 100,000 blocks. Still I would not hold up 0.9 over this since there are simple fixes for a user.
I had to refresh from beginning with 820,000 blocks. Monero currently has low transaction volume, the coin has to prepare for the situation which significant adoption occurred and number of transaction shoot up 10 folds. In that case see the problem would be very serious with refreshing (together with syncing database and disk space usage).