Author

Topic: Bech32 for Onion address V3 (Read 100 times)

jr. member
Activity: 168
Merit: 3
#Please, read:Daniel Ellsberg,-The Doomsday *wk
March 25, 2018, 11:08:12 AM
#4
No, they are not valid bitcoin address.

Valid bech32 bitcoin addresses are prefixed by bc (tb for testnet), and contains a witness program (which I'm sure the Tor rendezvous is not compatible with at all).

Thanks, I did suspect that  Grin
legendary
Activity: 3010
Merit: 3724
Join the world-leading crypto sportsbook NOW!
March 25, 2018, 10:47:28 AM
#3
My simple answer: no. As far as I understand, the tool from nullius is for encoding/decoding - NOT for generating... so your output looks valid. It should be a bech32 encoded address (which if decoded should return to you the original address  - but that is not a valid bitcoin public address.
full member
Activity: 198
Merit: 130
Some random software engineer
March 25, 2018, 10:47:06 AM
#2
No, they are not valid bitcoin address.

Valid bech32 bitcoin addresses are prefixed by bc (tb for testnet), and contains a witness program (which I'm sure the Tor rendezvous is not compatible with at all).
jr. member
Activity: 168
Merit: 3
#Please, read:Daniel Ellsberg,-The Doomsday *wk
March 25, 2018, 10:34:56 AM
#1
Hi,

I have used a vanity generator called mkp224o - This tool generates vanity ed25519 (hidden service version 3) onion addresses.
For context, see https://gitweb.torproject.org/torspec.git/plain/rend-spec-v3.txt

https://github.com/cathugger/mkp224o

Then I used nullius tool to convert it to bech32 address ( bech32 -e )...

the output was something like lets say ...

onion1xdnsv70edyuqrj666hlhtry2t93eq8lt565zqw2yug6sat9a5aj40mgrrtdfaz

My question is.. it a valid bitcoin address ? 
Jump to: