Topic: How to use Segwitaddress.ORG ? - page 2. (Read 671 times)

Im new to segwit and my first transaction (well recieved) was from the current signature campaign, and I can confirm btc.com seems to be working fine at displaying bech32 trasactions, not sure if the ones that begin with 3 are as cheap as bech32, but Lauda's transaction was 220 Satoshis/vByte for a 22 outputs transaction. There is still one person that didn't switch to segwit. Im not sure how the fee would get calculated for a transaction that is sent to a mix of bech32, nested and legacy addresses:

https://btc.com/4063544c31e9258a2a7eb37090bbc81f090259abaabb3f4e3fe79b25e317db59

To get the the reduced fee all outputs must be segwit?

That would likely only muddy the waters further, as that's a thread about Lightning, while the confusion here lies with SegWit.  While people tend to refer to them in the same breath whilst talking about improvements, they are very separate things.
  


Reading all the BIPs might be overkill, but on the other hand, I find the vast majority of clips about Bitcoin on YouTube completely unwatchable.   Anything by Andreas is usually a safe bet, but again, that particular link is an older video, so I don't know if there's a more recent one that's worth checking out.  The Segregated Witness wiki page might be worth a shot too.

The easiest way to demonstrate that SegWit has indeed been activated is to simply look at a list of the latest blocks being produced, whether it be XBT.eu or any other such site.  You can plainly observe that the vast majority of blocks being produced are over 1MB in size, something that would never have been possible prior to the activation of SegWit.

If anyone is still using software that doesn't support SegWit, that software won't see as plainly as you can that the blocks are larger than 1MB.  They'll still see that every block is less than 1MB because they simply ignore the data in (what should be correctly referred to as) the new "witness space" (which I assume is what they meant by "block extension").  In effect, some nodes will now read the same blocks differently to others, depending on whether they support SegWit or not.  When you send a Legacy transaction (i.e. not SegWit), all the data, including the signature data goes in the "base" 1MB space and every node can read that.  When you send a SegWit Transaction, the signature data gets to take advantage of the extra witness space, in order to fit more transactions in the base 1MB, but only SegWit-compatible nodes will recognise them.  This means we can effectively increase the blockweight in a backwards-compatible and entirely voluntary way.

That's super cheap. Is it limited to certain transactions or it's for all types of transactions?
What's your average fee/byte for each transaction? I am currently paying more than 200 sats/byte.


Don't worry, will keep it to me as always. Did it all in a hurry, when our campaign manager told us about the advantages of using SegWit addresses over non-SegWit and was intending to make it mandatory in a few weeks. Not their fault, it was all mine. But I will always remember your advice, thanks.

DO NOT GIVE YOUR PRIVATE KEYS TO ANY WEBSITE!  THAT'S LIKE THE COMBINATION TO YOUR SAFE!

I've switched to using the btc.com explorer it will show balances and all the normal stuff for bech32 addresses.

https://btc.com/0daf4879f56234f39fbf9cf825e38458f75f4a22f5d2289d0dda9af78aa8df8f

That's an example of a recent tx of mine where I paid a fee of 0.00007910 on a virtual transactions size of 113 bytes. It adds up to a reasonable saving.

A thumbs up to you, the message has been successfully verified.
I saw one more thing that I can't check bech32 addresses over blockchain.info's explorer?! It says "Unrecognized search pattern."
Can you guide me more on that? I mean, any explorers that support bech32 addresses to show balance and transactions?
Things are getting easier for me with SegWit, I hope that less fee and quick confirms will be back in my life. 

In Electrum go to the Addresses tab select the address with right click Sign/verify Message put your message in and click sign, it will ask for your password and then give you the signature.

Here's one I just did:

Message: Test signed message from TheQuin

Address: bc1q94c5auxrxzhgk5uyuee0e2nu2xwf5wz8r67sj5

Signature: IJ5AyA/s7laKapHX1Ml1XPn37QpiER/5ahQvDbYefd4FLF4Owi48Jvr23VeAG/2JZ3Yt/mHndSJjvAy9WFq1uxI=

The only drawback is that only people with a wallet that is capable of using Bech32 addresses can verify it. So you should be able to verify that on your Electrum but not on the websites that do verifications. It is not possible to verify the Segwit addresses starting with 3 at all because of the way they are encapsulated in a multisig address.

I'll be opening a thread in Meta and telling people about the situation, so as to stop a "possible hack" of my account.


Thanks to you and everyone who helped me out, I've finally downloaded Electrum wallet, saved my key and generated SegWit addresses as well.
Don't know how will I be able to sign messages from these bech32 addresses, though. But I am all fine now and hope that it will be beneficial for me as well as the senders/receivers from/to whom I get/send Bitcoins. Will sign a message and post a thread in Meta in a few moments.

That's good news. I always keep the private keys to all my old addresses for that reason. As was already pointed out if a key is compromised then potentially someone else could also sign a message but it is an unlikely way to hijack a bitcointalk account.


I'm not sure exactly which queries you mean. If it is about signing messages using Segwit addresses then the answer is not to use P2SH-P2WPKH addresses (the ones that start with 3) but to use bech32 native Segwit addresses starting bc1.
I've been using this on Electrum since mid-November. With Electrum it is easy to use multiple wallets so I've kept my legacy address wallet so I can still receive payments from sites that don't yet support withdrawals to bech32 addresses. Hopefully, after Core 0.16.0 is released then everyone will start to introduce support and I can retire the legacy wallet.

Yea, that will do IF the people going to send you coins check the meta section in the first place.
You can alternatively keep the private key of the address in case it's not actually compromised and  you eventually receive any payments there.
But DO NOT give it out as a receiving address any more.

Will electrum allow me to send coins to multiple addresses in a single transaction with a SegWit address, just like I do with my Legacy address?

---

I won't be using that address anymore, but to make everyone aware of the same, what should be done? Making a thread in Meta and signing a message with that address saying that its private key was used on a website and I believe it's now compromised, so don't send any coins there if someone asks anything by signing a message from that address. Will it do?

Thank you for making that clear and I stand corrected

Getting complicated since someone forked Segwit something and uses it for B2X

Not got a weeks to read and digest "BIPs 141, 143, and 144 " but do you have a Youtube link for this please
because the one I watched told a different story completely but is from 2016
https://www.youtube.com/watch?v=DzBAG2Jp4bg

Basically he says the block gets spread over blk.dat and a "Block Extension" file using Segwit but i would like
to get my facts right about this and understand why it's not just a case of changes on the nodes but also
code in the wallet.

Maybe better you answer this question here https://bitcointalk.org/index.php?topic=2679337.new#new
or open a new thread and PM me the link where we can go into detail because I am sure others would like to understand this too

This is strictly untrue. Segwit as specified by BIPs 141, 143, and 144 is activated on Bitcoin. The original segwit2x proposal is not and is dead. Segwit is absolutely implemented for Bitcoin and was not dropped.

You can say that again because Segwit is not implemented for Bitcoin and has been dropped but
it is confusing because I hear about Segwit wallets and I am not talking about Segwit2x here that uses B2X

Segwit proposal would had lead to bigger block sizes but they tried to redefine how they count bytes
to hide this for some reason which i really don't like
See https://www.youtube.com/watch?v=DzBAG2Jp4bg

You can always reuse addresses infinitely as long as you have the private key.
Wallets generate new addresses so people looking at the blockchain will not be able to track your transactions easily.
No matter how many addresses you use you'll always be able to control the funds if you used the same wallet to create the address.

Yes, you can use them.
You can't sign messages with Green Address or Greenbits because they are multisig addresses, meaning GreenAddress holds one set of private key while you have the other.

You can reuse any address (segwit or legacy ) as much as you like as long as you have the private key.

In bitcoin it's best to be paranoid about security so don't use that address anymore and consider it compromised.
If it's really compromised then whoever holds the private key can sign messages also.

With electrum you keep the same addresses. Once you start the software, it will ask you if you want a legacy wallet or a segwit address, and then you get a wallet file, and this file will give you access to your coins, much like Bitcoin Core's wallet.dat, and also you will get a seed which can generate the content of this file anywhere you are at without holding the file (so save it somewhere that nobody can see it or better memorize them and destroy it).

Not so sure about the Electrum part as I'm still not getting it, but all I can see is that, addresses are getting changed back to back whenever I get out of some apps (GreenBits and GreenAddress) and get back in. If it will be like this, how will I be able to receive coins multiple times over a single address when there will be a change after each transaction? Why can't we see a private key instead, so that we might just put it in some compatible wallet and start using it?

You can reuse segwit addresses an infinite amount of times, just like legacy addresses (im talking about in general, not about this specific website hich im not even going to click) , but please, do not put your private key on that website or on any website ever, ideally never export your private key, your wallet software should never show your private key. To move your founds from one wallet to another, then just send yourself the coins from one address to another.

Samourai wallet? Can I use the same address to get paid more than once? Hope it's not the same as Blockchain.info's addresses, as they change once we use it.


Yes, that transaction was done by me only. And I checked the source, which is why I used my private key there when I was online. I believe I should not receive any coins over that address anymore but should keep it to sign messages. Can you answer my queries told in the same comment?

It looks like the last tx out of that address was a couple of days ago to the same destination address as previously used, so I think Stedsm's funds are safe.
From searching around it looks like it is not a phishing site it's an open source paper wallet generator https://github.com/coinables/segwitaddress
But as Carlton Banks said NEVER enter a private key into a website and it would best to assume that key is now compromised.