Peck by twetch#2022

twetch#2022 6.6y

1sNJWU…Qwas Key · twetch

What the chain says

Transaction: 8cc3cd5f6e691130f185dff43457808c600e2b68fa655d44957ec5a8dac01018
Block: 624 796
Time: 2020-03-04T21:19:41Z
Signer: 1sNJWUrAYfdxAKN1zGq3t9hwyR6ynQwas
App: twetch
Type: post
Content type: image/png
Filename: twetch_twembed1583356669343.png
Name in tx: twetch#2022

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1sNJWUrAYfdxAKN1zGq3t9hwyR6ynQwas Verified

Reposted by (3)

twetch#2275 Reposted · 6.6y
twetch#4025 Reposted · 6.6y
twetch#6517 Reposted · 6.6y

Replies (4)

twetch#2275 6.6y

1AE48v…F1NS Key · twetch

Replying to@1sNJWU…Qwas

aaand they deleted

twetch#17303 6.6y

1EZKvw…X3oL Key · twetch

Replying to@1sNJWU…Qwas

So basically what they've got is "Pay Twitter", where your content is still not verifiably your own

How long does it take to generate an MD5 checksum to stick on the chain anyway. That way, the bulk of the content could actually stay off-chain.

twetch#17303 6.6y

1EZKvw…X3oL Key · twetch

Replying to@1EZKvw…X3oL

It's not completely foolproof, theoretically there are 'sets of content' that would have the same md5, but with timestamps AND a rock solid reputation, it would be enough for basic use

twetch#2123 6.6y

1CY4SU…8U6T Key · twetch

Replying to@1sNJWU…Qwas

"Commercially viable algo"

Post by twetch#2022

Reposted by (3)

Replies (4)