Bitcoin Forum
May 03, 2024, 07:44:11 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: What does the OP_RETURN signify in this transaction?  (Read 80 times)
dwtguau (OP)
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
October 18, 2023, 11:49:40 AM
 #1

I'm trying to understand what the OP_RETURN in this transaction (15c1d361fb7c5215050c16391c0445f1974f2c928a376b662ee1b4d85d46e416) signifies. It doesn't appear to make any sense when I try to decode it using UTF-8 or any online tool I could find. I've checked Ordiscan etc. and it doesn't seem to be linked to that. Anyone have any ideas?
1714765451
Hero Member
*
Offline Offline

Posts: 1714765451

View Profile Personal Message (Offline)

Ignore
1714765451
Reply with quote  #2

1714765451
Report to moderator
1714765451
Hero Member
*
Offline Offline

Posts: 1714765451

View Profile Personal Message (Offline)

Ignore
1714765451
Reply with quote  #2

1714765451
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714765451
Hero Member
*
Offline Offline

Posts: 1714765451

View Profile Personal Message (Offline)

Ignore
1714765451
Reply with quote  #2

1714765451
Report to moderator
NotATether
Legendary
*
Offline Offline

Activity: 1596
Merit: 6726


bitcoincleanup.com / bitmixlist.org


View Profile WWW
October 18, 2023, 11:56:48 AM
Merited by vapourminer (1)
 #2

You can put whatever data you want inside an OP_RETURN output, even nonsensical gibberish. Or at least the data of a protocol that is not known to us - or one that was not published at all and was the product of some basement dweller's experiment.

There is no restriction that the OP_RETURN data has to be legible or in ASCII text.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
o_e_l_e_o
In memoriam
Legendary
*
Offline Offline

Activity: 2268
Merit: 18509


View Profile
October 18, 2023, 12:14:07 PM
Merited by DaveF (2), vapourminer (1)
 #3

That transaction is the Tx0 for a Whirlpool coinjoin. The whirlpool coinjoin server uses the OP_RETURN output to keep track of eligible coinjoin UTXOs, fees paid, and so on. There is no human readable component to these OP_RETURN outputs.
DaveF
Legendary
*
Offline Offline

Activity: 3472
Merit: 6259


Crypto Swap Exchange


View Profile WWW
October 18, 2023, 02:01:11 PM
 #4

That transaction is the Tx0 for a Whirlpool coinjoin. The whirlpool coinjoin server uses the OP_RETURN output to keep track of eligible coinjoin UTXOs, fees paid, and so on. There is no human readable component to these OP_RETURN outputs.

Minor quibble. But it IS human readable I can read it. It just has no human discernible data.

I deal with this from some database people all the time, I have to keep telling then that the DB admin can read EVERYTHING, so make sure any private data is encrypted BEFORE it hits the database.
Or, only be decoded in a way that the people with DB admin access do not have a way to get to.

-Dave

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!