pull down to refresh

Alright @deSign_r, we've got some initial results!
This address: 12Wfw4L3oPJFk2q6osDoZLYAwdFkhvgt4E (which can be seen on mempool here) can be represented as:
The king, whose power and pride, were known through the realms of earth to shine, In harness proud as eagle with the morning wind entwin. Now with what grace he did command his people in this wise. Their daily toiling lives for them to thine
or
The king, a man of noble grace, did dwell in state within a towr that loomed above all other loft, where eagles, soaring free in azured heights would cast, in envied sight, a winking glace at him who ruled, and in his hand a golden rod of rule he held alight, with sceptered power to rule and right, and with
It doesn't have to be "The king..." that's just the first prompt I was trying.
That's an especially nice way to hide a seed. Can it be compared with the stenography approach shared here #71273 or is a totally different process and methodology?
Moreover, does it allow encoding just addresses or can encode anything? Can encode a privatekey or a seedphrase? What guarantee the process to not be reverted? I mean, how safe it is to use considering you sharing the source code?
reply
Thank you!. And yup any arbitrary data can be embedded. Seeds, addresses, love letters, the secret ingredient to coca cola.
The tricky part though is both parties (sender / reciever) will need to run the same quite complex code suite, same LLM weights, same LLM inference process, and same version of my "innocuous" algortihm on top. Otherwise they might misunderstand each other.
The benefit is it's decentralized, unlike something like cashApp where you can send me coins to my $username, but they could always de-bank me or alter the address unbeknownst to the sender and steal the coins.
I think my target for now is addresses and nostr pubKeys. But I want to get those tool into other peoples' hands to see what they can think up with this.
reply